X12 transaction code
EDI 879 Price Information (X12 879)
EDI 879 is the X12 Price Information transaction set, used when grocery or product pricing is distributed. A supplier, manufacturer, or broker sends the 879 to a retailer, distributor, or buying organization, which confirms receipt with a 997 Functional Acknowledgment.
- Standard
- X12
- Code
- 879
- Partner references
- 2
At a glance
EDI 879 at a glance
What the 879 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 879 Price Information |
|---|---|
| Business record | Price information |
| Who sends it to whom | A supplier, manufacturer, or broker sends the 879 to a retailer, distributor, or buying organization, which confirms receipt with a 997 Functional Acknowledgment. |
| When it is sent | A supplier creates a new item or approves a cost change in its ERP and must publish the price and its effective date to buyers before orders and invoices reference it. |
| Match on | Item, price type and effective period |
| Partner references | 2 trading partners in this directory |
| Related documents | X12 888 Item Maintenance, X12 889 Promotion Announcement, X12 875 Grocery Products Purchase Order |
Key segments in an EDI 879
The business segments that appear in at least half of the 2 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.
| Segment | Name | Purpose | Partner references |
|---|---|---|---|
| G91 | Price Change Status | To enable the supplier/broker to change pricing information. | 2 of 2 |
| N1 | Party Identification | To identify a party by type of organization, name, and code. | 2 of 2 |
| G62 | Date/Time | To specify pertinent dates and times. | 2 of 2 |
| G28 | Line Item Numbers | To provide basic product identification information. | 2 of 2 |
| G43 | Promotion/Price List Area | To specify the geographic area in which a promotion or price is in effect. | 2 of 2 |
| G40 | Bracket Price | To provide a vendor's pricing structure associated with a specific line item. | 2 of 2 |
| G61 | Contact | To identify a person or office to whom communications should be directed. | 1 of 2 |
| NTE | Note/Special Instruction | To transmit information in a free-form format, if necessary, for comment or special instruction. | 1 of 2 |
| G36 | Price List Reference | To provide price list references and descriptions. | 1 of 2 |
| G20 | Item Packing Detail | To specify packing details of the items shipped. | 1 of 2 |
Stacksync connects EDI documents such as the X12 879 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.
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
EDI 879 questions
What is an EDI 879?
EDI 879 is the X12 Price Information transaction set. Trading partners use it when grocery or product pricing is distributed. It carries the data for the price information, and your system matches it on item, price type and effective period.
Who sends an EDI 879 and who receives it?
A supplier, manufacturer, or broker sends the 879 to a retailer, distributor, or buying organization, which confirms receipt with a 997 Functional Acknowledgment. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 879 sent?
A supplier creates a new item or approves a cost change in its ERP and must publish the price and its effective date to buyers before orders and invoices reference it. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 879?
Across 2 partner document references listed here, the business segments that appear most often include G91 (Price Change Status), N1 (Party Identification), G62 (Date/Time), G28 (Line Item Numbers), G43 (Promotion/Price List Area), G40 (Bracket Price). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 879 and EDI 888?
The 879 carries the price information and is used when grocery or product pricing is distributed. The 888 carries the item master record and is used when product attributes are added or maintained.
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.
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.
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.
