X12

Outbound

SpartanNash X12 880 Grocery Products Invoice

SpartanNash

The EDI 880 is a grocery-specific Invoice submitted to SpartanNash for DSD and grocery product shipments. It includes bracket pricing, promotional allowances, and grocery-specific tax handling.

20segments

4loops

8mandatory

Book a demo

← All SpartanNash transactions

Schema Reference

20 segments · X12 880 Grocery Products Invoice

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 Repetition Separator M MIN 1 MAX 1 ID: I65 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator 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

G0101 Date

M DT 8-8

G0102 Invoice Number

M AN 1-22

G0104 Purchase Order Number

O AN 1-22

G6101 Contact Function Code

M ID 2-2

G6102 Name

M AN 1-60

G6103 Communication Number Qualifier

C ID 2-2

G6104 Communication Number

C AN 1-256

G6201 Date Qualifier

C ID 2-2

G6202 Date

C DT 8-8

G2701 Transportation Method/Type Code

M ID 1-2

G2705 Routing

C AN 1-35

G2301 Terms Type Code

M ID 2-2

G2302 Terms Basis Date Code

M ID 1-2

G2305 Terms Discount Percent

O R 1-6

G2306 Terms Discount Due Date

O DT 8-8

G2307 Terms Discount Days Due

O N0 1-3

G2308 Terms Net Due Date

C DT 8-8

G2309 Terms Net Days

C N0 1-3

G2310 Terms Discount Amount

O N2 1-10

G2311 Discounted Amount Due

O N2 1-10

G2312 Amount Subject to Terms Discount

O N2 1-10

G2314 Percent of Invoice Payable

O R 1-5

G2501 Shipment Method of Payment

M ID 2-2

G2502 F.O.B. Point Code

M ID 2-2

N1 Loop Repeat: 10

N101 Entity Identifier Code

M ID 2-3

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

G72 Loop Repeat: 100

G7201 Allowance or Charge Code

M ID 1-3

G7202 Allowance or Charge Method of Handling Code

M ID 2-2

G7203 Allowance or Charge Number

C AN 1-16

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

G7301 Free-form Description

M AN 1-45

G17 Loop Repeat: 9,999

G1701 Quantity Invoiced

M R 1-10

G1702 Unit or Basis for Measurement Code

M ID 2-2

G1703 Item List Cost

C R 1-9

G1704 U.P.C. Case Code

C AN 12-12

G1705 Product/Service ID Qualifier

C ID 2-2

G1706 Product/Service ID

C AN 1-48

G1710 Number of Units Shipped

C R 1-10

G1711 Unit or Basis for Measurement Code

C ID 2-2

G6901 Free-form Description

M AN 1-45

G2004 Weight

C R 1-10

G2005 Unit or Basis for Measurement Code

C ID 2-2

G72 Loop Repeat: 100

G7201 Allowance or Charge Code

M ID 1-3

G7202 Allowance or Charge Method of Handling Code

M ID 2-2

G7203 Allowance or Charge Number

C AN 1-16

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

G7301 Free-form Description

M AN 1-45

G3101 Number of Units Shipped

M R 1-10

G3102 Unit or Basis for Measurement Code

M ID 2-2

G3103 Weight

C R 1-10

G3104 Unit or Basis for Measurement Code

C ID 2-2

G3105 Volume

C R 1-8

G3106 Unit or Basis for Measurement Code

C ID 2-2

G3108 Price Bracket Identifier

O AN 1-3

G3301 Amount

M N2 1-15

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

How It Works

Automating SpartanNash EDI 880

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

Validate

Transform

Route

Monitor

Stacksync generates SpartanNash 880 Grocery Invoices from your billing data with bracket pricing, promotional deductions, and grocery tax fields mapped automatically — reducing invoice rejections for DSD suppliers.

SpartanNash EDI 880 FAQ

Common questions about 880 Grocery Products Invoice transactions with SpartanNash.

What is a SpartanNash EDI 880 Grocery Products Invoice?

The SpartanNash EDI 880 Grocery Products Invoice is an X12 transaction set used to exchange Grocery Products Invoice data electronically between trading partners. As a outbound document, it standardizes the communication of Grocery Products Invoice information between SpartanNash and their suppliers, carriers, or partners. Stacksync processes SpartanNash 880 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 SpartanNash's requirements in real time.

How does Stacksync automate SpartanNash EDI 880 Grocery Products Invoice transactions?

Stacksync handles SpartanNash EDI 880 Grocery Products Invoice 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 outbound 880 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 SpartanNash 880 document meets their specific formatting requirements before transmission or after receipt.

What are common SpartanNash EDI 880 errors and how do I fix them?

Common errors in SpartanNash EDI 880 Grocery Products Invoice 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 SpartanNash 880 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 SpartanNash EDI 880 with Stacksync?

Most SpartanNash EDI 880 Grocery Products Invoice 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 SpartanNash's 880 format and your system, running test transactions, and completing SpartanNash's certification process if required. Stacksync includes pre-built mappings for SpartanNash's most common 880 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

Can I customize SpartanNash EDI 880 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how SpartanNash EDI 880 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 SpartanNash updates their 880 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Ready to automate SpartanNash EDI?