EDI 870 Order Status Report

EDI 870 Definition

The EDI 870 transaction set is an electronic Order Status Report that is used by a supplier as a response to an EDI 869 Order Status Inquiry provided by a trading partner and reports the current status of EDI 850 Purchase Order in question. EDI 870 can be used to report on the status of the entire purchase order, selected products or services, requirement forecasts, or to update the supplier’s scheduled shipment.

Sent By: Supplier, Manufacturer, or Distributor

The supplier sends the EDI 870 to provide the buyer with a status update on a purchase order. This may be in response to an EDI 869 Order Status Inquiry, or sent proactively to keep the buyer informed.

Received By: Retailer, Buyer, or Trading Partner

The buyer receives the EDI 870 to understand where their order stands — whether items are confirmed, in production, shipped, backordered, or cancelled.

What EDI 870 Represents in Real Life

The EDI 870 is not just a status update.

It is the supplier’s way of keeping the buyer informed about what is happening with their order. In supply chains where timing matters, the 870 prevents surprises — buyers know early if something is delayed, backordered, or shipping ahead of schedule.

When an EDI 870 is processed successfully:

• • • The buyer knows the current status of every line item on their order
    • Backorders and delays are communicated proactively
    • Receiving teams can plan for incoming shipments
    • Customer service can provide accurate delivery timelines to end customers

In short, the EDI 870 keeps buyers informed and supply chains running smoothly.

EDI 870 Specification

This X12 Transaction Set contains the format and establishes the data contents of the Order Status Report Transaction Set (870) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to report the current status of a purchase order, selected line items, or the supplier’s scheduled shipment.

Source: Accredited Standards Committee X12. ASC X12 Standard [Table Data]. Data Interchange Standards Association, Inc., Falls Church, VA. https://x12.org

Components of an EDI 870 Order Status Report:

• • • Purchase order number
    • Purchase order date
    • Order status codes
    • Item/Service identifiers (UPC/EAN/GTIN)
    • Item price and quantity
    • Shipment status and carrier details
    • Consignee information

• • • Tracking and reference numbers
    • Scheduled ship dates
    • Quantity shipped vs. quantity ordered
    • Backorder status
    • Carrier and routing information

Related EDI Transactions

Other EDI documents directly related to the Order Status Report:

• • • EDI 869 – Order Status Inquiry
    • EDI 850 – Purchase Order
    • EDI 855 – Purchase Order Acknowledgment

Other related EDI documents include:

• • • EDI 810 – Invoice
    • EDI 812 – Credit / Debit Adjustment
    • EDI 820 – Payment or Order Remittance
    • EDI 830 – Planning Schedule with Release Capability
    • EDI 832 – Price/Sales Catalog
    • EDI 846 – Inventory Inquiry
    • EDI 856 – Advance Ship Notice
    • EDI 860 – Order Change Request
    • EDI 867 – Product Transfer and Resale Report
    • EDI 875 – Grocery Products Purchase Order
    • EDI 990 – Response to a Load Tender
    • EDI 997 – Functional Acknowledgement

EDI 870 Sample File Format (Raw EDI File)

ISA*00*          *00*          *12*111111111      *12*222222222      *230310*1859*U*00401*034792000*0*P*>
GS*RS*111111111*222222222*20230310*1859*34792100*X*004010
ST*870*34792102
BSR*3*PA*119294*20230310
REF*VR*SPAWO001
N1*OB*5678
N1*ST*1234
HL*1**O
PRF*37222892
ISR*CC*20230310
HL*2*1*I
PO1*1*1*EA***SK*123456*VP*56789
PID*F****Item Info
ISR*CC*20230310
QTY*39*1
N1*CN*John Doe*12*123456789
TD5*****5678
REF*2I*TMW3096806
HL*3*1*I
PO1*2*1*EA***SK*123457*VP*56788
PID*F****Item Info2
ISR*CC*20230310
QTY*39*1
N1*CN*John Doe*12*123456789
TD5*****5678
REF*2I*TMW3096806
CTT*2
SE*26*34792102
GE*1*34792100
IEA*1*034792000

What Each Line in the EDI 870 Sample Means

Each segment in an EDI 870 serves a specific purpose. Here is a breakdown of the sample file above:

ISA – Interchange Control Header. Opens the EDI envelope with sender/receiver IDs, date (230310), time (1859), and control number.

GS – Functional Group Header. Identifies the transaction type (RS = Order Status Report).

