To start and identify an interchange of zero or more functional groups and interchange-related control segments
Nordstrom X12 870 Order Status Report
X12 870 (Order Status Report) is the EDI transaction exchanged between Nordstrom (Nordstrom (Dropship) (via DSCO (dba Rithum))) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 12
- Loops
- 4
- X12 870
- All partners ↗
Transaction context
Where 870 Order Status Report fits on Nordstrom (Dropship) (via DSCO (dba Rithum))
- Nordstrom channels
- 3 of 8
- Trading partners
- 18
- Channels
- 24
3 of Nordstrom's 8 channels carry 870
partners across the Stacksync network trade 870
channels network-wide carry 870
Most common alongside 870
On Rithum, 870 runs on 10 channels.
The 870 is the seller's report of where a customer's order stands. It can cover the full order, specific line items, or selected products, with shipped, backordered, and cancelled quantities and revised dates. It is sent either in response to an 869 Order Status Inquiry or proactively on a prearranged schedule, such as when inventory is allocated. Buyers require it to plan around delays without manual follow-up. 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 fires: 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.
Common 870 rejection causes
- Status report codes applied inconsistently across line items, so buyers cannot reliably distinguish shipped, backordered, and cancelled quantities.
- Reported quantities that do not reconcile against the original purchase order lines, creating false shortage or overage signals.
- Missing or incorrect purchase order references, leaving status updates that cannot be attached to an open order.
- Scheduled status reports that stop arriving at the agreed interval, which buyers often treat as a vendor compliance issue.
Specification summary
X12 870 Order Status Report at the element level
The X12 870 specification defines 24 segments carrying 59 data elements, 43 of which are mandatory.
- 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 |
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
Full segment guideline — 12 segments 4 loops · X12 870 Order Status Report
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To indicate the beginning of an Order Status Report Transaction Set
HL Loop Repeat: 1,000
To identify dependencies among and the content of hierarchically related groups of data segments
To provide reference to a specific purchase order
REF Loop Repeat: 1,000
To specify identifying information
PO1 Loop Repeat: 1,000
To transmit a hash total for a specific element in the transaction set
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To specify basic and most frequently used line item data
To specify product subline detail item data
ISR Loop Repeat: 104
To specify detailed purchase order/item status
Trading partners
2+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
No trading partner matches your search.
Browse the full directory
Trading partners
5+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
IN Inventory Inquiry Advice SH Ship Notice Manifest PU Purchase Order IN Invoice PU Purchase Order Acknowledgment
No trading partner matches your search.
Browse the full directory
Nordstrom Nordstrom (Dropship) (via DSCO (dba Rithum)) EDI 870 FAQ
Common questions about 870 Order Status Report on the Nordstrom (Dropship) (via DSCO (dba Rithum)) channel.
What is X12 870 Order Status Report?
X12 870 (Order Status Report) is the EDI transaction set used to exchange order status report data. Nordstrom's Nordstrom (Dropship) (via DSCO (dba Rithum)) channel requires it from trading partners.
Does Nordstrom Nordstrom (Dropship) (via DSCO (dba Rithum)) require 870 for trading partners?
Yes, Nordstrom (Nordstrom (Dropship) (via DSCO (dba Rithum))) supports X12 870 Order Status Report. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Nordstrom 870 with Stacksync?
Most companies go live with Nordstrom 870 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which other Nordstrom channels accept 870?
X12 870 runs on 3 of Nordstrom's 8 channels. Besides Nordstrom (Dropship) (via DSCO (dba Rithum)), it is accepted on Nordstrom Rack (formerly HauteLook) (via Rithum DSCO), Nordstrom Rack (via DSCO (dba Rithum)). Each channel carries its own implementation guideline; Stacksync validates outbound documents against the correct guideline automatically.
Ready to automate your Nordstrom EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
