Transaction explainers · September 22, 2026

EDI 870 Order Status Report: The Complete Guide (2026)

How the EDI 870 reports order status — BSR headers, line-level statuses, jeopardy signaling — whether answering an 869 or on a scheduled cadence.

Bad news ages poorly in supply chains. An order that will ship two weeks late is a manageable problem the day you know it — and a crisis the day the truck doesn't arrive. The EDI 870 Order Status Report is the document for telling buyers the truth early: your structured account of where their orders stand, line by line, whether they asked or whether you report on a schedule.

Two modes, one document

The 870 works in response mode — answering a specific 869 Order Status Inquiry with matching scope — or in push mode, transmitted unsolicited at an agreed cadence covering open orders. A BSR header establishes which mode and what the report covers; the detail then walks orders and lines, attaching a status to each: in process, on schedule, delayed (with a revised date — the part that makes a delay report useful), backordered, in jeopardy, partially shipped, shipped with details.

Push mode deserves more use than it gets. A weekly 870 across open orders costs nearly nothing to produce from ERP data and preempts the entire inquiry cycle: the buyer's planners see current state in their own system without asking, and your customer service inbox loses its worst recurring thread.

The jeopardy signal

The highest-value status in the vocabulary is the uncomfortable one: this line is in trouble. Reporting jeopardy early — a component shortage, a capacity crunch, a slipped date — hands the buyer options while options exist: reallocate, adjust promotions, source elsewhere, or simply re-plan. Suppliers hide problems on the theory that things might recover; buyers, who have been on the other end of that theory, structure their scorecards to punish the surprise far more than the delay. An honest 870 converts a future scorecard event into a present planning conversation.

The discipline this requires is internal: your order data has to know a line is in jeopardy. Which is really a planning-system question — if revised dates and shortage flags live in your ERP, the 870 merely transmits them; if they live in a planner's head, no document format can help. The practical middle ground is exception discipline: planners maintain revised dates only where reality diverges from plan, and the reporting layer treats everything else as on schedule. That keeps the data burden proportional to the trouble, which is what makes honest reporting sustainable.

Consistency with the rest of the chain

Status reports don't exist alone. What you report must line up with what the 855 acknowledgment committed, what the eventual 856 ship notice will announce, and what fulfillment actually does. Contradictions between documents — a line reported on-schedule that ships late, a shipped status with no ASN behind it — read as either sloppy data or evasion, and both erode the trust the document exists to build. The mechanical safeguard is generating every 870 from the same live order state that drives the other documents, never from a separately-maintained status file.

Buyers notice the difference quickly. Status feeds that reconcile with the documents around them get consumed automatically on the buyer's side; feeds that contradict them get routed to a human for suspicion, which defeats the purpose of sending structured status at all.

That's how EDISQ produces them: status assembled from current ERP order and shipment data, on inquiry or on schedule, with the response scope matched to what each partner's spec expects.

What reporting costs

Status reports are the cheapest goodwill in EDI. On EDISQ's meter, an 870 is one document: free within the monthly 25, then from $0.50 with the per-document rate declining to $0.10 across volume tiers — no mapping or setup charges, transport included. A standing weekly status feed to your major buyers runs a few dollars a month and buys the reputation of a supplier who never surprises anyone.

FAQ

When is an 870 sent?

Two triggers: in response to a buyer's 869 inquiry, or unsolicited on an agreed schedule — a standing status feed on open orders. Some relationships use both.

What statuses can an 870 carry?

Per order and per line: accepted and in process, on schedule, delayed with revised dates, backordered, in jeopardy, partially or fully shipped. Codes vary by spec, but the vocabulary covers the fulfillment lifecycle.

Is an 870 binding like an 855?

It is a report, not a commitment document — but buyers plan against it, and a status that proves false damages trust the way a broken acknowledgment does. Report what your data actually says.

How does EDISQ price 870s?

Per document like all else: the first 25 each month free, then from $0.50 stepping down to $0.10 at volume. A scheduled weekly status run stays trivially cheap.