ST – Transaction Set Header. “870” identifies the document type with control number 34792102.

BSR – Status Report Identification. Report type (3 = Response to inquiry), status (PA = Partially shipped), order number (119294), and report date.

REF*VR – Vendor Reference. VR = Vendor Order Reference. The supplier’s internal reference (SPAWO001).

N1*OB – Ordered By Name. OB = Ordered By. Identifies the party that placed the order (5678).

N1*ST – Ship To Name. ST = Ship To. Identifies the delivery destination (1234).

HL*1**O – Hierarchical Level – Order. The HL segment creates a parent-child structure. Level 1 with code O = Order level.

PRF – Purchase Order Reference. Links this status report to purchase order number 37222892.

ISR*CC – Item Status Report. CC = Order status confirmed as complete. The status date is 20230310.

HL*2*1*I – Hierarchical Level – Item. Level 2, child of level 1, with code I = Item level. This begins the first line item detail.

PO1 – Line Item Detail. Line 1: quantity 1, unit of measure EA (Each), SKU 123456, vendor part 56789.

PID – Product Description. F = Free-form description. “Item Info” describes the product.

QTY*39 – Quantity Information. Qualifier 39 = Quantity shipped to date. 1 unit shipped.

N1*CN – Consignee Name. CN = Consignee. “John Doe” with DUNS number 123456789 — the person or company receiving the goods.

TD5 – Carrier Details. Contains the routing/carrier code (5678).

REF*2I – Tracking Reference. 2I = Tracking number. TMW3096806 is the shipment tracking reference.

CTT – Transaction Totals. 2 total line items in this status report.

SE / GE / IEA – Closing segments. SE closes the transaction (26 segments), GE closes the functional group, and IEA closes the interchange envelope.

Real-World Example: Supplier Reporting Order Status to a Retailer

A retailer placed a purchase order for two items. The supplier is providing a status update.

• • • The retailer sends an EDI 869 Order Status Inquiry to the supplier
    • The supplier checks order and shipment status in their system
    • Elevate generates an EDI 870 Order Status Report with current details
    • The report shows both items confirmed and shipped with tracking numbers
    • The retailer’s system updates the order status automatically
    • The retailer’s receiving team prepares for the incoming shipment

When 870 is accurate, buyers have full visibility without needing to call or email.

Why EDI 870 Accuracy is Critical

Inaccurate status reports create confusion and erode trust.

Common problems include:

• • • Status codes that don’t reflect actual order progress
    • Missing or incorrect tracking numbers
    • Wrong quantities reported as shipped
    • Outdated dates that don’t match current shipment schedules

These issues lead to:

• • • Buyers making decisions based on wrong information
    • Receiving teams unprepared for deliveries
    • Unnecessary follow-up calls and emails
    • Erosion of trading partner confidence
    • Potential compliance issues with retailers who mandate accurate reporting

A clean EDI 870 builds trust and reduces back-and-forth communication.

Common Challenges with EDI 870 Order Status Reports

• • • Different trading partners expect different status code conventions
    • Real-time status data requires tight integration with WMS and TMS systems
    • Partial shipments and backorders create complex multi-status scenarios
    • Hierarchical (HL) loop structure can be difficult to map correctly
    • Proactive vs. inquiry-based reporting varies by partner requirements

Flexible EDI systems handle these scenarios without breaking the flow.

How to Start Sending EDI 870

If your business needs to start sending EDI 870 Order Status Reports to trading partners, here is a general roadmap:

1. 1. 1. Understand your trading partner’s requirements: Each buyer may have different expectations for status codes, frequency of updates, and whether reports are inquiry-based (responding to an 869) or proactive.
      2. Choose an EDI platform: You need EDI software to translate your data into the proper ANSI X12 format. Cloud-based platforms like Elevate make this straightforward with transparent pricing, no contracts, and end-to-end support.
      3. Map your data: Connect the fields in your ERP, WMS, or TMS to the corresponding EDI 870 segments. This includes order references, item details, quantities shipped, carrier information, and tracking numbers.
      4. Test with your trading partner: Before going live, send test 870 transactions to validate that the data maps correctly and the status codes meet their requirements.
      5. Go live and monitor: Once testing is complete, begin sending production 870s. Monitor for errors, acknowledgment failures, and data mismatches. A good EDI platform will alert you to issues in real time.

Need help with EDI 945 implementation and more?

Elevate is built for small businesses and includes hands-on onboarding so you don’t have to figure it out alone.

FAQs