How it works — the full flow
An order, end to end. No marketing fog.
Pick a retailer below to see the exact flow. Every box is a real EDI segment we parse, generate, or validate — the segment, the rule, the timing window.
X12 4010 (UL/GLN qualifier)
BIG04 = 10-digit numeric PO; REF*IA vendor number; FOB CC or PP only.
855 within 24 h of 850
856 within 30 min of ship, before truck arrival
810 within 24 h of ship
Retailer transmits the PO
AS2 (or SFTP) delivers the 850. The platform parses every BEG/N1/PO1/SAC segment, validates against the retailer’s envelope rules, and creates an Order with line items, ship-to, deadlines, and SDQ multi-store allocations where applicable.
We answer the protocol handshake
The platform auto-generates a 997 functional acknowledgment within the retailer’s SLA window. AK1/AK2/AK5/AK9 segments populate from the inbound control numbers. If syntax was bad, the 997 carries the rejection and the order is parked in quarantine.
Vendor reviews and acknowledges the order
In one click the platform queues a 855 PO acknowledgment with retailer-specific rules baked in (BAK pairing, ACK01 codes, line-level accept / reject / backorder). For retailers like Best Buy that do not use 855 in the core-vendor flow, this step is skipped automatically.
Vendor builds the shipment, prints labels
When the shipment is ready, the platform generates a 856 ASN with full carton-level detail — SSCC18 serial numbers, GS1-128 encoded MAN segments, carrier and tracking fields. SOPI or SOIP hierarchy is selected per retailer config.
Vendor invoices the shipment
Invoices auto-create from shipments and stay in sync as line items change. The 810 carries retailer-specific REF/FOB/CAD segments and the right BIG04 PO format (10-digit Walmart, 6-char Best Buy, 6-digit Meijer, etc.).
Optional: retailer disputes a doc
When a 855/856/810 makes it past the 997 (syntax OK) but fails business validation — wrong UPC, missing line, FOB code mismatch — the retailer sends a 824. We parse the TED/RED segments, link them back to the original outbound doc, and surface the offending segment in the dashboard.
Retailer pays
The 820 remittance lines up against the 810 it pays — we match by reference number, surface partial-pay amounts, and pull any chargeback deductions into the chargeback workflow.
Want to watch this happen on your own data?
Sign up. Click practice. Our simulator transmits a real 850 to your account over AS2 and the full lifecycle plays out in your dashboard — live, with timestamps.