Does an EDI 855 Confirm an Order or Just Receipt?
Learn what EDI 855 actually confirms, how its BAK and ACK codes work, and when retailers require it to avoid shipping chargebacks.
An EDI 855 is the purchase order acknowledgment a supplier sends back after receiving a customer's 850, telling the buyer whether the order is accepted as written, accepted with changes, or rejected. An EDI 855 is the purchase order acknowledgment you send back after a customer's 850 purchase order, telling the buyer whether you accept the order as written, accept it with changes, or reject it. It's a commercial commitment on quantity, price, and ship date, not a technical receipt. That distinction trips up a lot of teams building their first supplier EDI setup, so it's worth getting straight before you map a single segment.
What's the difference between an EDI 855 and a 997?
The 997 confirms a file arrived and parsed correctly. The 855 confirms the business terms of the order. Where a 997 Functional Acknowledgment only says "your file arrived and parsed," the 855 is a business-level answer: line one accepted as ordered, line two backordered until the 22nd, line three price-corrected. One is a syntax check performed by your translator in milliseconds. The other requires a human or a system to actually decide what you're committing to ship.
The real answer sits in the BAK segment. BAK02 carries the acknowledgment type, and BAK02 = acknowledgment type: AC = acknowledged, AD = acknowledged with detail changes, AK = acknowledged with changes, RJ = rejected. The 997 never touches any of that. If you're still fuzzy on how the 997 fits into the acknowledgment chain, it's covered in our earlier post on EDI functional acknowledgments.
Is the EDI 855 mandatory, or just a best practice?
It depends entirely on the trading partner's implementation guide, not on the X12 standard or any regulation. Who it applies to: suppliers whose customer's EDI implementation guide lists the 855 as required. It is a trading partner rule, not a regulation. X12 publishes the transaction set; it doesn't force anyone to send it.
In practice this plays out exactly like the retailer-specific 856 and 852 enforcement we've covered before. Some partners build the requirement into contract language. Insight's trading partner agreement states that by accepting the purchase order and returning the appropriately coded 855, Trading Partner accepts all values and terms defined in the document, with a three-hour response window. Others set the clock differently: published guides set deadlines from 60 minutes to 48 hours after the PO arrives. You cannot assume one partner's rule applies to the next. Map BAK02 per partner, because D&H Distributing allows AC, AD and RD, while 3M allows only AC, even when nothing changed.
What do the ACK line-item codes actually mean?
Each PO1 loop in the 855 gets its own ACK segment showing what the seller can actually fulfill at that line, separate from the header-level BAK decision. The transaction then uses PO1 loops - one per line - each carrying the original line number, the acknowledged quantity, and a line-level acknowledgment code (IA = item accepted, IB = item not accepted, IC = item partially accepted, IP = item on back-order).
Here's a typical line-level split on a partial fulfillment:
| PO1 line | Ordered qty | ACK code | Acknowledged qty | Meaning |
|---|---|---|---|---|
| Line 1 | 100 units | IC | 80 units | Accepted with changes, 80 confirmed |
| Line 1 (continued) | remaining 20 | IP | 20 units | Back-ordered, not available now |
Vendors use different codes depending on the implementation guide. Amazon vendor documentation notes that the three you'll use most often against Amazon are IA (item accepted), IR (item rejected), and IB (item backordered). Other implementation guides add IQ for quantity changes and ID for item not available. Check the buyer's spec before you hardcode a code list, because the EDI academy's full reference lists over twenty valid line-status codes across all X12 versions, and most buyers only accept a handful of them.
What happens if the 855 and the eventual shipment don't match?
The acknowledged quantities on the 855 become the reference point for everything downstream, not the original 850. A mismatch against the 855 is what triggers a discrepancy chargeback at the distribution center, not a mismatch against the PO. These changes, documented in the 855, become the agreed-upon version of the order for downstream documents - if the supplier ships 8 units and the 856 matches the 855's acknowledged quantity, no discrepancy chargeback is triggered at the DC. Retailers reconcile the ASN against what was acknowledged, not against what was originally ordered.
The practical fix is generating the 855 off the right source document. Generate the 855 from the sales order after someone has decided what you can ship, not from the 850. Each sales order line needs a status field the 855 map can read, plus the confirmed quantity, price and ship date. If your 855 fires straight off the inbound 850 before inventory allocation runs, you're acknowledging numbers nobody has actually verified, and the 856 you send later will drift from both documents.
Should you automate 855 generation, and how?
Yes, for any partner sending more than a handful of POs a day. Manual acknowledgment doesn't scale and is a frequent compliance failure point during retailer audits. Most ERP systems can trigger an 855 automatically once a sales order is confirmed from the inbound 850, and TrueCommerce's own integration notes describe pulling the reviewed order back out of the ERP so the acknowledgment carries the order desk's real adjustments rather than a blind echo of the 850. SPS Commerce, Cleo, and IBM Sterling all offer mapping templates for this same flow, so the heavy lift is usually ERP-side workflow design, not the EDI translation itself.
There's a parallel worth noting on the transport side. Carriers respond to load tenders with an EDI 990, the functional equivalent of a supplier acknowledging a PO, and that response gets handled through multi-carrier TMS platforms like MercuryGate, Descartes, Alpega, or Cargoson rather than manually per shipment. Same pattern, different document.
Does the 855 ever get confused with other acknowledgment transactions?
Yes, most often with the 895. The 895 confirms a delivery or return, not a purchase order. EDI 895 is a separate transaction (Delivery/Return Acknowledgment or Adjustment) sometimes confused with the 855; the 855 acknowledges a purchase order, not a delivery. The 895 shows up mainly in direct-store-delivery and grocery replenishment, closing out what was physically delivered against an earlier 894 base record. If you're confirming you can fill an order, that's always the 855. If you're confirming goods arrived in good condition, that's a different transaction entirely.
The sequence to keep straight: 850 places the order, 855 confirms or adjusts it, 856 tells the buyer what's actually shipping, and 810 invoices against the acknowledged numbers, with a 997 validating file syntax at every hop. Get the 855 generation logic right and most of your downstream 856 and 810 chargebacks disappear before they start.