--- title: "Retail EDI item and pack validation for supplement brands" description: "Validate retailer item numbers against the approved NetSuite package and case count before an Orderful order is accepted or a shipment document is built." canonical: https://www.stacksync.com/blog/edi-for-supplement-brands-entering-retail-validate-item-numbers-and-pack-configurations last_modified: 2026-09-21 --- # EDI for Supplement Brands Entering Retail: Validate Item Numbers and Pack Configurations > 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 30-serving tub ordered in cases of six can pass Orderful validation and still ship the 20-serving tub; the fix is an approved item crosswalk, not a name match. Author Alexis Favre · Co-Founder & CTO Published September 21, 2026 Read time 4 min read APP TIPS ## The operating decision Retail EDI for supplement brands depends on an approved crosswalk between retailer item numbers and the exact nutrition product, package, and case configuration. Validate that relationship before accepting an order or building a shipment document. A matching flavor or serving count does not prove the retailer ordered the same sellable item. Explore the complete [nutrition and supplements integration and automation hub](https://www.stacksync.com/industry/cpg/nutrition-supplements) for the systems and processes around this guide. ![Summary card: Retail EDI item and pack validation for supplement brands](https://www.stacksync.com/images/blog-highlights/icp-edi-for-supplement-brands-entering-retail-validate-item-numbers-and-pack-configurations.webp) ## What this looks like in nutrition and supplements A retailer lists a 30-serving tub under its own item number and orders cases of six. The brand also sells a 20-serving tub online. If the mapping uses the shortened product name, the EDI order can pass technical validation while asking the warehouse to ship the wrong package. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Retailer item | Product operations | Map the partner item number to the approved formula or product, package, and case configuration. | | Order line | Retail operations | Preserve retailer line reference, requested quantity, unit, location, and dates. | | Shipment evidence | Warehouse | Use the actual shipped product and approved pack representation. | | Partner mapping version | Integration owner | Record the effective mapping and partner validation results for the tested configuration. | ![Record ownership diagram: Retailer item, Order line, Shipment evidence](https://www.stacksync.com/images/blog-diagrams/icp-edi-for-supplement-brands-entering-retail-validate-item-numbers-and-pack-configurations.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Approve the item crosswalk Review retailer item number, internal SKU, package size, and case count together. Keep online bundles and wholesale cases distinct even when they share the same consumer-facing name. 2. 02 Validate incoming quantities Check units and pack multiples under the retailer’s rules. Route unknown or inconsistent configurations to the product owner rather than rounding into an apparently valid order. 3. 03 Build from accepted records Create acknowledgments from the approved order decision and shipment documents from warehouse evidence. Preserve the partner line references so partial shipments remain explainable. 4. 04 Test commercial edge cases Include a discontinued package, changed case count, and split shipment in partner testing. Technical document acceptance should accompany a human review of product and quantity meaning. 5. 05 Reuse a retailer item number in the Orderful test stream first In the Orderful test stream, send a purchase order that uses a retailer item number the partner previously assigned to the 20-serving tub and now assigns to the 30-serving tub. In NetSuite, the new order should resolve to the 30-serving package under the current mapping version, while a historical order for the same number still shows the 20-serving tub. Ship the order short and confirm the shipment document carries the retailer's original line reference and the quantity that left the warehouse, not the ordered quantity. Stop the rollout if either order resolves to the wrong tub, if history was rewritten, or if the document reports the ordered count. ![5-step operating sequence: Retail EDI item and pack validation for supplement brands](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-edi-for-supplement-brands-entering-retail-validate-item-numbers-and-pack-configurations.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Retailer reuses an item number Confirm the effective product mapping and preserve historical order interpretation. ### Case count changes Version the pack definition and review open orders before applying it. ### Substitute product is proposed Obtain the required commercial approval and partner-compliant representation before shipping. ## What to verify before expanding - The retailer item resolves to the exact approved package. - Shipment documents retain the original partner line and actual shipped quantity. - A reused retailer item number resolves by the applicable product-mapping version without rewriting historical orders. - A changed case count is reviewed against open purchase orders before the new conversion is accepted for shipment documents. ## 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 example and the exception your team handles most often, for example retailer reuses an item number. - [Shopify–NetSuite Sync for Nutrition Brands: Map Flavors, Serving Sizes, and Bundle SKUs](https://www.stacksync.com/blog/shopify-netsuite-sync-for-nutrition-brands-map-flavors-serving-sizes-and-bundle-skus) - [Amazon–NetSuite Sync for Supplement Brands: Match Seller SKUs, ASINs, and Order Lines](https://www.stacksync.com/blog/amazon-netsuite-sync-for-supplement-brands-match-seller-skus-asins-and-order-lines) - [HubSpot–NetSuite Sync for Nutrition Brands Selling to Practitioners and Retailers](https://www.stacksync.com/blog/hubspot-netsuite-sync-for-nutrition-brands-selling-to-practitioners-and-retailers) - [NetSuite AI Agents FAQ: Smarter Automation](https://www.stacksync.com/blog/netsuite-ai-agents-faq-smarter-automation-2025) - [Syncing Custom Fields From a Legacy NetSuite to HubSpot](https://www.stacksync.com/blog/sync-netsuite-custom-fields-to-hubspot) 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 Does a valid EDI file establish product compliance? No. It establishes only the applicable technical validation result. Product approval, labeling, quality, and commercial acceptance remain separate responsibilities. Is the Orderful connection a two-way sync with NetSuite? No. Orderful moves partner-addressed documents in and out; NetSuite remains where the order, item, and shipment records live and are decided. Acknowledgments and shipment notices are built from NetSuite records after a person or a validation rule has accepted them, and nothing in the EDI stream writes back to the item master. Treat the pack crosswalk as NetSuite data that EDI reads, never as something the retailer's document can change. Should online bundle SKUs be in the retailer crosswalk at all? Leave them out. The crosswalk should contain only the packages the retailer has agreed to buy, each with its case count, so an online bundle cannot be selected by accident when a partner item number is ambiguous. Add a package to the crosswalk only when the retailer's item setup confirms it, and record the date so an order from before that date is not re-mapped. 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 Supplement Return Workflows: Connect Zendesk Requests to Warehouse and Finance Review 5 min read read](https://www.stacksync.com/blog/supplement-return-workflows-connect-zendesk-requests-to-warehouse-and-finance-review) [App tips Wholesale Sample-to-Order Workflows for Nutrition Brands Using HubSpot and NetSuite 5 min read read](https://www.stacksync.com/blog/wholesale-sample-to-order-workflows-for-nutrition-brands-using-hubspot-and-netsuite) [App tips AI Agents for Nutrition Brands: Assemble Product and Batch-Document Requests 5 min read read](https://www.stacksync.com/blog/ai-agents-for-nutrition-brands-assemble-product-and-batch-document-requests) ## 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/)