X12 transaction code
EDI 870 Order Status Report (X12 870)
EDI 870 is the X12 Order Status Report transaction set, used when order progress is reported. The supplier or vendor sends the 870 to the buyer, either as a reply to the buyer's 869 inquiry or on an agreed reporting schedule.
- Standard
- X12
- Code
- 870
- Partner references
- 18
At a glance
EDI 870 at a glance
What the 870 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 870 Order Status Report |
|---|---|
| Business record | Order-status response |
| Who sends it to whom | The supplier or vendor sends the 870 to the buyer, either as a reply to the buyer's 869 inquiry or on an agreed reporting schedule. |
| When it is sent | A supplier's system reaches a reporting milestone, such as inventory allocation or a change in expected ship date, or receives an 869 inquiry, and generates an 870 with the current order status. |
| Match on | Purchase order, status time and order line |
| Partner references | 18 trading partners in this directory |
| Related documents | X12 869 Order Status Inquiry, X12 850 Purchase Order, X12 856 Ship Notice/Manifest |
Key segments in an EDI 870
The business segments that appear in at least half of the 24 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.
| Segment | Name | Purpose | Partner references |
|---|---|---|---|
| BSR | Beginning Segment for Order Status Report | To indicate the beginning of an Order Status Report Transaction Set. | 24 of 24 |
| HL | Hierarchical Level | To identify dependencies among and the content of hierarchically related groups of data segments. | 24 of 24 |
| PRF | Purchase Order Reference | To provide reference to a specific purchase order. | 24 of 24 |
| PO1 | Baseline Item Data | To specify basic and most frequently used line item data. | 24 of 24 |
| REF | Reference Identification | To specify identifying information. | 23 of 24 |
| CTT | Transaction Totals | To transmit a hash total for a specific element in the transaction set. | 23 of 24 |
| ISR | Item Status Report | To specify detailed purchase order/item status. | 21 of 24 |
| SLN | Subline Item Detail | To specify product subline detail item data. | 13 of 24 |
Stacksync connects EDI documents such as the X12 870 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.
Implementation guide
X12 870 mapping and validation
X12 870 Order Status Report is used when order progress is reported. Preserve purchase order, status time and order line so the order-status response in your business system stays connected to the original document.
Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | order-status response purchase order, status time and order line |
|
| Update the receiving system | Processing the order-status response ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the order-status response Original document reference and matching response |
|
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 869 Order Status Inquiry
order-status inquiry: a buyer requests an order update.
- X12 850 Purchase Order
purchase order or sales order: a buyer places an order.
- X12 856 Ship Notice/Manifest
shipment notice (ASN): an order ships, before the goods arrive.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when order progress is reported. Name the operational owner of the order-status response and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map purchase order, status time and order line. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic order-status response data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful order-status response processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 870 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic order-status response data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out order-status response without processing it twice.
Document structure
X12 870 Order Status Report at the element level
The X12 870 reference contains 24 segment entries and 59 data elements; 43 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 24
- Data elements
- 59
- Mandatory elements
- 43
| Segment | Elements | Mandatory |
|---|---|---|
| BSR | 4 | 4 |
| REF | 2 | 1 |
| N1 | 2 | 1 |
| HL | 2 | 2 |
| PRF | 1 | 1 |
| ISR | 2 | 1 |
| PID | 2 | 1 |
| QTY | 2 | 1 |
| CTT | 1 | 1 |
- Status Report Code
- Order/Item Code
- Reference Identification
- Date
- Reference Identification Qualifier
- Entity Identifier Code
- Hierarchical ID Number
- Hierarchical Level Code
Find your trading partner for X12 870
18 partners, 24 channels. Choose a channel to inspect its listed document reference and implementation context.
- AAFES (Army and Air Force Exchange Service)
- BrandX
- Cole Haan
- Dillard's Department Stores, Inc.
- DSW (formerly Shoes.com)
- DSW Inc.
- Ford Motor Company
- JCPenney
- Jordan's Furniture
- Men's Wearhouse via DSCO
- Menards
- Neiman Marcus
- Nordstrom
- Road Runner Sports
- Saks Fifth Avenue & Saks OFF 5th
- Shoe Carnival Drop Ship
- URBN
- Zappos
Catalog breakdown
Where X12 870 Order Status Report appears in this catalog
The largest groups of classified 870 catalog entries are in apparel & footwear, retail and furniture & home.
By industry
- apparel & footwear 17 channels
- retail 3 channels
- furniture & home 1 channel
- automotive 1 channel
- other industries 1 channel
- building & hardware 1 channel
By network
- Rithum 10 channels
- TrueCommerce 1 channel
- Radial Vendornet Saksvnet 1 channel
- InterTrade 1 channel
- SPS Commerce 1 channel
- DSCO v.4010 (dba Rithum 1 channel
FAQ
EDI 870 questions
What is an EDI 870?
EDI 870 is the X12 Order Status Report transaction set. Trading partners use it when order progress is reported. It carries the data for the order-status response, and your system matches it on purchase order, status time and order line.
Who sends an EDI 870 and who receives it?
The supplier or vendor sends the 870 to the buyer, either as a reply to the buyer's 869 inquiry or on an agreed reporting schedule. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 870 sent?
A supplier's system reaches a reporting milestone, such as inventory allocation or a change in expected ship date, or receives an 869 inquiry, and generates an 870 with the current order status. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 870?
Across 24 partner document references listed here, the business segments that appear most often include BSR (Beginning Segment for Order Status Report), HL (Hierarchical Level), PRF (Purchase Order Reference), PO1 (Baseline Item Data), REF (Reference Identification), CTT (Transaction Totals). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 870 and EDI 869?
The 870 carries the order-status response and is used when order progress is reported. The 869 carries the order-status inquiry and is used when a buyer requests an order update.
What should I map for X12 870?
Start with purchase order, status time and order line and the target order-status response. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 870 error handling?
Represent mixed line statuses without declaring the whole order shipped. Keep an older status report from overwriting a more recent fulfillment state. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 870?
The directory on this page links 18 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
Connect EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
