--- title: "EDI 879 Price Information: X12 879 Guide | Stacksync" description: "EDI 879 is the X12 Price Information, used when grocery or product pricing is distributed. See key segments (G91, N1, G62) and mapping checks." canonical: https://www.stacksync.com/edi/x12/879-price-information last_modified: 2026-09-29 --- X12 transaction code # EDI 879 Price Information (X12 879) > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md 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 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) 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. **X12 879 Price Information summary** | | | | --- | --- | | 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](https://www.stacksync.com/edi/x12/888-item-maintenance), [X12 889 Promotion Announcement](https://www.stacksync.com/edi/x12/889-promotion-announcement), [X12 875 Grocery Products Purchase Order](https://www.stacksync.com/edi/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](https://www.stacksync.com/edi), check [pricing](https://www.stacksync.com/pricing) and [security](https://www.stacksync.com/security), or [book a demo](https://www.stacksync.com/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. **Map records and test the business result** | Document or decision | Record and matching IDs | What to test | | --- | --- | --- | | Match the business record | **price information** item, price type and effective period | Define which combination of item, price type and effective period identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the price information** ID assigned by the receiving system and processing result | Keep promotional and regular prices distinct. Test overlapping effective dates and resolve which price is valid for the order date. | | Check the processing result | **Processing status for the price information** Original document reference and matching response | Reconcile the price information 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. - [X12 888 Item Maintenance](https://www.stacksync.com/edi/x12/888-item-maintenance) **item master record:** product attributes are added or maintained. - [X12 889 Promotion Announcement](https://www.stacksync.com/edi/x12/889-promotion-announcement) **promotion record:** a promotion is announced or revised. - [X12 875 Grocery Products Purchase Order](https://www.stacksync.com/edi/x12/875-grocery-products-purchase-order) **grocery purchase order:** a grocery buyer places an order. ### Implementation steps 1. #### 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. 2. #### 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. 3. #### 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. 4. #### 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. ### Related documents and resources - [X12 888 Item Maintenance](https://www.stacksync.com/edi/x12/888-item-maintenance) - [X12 889 Promotion Announcement](https://www.stacksync.com/edi/x12/889-promotion-announcement) - [X12 875 Grocery Products Purchase Order](https://www.stacksync.com/edi/x12/875-grocery-products-purchase-order) - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) **Sources.** Sources reviewed 2026-09-15. - [X12 transaction-set directory](https://x12.org/products/transaction-sets) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) 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 **Segments with elements marked mandatory in this reference** | 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 | Key identifiers in 879 - 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. - [Harbor Foods](https://www.stacksync.com/edi/harbor-wholesale-foods) [Harbor Wholesale Foods (via SPS Commerce)](https://www.stacksync.com/edi/harbor-wholesale-foods/harbor-wholesale-foods-via-sps-commerce/x12-879-price-information) - [Thrive Market](https://www.stacksync.com/edi/thrive-market) [Thrive Market](https://www.stacksync.com/edi/thrive-market/thrive-market/x12-879-price-information) 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 Partner entries with the most listed channels - [Harbor Foods](https://www.stacksync.com/edi/harbor-wholesale-foods) - [Thrive Market](https://www.stacksync.com/edi/thrive-market) 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. [Book an EDI demo](https://www.stacksync.com/book-a-demo) [Explore the EDI platform](https://www.stacksync.com/edi)