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

Book a demo

← All Schnucks transactions

Schema Reference

12 segments · X12 894 Delivery/Return Base Record

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

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

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

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

LS01 Loop Identifier Code

M AN 1-6

G83 Loop Repeat: 9,999

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

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

LE01 Loop Identifier Code

M AN 1-6

G8401 Quantity

C R 1-15

G8402 Total Invoice Amount

C N2 1-10

G8601 Signature

O AN 1-12

G8501 Integrity Check Value

M AN 1-12

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.

What is a Schnucks EDI 894 Delivery/Return Base Record?

The Schnucks EDI 894 Delivery/Return Base Record is an X12 transaction set used to exchange Delivery/Return Base Record data electronically between trading partners. As a inbound document, it standardizes the communication of Delivery/Return Base Record information between Schnucks and their suppliers, carriers, or partners. Stacksync processes Schnucks 894 transactions automatically, parsing the X12 segments and mapping them to the corresponding records in your ERP, WMS, or database. This eliminates manual data entry, reduces errors, and ensures your systems stay in sync with Schnucks's requirements in real time.

How does Stacksync automate Schnucks EDI 894 Delivery/Return Base Record transactions?

Stacksync handles Schnucks EDI 894 Delivery/Return Base Record transactions through an automated pipeline: receive the X12 document, validate the envelope and segment structure, map fields to your system's schema, and sync the data in real time. For inbound 894 transactions, Stacksync either generates the document from your system's data or processes incoming documents and routes them to the correct records. The platform includes built-in compliance validation so every Schnucks 894 document meets their specific formatting requirements before transmission or after receipt.

What are common Schnucks EDI 894 errors and how do I fix them?

Common errors in Schnucks EDI 894 Delivery/Return Base Record transactions include missing mandatory segments, invalid qualifier codes, incorrect date or time formats, and data values exceeding maximum field lengths. Reference number mismatches between related documents (e.g., PO numbers that don't match) also cause rejections. Stacksync validates Schnucks 894 documents against known requirements before transmission and after receipt, catching errors proactively. When issues occur, the platform provides human-readable error descriptions with the specific segment and element that failed, rather than raw X12 error codes.

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

Most Schnucks EDI 894 Delivery/Return Base Record integrations with Stacksync go live within 3 to 5 business days. The setup involves authenticating your EDI connection (AS2, SFTP, or VAN), configuring field mappings between Schnucks's 894 format and your system, running test transactions, and completing Schnucks's certification process if required. Stacksync includes pre-built mappings for Schnucks's most common 894 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

Can I customize Schnucks EDI 894 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how Schnucks EDI 894 segments and elements map to your system's fields. You can set data transformations (date format conversion, code translation tables), conditional routing rules, and default values for optional fields. The mappings are version-controlled, so changes can be reviewed and rolled back if needed. If Schnucks updates their 894 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Ready to automate Schnucks EDI?