EDI 894 - Delivery, Return Base Record
The EDI 894, also known as Delivery, Return Base Record, is a direct-store-delivery document detailing products delivered or returned at a store.
The EDI 894, also known as Delivery, Return Base Record, is a direct-store-delivery document detailing products delivered or returned at a store.
What is the Purpose of EDI 894 - Delivery, Return Base Record?
The EDI 894 (Delivery/Return Base Record) enables suppliers to notify retailers about incoming shipments, including detailed item quantities. This advance notification is particularly important in the food and beverage industry, where accurate quantities, pricing, and shipment details are crucial for smooth product transfers.
What are the important elements of EDI 894 - Delivery, Return Base Record?
The EDI 894 (Delivery/Return Base Record) is a standardized electronic document used to communicate delivery and return information. Here are the key elements: 1. Header Information: - Base Record Number - Transaction Date/Time - Transaction Type Code - Purpose Code - Record Type (Delivery/Return) - Status Code - Currency Code 2. Partner Information: - Delivery/Return Location (name, ID, address) - Sender Information - Receiver Information - Carrier Details - Route Information - Additional Trading Partner IDs 3. Delivery/Return Details: - Line Item Numbers - Product Identifiers - Item Descriptions - Quantities Delivered/Returned - Unit of Measure - Status Information - Reason Codes - Condition Codes 4. Date Information: - Delivery/Return Date - Base Record Date - Transaction Date - Processing Date - Expected Resolution Date - Settlement Date - Reference Period 5. Documentation Details: - Proof of Delivery - Return Authorization - Driver Information - Signature Details - Incident Reports - Supporting Documents - Resolution Information 6. Reference Numbers: - Original Order Numbers - Invoice Numbers - Shipping References - Authorization Numbers - Route Numbers - Store Numbers 7. Financial Information: - Original Values - Return Values - Adjustments - Credits/Debits - Settlement Information - Payment Terms - Charges 8. Additional Elements: - Special Instructions - Handling Requirements - Quality Information - Disposition Instructions - Follow-up Actions - Resolution Requirements 9. Control Segments: - Transaction Set Control Numbers - Segment Counts - Hash Totals - Control Totals The EDI 894 is essential for tracking deliveries and returns, maintaining accurate records, and ensuring proper resolution of delivery/return issues.
What are the potential issues with EDI 894 - Delivery, Return Base Record?
Here are the potential issues that can occur with EDI 894 (Delivery/Return Base Record) transmissions: 1. Base Record Information Problems: - Incorrect record numbers - Wrong transaction types - Invalid purpose codes - Missing record types - Wrong status codes - Invalid delivery/return codes - Missing base information 2. Product Detail Issues: - Wrong product identifiers - Invalid item descriptions - Missing quantities - Incorrect unit measures - Wrong condition codes - Invalid reason codes - Missing product specifications 3. Location Information Problems: - Wrong delivery locations - Invalid return locations - Missing carrier details - Incorrect route information - Wrong facility codes - Invalid stop numbers - Missing dock information 4. Date/Time Problems: - Wrong delivery dates - Invalid return dates - Missing transaction dates - Incorrect processing dates - Wrong resolution dates - Invalid settlement dates - Missing effective dates 5. Documentation Issues: - Missing proof of delivery - Invalid return authorization - Wrong incident reports - Incorrect supporting documents - Missing driver information - Wrong signature details - Invalid verification data 6. Financial Information Problems: - Incorrect original values - Wrong return values - Invalid adjustments - Missing credits/debits - Wrong settlement information - Invalid payment terms - Missing charge details 7. Format and Structure Issues: - Missing mandatory segments - Invalid segment sequence - Wrong element usage - Incorrect qualifiers - Version/release mismatches - Character set problems - Wrong hierarchical structure 8. System Integration Challenges: - DSD system incompatibilities - ERP integration problems - Translation errors - Interface failures - Database synchronization - Data transformation errors - Mapping discrepancies 9. Reference Number Problems: - Missing original order numbers - Invalid invoice references - Wrong shipping references - Incorrect authorization codes - Missing route numbers - Wrong store numbers - Invalid control numbers These issues can impact delivery and return processing accuracy, requiring robust validation and error handling procedures.
EDI 894 - Delivery, Return Base Record
The EDI 894, also known as Delivery, Return Base Record, is a direct-store-delivery document detailing products delivered or returned at a store.
What is the Purpose of EDI 894 - Delivery, Return Base Record?
The EDI 894 (Delivery/Return Base Record) enables suppliers to notify retailers about incoming shipments, including detailed item quantities. This advance notification is particularly important in the food and beverage industry, where accurate quantities, pricing, and shipment details are crucial for smooth product transfers.
What are the important elements of EDI 894 - Delivery, Return Base Record?
The EDI 894 (Delivery/Return Base Record) is a standardized electronic document used to communicate delivery and return information. Here are the key elements: 1. Header Information: - Base Record Number - Transaction Date/Time - Transaction Type Code - Purpose Code - Record Type (Delivery/Return) - Status Code - Currency Code 2. Partner Information: - Delivery/Return Location (name, ID, address) - Sender Information - Receiver Information - Carrier Details - Route Information - Additional Trading Partner IDs 3. Delivery/Return Details: - Line Item Numbers - Product Identifiers - Item Descriptions - Quantities Delivered/Returned - Unit of Measure - Status Information - Reason Codes - Condition Codes 4. Date Information: - Delivery/Return Date - Base Record Date - Transaction Date - Processing Date - Expected Resolution Date - Settlement Date - Reference Period 5. Documentation Details: - Proof of Delivery - Return Authorization - Driver Information - Signature Details - Incident Reports - Supporting Documents - Resolution Information 6. Reference Numbers: - Original Order Numbers - Invoice Numbers - Shipping References - Authorization Numbers - Route Numbers - Store Numbers 7. Financial Information: - Original Values - Return Values - Adjustments - Credits/Debits - Settlement Information - Payment Terms - Charges 8. Additional Elements: - Special Instructions - Handling Requirements - Quality Information - Disposition Instructions - Follow-up Actions - Resolution Requirements 9. Control Segments: - Transaction Set Control Numbers - Segment Counts - Hash Totals - Control Totals The EDI 894 is essential for tracking deliveries and returns, maintaining accurate records, and ensuring proper resolution of delivery/return issues.
What are the potential issues with EDI 894 - Delivery, Return Base Record?
Here are the potential issues that can occur with EDI 894 (Delivery/Return Base Record) transmissions: 1. Base Record Information Problems: - Incorrect record numbers - Wrong transaction types - Invalid purpose codes - Missing record types - Wrong status codes - Invalid delivery/return codes - Missing base information 2. Product Detail Issues: - Wrong product identifiers - Invalid item descriptions - Missing quantities - Incorrect unit measures - Wrong condition codes - Invalid reason codes - Missing product specifications 3. Location Information Problems: - Wrong delivery locations - Invalid return locations - Missing carrier details - Incorrect route information - Wrong facility codes - Invalid stop numbers - Missing dock information 4. Date/Time Problems: - Wrong delivery dates - Invalid return dates - Missing transaction dates - Incorrect processing dates - Wrong resolution dates - Invalid settlement dates - Missing effective dates 5. Documentation Issues: - Missing proof of delivery - Invalid return authorization - Wrong incident reports - Incorrect supporting documents - Missing driver information - Wrong signature details - Invalid verification data 6. Financial Information Problems: - Incorrect original values - Wrong return values - Invalid adjustments - Missing credits/debits - Wrong settlement information - Invalid payment terms - Missing charge details 7. Format and Structure Issues: - Missing mandatory segments - Invalid segment sequence - Wrong element usage - Incorrect qualifiers - Version/release mismatches - Character set problems - Wrong hierarchical structure 8. System Integration Challenges: - DSD system incompatibilities - ERP integration problems - Translation errors - Interface failures - Database synchronization - Data transformation errors - Mapping discrepancies 9. Reference Number Problems: - Missing original order numbers - Invalid invoice references - Wrong shipping references - Incorrect authorization codes - Missing route numbers - Wrong store numbers - Invalid control numbers These issues can impact delivery and return processing accuracy, requiring robust validation and error handling procedures.
Curious about other types?
Search transaction type
More articles
Our platform is designed to empower businesses of all sizes to work smarter and achieve their goals with confidence.
Oct 27, 2026
A 997 confirms an EDI file parsed cleanly. The order answer comes in the 855. See what the MDN, 997, 999 and 855 each confirm, plus a go-live checklist.
Oct 27, 2026
Tips and best practices for building a reliable and efficient task management process.
Oct 23, 2026
What EDI 824 Application Advice and 864 Text Message rejections mean, how to read them, and how to fix the invoice, ASN, and PO errors behind them.
Oct 23, 2026
Tips and best practices for building a reliable and efficient task management process.
Oct 21, 2026
How the EDI 832 Price/Sales Catalog works, segment by segment, plus the item data errors that cause rejections and chargebacks across retailers and distributors.
Oct 21, 2026
Tips and best practices for building a reliable and efficient task management process.
Oct 27, 2026
A 997 confirms an EDI file parsed cleanly. The order answer comes in the 855. See what the MDN, 997, 999 and 855 each confirm, plus a go-live checklist.
Oct 23, 2026
What EDI 824 Application Advice and 864 Text Message rejections mean, how to read them, and how to fix the invoice, ASN, and PO errors behind them.
Oct 21, 2026
How the EDI 832 Price/Sales Catalog works, segment by segment, plus the item data errors that cause rejections and chargebacks across retailers and distributors.
Oct 19, 2026
How the EDI 845, 844, and 849 work together for distributor contract pricing and chargebacks, with a worked dollar example and the errors that cause denied claims.
