--- title: "Orderful NetSuite EDI for household distributor case orders" description: "Orderful purchase orders map to NetSuite items and case definitions per distributor, so acknowledgments, ship notices, and invoices match what shipped." canonical: https://www.stacksync.com/blog/household-products-edi-connect-distributor-purchase-orders-to-case-level-shipments last_modified: 2026-09-21 --- # Household Products EDI: Connect Distributor Purchase Orders to Case-Level Shipments > 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 Distributor item numbers resolve to the exact NetSuite case configuration, so EDI acknowledgments, ship notices, and invoices describe the pouches that shipped. Author Alexis Favre · Co-Founder & CTO Published September 21, 2026 Read time 5 min read APP TIPS ## The operating decision Household-product distributor EDI should preserve the ordered sellable unit and approved case definition through shipment and invoice. Map customer item numbers and locations before accepting orders, then build outbound documents from the actual operational records. Refill, concentrate, and multipack identities must remain explicit even when descriptions look similar. Explore the complete [household consumables integration and automation hub](https://www.stacksync.com/industry/cpg/household-consumables) for the systems and processes around this guide. ![Summary card: Orderful NetSuite EDI for household distributor case orders](https://www.stacksync.com/images/blog-highlights/icp-household-products-edi-connect-distributor-purchase-orders-to-case-level-shipments.webp) ## What this looks like in household consumables A distributor orders cases of refill pouches using its internal item number. The brand also sells multipacks online and stocks individual pouches. A technically valid EDI mapping that selects the online pack can produce the wrong physical quantity while preserving the order’s apparent product family. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Distributor item | Product operations | Map the partner code to the exact product and case configuration. | | Purchase-order line | Order operations | Preserve partner line, quantity, unit, destination, and commercial reference. | | Actual shipment | Warehouse | Own the physical product, case contents, and shipment-specific quantities. | | EDI status | Integration operations | Track document identity, validation, transmission, and partner acknowledgment separately. | ![Record ownership diagram: Distributor item, Purchase-order line, Actual shipment](https://www.stacksync.com/images/blog-diagrams/icp-household-products-edi-connect-distributor-purchase-orders-to-case-level-shipments.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Confirm the partner crosswalk Review each distributor item number, internal SKU, and case definition. Retain customer-specific configurations rather than applying the ecommerce pack to every channel. 2. 02 Validate order meaning Check product, unit, quantity, and ship-to before accepting the ERP order. Hold unknown codes and inconsistent case quantities for the responsible owner. 3. 03 Construct each document correctly Use accepted order decisions for acknowledgments, actual shipment evidence for notices, and finance records for invoices. Preserve partner references across the business chain. 4. 04 Reconcile partial delivery Keep unshipped balances and later shipments visible. A delivered EDI file should not close an order whose physical remainder is still outstanding. 5. 05 Send one distributor PO through Orderful and audit every quantity Run a distributor test purchase order through Orderful for its refill-pouch item number. In NetSuite, the order line should point to the distributor's case item, not the online multipack, in the case quantity the partner ordered. Ship part of the order and check the outbound ship notice: its quantity must equal the shipped cases, and the open balance in NetSuite must equal the remainder. Then have the distributor announce a new case count. Open orders under the old definition should be flagged for review, not restated. A line mapped to the multipack, a notice reporting the full order, or an old order silently reinterpreted stops the rollout. ![5-step operating sequence: Orderful NetSuite EDI for household distributor case orders](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-household-products-edi-connect-distributor-purchase-orders-to-case-level-shipments.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Distributor changes its case definition Version the mapping and review open orders before applying the new factor. ### Shipment includes mixed cases Use the required item-level contents and partner hierarchy. ### Document repeats after a retry Preserve the business identity and avoid a second apparent order or shipment. ## What to verify before expanding - Distributor cases cannot silently inherit an ecommerce multipack definition. - Outbound quantities match actual shipment evidence and remaining order balance. - A distributor case-definition change preserves earlier order interpretation and flags open orders that require mapping review. - Mixed cases retain item-level contents in the partner hierarchy instead of being represented by one average case factor. ## 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 distributor item example and the exception your team handles most often, for example distributor changes its case definition. - [Shopify–NetSuite Sync for Household Brands: Map Refills, Concentrates, and Multipacks](https://www.stacksync.com/blog/shopify-netsuite-sync-for-household-brands-map-refills-concentrates-and-multipacks) - [Amazon–NetSuite Sync for Household Consumables: Reconcile Marketplace Order Quantities](https://www.stacksync.com/blog/amazon-netsuite-sync-for-household-consumables-reconcile-marketplace-order-quantities) - [Salesforce–NetSuite Sync for Household Brands Serving Janitorial Distributors](https://www.stacksync.com/blog/salesforce-netsuite-sync-for-household-brands-serving-janitorial-distributors) - [Common EDI Errors in Supply Chain Integrations and How to Fix Them](https://www.stacksync.com/blog/common-edi-errors-supply-chain) - [How to Sync Zendesk with Salesforce: A Two-Way Integration Guide](https://www.stacksync.com/blog/how-to-sync-zendesk-with-salesforce) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Orderful transaction model](https://docs.orderful.com/reference/orderful-transactions) - [Stacksync NetSuite supported objects](https://docs.stacksync.com/two-way-sync/connectors/netsuite) FAQ ## Frequently asked questions Is EDI validation enough to catch a wrong refill item? Not necessarily. A document can be technically valid while pointing to the wrong business item. Product and pack checks must be part of the operational release gate. Orderful checks that the document follows the partner's specification; it has no view of whether the item number maps to the pouch case or the online multipack. That check belongs to the crosswalk step in NetSuite before the order is accepted. Are the Orderful documents part of the NetSuite two-way sync? No. EDI through Orderful is document transport between you and the distributor: a purchase order arrives, and an acknowledgment, ship notice, and invoice go out. Two-way sync is a different product for keeping shared records aligned between applications you own. In this setup NetSuite is the system of record, Orderful carries documents to and from the partner, and the mapping between them is a configured translation, not a live record sync. If a distributor sends an item number you have never mapped, what stops the order? The crosswalk check holds the line before any NetSuite order is created, and the acknowledgment going back to the distributor should not report that line as accepted until product operations adds the mapping. Integration operations sees the held document with its partner reference and validation state; product operations sees the unknown code with the order it came from. Nothing is guessed from the description text, and the remaining lines proceed only if your policy allows partial acceptance. 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 Orderful integrations](https://www.stacksync.com/connectors/orderful) - [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 Household Product Replenishment Workflows: Prevent Duplicate Wholesale Orders 5 min read read](https://www.stacksync.com/blog/household-product-replenishment-workflows-prevent-duplicate-wholesale-orders) [App tips Household Product Return Workflows: Route Damaged and Unsellable Goods for Review 5 min read read](https://www.stacksync.com/blog/household-product-return-workflows-route-damaged-and-unsellable-goods-for-review) [App tips AI Agents for Household Brands: Investigate Refill and Case-Quantity Disputes 5 min read read](https://www.stacksync.com/blog/ai-agents-for-household-brands-investigate-refill-and-case-quantity-disputes) ## 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/)