Skip to content
X12 EDI

Sprouts Farmers Market X12 876 Grocery Products Purchase Order Change

Plan X12 876 Grocery Products Purchase Order Change for Sprouts Farmers Market (via SPS Commerce). Connect document identifiers to your business records, test exception handling and track each exchange to completion.

Segments
18
Loops
3
X12 876
Partner references ↗

Implementation guide

Sprouts Farmers Market (via SPS Commerce): 876 mapping and validation

X12 876 Grocery Products Purchase Order Change is used when a grocery buyer revises an order. Preserve original grocery order, revision and item so the grocery order change in your business system stays connected to the original document.

This document is listed for Sprouts Farmers Market (via SPS Commerce). Confirm the version, required fields and responses that apply to your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record grocery order change

original grocery order, revision and item

  • Define which combination of original grocery order, revision and item identifies one business record, its lines and any later revision.
Update the receiving system Processing the grocery order change

ID assigned by the receiving system and processing result

  • Apply a pack-quantity change to the original order line.
  • Test a late reduction after warehouse picking and require operational review.
Check the processing result Processing status for the grocery order change

Original document reference and matching response

  • Reconcile the grocery order change with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

The document reference includes 18 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.

How the related documents differ

Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.

Implementation steps

  1. Choose the starting event and owner

    Decide which application acts when a grocery buyer revises an order. Name the operational owner of the grocery order change and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map original grocery order, revision and item. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Sprouts Farmers Market guide. Preserve the source reference alongside any new destination identifier.

  3. Test failures before launch

    Run the failure cases in the mapping table against realistic grocery order change data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.

  4. Track every document to completion

    Record transport delivery and document validation separately from successful grocery order change processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 876 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic grocery order change data.
  • Each submitted document can be traced through delivery, validation and processing in the receiving system.
  • Your team knows how to investigate and recover a rejected or timed-out grocery order change without processing it twice.

Transaction context

Where 876 Grocery Products Purchase Order Change fits on Sprouts Farmers Market (via SPS Commerce)

Sprouts Farmers Market channels
2 of 2

2 of Sprouts Farmers Market's 2 channels list 876

Trading partners
3

partner references list 876

Channels
4

channel entries list 876

The directory associates SPS Commerce and 876 with 2 channels.

Document structure

X12 876 Grocery Products Purchase Order Change at the element level

The X12 876 reference contains 24 segment entries and 80 data elements; 46 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
24
Data elements
80
Mandatory elements
46
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
G92 3 3
N9 2 1
G61 4 2
NTE 2 1
G23 6 2
N1 4 1
N3 2 1
G68 9 2
G69 1 1
G72 3 2
G73 1 1
Key identifiers in 876
  • Change or Response Type Code
  • Date
  • Purchase Order Number
  • Reference Identification Qualifier
  • Contact Function Code
  • Name
  • Description
  • Terms Type Code
Segment reference — 18 segments 3 loops · X12 876 Grocery Products Purchase Order Change
ISA Interchange Control Header 16 elements

To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header 8 elements

To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header 3 elements

To indicate the start of a transaction set and to assign a control number

G92 Purchase Order Change Type 3 elements

To identify the reason for a change to a previously transmitted purchase order

N9 Extended Reference Information 2 elements

To transmit identifying information as specified by the Reference Identification Qualifier

G61 Contact 4 elements

To identify a person or office to whom communications should be directed

G62 Date/Time 2 elements

To specify pertinent dates and times

NTE Note/Special Instruction 2 elements

To transmit information in a free-form format, if necessary, for comment or special instruction

G66 Transportation Instructions 1 element

To specify transportation instructions relating to the shipment

G23 Terms of Sale 6 elements

To specify the terms of sale

N1 Loop Repeat: 10
N1 Party Identification 4 elements

To identify a party by type of organization, name, and code

G68 Loop Repeat: 9,999
G68 Line Item Detail - Product 8 elements

To specify basic and most frequently used purchase order line item data

G69 Line Item Detail - Description 1 element

To describe an item in free-form format

G70 Line Item Detail - Miscellaneous 3 elements

To provide for miscellaneous information relative to a line item

G72 Loop Repeat: 100
G76 Total Purchase Order 2 elements

To specify summary details of total items shipped in terms of quantity, weight, and volume, and to specify payment method

SE Transaction Set Trailer 2 elements

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

G72 Allowance or Charge 3 elements

To specify allowances, charges, or services

G73 Allowance or Charge Description 1 element

To describe the allowance or charge in free-form format

Related references

876 Grocery Products Purchase Order Change on other Sprouts Farmers Market channels

Compare the listed channel references and confirm their current implementation guides.

Showing 1 of 1 references

Browse the full directory

Sprouts Farmers Market (via SPS Commerce) EDI 876 questions

Common questions about 876 Grocery Products Purchase Order Change on the Sprouts Farmers Market (via SPS Commerce) channel.

What is X12 876 Grocery Products Purchase Order Change used for?

876 is used when a grocery buyer revises an order. It carries information for the grocery order change. Match it to your business system using original grocery order, revision and item.

Is 876 required for Sprouts Farmers Market (via SPS Commerce)?

876 is listed for Sprouts Farmers Market (via SPS Commerce). Confirm the required version and direction for your business unit and account with the partner.

What should I map for X12 876?

Start with original grocery order, revision and item and the target grocery order change. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.

How should I test 876 error handling?

Apply a pack-quantity change to the original order line. Test a late reduction after warehouse picking and require operational review. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does 876 relate to other EDI messages?

X12 875 Grocery Products Purchase Order; X12 880 Grocery Products Invoice are related documents also listed on Sprouts Farmers Market (via SPS Commerce). Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

What is the difference between 876 and 875?

876 is used when a grocery buyer revises an order. 875 is used when a grocery buyer places an order. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

Connect Sprouts Farmers Market EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.