BSR
Beginning segment for order status report: the status report code, the order/item code, the reference number, and the date.
EDI 870: Order Status Report
A supplier’s report on the status of an order or its lines: in process, shipped, backordered, cancelled. Supplier to buyer, on request or on a schedule. This page covers what the 870 is for, the segments you meet when you open one, the documents it travels with, where it tends to go wrong, and how it moves over AS2 into your systems on Files.com, which receives, parses, validates, and routes it as configuration.
No credit card required · 7-day free trial · Live in minutes
#1 MFT vendor in Gartner Peer Insights
Trusted by 4,000+ companies
Every protocol included
What The 870 Is For
The 870 reports where an order stands. A supplier sends it, in reply to an 869 Order Status Inquiry or on a schedule, to say for each order and line whether it is in process, scheduled, shipped, partially shipped, backordered, or cancelled, with dates and quantities.
Buyers use it between the 855 acknowledgment and the 856 ship notice, when an order is open and the question is simply when it will ship. Marketplaces and large distributors often require it for open backorders.
The Segments You Meet First
In document order, the segments that carry the 870's meaning. A partner's implementation guide says which are required and which fields each must hold.
N1
Parties.
HL
Hierarchical level: order and item levels.
PRF
Purchase order reference: the PO being reported on.
ISR
Item status report: the status code and the date it applies to.
QTY
Quantities in each status.
Where It Goes Wrong
Status codes that lag reality, so an 870 says in process while the 856 has already shipped, and reports that cover only some of the open lines. An 870 is only useful if it is current.
The Documents It Travels With
The 870 rarely moves alone. These are the documents that precede, answer, or settle it.
869 · Order Status Inquiry
Travels with this document in the same exchange.
855 · Purchase Order Acknowledgment
The supplier’s answer to a purchase order: accepted, rejected, changed, or backordered, line by line.
See The 855856 · Ship Notice / Manifest (ASN)
The advance ship notice: what is in the shipment, how it is packed, and how it is labeled, sent before it arrives.
See The 856850 · Purchase Order
A buyer’s order to a supplier: the items, quantities, prices, dates, and ship-to locations.
See The 850How The 870 Moves On Files.com
A partner sends the 870 over AS2, SFTP, or FTPS, and it lands in that partner’s inbox folder on Files.com with the transport receipt recorded. From there it is a workflow, not a project: TransformScript parses the X12 natively into the JSON, CSV, or XML your ERP or WMS reads, content validation flags a document whose contents are wrong before anything ingests it, and an automation routes the result to the system and the people who act on it.
Outbound is the mirror image. Your system exports its record, TransformScript builds the 870 the partner’s guide specifies, and the file dropped in the partner’s outbox goes out over AS2 with automatic retries until the MDN confirms delivery. Every transmission in both directions is in the audit log, and delivery monitoring alerts when a 870 that was due never arrives. The full picture is on the EDI software page.
EDI 870 Questions
What teams ask about the 870 and how it moves on Files.com.
An EDI 870 is the X12 Order Status Report. A supplier sends it to report the status of open orders and their lines, in process, shipped, backordered, or cancelled, with dates and quantities, in response to an 869 inquiry or on a schedule.
Yes. Files.com is a standards-compliant RFC 4130 AS2 endpoint, and a 870 sent by a trading partner lands in that partner’s inbox folder with a signed MDN receipt returned to the sender. Partners who exchange over SFTP or FTPS connect to the same platform and the document lands in the same place.
Yes. TransformScript parses the X12 870 natively and writes the JSON, CSV, or XML your systems ingest, as a step in the workflow that fires when the document arrives. Outbound, the same engine builds a 870 from your system’s export and drops it in the partner’s outbox for delivery.
Exchange The 870 Without The Legacy Stack
Start the 7-day trial, turn AS2 on, and exchange certificates with your partner. The 870 lands in their folder, parses into the record your system reads, and every transmission carries a signed receipt.
No credit card required • Free for 7 days • Live in minutes