B2B Integration Lab.
Transform your data. Understand the response.
Practical tools for exploring purchase-order mappings and troubleshooting acknowledgments. Your files and pasted messages stay in your browser. Nothing is transmitted to a trading partner.
ERP file → ready-to-review output.
Upload an export, match its fields, and download the converted document.
One order, up to 1,000 line items. JSON / XML / delimited TXT input. X12 850 and EDIFACT ORDERS output are message bodies for review, without interchange envelopes or partner-specific validation. Line units are assumed to be each (EA / PCE); prices retain the source currency without adding a currency code.
TXT: use a header row with comma, tab, pipe or semicolon separators, or key=value lines. Fixed-width and binary exports need a structured export first.
Your field mapping appears here.
Start with an ERP export or load the example. Review the suggested matches before converting.
A rejection code. A clear next step.
Paste the 997 from your integration log. Explanations update as you type.
Supports X12 997 AK1–AK5 / AK9 details, complete envelopes, and excerpts. Unknown codes are flagged. This is a code-based explanation, not a guess at the receiver’s internal system.
997 code reference ↗Paste a 997 acknowledgment to begin.
Purchase order
Sample data · editable
Field by field
A simplified mapping guide
- PO number
BEG03 - PO date
BEG05 - Buyer
N1 · BY - Supplier
N1 · SU - Quantity
PO102 - Unit price
PO104 - Item SKU
PO107
The date becomes YYYYMMDD. Each source item becomes a PO1 line. This example uses one line item.
Illustrative X12 850
Transaction-set subset
ST*850*0001~
BEG*00*SA*PO-2026-001**20260913~
N1*BY*Demo Retail~
N1*SU*Demo Supply~
PO1*1*10*EA*25.00**VN*DEMO-01~
CTT*1~
SE*7*0001~No ISA/GS envelopes, partner rules, transport, or real acknowledgment processing.
Choose a scenario, then run validation to see what passes or needs attention.
Looking for a document code or example syntax?
Search the EDI Field GuideFrom a single transaction to a view of operations.
Open Incident Workbench