Genius PO Number Field Overload Map Multiple order reference formats enter the single Genius SalesOrderHeader PoNumber field. WooCommerce and internal sales values are transformed or concatenated, while marketplace and vendor references often pass through unchanged. What Actually Lands in Genius "PO Number" One ERP field receives transformed web orders, concatenated inside-sales references, raw marketplace POs, native Amazon IDs, and occasional legacy/noisy values. Order source Before entry into PO Number Genius field Ontology meaning WooCommerce stores HR264065, PS20935, HT40348, CVR2303 Inside sales HR-81650 Customer PO: ABC-123 Amazon 112-0088405-9659408 75V9HXUW Retail / EDI vendors 92788828, 249236826, MCOM37542722 Web order normalization Strip store prefix letters Prepend WEB- in Genius Internal sales pattern Strip HR- prefix New Genius-era entry: internal # + " - " + customer PO Native source ID Stored unchanged Vendor PO passthrough Stored as the vendor sent it SalesOrderHeader PoNumber WEB-264065 81650 - ABC-123 112-0088405-9659408 75V9HXUW 92788828 MCOM37542722 HR252784-ElijiaWilper Stock Treads Useful for reverse lookup Unsafe as a clean PO concept Source order ID Customer PO # Vendor / channel PO Legacy / dirty data modified modified + joined not modified not modified WEB-##### internal + PO native ID raw PO Model as SourceReferenceRaw, then derive channel, order ID, customer PO, legacy reference, and quality. Master key remains SalesOrderHeaderEntity.Code. PoNumber is useful for channel-to-Genius reverse lookup, not as the production or invoice spine.