How XML Order Fields Map to an 850
XML names every field; X12 identifies it by segment and position. Tag names vary by system (cXML, a custom ERP export, a marketplace feed), but the purchase order content is the same. A typical mapping:
| XML element (example) | X12 850 |
|---|---|
| <OrderID> / <PONumber> | BEG03 |
| <OrderDate> | BEG05 (CCYYMMDD) |
| <ShipTo><Name> | N1*ST, N102 |
| <ShipTo><Address> | N3 and N4 |
| <Item><Quantity> | PO102 |
| <Item><UnitOfMeasure> | PO103 (EA, CA, PK) |
| <Item><UnitPrice> | PO104 |
| <Item><SupplierPartID> | PO106 = VN, PO107 |
| <Item><Description> | PID05 |
What Usually Goes Wrong
Hand-built X12 tends to fail on the envelope, not the content: ISA fields that are not padded to fixed width, an SE01 count that forgets the ST and SE segments, control numbers that do not match between ISA and IEA, or a CTT01 that counts the wrong thing. The EDI viewer and validator checks all of these and tells you which segment to fix. The 850 guide covers each segment.
When It Is More Than One Feed
OrderSync reads orders from EDI partners, PDFs, email and spreadsheets, checks them against your catalog and pricing, and puts clean orders in one queue for your team to approve. If you have XML order feeds as well, bring a sample to an intro call and we will tell you how we would handle them. Developers can also look at the extraction API.