Every B2B order in EDI follows the same lifecycle: a sequence of standardized documents that hand the order from buyer to supplier and back, with no one re-keying the data. Once you see how the transactions connect, the whole alphabet soup of numbers becomes a single, predictable flow. This is the map that ties together every transaction guide on this site.
This guide walks the order from forecast to payment, names the document at each stage, and links the deep guide for each one. Use it as the starting point, then drill into any transaction.
What Is the EDI Order Lifecycle?
The EDI order lifecycle is the standardized sequence of ASC X12 transactions that carries a single order from demand planning through purchase order, shipment, receipt, invoice, and payment, with each document handed system to system and no manual re-keying. Every transaction in the sequence is defined by the same standards body, which is why a purchase order from a national retailer and one from a regional grocer share the same 850 structure.
Authoritative references for the transactions in this lifecycle:
- The X12.org Transaction Sets reference defines every transaction named below, from the 850 purchase order through the 820 payment
- GS1 US governs the UPC, GTIN, and SSCC identifiers that tie these documents to physical products and cartons across the flow
The lifecycle is a convention rather than a single specification: a well-worn order of documents that trading partners follow, adding or dropping stages based on their industry and relationship. A grocery distributor and an auto-parts supplier run the same backbone with different variants. The sections below walk that order from start to finish.
The Lifecycle at a Glance
The five documents almost every retail order uses. Select one for details.
Order
Ship
Bill and pay
Buyer
the retailer or distributor ordering from you
Supplier
you, the brand or distributor shipping the order
850
Buyer to supplier
Purchase order
- When
- Whenever the buyer orders
- What's in it
- Items, quantities, prices, ship-to locations, ship and delivery dates.
- Where it goes wrong
- Keying it into your ERP by hand. Every typo becomes a short ship or a chargeback.
Every document gets a 997 back. The functional acknowledgment confirms the file arrived and parsed. It doesn't mean the order was accepted.
Freight runs alongside the 856, between the shipper and the carrier: a 204 load tender, a 990 acceptance, 214 status updates and a 210 freight invoice.
The same flow as a table, with every planning and warehouse variant:
| Stage | Document | Direction | What happens |
|---|---|---|---|
| Plan | 830, 862, 866, 846, 852, 832 | Both | Demand, inventory, sell-through, and catalog are shared |
| Quote | 840 / 843 | Both | Buyer requests quotes; supplier returns pricing |
| Order | 850 | Buyer to supplier | The purchase order is placed |
| Acknowledge | 855 | Supplier to buyer | The supplier accepts, rejects, or changes lines |
| Change | 860 / 865 | Both | The order is revised and the change is acknowledged |
| Ship | 856, 940/945 | Supplier to buyer | The shipment is announced with pack detail |
| Receive | 861 | Buyer to supplier | What actually arrived is reported |
| Bill and pay | 810 / 820 | Both | The invoice is sent and payment is remitted |
| Confirm | 997 | Both | Every document gets a receipt |
Stage 1: Plan and Forecast
Before any order, trading partners share the data that shapes demand. A buyer may send an 830 Planning Schedule with forecast and firm releases, or an 852 Product Activity Data feed showing what is actually selling so the supplier can replenish. The 846 Inventory Inquiry/Advice communicates stock levels, and the 832 Price/Sales Catalog publishes the supplier's items and prices so both sides agree on what can be ordered.
Not every relationship uses this stage, but when it exists, it is what turns reactive order-taking into planned replenishment.
Stage 2: Place the Order
The order starts with the 850 Purchase Order. The buyer's system sends it, and the supplier's system turns it into a sales order automatically, with no manual keying. The 850 carries the line items, quantities, prices, ship-to, and dates. In a blanket-PO relationship, the planning schedule (830) can drive releases instead of a fresh 850 each time.
Stage 3: Acknowledge and Change
The supplier returns an 855 Purchase Order Acknowledgment to confirm the order, accept or reject each line, or propose changes. If the buyer needs to revise the order, it sends an 860 Purchase Order Change, and the supplier replies with an 865 Change Acknowledgment. Together the 855 and 865 keep both sides agreed on the current state of the order before anything ships.
Stage 4: Ship
When the goods go out, the supplier sends an 856 Ship Notice (ASN) ahead of the truck, with full pack-level detail and SSCC-18 carton labels so the buyer can receive by scanning. See the advance ship notice definition for how the pack hierarchy works. When a brand uses a third-party warehouse, the 940 Warehouse Shipping Order instructs the 3PL to ship and the 945 Warehouse Shipping Advice confirms what left the dock. Moving the freight itself runs on a parallel set of documents: the shipper or 3PL tenders the load to a carrier with a 204 Load Tender, the carrier accepts with a 990, and reports progress with 214 status messages until delivery.
Stage 5: Receive
After the shipment arrives, the buyer sends an 861 Receiving Advice reporting what actually came in against what the ASN and purchase order said. Discrepancies, short shipments, overages, or damage, surface here, before the invoice is paid.
Stage 6: Invoice and Pay
The supplier bills with an 810 Invoice, referencing the original PO so the buyer can run a three-way match against the order and the receiving record. Grocery orders are billed with the 880 Grocery Products Invoice instead. The buyer then sends an 820 Payment/Remittance Advice reporting which invoices were paid and how. If something is deducted, an 812 Credit/Debit Adjustment or 824 Application Advice explains it.
How Fast Each Step Is Expected
Deadlines come from each retailer's implementation guide, so yours govern. These are the windows most suppliers work to:
| Document | Typical expectation | What happens when it's late |
|---|---|---|
| 997 | Within 24 hours of receiving any document | The sender assumes the file never arrived and may resend or escalate |
| 855 | Within 24 to 48 hours of the 850 | Counts against you on supplier scorecards, and the buyer can't plan around lines you haven't confirmed |
| 856 | When the goods ship, and always before they arrive | The receiving dock can't scan the cartons in; ASN chargebacks are the most common EDI penalty |
| 810 | After shipment, once quantities are final | Payment terms often start from a valid invoice, so a late or wrong 810 delays payment |
| 820 | On the buyer's payment terms | Without it, matching payments to invoices is manual |
For what these misses cost at specific retailers, see the EDI chargeback database and the retailer compliance guides.
Where Orders Usually Break
Most problems happen at a handoff, not inside a document:
- 850 to 855. Lines the supplier can't fill are accepted anyway and shorted later, so the 855 says one thing and the 856 another.
- 860 without an 865. The buyer changes quantities or dates, the change never reaches the warehouse, and the original order ships.
- 856 that doesn't match the truck. Carton counts or SSCC-18 labels don't match what's physically received, which triggers receiving delays and chargebacks.
- 810 that doesn't match the 850 and 856. Prices in different units, or quantities invoiced as ordered rather than as shipped, fail the buyer's three-way match and come back as an 824.
- No 997 tracking. A file that silently failed looks the same as one that was received until someone asks where the order is.
The 997 Underneath Every Step
One document runs beneath the whole lifecycle: the 997 Functional Acknowledgment. Every transaction above gets a 997 in return, confirming the file arrived and passed structural validation. A missing 997 is treated as a failed transmission, which is why partners track them closely. The 997 is the receipt; it does not say the order was accepted, only that the document was received.
Why the Lifecycle Matters
Each handoff is a place an order can break: an unacknowledged change, a late ASN, an invoice that does not match receipt. Most chargebacks trace back to one of these gaps. Seeing the lifecycle as a connected flow, rather than isolated documents, is what lets you find the weak handoff and fix it.
Every step above assumes both sides are EDI-capable. Orders that arrive by email, PDF, or spreadsheet fall outside this flow entirely, which is why distributors increasingly pair EDI with document extraction so every channel lands in the same pipeline. Upload any document to the free EDI inspector to see it parsed, or book a 15-minute walkthrough to see a full order cycle on real data.
Frequently Asked Questions
How does EDI work in an order?
An EDI order is a sequence of standardized documents. The buyer sends an 850 purchase order, the supplier returns an 855 acknowledgment, the supplier ships with an 856 ASN, the buyer confirms receipt with an 861, the supplier bills with an 810 invoice, and the buyer pays with an 820. A 997 confirms receipt of each document.
What is the order of EDI transactions?
The common sequence is: planning (830, 852, 846, 832), then 850 purchase order, 855 acknowledgment, 860 and 865 for changes, 856 ship notice, 861 receiving advice, 810 invoice, and 820 payment. A 997 functional acknowledgment is returned for every document.
What is the difference between an 855 and an 856?
The 855 is the purchase order acknowledgment, sent right after the 850 to confirm the order. The 856 is the advance ship notice, sent later when the goods actually ship. The 855 answers "can you fill it"; the 856 says "here is what is on the truck."
Do all EDI orders use every transaction?
No. The core retail flow is 850, 855, 856, 810, with a 997 for each. Planning documents (830, 852), change documents (860, 865), warehouse documents (940, 945), and grocery variants (875, 880) are added when the relationship and industry call for them.
What comes after an EDI 850?
The supplier returns a 997 to confirm the 850 arrived, then an 855 purchase order acknowledgment to accept, reject or change each line. Next comes the 856 advance ship notice when the order ships, then the 810 invoice.
Is a 997 required for every EDI document?
In practice, yes. Most trading partners expect a 997 functional acknowledgment for every document they send, usually within 24 hours. The 997 only confirms the file arrived and parsed; it doesn't mean the order was accepted. That's the 855's job.
What is the difference between a 997 and an 855?
A 997 is a technical receipt: the document arrived and its structure is valid. An 855 is a business answer: the supplier can fill these lines, at these quantities, by this date. An 850 usually gets both.
Where do carrier documents like the 204 and 214 fit in?
They run alongside the order flow, between the shipper and the carrier rather than between buyer and supplier. The shipper tenders the load with a 204, the carrier accepts with a 990, reports progress with 214 status messages, and bills freight with a 210.