X12
Inbound

Schnucks X12 894 Delivery/Return Base Record

Schnucks
The EDI 894 (Delivery/Return Base Record) document is used by Schnucks for electronic data interchange. It enables automated processing and compliance with Schnucks's trading partner requirements.
12segments
2loops
8mandatory

Schema Reference

12 segments · X12 894 Delivery/Return Base Record

ISA ISA Interchange Control Header
Mandatory Max: 1
ISA01 Authorization Information Qualifier
M ID 2-2
ISA02 Authorization Information
M AN 10-10
ISA03 Security Information Qualifier
M ID 2-2
ISA04 Security Information
M AN 10-10
ISA05 Interchange ID Qualifier
M ID 2-2
ISA06 Interchange Sender ID
M AN 15-15
ISA07 Interchange ID Qualifier
M ID 2-2
ISA08 Interchange Receiver ID
M AN 15-15
ISA09 Interchange Date
M DT 6-6
ISA10 Interchange Time
M TM 4-4
ISA11 Interchange Control Standards Identifier
M ID 1-1
ISA12 Interchange Control Version Number
M ID 5-5
ISA13 Interchange Control Number
M N0 9-9
ISA14 Acknowledgment Requested
M ID 1-1
ISA15 Usage Indicator
M ID 1-1
GS GS Functional Group Header
Mandatory Max: 1
GS01 Functional Identifier Code
M ID 2-2
GS02 Application Sender's Code
M AN 2-15
GS03 Application Receiver's Code
M AN 2-15
GS04 Date
M DT 8-8
GS05 Time
M TM 4-8
GS06 Group Control Number
M N0 1-9
GS07 Responsible Agency Code
M ID 1-2
GS08 Version / Release / Industry Identifier Code
M AN 1-12
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
G82 Delivery/Return Base Record Identifier
Mandatory Max: 1
G8201 Credit/Debit Flag Code
M ID 1-1
G8202 Supplier's Delivery/Return Number
M AN 1-22
G8203 D-U-N-S Number
M ID 9-9
G8204 Receiver's Location Number
M AN 1-6
G8205 D-U-N-S Number
M ID 9-9
G8206 Supplier's Location Number
M AN 1-6
G8207 Physical Delivery or Return Date
M DT 8-8
LS Loop Repeat: 1
LS Loop Header
Optional Max: 1
LS01 Loop Identifier Code
M AN 1-6
G83 Loop Repeat: 9,999
G83 Line Item Detail/Direct Store Delivery
Optional Max: 1
G8301 Direct Store Delivery Sequence Number
M N0 1-4
G8302 Quantity
M R 1-15
G8303 Unit or Basis for Measurement Code
M ID 2-2
G8304 U.P.C./EAN Consumer Package Code
C AN 12-12
G8308 Item List Cost
O R 1-9
G8309 Pack
C N0 1-6
G8310 Cash Register Item Description
O AN 1-20
G72 Allowance or Charge
Optional Max: 10
G7201 Allowance or Charge Code
M ID 1-3
G7202 Allowance or Charge Method of Handling Code
M ID 2-2
G7205 Allowance or Charge Rate
C R 1-15
G7206 Allowance or Charge Quantity
C R 1-10
G7207 Unit or Basis for Measurement Code
C ID 2-2
G7208 Allowance or Charge Total Amount
C N2 1-15
LE Loop Trailer
Optional Max: 1
LE01 Loop Identifier Code
M AN 1-6
G84 Delivery/Return Record of Totals
Mandatory Max: 1
G8401 Quantity
C R 1-15
G8402 Total Invoice Amount
C N2 1-10
G86 Signature
Mandatory Max: 1
G8601 Signature
O AN 1-12
G85 Record Integrity Check
Mandatory Max: 1
G8501 Integrity Check Value
M AN 1-12
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-10
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating Schnucks EDI 894

Stacksync validates, transforms, and delivers your 894 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate
Transform
Route
Monitor
Stacksync processes Schnucks EDI 894 (Delivery/Return Base Record) documents automatically — syncing data to your system in real time with no manual intervention required.

Schnucks EDI 894 FAQ

Common questions about 894 Delivery/Return Base Record transactions with Schnucks.

How long does it take to set up Schnucks EDI with Stacksync?

Most suppliers are fully connected and processing live Schnucks EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with Schnucks?

No. Stacksync handles the entire EDI transport layer. We connect directly to Schnucks's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with Schnucks compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for Schnucks?

Stacksync supports all EDI document types required by Schnucks — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect Schnucks EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between Schnucks's EDI network and your system in real time.

What happens when Schnucks updates their EDI specifications?

Stacksync monitors Schnucks's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.