--- title: "EDI 894 Delivery/Return Base Record | X12 | Stacksync" description: "EDI 894 is the X12 Delivery/Return Base Record, used when delivery or return details establish a reconciliation baseline." canonical: https://www.stacksync.com/edi/x12/894-delivery-return-base-record last_modified: 2026-09-29 --- X12 transaction code # EDI 894 Delivery/Return Base Record (X12 894) > 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 894 is the X12 Delivery/Return Base Record transaction set, used when delivery or return details establish a reconciliation baseline. The DSD supplier or distributor sends the 894 to the retailer's store or headquarters system; the retailer responds with an 895 Delivery/Return Acknowledgment or Adjustment, or a 997. Standard X12 Code 894 Partner references 8 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) At a glance ## EDI 894 at a glance What the 894 carries, who sends it to whom, when it goes out, and the segments trading partners list for it. **X12 894 Delivery/Return Base Record summary** | | | | --- | --- | | Document | X12 894 Delivery/Return Base Record | | Business record | Delivery or return base record | | Who sends it to whom | The DSD supplier or distributor sends the 894 to the retailer's store or headquarters system; the retailer responds with an 895 Delivery/Return Acknowledgment or Adjustment, or a 997. | | When it is sent | A route driver delivers product to, or collects returns from, a store on a DSD route and the delivery record must reach the retailer for check-in; some retailers expect it within 4 hours of delivery. | | Match on | Delivery reference, store and item | | Partner references | 8 trading partners in this directory | | Related documents | [X12 895 Delivery/Return Acknowledgment or Adjustment](https://www.stacksync.com/edi/x12/895-delivery-return-acknowledgment-or-adjustment) | ### Key segments in an EDI 894 The business segments that appear in at least half of the 8 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 | | --- | --- | --- | --- | | G82 | Delivery/Return Base Record Identifier | To transmit identifying numbers, dates, and other basic data relating to the transaction set. | 8 of 8 | | G83 | Line Item Detail/Direct Store Delivery | To specify the basic, and most frequently used line item data for the delivery record transaction. | 8 of 8 | | G72 | Allowance or Charge | To specify allowances, charges, or services. | 8 of 8 | | G84 | Delivery/Return Record of Totals | To specify summary details of total items in terms of quantity or amount. | 8 of 8 | | G86 | Signature Identification | To transmit an electronic identity. | 8 of 8 | | G85 | Record Integrity Check | To provide a secure method of identifying authenticity of record content. | 8 of 8 | | N9 | Extended Reference Information | To transmit identifying information as specified by the Reference Identification Qualifier. | 4 of 8 | | G23 | Terms of Sale | To specify the terms of sale. | 4 of 8 | Stacksync connects EDI documents such as the X12 894 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 894 mapping and validation X12 894 Delivery/Return Base Record is used when delivery or return details establish a reconciliation baseline. Preserve delivery reference, store and item so the delivery or return base record 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 | **delivery or return base record** delivery reference, store and item | Define which combination of delivery reference, store and item identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the delivery or return base record** ID assigned by the receiving system and processing result | Separate returned units from delivered units when calculating the net quantity. Retain the original delivery record when a receiving party later disputes a quantity. | | Check the processing result | **Processing status for the delivery or return base record** Original document reference and matching response | Reconcile the delivery or return base record 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 895 Delivery/Return Acknowledgment or Adjustment](https://www.stacksync.com/edi/x12/895-delivery-return-acknowledgment-or-adjustment) **delivery or return response:** delivery or return quantities are acknowledged or adjusted. ### Implementation steps 1. #### Choose the starting event and owner Decide which application acts when delivery or return details establish a reconciliation baseline. Name the operational owner of the delivery or return base record and the team that resolves rejected or ambiguous messages. 2. #### Keep record IDs connected Map delivery reference, store and item. 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 delivery or return base record 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 delivery or return base record processing. Give unresolved errors an owner and check the receiving system before approving retries. ### Go-live checklist - An approved 894 sample and the agreed version and partner guide are available. - The mapping tests pass with realistic delivery or return base record 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 delivery or return base record without processing it twice. ### Related documents and resources - [X12 895 Delivery/Return Acknowledgment or Adjustment](https://www.stacksync.com/edi/x12/895-delivery-return-acknowledgment-or-adjustment) - [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 894 Delivery/Return Base Record at the element level The X12 894 reference contains 17 segment entries and 72 data elements; 45 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields. Segments 17 Data elements 72 Mandatory elements 45 **Segments with elements marked mandatory in this reference** | Segment | Elements | Mandatory | | --- | --- | --- | | G82 | 7 | 5 | | N9 | 2 | 1 | | LS | 1 | 1 | | G83 | 11 | 3 | | G72 | 8 | 2 | | LE | 1 | 1 | | G23 | 3 | 2 | | G85 | 1 | 1 | Key identifiers in 894 - Credit/Debit Flag Code - Supplier's Delivery/Return Number - D-U-N-S Number - Supplier's Location Number - Physical Delivery or Return Date - Reference Identification Qualifier - Loop Identifier Code - Direct Store Delivery Sequence Number ## Find your trading partner for X12 894 8 partners, 8 channels. Choose a channel to inspect its listed document reference and implementation context. - [Ahold Delhaize](https://www.stacksync.com/edi/ahold-delhaize) [Food Lion (Delhaize America)](https://www.stacksync.com/edi/ahold-delhaize/food-lion-delhaize-america/x12-894-delivery-return-base-record) - [HEB (Here Everything's Better)](https://www.stacksync.com/edi/heb-here-everythings-better) [HEB (Here Everything's Better) (Standard)](https://www.stacksync.com/edi/heb-here-everythings-better/heb-here-everything-s-better-standard/x12-894-delivery-return-base-record) - [Kroger](https://www.stacksync.com/edi/kroger) [Peyton's Group (a Kroger Division)](https://www.stacksync.com/edi/kroger/peyton-s-group-a-kroger-division/x12-894-delivery-return-base-record) - [Meijer](https://www.stacksync.com/edi/meijer) [Meijer (Grocery)](https://www.stacksync.com/edi/meijer/meijer-grocery/x12-894-delivery-return-base-record) - [Raley's Supermarkets](https://www.stacksync.com/edi/raleys-supermarkets) [Raley's Supermarkets](https://www.stacksync.com/edi/raleys-supermarkets/raley-s-supermarkets/x12-894-delivery-return-base-record) - [Schnucks](https://www.stacksync.com/edi/schnucks) [Schnucks](https://www.stacksync.com/edi/schnucks/schnucks/x12-894-delivery-return-base-record) - [Sprouts Farmers Market](https://www.stacksync.com/edi/sprouts-farmers-market) [Sprouts Farmers Market (via SPS Commerce)](https://www.stacksync.com/edi/sprouts-farmers-market/sprouts-farmers-market-via-sps-commerce/x12-894-delivery-return-base-record) - [Stater Bros. Markets](https://www.stacksync.com/edi/stater-brothers) [Stater Bros. Markets](https://www.stacksync.com/edi/stater-brothers/stater-bros-markets/x12-894-delivery-return-base-record) Catalog breakdown ## Where X12 894 Delivery/Return Base Record appears in this catalog The largest groups of classified 894 catalog entries are in grocery & food. ### By industry - grocery & food 8 channels ### By network - SPS Commerce 1 channel Partner entries with the most listed channels - [Ahold Delhaize](https://www.stacksync.com/edi/ahold-delhaize) - [HEB (Here Everything's Better)](https://www.stacksync.com/edi/heb-here-everythings-better) - [Kroger](https://www.stacksync.com/edi/kroger) - [Meijer](https://www.stacksync.com/edi/meijer) - [Raley's Supermarkets](https://www.stacksync.com/edi/raleys-supermarkets) - [Schnucks](https://www.stacksync.com/edi/schnucks) - [Sprouts Farmers Market](https://www.stacksync.com/edi/sprouts-farmers-market) - [Stater Bros. Markets](https://www.stacksync.com/edi/stater-brothers) FAQ ## EDI 894 questions ### What is an EDI 894? EDI 894 is the X12 Delivery/Return Base Record transaction set. Trading partners use it when delivery or return details establish a reconciliation baseline. It carries the data for the delivery or return base record, and your system matches it on delivery reference, store and item. ### Who sends an EDI 894 and who receives it? The DSD supplier or distributor sends the 894 to the retailer's store or headquarters system; the retailer responds with an 895 Delivery/Return Acknowledgment or Adjustment, or a 997. Your trading partner agreement confirms the direction and version for your account. ### When is an EDI 894 sent? A route driver delivers product to, or collects returns from, a store on a DSD route and the delivery record must reach the retailer for check-in; some retailers expect it within 4 hours of delivery. Your partner guide sets any deadline or schedule for the document. ### What are the key segments in an EDI 894? Across 8 partner document references listed here, the business segments that appear most often include G82 (Delivery/Return Base Record Identifier), G83 (Line Item Detail/Direct Store Delivery), G72 (Allowance or Charge), G84 (Delivery/Return Record of Totals), G86 (Signature Identification), G85 (Record Integrity Check). Each partner guide sets which segments and elements your account must send. ### What is the difference between EDI 894 and EDI 895? The 894 carries the delivery or return base record and is used when delivery or return details establish a reconciliation baseline. The 895 carries the delivery or return response and is used when delivery or return quantities are acknowledged or adjusted. ### What should I map for X12 894? Start with delivery reference, store and item and the target delivery or return base record. 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 894 error handling? Separate returned units from delivered units when calculating the net quantity. Retain the original delivery record when a receiving party later disputes a quantity. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment. ### Which partners list X12 894? The directory on this page links 8 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)