Skip to content
X12 EDI

Associated Wholesale Grocers (AWG) X12 875 Grocery Products Purchase Order

Plan X12 875 Grocery Products Purchase Order for Associated Wholesale Grocers (AWG) / Associated Wholesale Grocers (Edict Systems). Connect document identifiers to your business records, test exception handling and track each exchange to completion.

Segments
18
Loops
3
X12 875
Partner references ↗

Implementation guide

Associated Wholesale Grocers (AWG) / Associated Wholesale Grocers (Edict Systems): 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.

This document is listed for Associated Wholesale Grocers (AWG) / Associated Wholesale Grocers (Edict Systems). 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 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.

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 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 Associated Wholesale Grocers (AWG) 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.

Transaction context

Where 875 Grocery Products Purchase Order fits on Associated Wholesale Grocers (Edict Systems)

On Associated Wholesale Grocers (Edict Systems), the X12 875 Grocery Products Purchase Order can precede the 880 Grocery Products Invoice in an example Grocery replenishment cycle. Confirm the required sequence for your trading agreement.

Associated Wholesale Grocers (AWG) channels
1 of 1

1 of Associated Wholesale Grocers (AWG)'s 1 channel list 875

Trading partners
34

partner references list 875

Channels
38

channel entries list 875

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
Segment reference — 18 segments 3 loops · X12 875 Grocery Products Purchase Order
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 2 elements

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

G50 Purchase Order Identification 3 elements

To transmit identifying dates and numbers for this transaction set

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 2 elements

To specify transportation instructions relating to the shipment

N1 Loop Repeat: 10
N1 Party Identification 4 elements

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

N3 Party Location 2 elements

To specify the location of the named party

N4 Geographic Location 3 elements

To specify the geographic place of the named party

G72 Loop Repeat: 100
G72 Allowance or Charge 3 elements

To specify allowances, charges, or services

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 1 element

To provide for miscellaneous information relative to a line item

G76 Total Purchase Order 7 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)

Related references

Other transactions in Associated Wholesale Grocers (Edict Systems)

Other EDI documents listed on this channel.

Associated Wholesale Grocers (AWG) / Associated Wholesale Grocers (Edict Systems) EDI 875 questions

Common questions about 875 Grocery Products Purchase Order on the Associated Wholesale Grocers (Edict Systems) channel.

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.

Is 875 required for Associated Wholesale Grocers (AWG) / Associated Wholesale Grocers (Edict Systems)?

875 is listed for Associated Wholesale Grocers (AWG) / Associated Wholesale Grocers (Edict Systems). Confirm the required version and direction for your business unit and account with the partner.

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 is a related document also listed on Associated Wholesale Grocers (Edict Systems). 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 Associated Wholesale Grocers (AWG) 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.