X12 transaction code
X12 870 Order Status Report
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 870
- Trading partners
- 18
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 |
- Status Report Code
- Order/Item Code
- Reference Identification
- Date
- Reference Identification Qualifier
- Entity Identifier Code
- Hierarchical ID Number
- Hierarchical Level Code
Trading partners that support X12 870
18 partners, 24 channels. Click a channel for the full segment guideline.
- 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
Usage breakdown
Who trades X12 870 Order Status Report
870 is used most heavily in apparel & footwear, retail and furniture & home.
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. 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.
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
X12 870 questions
What is X12 870 Order Status Report?
X12 870 (Order Status Report) is an EDI transaction set defined by ANSI ASC X12 for exchanging order status report between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 18 Stacksync trading partners support this code across 24 channels.
Which trading partners use X12 870?
18 Stacksync partners accept X12 870: 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, and more. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 870 with my ERP?
Stacksync handles the full X12 870 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.
Ready to automate your EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
