X12 transaction code
EDI 869 Order Status Inquiry (X12 869)
EDI 869 is the X12 Order Status Inquiry transaction set, used when a buyer requests an order update. The buyer sends the 869 to the supplier, who responds with an 870 Order Status Report.
- Standard
- X12
- Code
- 869
- Partner references
- 1
At a glance
EDI 869 at a glance
What the 869 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 869 Order Status Inquiry |
|---|---|
| Business record | Order-status inquiry |
| Who sends it to whom | The buyer sends the 869 to the supplier, who responds with an 870 Order Status Report. |
| When it is sent | 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. |
| Match on | Purchase order, inquiry and requested line |
| Partner references | 1 trading partner in this directory |
| Related documents | X12 870 Order Status Report, X12 850 Purchase Order |
Key segments in an EDI 869
The business segments in the one partner document reference listed below. 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 |
|---|---|---|---|
| BSI | Beginning Segment for Order Status Inquiry | To indicate the beginning of an order status inquiry and provide the type of customer status inquiry. | 1 of 1 |
| HL | Hierarchical Level | To identify dependencies among and the content of hierarchically related groups of data segments. | 1 of 1 |
| PRF | Purchase Order Reference | To provide reference to a specific purchase order. | 1 of 1 |
| LIN | Item Identification | To specify basic item identification data. | 1 of 1 |
| REF | Reference Identification | To specify identifying information. | 1 of 1 |
| CTT | Transaction Totals | To transmit a hash total for a specific element in the transaction set. | 1 of 1 |
Stacksync connects EDI documents such as the X12 869 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 869 mapping and validation
X12 869 Order Status Inquiry is used when a buyer requests an order update. Preserve purchase order, inquiry and requested line so the order-status inquiry 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 inquiry purchase order, inquiry and requested line |
|
| Update the receiving system | Processing the order-status inquiry ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the order-status inquiry 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 870 Order Status Report
order-status response: order progress is reported.
- X12 850 Purchase Order
purchase order or sales order: a buyer places an order.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a buyer requests an order update. Name the operational owner of the order-status inquiry and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map purchase order, inquiry and requested 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 inquiry 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 inquiry processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 869 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic order-status inquiry 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 inquiry without processing it twice.
Document structure
X12 869 Order Status Inquiry at the element level
The X12 869 reference contains 12 segment entries and 42 data elements; 37 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- 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
Find your trading partner for X12 869
1 partner, 1 channel. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 869 Order Status Inquiry appears in this catalog
The largest groups of classified 869 catalog entries are in furniture & home.
By industry
- furniture & home 1 channel
By network
- TrueCommerce 1 channel
FAQ
EDI 869 questions
What is an EDI 869?
EDI 869 is the X12 Order Status Inquiry transaction set. Trading partners use it when a buyer requests an order update. It carries the data for the order-status inquiry, and your system matches it on purchase order, inquiry and requested line.
Who sends an EDI 869 and who receives it?
The buyer sends the 869 to the supplier, who responds with an 870 Order Status Report. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 869 sent?
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. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 869?
The one partner document reference listed here includes BSI (Beginning Segment for Order Status Inquiry), HL (Hierarchical Level), PRF (Purchase Order Reference), LIN (Item Identification), REF (Reference Identification), CTT (Transaction Totals). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 869 and EDI 870?
The 869 carries the order-status inquiry and is used when a buyer requests an order update. The 870 carries the order-status response and is used when order progress is reported.
What should I map for X12 869?
Start with purchase order, inquiry and requested line and the target order-status inquiry. 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 869 error handling?
Test an inquiry for one line on a multi-line order. Route an unknown order reference to an explicit exception response. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 869?
The directory on this page links 1 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.
