--- title: "Retailer EDI 850 and 860 intake for building products" description: "Map retailer 850 orders and 860 changes to NetSuite items and packs, apply each revision once to the accepted order, and respond from that result." canonical: https://www.stacksync.com/blog/building-products-edi-retailer-order-packaging-revisions last_modified: 2026-09-18 --- # Building-products retailer EDI: validate packaging and order revisions before acceptance > 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 A retailer orders cartons while NetSuite counts pieces; this intake keeps the partner line identity, applies each revision once, and separates receipt from acceptance. Author Alexis Favre · Co-Founder & CTO Published September 18, 2026 Read time 4 min read APP TIPS ## The operating decision Building-products retailer EDI intake should map the partner’s item, packaging unit and order-line identity to the manufacturer’s approved product model. Preserve requested delivery details and apply changes against the current accepted order. An 850 purchase order or 860 change can be structurally valid while its product or quantity meaning remains unresolved. Separate transport, business validation and operational approval so the partner response reflects what the manufacturer actually accepted. Explore the complete [building products manufacturing integration and automation hub](https://www.stacksync.com/industry/manufacturing/building-products) for the systems and processes around this guide. ![Summary card: Retailer EDI 850 and 860 intake for building products](https://www.stacksync.com/images/blog-highlights/icp-building-products-edi-retailer-order-packaging-revisions.webp) ## What this looks like in building products manufacturing A manufacturer receives retailer orders for cartons of a building product while its ERP tracks pieces. A later change moves one delivery and increases a quantity after the original order is allocated. If the mapping loses the partner line identifier or assumes every carton contains the current catalog pack, it can update the wrong demand or misstate the requirement. The intake needs the agreed item cross-reference, applicable pack definition and processing history before it can determine whether the request is new, repeated or a consequential revision. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Retailer item reference | Product operations | Map the partner item to the approved manufacturer variant and packaging definition. | | Partner PO line | Customer operations | Preserve customer, PO, line and revision references through the ERP cross-reference. | | Delivery requirement | Logistics | Retain the requested destination and agreed date meaning separately from accepted shipment plans. | | Business acceptance | Order management | Record accepted quantities, unresolved differences and required response state per the partner process. | ![Record ownership diagram: Retailer item reference, Partner PO line, Delivery requirement](https://www.stacksync.com/images/blog-diagrams/icp-building-products-edi-retailer-order-packaging-revisions.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Review the partner’s unit and change conventions Use current implementation examples to establish item references, packaging units and revision behavior. Confirm how cancellations and partial acceptance are represented. Do not extend another retailer’s mapping solely because both use the same transaction-set number. 2. 02 Resolve the product and pack relationship Retain source quantity and unit, then calculate the internal requirement using an approved definition. Check the effective scope when packaging changes. Unknown cross-references should become review cases instead of new catalog entries generated during order intake. 3. 03 Compare the revision with committed work Find the existing accepted order and its allocations or shipments. Identify the exact line changes and route production or logistics impacts to their owners. A requested delivery change is not confirmation that the current load can be rearranged. 4. 04 Apply accepted changes once Use the stable business references and processing ledger to prevent repeated documents from adding demand. Retain the destination order and line identities. Reconcile an uncertain application response before retrying a transactional update. 5. 05 Prepare the partner response from the decision Use the accepted business result and partner rules to generate the required response. Keep transmission retries separate from order application. An operator should be able to see which stage failed without resubmitting the entire order blindly. ![5-step operating sequence: Retailer EDI 850 and 860 intake for building products](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-building-products-edi-retailer-order-packaging-revisions.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### The retailer changes its pack reference Require the reviewed cross-reference and effective definition before accepting affected quantities. ### An order change targets a shipped line Route the remaining commercial or return implications to the designated process rather than automatically reversing shipment history. ### A repeated original order arrives after a revision Recognize its older state and prevent it from restoring superseded quantities or dates. ## What to verify before expanding - Retailer cartons convert to the intended product quantity under the approved definition. - The original partner line remains traceable after ERP mapping. - A late original document cannot undo an accepted later revision. - Response transmission can be retried without repeating the order update. ## Connect this process to the rest of your operation [Explore Stacksync EDI](https://www.stacksync.com/edi) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real retailer item reference example and the exception your team handles most often, for example the retailer changes its pack reference. - [Building-products manufacturers: connect Salesforce dealer quotes to Acumatica orders](https://www.stacksync.com/blog/building-products-salesforce-acumatica-dealer-quote) - [Building products on Shopify: sync NetSuite bundles, pieces and saleable stock](https://www.stacksync.com/blog/building-products-netsuite-shopify-bundle-unit-sync) - [Building-products manufacturing: build a Dynamics-to-SQL Server ready-to-ship view](https://www.stacksync.com/blog/building-products-dynamics-sql-server-ready-to-ship) - [EDI Integration for Ecommerce: Scale Without Chargebacks](https://www.stacksync.com/blog/edi-integration-ecommerce-brands) - [Build a Daily Shopify Delivery-Risk Report in Slack](https://www.stacksync.com/blog/build-a-daily-shopify-delivery-risk-report-in-slack) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Oracle NetSuite: using external IDs](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_156334828635.html) - [X12: supply chain transaction flow](https://x12.org/flow/supply-chain) FAQ ## Frequently asked questions Does EDI onboarding prove every product mapping is correct? No. Validate representative items, packaging changes and revisions under the actual partner agreement. Connection success is only one part of readiness. Can the workflow acknowledge receipt before business review ends? Follow the partner’s agreed protocol and distinguish technical receipt from commercial acceptance in the internal state model. What should a buyer ask to see? Ask for an original order, a packaging ambiguity, a line revision and a replay. Inspect the quantities, review queue, destination references and resulting partner response. About the author Alexis Favre Co-Founder & CTO Alexis Favre is the Co-Founder and CTO of Stacksync (YC W24), the first real-time and two-way sync for enterprise data at scale. Alexis is a Y Combinator alumni with expertise in large scale data engineering. [All posts by Alexis Favre](https://www.stacksync.com/blog/author/alexis-favre) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [connector PostgreSQL integrations](https://www.stacksync.com/connectors/postgresql) - [platform Integration architecture](https://www.stacksync.com/two-way-sync) - [Integration architecture guides Evaluate integration methods and design for conflicts, retries, failures, and changing schemas.](https://www.stacksync.com/blog#topic-integration-architecture) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips Build a Daily Shopify Delivery-Risk Report in Slack 8 min read read](https://www.stacksync.com/blog/build-a-daily-shopify-delivery-risk-report-in-slack) [App tips Building-products damage claims: connect shipment evidence, replacements and credit review 4 min read read](https://www.stacksync.com/blog/building-products-damage-shortage-claim-workflow) [App tips Building-products staged deliveries: coordinate project releases without losing the original order 4 min read read](https://www.stacksync.com/blog/building-products-staged-jobsite-delivery-workflow) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)