Bottom line first: an 850 going out does not mean the goods are coming. What actually lets a warehouse commit labor and slots is the EDI 855 coming back. Without that acknowledgment, every unit you stage against the 850 is a bet on the supplier's inventory and goodwill. Across 30-plus go-lives, I have learned that when the 855 line breaks, nine times out of ten it is not a technical failure. It is the warehouse treating the 855 as paperwork — the 850 goes out, slots get reserved, shifts get scheduled, and then the supplier comes back a week later with quantities cut in half and the whole staging plan collapses.
I have seen this exact failure three times. The worst was a home-goods retail client in the fall of 2024. Ahead of peak season they sent an 850 for 1,200 units of a seasonal item. The warehouse cleared slots three days early and built the pick schedule around it. The EDI 855 did not come back for five days, and when it finally arrived the quantity was cut from 1,200 to 640 and the ship date pushed back 12 days. Customer service had already taken pre-orders against the original plan. Half the slots sat empty waiting for freight, and the other half could not ship because the dates had moved. The whole warehouse spent a week cleaning up after one missing document.
What an EDI 855 Actually Says: AC, AD, and RD
An EDI 855 is the supplier's formal answer to an 850 purchase order — the purchase order acknowledgment under the X12 standard. Note that it is not the same thing as a 997. A 997 only says "your file arrived." An 855 says "here is what we will actually do about this order." Mistaking a 997 for an 855 is the most common failure I see, and there is no close second.
The BAK segment of an 855 says one of three things. AC means the order is accepted in full — quantities, prices, and dates match the 850, and the warehouse can stage with confidence. AD means accepted with changes: the supplier altered quantities, prices, or dates, spelled out line by line in the ACK segments. RD means the whole order is rejected, and the deal has to be renegotiated. The line-level ACK codes are where the real work lives: IA means the line is accepted, IB means backordered and shipping later, IC means the line changed, IQ means the quantity changed, IR means the line is rejected. A ten-line order with nine IA lines and one IR line still changes the staging plan — the warehouse has to read every line, not just the header.
One point that gets missed: a changed acknowledgment is not the supplier rewriting the deal unilaterally. Under most trading partner agreements, an 855 with changes is the supplier's new offer, and the buyer has to accept it or send an 860 change request before anything is settled. The warehouse should move only after purchasing confirms the changes. If you restage on the 855 alone and purchasing negotiates the old terms back, you end up restaging twice.
When the EDI 855 Is Late, Silent, or Changed: Three Tiers of Response
Before the 855 arrives, the warehouse has exactly three things it can do, and they have to be tiered — not one blanket rule.
Tier one: the 855 comes back on time with AC, full acceptance. Run the normal process, but nail down one step — flip the order status in the WMS from "awaiting confirmation" to "confirmed" before releasing staging. If the system still shows the order as unconfirmed, slots stay blocked and orders stay stuck, and when the 856 advance ship notice arrives nothing matches, so receiving ends up working off a paper log. I have seen this exact failure three times, and every time the cause was the same: at go-live somebody skipped one status flip to save effort.
Tier two: the 855 comes back AD, accepted with changes. Reconcile the ACK segments line by line, then sort the differences into three buckets. If quantities were cut, calculate the size of the gap first. The numbers below are a hypothetical worked example, invented only to show the arithmetic: a SKU ordered at 1,200 units comes back confirmed at 800, leaving a 400-unit gap; at a daily outbound rate of 50 units, that gap equals 8 days of sales; on-hand safety stock of 300 units covers only 6 days, leaving a 2-day shortfall. That 2-day number is what the warehouse reports to purchasing immediately — either source 400 units from an alternate supplier, or tell sales to push pre-orders for this SKU back by 2 days. If the ship date moved, freeze staging and do not hold slots for freight that is not coming; in peak season a slot is worth more than gold. If the price changed, the warehouse does not need to act, but copy the 855 to finance so receiving reconciles against the 855 price, not the 850 price — otherwise month-end reconciliation turns into another round of arguing.
Tier three: the 855 never comes, or it arrives past the window in the agreement. Most retail vendor agreements set the 855 deadline at 24 to 48 hours. Past that window, the warehouse should plan as if the supplier may not be able to fill the order. The rule I put in place: freeze staging for 48 hours, hold off on reserving slots and building pick schedules, and have purchasing chase the supplier; if there is still no answer after 72 hours, start alternate sourcing right away. Write this timeline into the go-live checklist and into the system as an automatic reminder. Do not rely on people remembering. People forget. Systems do not.
| Acknowledgment | BAK code | Warehouse action | Staging status |
|---|---|---|---|
| Accepted in full | AC | Flip status to confirmed, release staging | Stage normally |
| Accepted with changes | AD | Reconcile ACK lines, size the gap, notify purchasing | Freeze the gap, wait for purchasing |
| Rejected in full | RD | Stop staging, release slots, start alternate sourcing | Fully frozen |
| No reply past deadline | — | Freeze 48 hours, alternate sourcing at 72 hours | Frozen, watch |
Here is the counterintuitive part: a slow 855 is sometimes not the supplier dragging its feet — it is your own 850 being wrong. A price that does not match the last order, a stale item code, a ship date nobody can meet — any of these can land your order in the supplier's exception queue, where no human has even seen it yet. So when an 855 is late, do not only chase the supplier. Check whether your 850 got bounced by their system first. In at least two projects I worked on, that was the answer: three days of chasing, and it turned out our own team had mistyped one digit of an item code.
Go-Live Night Checklist: Walk the 855 Line Before It Breaks
On go-live night, do not skip the 855 page of the checklist. First, confirm that the 997 and the 855 are two separate tracks: the 997 only signs for the file, and only the 855 flips the staging status — and the test cases must include one where only a 997 comes back and the system must not release staging. Second, cover every ACK code: IA, IB, IC, IQ, IR each get a test document, not just the happy path of full acceptance. Third, set the timeout alert: if no 855 arrives within 24 hours, the system automatically alerts purchasing and the warehouse duty lead, and the alert must name the order number, the supplier, and how long it has been overdue — not just "there is an exception." Fourth, the change report: for any AD acknowledgment, the system generates a table of quantity, price, and date differences and pushes it to purchasing for confirmation, and the WMS must not restage on the new quantities until purchasing confirms. Fifth, keep a manual fallback: if a document fails to parse or carries a code outside the partner's list, the system must let a person intervene — never silently drop the document, because a dropped document cannot be found again.
An 855 is, at the end of the day, the supplier giving the warehouse a straight answer. With that answer, staging has a foundation. Without it, an 850 is just a wish list. Warehouse work never starts when the freight arrives — it starts before that, by working out what happens if the freight does not arrive at all.
By Lin Xiao, WMS Implementation Consultant







