A retailer sends your company a purchase order, your warehouse ships it, and your finance team bills it. Retail EDI (electronic data interchange) carries the documents for those steps in a structured format the retailer and supplier can process without retyping them. The order number and line references let each system tie later documents back to the order.
When the retailer says a shipment notice is missing, follow the same chain in reverse. Find the warehouse shipment, check whether the matching notice was sent, then look for the receiver’s acknowledgment. Each record proves a different step.
Format, delivery, and retailer rules
In North American retail, X12 transaction sets define the document types and their structure. A connection such as SFTP or AS2 carries the document. The retailer’s implementation requirements specify which fields and codes it expects, when each document is due, and which acknowledgments it sends. A supplier can use the same document type for two retailers and need separate mappings for their carton or item identifiers.
An EDI gateway can translate between the retailer’s format and the records your ERP uses. The ERP may store one sales order with multiple fulfillment records, while the retailer expects a separate ship notice for each shipment. Test a split shipment and a rejected notice with the retailer before the connection goes live so you know where both cases appear.
The purchase order through the invoice
In the X12 supply chain flow, the retailer sends the order and the supplier sends business responses as the order moves through fulfillment. Your trading agreement determines which documents the relationship uses.
| Document | Typical sender | What the recipient learns |
|---|---|---|
| 850 purchase order | Retailer | Which items and quantities to supply and when they are due. |
| 997 functional acknowledgment | Receiver of a document | Whether the document passed the receiver’s X12 syntax checks. |
| 855 purchase order acknowledgment | Supplier | Which order lines the supplier accepts, rejects, or proposes to change. |
| 856 advance ship notice (ASN) | Supplier | What shipped and how it is packed, using the identifiers the retailer requires. |
| 810 invoice | Supplier | Which goods or services the supplier is billing for and what it is charging. |
Suppose the retailer orders 100 units and the warehouse sends 60 in the first shipment. The first ASN describes those 60 units and their cartons, with its own shipment reference. If a notice for the remaining units arrives later, the two notices belong to the same order and different shipments. A check that looks for any ASN on the order can miss the second shipment altogether.
Keep the original EDI control reference with each transaction so a functional acknowledgment can be matched to the document it covers. In an AS2 exchange, a message disposition notification (MDN) records a transport outcome. The functional acknowledgment reports the syntax check, while an application response can carry a business validation result. Check which responses your trading partner sends before deciding what evidence counts as received or accepted. See the AWS AS2 documentation.
How to trace a missing ship notice
Start from a shipped warehouse record and match the retailer, order line, and shipment reference to the EDI transaction. Keep the warehouse ship time, the time the gateway sent the notice, and the latest acknowledgment in separate fields. If you only have the gateway’s latest status, ask for the original timestamps before judging whether the notice met the retailer’s deadline.
Separate missing, rejected, and stale evidence so each case goes to the right owner. A shipment with fresh warehouse data and no matching notice goes to the person who owns the outbound mapping. A rejected notice goes to whoever can fix the field the receiver flagged. If the EDI feed is stale, check the feed first because the notice may have gone out after the last refresh.
Review the keys where the join fails. A retailer item ID may identify a case while a warehouse SKU identifies an individual unit. Use a documented pack conversion and keep the original quantities visible, as you would when matching product records across channels.
If someone corrects a rejected notice, keep the original rejection and link it to the replacement. The latest record helps you decide what to do now, while the original timestamps show whether the first attempt met the deadline. When the status is uncertain, check the existing document reference in the gateway before sending a replacement. A second document may be treated as a duplicate or a correction under the retailer’s rules.
How Permute can bring order evidence together
Permute sells software for connecting business data and making it usable in reports, apps, and AI tools. For a retail workflow, you can bring in authorized order, shipment, and EDI status exports as structured files. Use the systems we connect to check the available sources for your stack.
Define the order and shipment match once, then apply the same retailer rule to each refresh. An operations lead reviewing a suspected missing notice can see the warehouse shipment and the last available EDI record side by side, with timestamps that show whether the inputs are current enough to act on.
Explore one retailer’s order and shipment exports
Load a sample of the records your team already uses to trace an order.
Who sends the documents and owns the deadline
This workflow reads source records. Your EDI provider or existing integration sends retailer documents, and your team corrects orders, shipments, and notices in the systems that own them. Use the actual refresh interval to decide which deadlines you can monitor. A daily export can support a retrospective review, while an alert before a shipping cutoff needs data that arrives with time to act.
If the same warehouse also handles storefront and marketplace orders, use ecommerce order management across channels to check which shipping commitments and confirmations need separate rules.
Follow the order number from the retailer to the warehouse, then follow the shipment reference back to the notice. Keep the functional acknowledgment and the supplier’s business response as separate records. When a handoff is missing, the matched records and their timestamps tell you where to look and whether you can still fix it.
Review a missed shipment handoff with Permute
Bring the records for one late or rejected notice and the retailer deadline your team was trying to meet.
Questions suppliers ask about retail EDI
Why did we get a 997 but still need to send an 855?
The 997 reports the result of checking the document’s syntax. If your retailer expects an 855, it still needs your response about the order lines and what you can supply.
Can one purchase order have more than one ASN?
Yes. For a split order, check the retailer’s instructions and match each notice to the shipment and order lines it covers. A match on purchase order number alone can leave a shipment unaccounted for.