Mapping from EDI, GS1 and legacy order flows

Message map

850 / ORDERS → PO · 855 / ORDRSP → PO_RESPONSE · 860 / ORDCHG → PO_CHANGE / PO_CANCEL · 856 / DESADV → ASN · 861 / RECADV → RECEIPT · 810 / INVOIC → INVOICE · 812 → CREDIT_NOTE · 820 / REMADV → REMITTANCE · 846 / INVRPT → INVENTORY · 830 / DELFOR → FORECAST · 214 / IFTSTA → TRANSPORT_STATUS · 997 / CONTRL → ACK · 832 / PRICAT → PRODUCT, PRICE_LIST · 863 / QALITY → COA · 842 → NONCONFORMANCE.

EPCIS 2.0 events map 1:1 to EPCIS_EVENT; TransformationEvent maps to LOT_GENEALOGY.

Four-document order flows

Partners using a classic four-document flow (order → acknowledgement → ship notice → invoice, with an inventory/price file) map those four documents to PO, PO_RESPONSE, ASN and INVOICE, and their inventory file to INVENTORY. Add COA and LOT_GENEALOGY for nutraceutical compliance.

Field-level mapping

Each message guide lists, per field, the X12 element, EDIFACT segment, GS1/EPCIS element and SAP field. These are reference mappings, not certified translations; confirm with your EDI provider's implementation guide.

Code mapping

Map your internal codes once to the NutraB2B lists (e.g. your UoM 'KG' → KGM, 'Net 30' → NET30). Download every list as CSV/JSON from the Code lists tab.