--- title: "EDI 870 Order Status Report: X12 870 Guide | Stacksync" description: "EDI 870 is the X12 Order Status Report, used when order progress is reported. See key segments (BSR, HL, PRF) and mapping checks." canonical: https://www.stacksync.com/edi/x12/870-order-status-report last_modified: 2026-09-29 --- X12 transaction code # EDI 870 Order Status Report (X12 870) > 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 870 is the X12 Order Status Report transaction set, used when order progress is reported. 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. Standard X12 Code 870 Partner references 18 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) At a glance ## EDI 870 at a glance What the 870 carries, who sends it to whom, when it goes out, and the segments trading partners list for it. **X12 870 Order Status Report summary** | | | | --- | --- | | Document | X12 870 Order Status Report | | Business record | Order-status response | | Who sends it to whom | 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 is sent | 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. | | Match on | Purchase order, status time and order line | | Partner references | 18 trading partners in this directory | | Related documents | [X12 869 Order Status Inquiry](https://www.stacksync.com/edi/x12/869-order-status-inquiry), [X12 850 Purchase Order](https://www.stacksync.com/edi/x12/850-purchase-order), [X12 856 Ship Notice/Manifest](https://www.stacksync.com/edi/x12/856-ship-notice-manifest) | ### Key segments in an EDI 870 The business segments that appear in at least half of the 24 partner document references listed below, most common first. 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 | | --- | --- | --- | --- | | BSR | Beginning Segment for Order Status Report | To indicate the beginning of an Order Status Report Transaction Set. | 24 of 24 | | HL | Hierarchical Level | To identify dependencies among and the content of hierarchically related groups of data segments. | 24 of 24 | | PRF | Purchase Order Reference | To provide reference to a specific purchase order. | 24 of 24 | | PO1 | Baseline Item Data | To specify basic and most frequently used line item data. | 24 of 24 | | REF | Reference Identification | To specify identifying information. | 23 of 24 | | CTT | Transaction Totals | To transmit a hash total for a specific element in the transaction set. | 23 of 24 | | ISR | Item Status Report | To specify detailed purchase order/item status. | 21 of 24 | | SLN | Subline Item Detail | To specify product subline detail item data. | 13 of 24 | Stacksync connects EDI documents such as the X12 870 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 870 mapping and validation X12 870 Order Status Report is used when order progress is reported. Preserve purchase order, status time and order line so the order-status response 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 response** purchase order, status time and order line | Define which combination of purchase order, status time and order line identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the order-status response** ID assigned by the receiving system and processing result | Represent mixed line statuses without declaring the whole order shipped. Keep an older status report from overwriting a more recent fulfillment state. | | Check the processing result | **Processing status for the order-status response** Original document reference and matching response | Reconcile the order-status response 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 869 Order Status Inquiry](https://www.stacksync.com/edi/x12/869-order-status-inquiry) **order-status inquiry:** a buyer requests an order update. - [X12 850 Purchase Order](https://www.stacksync.com/edi/x12/850-purchase-order) **purchase order or sales order:** a buyer places an order. - [X12 856 Ship Notice/Manifest](https://www.stacksync.com/edi/x12/856-ship-notice-manifest) **shipment notice (ASN):** an order ships, before the goods arrive. ### Implementation steps 1. #### Choose the starting event and owner Decide which application acts when order progress is reported. Name the operational owner of the order-status response and the team that resolves rejected or ambiguous messages. 2. #### Keep record IDs connected Map purchase order, status time and order 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 response 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 response processing. Give unresolved errors an owner and check the receiving system before approving retries. ### Go-live checklist - An approved 870 sample and the agreed version and partner guide are available. - The mapping tests pass with realistic order-status response 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 response without processing it twice. ### Related documents and resources - [X12 869 Order Status Inquiry](https://www.stacksync.com/edi/x12/869-order-status-inquiry) - [X12 850 Purchase Order](https://www.stacksync.com/edi/x12/850-purchase-order) - [X12 856 Ship Notice/Manifest](https://www.stacksync.com/edi/x12/856-ship-notice-manifest) - [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 870 Order Status Report at the element level The X12 870 reference contains 24 segment entries and 59 data elements; 43 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields. Segments 24 Data elements 59 Mandatory elements 43 **Segments with elements marked mandatory in this reference** | 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 ## Find your trading partner for X12 870 18 partners, 24 channels. Choose a channel to inspect its listed document reference and implementation context. - [AAFES (Army and Air Force Exchange Service)](https://www.stacksync.com/edi/aafes-army-and-air-force-exchange-service) [AAFES (via DSCO (dba Rithum))](https://www.stacksync.com/edi/aafes-army-and-air-force-exchange-service/aafes-via-dsco-dba-rithum/x12-870-order-status-report) - [BrandX](https://www.stacksync.com/edi/brandx) [BrandX](https://www.stacksync.com/edi/brandx/brandx/x12-870-order-status-report) - [Cole Haan](https://www.stacksync.com/edi/cole-haan) [Cole Haan DS](https://www.stacksync.com/edi/cole-haan/cole-haan-ds/x12-870-order-status-report) - [Dillard's Department Stores, Inc.](https://www.stacksync.com/edi/dillards-department-stores-inc) [Dillards Department Stores(Inovis VAN)](https://www.stacksync.com/edi/dillards-department-stores-inc/dillards-department-stores-inovis-van/x12-870-order-status-report) [Dillards Department Stores(TGMS Customers)](https://www.stacksync.com/edi/dillards-department-stores-inc/dillards-department-stores-tgms-customers/x12-870-order-status-report) [Dillards Department Stores via InterTrade](https://www.stacksync.com/edi/dillards-department-stores-inc/dillards-department-stores-via-intertrade/x12-870-order-status-report) - [DSW (formerly Shoes.com)](https://www.stacksync.com/edi/famous-dropship) [DSW (formerly Shoes.com) (Dropship) (via DSCO (dba Rithum))](https://www.stacksync.com/edi/famous-dropship/dsw-formerly-shoes-com-dropship-via-dsco-dba-rithum/x12-870-order-status-report) - [DSW Inc.](https://www.stacksync.com/edi/dsw-inc) [DSW Dropship (via DSCO (dba Rithum))](https://www.stacksync.com/edi/dsw-inc/dsw-dropship-via-dsco-dba-rithum/x12-870-order-status-report) - [Ford Motor Company](https://www.stacksync.com/edi/ford-motor-company-sds) [Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS)](https://www.stacksync.com/edi/ford-motor-company-sds/ford-motor-company-customer-service-division-north-america-supplier-direct-ship-sds/x12-870-order-status-report) - [JCPenney](https://www.stacksync.com/edi/jcpenney) [JCPenney (Stores Retail) (870)](https://www.stacksync.com/edi/jcpenney/jcpenney-stores-retail-870/x12-870-order-status-report) [JCPenney (eCom Catalog) (870)](https://www.stacksync.com/edi/jcpenney/jcpenney-ecom-catalog-870/x12-870-order-status-report) - [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-870-order-status-report) - [Men's Wearhouse via DSCO](https://www.stacksync.com/edi/mens-wearhouse) [Men's Wearhouse (Tailored Brands) (via DSCO (dba Rithum))](https://www.stacksync.com/edi/mens-wearhouse/men-s-wearhouse-tailored-brands-via-dsco-dba-rithum/x12-870-order-status-report) - [Menards](https://www.stacksync.com/edi/menard) [Menards](https://www.stacksync.com/edi/menard/menards/x12-870-order-status-report) - [Neiman Marcus](https://www.stacksync.com/edi/neiman-marcus) [Neiman Marcus (via DSCO v.4010 (dba Rithum))](https://www.stacksync.com/edi/neiman-marcus/neiman-marcus-via-dsco-v-4010-dba-rithum/x12-870-order-status-report) - [Nordstrom](https://www.stacksync.com/edi/nordstrom) [Nordstrom (Dropship) (via DSCO (dba Rithum))](https://www.stacksync.com/edi/nordstrom/nordstrom-dropship-via-dsco-dba-rithum/x12-870-order-status-report) [Nordstrom Rack (formerly HauteLook) (via Rithum DSCO)](https://www.stacksync.com/edi/nordstrom/nordstrom-rack-formerly-hautelook-via-rithum-dsco/x12-870-order-status-report) [Nordstrom Rack (via DSCO (dba Rithum))](https://www.stacksync.com/edi/nordstrom/nordstrom-rack-via-dsco-dba-rithum/x12-870-order-status-report) - [Road Runner Sports](https://www.stacksync.com/edi/road-runner-sports-dropship) [Road Runner Sports (via SPS Commerce)](https://www.stacksync.com/edi/road-runner-sports-dropship/road-runner-sports-via-sps-commerce/x12-870-order-status-report) - [Saks Fifth Avenue & Saks OFF 5th](https://www.stacksync.com/edi/saks-fifth-avenue--saks-off-5th) [Saks OFF 5TH (Dropship) (via DSCO (dba Rithum))](https://www.stacksync.com/edi/saks-fifth-avenue--saks-off-5th/saks-off-5th-dropship-via-dsco-dba-rithum/x12-870-order-status-report) [Saks Fifth Avenue & Saks OFF 5th - Dropship via Radial/VendorNet (SAKSVNET)](https://www.stacksync.com/edi/saks-fifth-avenue--saks-off-5th/saks-fifth-avenue-saks-off-5th-dropship-via-radial-vendornet-saksvnet/x12-870-order-status-report) - [Shoe Carnival Drop Ship](https://www.stacksync.com/edi/shoe-carnival-drop-ship) [Shoe Carnival Dropship via DSCO](https://www.stacksync.com/edi/shoe-carnival-drop-ship/shoe-carnival-dropship-via-dsco/x12-870-order-status-report) - [URBN](https://www.stacksync.com/edi/urbn) [URBN Suppliers (via DSCO (dba Rithum))](https://www.stacksync.com/edi/urbn/urbn-suppliers-via-dsco-dba-rithum/x12-870-order-status-report) - [Zappos](https://www.stacksync.com/edi/zappos) [Zappos (via DSCO (dba Rithum))](https://www.stacksync.com/edi/zappos/zappos-via-dsco-dba-rithum/x12-870-order-status-report) Catalog breakdown ## Where X12 870 Order Status Report appears in this catalog The largest groups of classified 870 catalog entries are in apparel & footwear, retail and furniture & home. ### 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 Partner entries with the most listed channels - [Dillard's Department Stores, Inc.](https://www.stacksync.com/edi/dillards-department-stores-inc) - [Nordstrom](https://www.stacksync.com/edi/nordstrom) - [JCPenney](https://www.stacksync.com/edi/jcpenney) - [Saks Fifth Avenue & Saks OFF 5th](https://www.stacksync.com/edi/saks-fifth-avenue--saks-off-5th) - [AAFES (Army and Air Force Exchange Service)](https://www.stacksync.com/edi/aafes-army-and-air-force-exchange-service) - [BrandX](https://www.stacksync.com/edi/brandx) - [Cole Haan](https://www.stacksync.com/edi/cole-haan) - [DSW (formerly Shoes.com)](https://www.stacksync.com/edi/famous-dropship) FAQ ## EDI 870 questions ### What is an EDI 870? EDI 870 is the X12 Order Status Report transaction set. Trading partners use it when order progress is reported. It carries the data for the order-status response, and your system matches it on purchase order, status time and order line. ### Who sends an EDI 870 and who receives it? 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. Your trading partner agreement confirms the direction and version for your account. ### When is an EDI 870 sent? 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. Your partner guide sets any deadline or schedule for the document. ### What are the key segments in an EDI 870? Across 24 partner document references listed here, the business segments that appear most often include BSR (Beginning Segment for Order Status Report), HL (Hierarchical Level), PRF (Purchase Order Reference), PO1 (Baseline Item Data), REF (Reference Identification), CTT (Transaction Totals). Each partner guide sets which segments and elements your account must send. ### What is the difference between EDI 870 and EDI 869? The 870 carries the order-status response and is used when order progress is reported. The 869 carries the order-status inquiry and is used when a buyer requests an order update. ### What should I map for X12 870? Start with purchase order, status time and order line and the target order-status response. 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 870 error handling? Represent mixed line statuses without declaring the whole order shipped. Keep an older status report from overwriting a more recent fulfillment state. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment. ### Which partners list X12 870? The directory on this page links 18 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)