--- title: "EDI 869 Order Status Inquiry: X12 869 Guide | Stacksync" description: "EDI 869 is the X12 Order Status Inquiry, used when a buyer requests an order update. See key segments (BSI, HL, PRF) and mapping checks." canonical: https://www.stacksync.com/edi/x12/869-order-status-inquiry last_modified: 2026-09-29 --- X12 transaction code # EDI 869 Order Status Inquiry (X12 869) > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md 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 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) 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. **X12 869 Order Status Inquiry summary** | | | | --- | --- | | 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](https://www.stacksync.com/edi/x12/870-order-status-report), [X12 850 Purchase Order](https://www.stacksync.com/edi/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](https://www.stacksync.com/edi), check [pricing](https://www.stacksync.com/pricing) and [security](https://www.stacksync.com/security), or [book a demo](https://www.stacksync.com/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. **Map records and test the business result** | Document or decision | Record and matching IDs | What to test | | --- | --- | --- | | Match the business record | **order-status inquiry** purchase order, inquiry and requested line | Define which combination of purchase order, inquiry and requested line identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the order-status inquiry** ID assigned by the receiving system and processing result | Test an inquiry for one line on a multi-line order. Route an unknown order reference to an explicit exception response. | | Check the processing result | **Processing status for the order-status inquiry** Original document reference and matching response | Reconcile the order-status inquiry 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 870 Order Status Report](https://www.stacksync.com/edi/x12/870-order-status-report) **order-status response:** order progress is reported. - [X12 850 Purchase Order](https://www.stacksync.com/edi/x12/850-purchase-order) **purchase order or sales order:** a buyer places an order. ### Implementation steps 1. #### 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. 2. #### 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. 3. #### 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. 4. #### 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. ### Related documents and resources - [X12 870 Order Status Report](https://www.stacksync.com/edi/x12/870-order-status-report) - [X12 850 Purchase Order](https://www.stacksync.com/edi/x12/850-purchase-order) - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) **Sources.** Sources reviewed 2026-09-15. - [X12 transaction-set directory](https://x12.org/products/transaction-sets) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) 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 **Segments with elements marked mandatory in this reference** | Segment | Elements | Mandatory | | --- | --- | --- | | BSI | 3 | 3 | | HL | 2 | 2 | | PRF | 2 | 1 | | LIN | 5 | 2 | | REF | 2 | 1 | | CTT | 1 | 1 | Key identifiers in 869 - 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. - [Jordan's Furniture](https://www.stacksync.com/edi/jordans-furniture) [Jordan's Furniture (via TrueCommerce)](https://www.stacksync.com/edi/jordans-furniture/jordan-s-furniture-via-truecommerce/x12-869-order-status-inquiry) 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 Partner entries with the most listed channels - [Jordan's Furniture](https://www.stacksync.com/edi/jordans-furniture) 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. [Book an EDI demo](https://www.stacksync.com/book-a-demo) [Explore the EDI platform](https://www.stacksync.com/edi)