Skip to content

X12 transaction code

X12 875 Grocery Products Purchase Order

X12 875 Grocery Products Purchase Order: explore its business purpose, mapping identifiers, validation tests and 34 partner references across 38 listed channels.

Standard
X12
Code
875
Partner references
34

Implementation guide

X12 875 mapping and validation

X12 875 Grocery Products Purchase Order is used when a grocery buyer places an order. Preserve purchase order, item and pack or unit basis so the grocery purchase order in your business system stays connected to the original document.

Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.

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

purchase order, item and pack or unit basis

  • Define which combination of purchase order, item and pack or unit basis identifies one business record, its lines and any later revision.
Update the receiving system Processing the grocery purchase order

ID assigned by the receiving system and processing result

  • Test catch-weight or variable-quantity items using the units agreed in the partner guide.
  • Separate case quantities from each quantities during sales-order creation.
Check the processing result Processing status for the grocery purchase order

Original document reference and matching response

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

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 places an order. Name the operational owner of the grocery purchase order and the team that resolves rejected or ambiguous messages.

  2. Keep record IDs connected

    Map purchase order, item and pack or unit basis. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner 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 purchase order 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 purchase order processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

  • An approved 875 sample and the agreed version and partner guide are available.
  • The mapping tests pass with realistic grocery purchase order 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 purchase order without processing it twice.

Document structure

X12 875 Grocery Products Purchase Order at the element level

The X12 875 reference contains 36 segment entries and 210 data elements; 60 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments
36
Data elements
210
Mandatory elements
60
Segments with elements marked mandatory in this reference
Segment Elements Mandatory
G50 5 3
N9 5 1
G61 5 2
NTE 2 1
G23 13 2
N1 4 1
N2 2 1
N3 2 1
G72 11 2
G73 1 1
G68 15 2
G69 1 1
Key identifiers in 875
  • Order Status Code
  • Date
  • Purchase Order Number
  • Reference Identification Qualifier
  • Contact Function Code
  • Name
  • Description
  • Terms Type Code

Find your trading partner for X12 875

34 partners, 38 channels. Choose a channel to inspect its listed document reference and implementation context.

Catalog breakdown

Where X12 875 Grocery Products Purchase Order appears in this catalog

The largest groups of classified 875 catalog entries are in grocery & food and consumer goods.

By industry

  • grocery & food 37 channels
  • consumer goods 1 channel

By network

  • Edict Systems 5 channels
  • SPS Commerce 3 channels

FAQ

X12 875 questions

What is X12 875 Grocery Products Purchase Order used for?

875 is used when a grocery buyer places an order. It carries information for the grocery purchase order. Match it to your business system using purchase order, item and pack or unit basis.

Which partners list X12 875?

The directory on this page links 34 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.

What should I map for X12 875?

Start with purchase order, item and pack or unit basis and the target grocery purchase order. 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 875 error handling?

Test catch-weight or variable-quantity items using the units agreed in the partner guide. Separate case quantities from each quantities during sales-order creation. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

How does 875 relate to other EDI messages?

X12 880 Grocery Products Invoice; X12 876 Grocery Products Purchase Order Change are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

What is the difference between 875 and 880?

875 is used when a grocery buyer places an order. 880 is used when grocery goods are ready for detail billing. Each message represents a different business step. Keep their record references connected and track the processing result for each message.

Connect 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.