X12 transaction code
X12 869 Order Status Inquiry
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 869
- Trading partners
- 1
Specification summary
X12 869 Order Status Inquiry at the element level
The X12 869 specification defines 12 segments carrying 42 data elements, 37 of which are mandatory.
- Segments
- 12
- Data elements
- 42
- Mandatory elements
- 37
| Segment | Elements | Mandatory |
|---|---|---|
| BSI | 3 | 3 |
| HL | 2 | 2 |
| PRF | 2 | 1 |
| LIN | 5 | 2 |
| REF | 2 | 1 |
| CTT | 1 | 1 |
- Reference Identification
- Date
- Order/Item Code
- Hierarchical ID Number
- Hierarchical Level Code
- Purchase Order Number
- Product/Service ID Qualifier
- Product/Service ID
Trading partners that support X12 869
1 partner, 1 channel. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 869 Order Status Inquiry
869 is used most heavily in furniture & home.
The 869 is the buyer's electronic request for the current status of one or more previously placed orders, asking for details such as ship dates and the shipment, backorder, or cancellation status of ordered items. Trading partners use it to replace phone and email follow-up when expected order-visibility documents have not arrived; the supplier is expected to answer with an 870 Order Status Report. The buyer sends the 869 to the supplier, who responds with an 870 Order Status Report. An open purchase order passes its expected acknowledgment or ship date without an 855 or 856 arriving, and the buyer's purchasing system issues an 869 to ask where the order stands.
By industry
- furniture & home 1 channel
By network
- TrueCommerce 1 channel
FAQ
X12 869 questions
What is X12 869 Order Status Inquiry?
X12 869 (Order Status Inquiry) is an EDI transaction set defined by ANSI ASC X12 for exchanging order status inquiry between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 1 Stacksync trading partner supports this code across 1 channel.
Which trading partners use X12 869?
1 Stacksync partner accepts X12 869: Jordan's Furniture. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 869 with my ERP?
Stacksync handles the full X12 869 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.
