--- title: "EDI 895 Delivery/Return Acknowledgment | X12 | Stacksync" description: "EDI 895 is the X12 Delivery/Return Acknowledgment or Adjustment, used when delivery or return quantities are acknowledged or adjusted." canonical: https://www.stacksync.com/edi/x12/895-delivery-return-acknowledgment-or-adjustment last_modified: 2026-09-29 --- X12 transaction code # EDI 895 Delivery/Return Acknowledgment or Adjustment (X12 895) > 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 895 is the X12 Delivery/Return Acknowledgment or Adjustment transaction set, used when delivery or return quantities are acknowledged or adjusted. The retailer's store or headquarters receiving system sends the 895 back to the DSD supplier or distributor after checking in the delivery reported on the 894. Standard X12 Code 895 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 895 at a glance What the 895 carries, who sends it to whom, when it goes out, and the segments trading partners list for it. **X12 895 Delivery/Return Acknowledgment or Adjustment summary** | | | | --- | --- | | Document | X12 895 Delivery/Return Acknowledgment or Adjustment | | Business record | Delivery or return response | | Who sends it to whom | The retailer's store or headquarters receiving system sends the 895 back to the DSD supplier or distributor after checking in the delivery reported on the 894. | | When it is sent | Store personnel complete check-in of a DSD delivery and the receiving system confirms the driver's 894 or reports the quantity and item corrections found at the back door. | | Match on | Original delivery, response and affected item | | Partner references | 1 trading partner in this directory | | Related documents | [X12 894 Delivery/Return Base Record](https://www.stacksync.com/edi/x12/894-delivery-return-base-record) | ### Key segments in an EDI 895 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 | | --- | --- | --- | --- | | G87 | Delivery/Return Adjustment Identification | To transmit identifying numbers, dates, and other basic data relating to the transaction set. | 1 of 1 | | G89 | Line-Item Detail Adjustment | To transmit line-item detail adjustments. | 1 of 1 | | G72 | Allowance or Charge | To specify allowances, charges, or services. | 1 of 1 | | G23 | Terms of Sale | To specify the terms of sale. | 1 of 1 | | G84 | Delivery/Return Record of Totals | To specify summary details of total items in terms of quantity or amount. | 1 of 1 | | G86 | Signature | To transmit an electronic identity. | 1 of 1 | | G85 | Record Integrity Check | To provide a secure method of identifying authenticity of record content. | 1 of 1 | Stacksync connects EDI documents such as the X12 895 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 895 mapping and validation X12 895 Delivery/Return Acknowledgment or Adjustment is used when delivery or return quantities are acknowledged or adjusted. Preserve original delivery, response and affected item so the delivery or return 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 | **delivery or return response** original delivery, response and affected item | Define which combination of original delivery, response and affected item identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the delivery or return response** ID assigned by the receiving system and processing result | Apply an adjustment to the correct base-record line. Test multiple responses without applying the same quantity correction twice. | | Check the processing result | **Processing status for the delivery or return response** Original document reference and matching response | Reconcile the delivery or return 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 894 Delivery/Return Base Record](https://www.stacksync.com/edi/x12/894-delivery-return-base-record) **delivery or return base record:** delivery or return details establish a reconciliation baseline. ### Implementation steps 1. #### Choose the starting event and owner Decide which application acts when delivery or return quantities are acknowledged or adjusted. Name the operational owner of the delivery or return response and the team that resolves rejected or ambiguous messages. 2. #### Keep record IDs connected Map original delivery, response and affected 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 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 delivery or return response processing. Give unresolved errors an owner and check the receiving system before approving retries. ### Go-live checklist - An approved 895 sample and the agreed version and partner guide are available. - The mapping tests pass with realistic delivery or return 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 delivery or return response without processing it twice. ### Related documents and resources - [X12 894 Delivery/Return Base Record](https://www.stacksync.com/edi/x12/894-delivery-return-base-record) - [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 895 Delivery/Return Acknowledgment or Adjustment at the element level The X12 895 reference contains 15 segment entries and 65 data elements; 40 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields. Segments 15 Data elements 65 Mandatory elements 40 **Segments with elements marked mandatory in this reference** | Segment | Elements | Mandatory | | --- | --- | --- | | G87 | 6 | 5 | | LS | 1 | 1 | | G89 | 7 | 1 | | G72 | 7 | 2 | | LE | 1 | 1 | | G23 | 11 | 2 | | G85 | 1 | 1 | Key identifiers in 895 - Initiator Code - Credit/Debit Flag Code - Supplier's Delivery/Return Number - Integrity Check Value - Adjustment Number - Loop Identifier Code - Direct Store Delivery Sequence Number - Allowance or Charge Code ## Find your trading partner for X12 895 1 partner, 1 channel. Choose a channel to inspect its listed document reference and implementation context. - [Stater Bros. Markets](https://www.stacksync.com/edi/stater-brothers) [Stater Bros. Markets](https://www.stacksync.com/edi/stater-brothers/stater-bros-markets/x12-895-delivery-return-acknowledgment-or-adjustment) Catalog breakdown ## Where X12 895 Delivery/Return Acknowledgment or Adjustment appears in this catalog The largest groups of classified 895 catalog entries are in grocery & food. ### By industry - grocery & food 1 channel Partner entries with the most listed channels - [Stater Bros. Markets](https://www.stacksync.com/edi/stater-brothers) FAQ ## EDI 895 questions ### What is an EDI 895? EDI 895 is the X12 Delivery/Return Acknowledgment or Adjustment transaction set. Trading partners use it when delivery or return quantities are acknowledged or adjusted. It carries the data for the delivery or return response, and your system matches it on original delivery, response and affected item. ### Who sends an EDI 895 and who receives it? The retailer's store or headquarters receiving system sends the 895 back to the DSD supplier or distributor after checking in the delivery reported on the 894. Your trading partner agreement confirms the direction and version for your account. ### When is an EDI 895 sent? Store personnel complete check-in of a DSD delivery and the receiving system confirms the driver's 894 or reports the quantity and item corrections found at the back door. Your partner guide sets any deadline or schedule for the document. ### What are the key segments in an EDI 895? The one partner document reference listed here includes G87 (Delivery/Return Adjustment Identification), G89 (Line-Item Detail Adjustment), G72 (Allowance or Charge), G23 (Terms of Sale), G84 (Delivery/Return Record of Totals), G86 (Signature). Each partner guide sets which segments and elements your account must send. ### What is the difference between EDI 895 and EDI 894? The 895 carries the delivery or return response and is used when delivery or return quantities are acknowledged or adjusted. The 894 carries the delivery or return base record and is used when delivery or return details establish a reconciliation baseline. ### What should I map for X12 895? Start with original delivery, response and affected item and the target delivery or return 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 895 error handling? Apply an adjustment to the correct base-record line. Test multiple responses without applying the same quantity correction twice. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment. ### Which partners list X12 895? 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)