X12 transaction code
X12 879 Price Information
X12 879 Price Information: explore its business purpose, mapping identifiers, validation tests and 2 partner references across 2 listed channels.
- Standard
- X12
- Code
- 879
- Partner references
- 2
Implementation guide
X12 879 mapping and validation
X12 879 Price Information is used when grocery or product pricing is distributed. Preserve item, price type and effective period so the price information 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.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | price information item, price type and effective period |
|
| Update the receiving system | Processing the price information ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the price information Original document reference and matching response |
|
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.
- X12 888 Item Maintenance
item master record: product attributes are added or maintained.
- X12 889 Promotion Announcement
promotion record: a promotion is announced or revised.
- X12 875 Grocery Products Purchase Order
grocery purchase order: a grocery buyer places an order.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when grocery or product pricing is distributed. Name the operational owner of the price information and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map item, price type and effective period. 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.
-
Test failures before launch
Run the failure cases in the mapping table against realistic price information data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful price information processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 879 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic price information 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 price information without processing it twice.
Document structure
X12 879 Price Information at the element level
The X12 879 reference contains 20 segment entries and 67 data elements; 38 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 20
- Data elements
- 67
- Mandatory elements
- 38
| Segment | Elements | Mandatory |
|---|---|---|
| G91 | 1 | 1 |
| N1 | 4 | 1 |
| G61 | 4 | 2 |
| NTE | 2 | 1 |
| G36 | 2 | 2 |
| G69 | 1 | 1 |
| G43 | 3 | 1 |
| G46 | 5 | 2 |
| G40 | 5 | 1 |
- Change Type Code
- Entity Identifier Code
- Contact Function Code
- Name
- Description
- Price List Number
- Date
- Free-form Description
Find your trading partner for X12 879
2 partners, 2 channels. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 879 Price Information appears in this catalog
The largest groups of classified 879 catalog entries are in grocery & food.
By industry
- grocery & food 2 channels
By network
- SPS Commerce 1 channel
FAQ
X12 879 questions
What is X12 879 Price Information used for?
879 is used when grocery or product pricing is distributed. It carries information for the price information. Match it to your business system using item, price type and effective period.
Which partners list X12 879?
The directory on this page links 2 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 879?
Start with item, price type and effective period and the target price information. 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 879 error handling?
Keep promotional and regular prices distinct. Test overlapping effective dates and resolve which price is valid for the order date. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 879 relate to other EDI messages?
X12 888 Item Maintenance; X12 889 Promotion Announcement; X12 875 Grocery Products Purchase Order 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 879 and 888?
879 is used when grocery or product pricing is distributed. 888 is used when product attributes are added or maintained. 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.
