X12

Inbound

SpartanNash X12 875 Grocery Products Purchase Order

SpartanNash

The EDI 875 is a grocery-specific Purchase Order used by SpartanNash for food and consumable products. It includes DSD (direct store delivery) requirements, shelf-life data, and UPC details specific to grocery supply chains.

17segments

3loops

8mandatory

Book a demo

← All SpartanNash transactions

Schema Reference

17 segments · X12 875 Grocery Products Purchase Order

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

G5001 Order Status Code

M ID 1-1

G5002 Date

M DT 8-8

G5003 Purchase Order Number

M AN 1-22

G5007 Purchase Order Type Code

O ID 2-2

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-50

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

NTE01 Note Reference Code

O ID 3-3

NTE02 Description

M AN 1-80

G6601 Shipment Method of Payment

O ID 2-2

G6602 Transportation Method/Type Code

O ID 1-2

G6604 Unit Load Option Code

O ID 2-2

G6605 Routing

O AN 1-35

G6606 F.O.B. Point Code

O ID 2-2

G6607 F.O.B. Point

O AN 1-30

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

G68 Loop Repeat: 9,999

G6801 Quantity Ordered

M R 1-15

G6802 Unit or Basis for Measurement Code

M ID 2-2

G6803 Item List Cost

O R 1-9

G6804 U.P.C. Case Code

C AN 12-12

G6807 Product/Service ID Qualifier

C ID 2-2

G6808 Product/Service ID

C AN 1-48

G6901 Free-form Description

M AN 1-45

G7001 Pack

O N0 1-6

G7004 Purchase Order Instruction Code

O ID 2-2

G7009 Pallet Block and Tiers

O N0 6-6

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

G7301 Free-form Description

M AN 1-45

G7601 Quantity Ordered

M R 1-15

G7602 Unit or Basis for Measurement Code

M ID 2-2

G7603 Weight

C R 1-10

G7604 Unit or Basis for Measurement Code

C ID 2-2

G7605 Volume

C R 1-8

G7606 Unit or Basis for Measurement Code

C ID 2-2

G7608 Amount

O 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 875

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

Validate

Transform

Route

Monitor

Stacksync syncs SpartanNash 875 Grocery POs to your system with DSD routing, shelf-life requirements, and grocery UPCs mapped automatically — purpose-built for food and consumable suppliers.

SpartanNash EDI 875 FAQ

Common questions about 875 Grocery Products Purchase Order transactions with SpartanNash.

What is a SpartanNash EDI 875 Grocery Products Purchase Order?

The SpartanNash EDI 875 Grocery Products Purchase Order is an X12 transaction set used to exchange Grocery Products Purchase Order data electronically between trading partners. As a inbound document, it standardizes the communication of Grocery Products Purchase Order information between SpartanNash and their suppliers, carriers, or partners. Stacksync processes SpartanNash 875 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 875 Grocery Products Purchase Order transactions?

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

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

Common errors in SpartanNash EDI 875 Grocery Products Purchase Order 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 875 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 875 with Stacksync?

Most SpartanNash EDI 875 Grocery Products Purchase Order 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 875 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 875 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 875 field mappings in Stacksync?

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

Ready to automate SpartanNash EDI?