X12 transaction code

X12 870 Order Status Report

X12 870 Order Status Report: explore its business purpose, mapping identifiers, validation tests and 18 partner references across 24 listed channels.

Standard: X12
Code: 870
Partner references: 18

Book an EDI demo ← All trading partners

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.

Map records and test the business result
Document or decision	Record and matching IDs	What to test
Match the business record	order-status response purchase order, status time and order line	Define which combination of purchase order, status time and order line identifies one business record, its lines and any later revision.
Update the receiving system	Processing the order-status response ID assigned by the receiving system and processing result	Represent mixed line statuses without declaring the whole order shipped. Keep an older status report from overwriting a more recent fulfillment state.
Check the processing result	Processing status for the order-status response Original document reference and matching response	Reconcile the order-status response with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

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): shipment contents are known before the agreed notification deadline.

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

Segments with elements marked mandatory in this reference
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

Key identifiers in 870

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.

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

Partner entries with the most listed channels

FAQ

X12 870 questions

What is X12 870 Order Status Report used for?

870 is used when order progress is reported. It carries information for the order-status response. Match it to your business system using purchase order, status time and order line.

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.

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.

How does 870 relate to other EDI messages?

X12 869 Order Status Inquiry; X12 850 Purchase Order; X12 856 Ship Notice Manifest are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

What is the difference between 870 and 869?

870 is used when order progress is reported. 869 is used when a buyer requests an order update. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

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.

Book an EDI demo Explore the EDI platform