--- title: "Shopify NetSuite sync for snack multipacks and cases" description: "Map each Shopify variant to a versioned NetSuite pack recipe so a six-pack order lands as twelve units, not a 24-bar grocery case." canonical: https://www.stacksync.com/blog/shopify-netsuite-sync-for-snack-brands-match-single-units-multipacks-and-cases last_modified: 2026-09-21 --- # Shopify–NetSuite Sync for Snack Brands: Match Single Units, Multipacks, and Cases > 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 Snack brands selling bars, six-packs, and grocery cases need a dated pack recipe between each Shopify variant and its NetSuite line before orders reach ERP processing. Author Ruben Burdin · Founder & CEO Published September 21, 2026 Read time 5 min read DATA ENGINEERING ## The operating decision Snack-brand two-way sync needs an explicit sellable-pack crosswalk. A single bar, a six-pack, and a wholesale case may share a flavor but represent different quantities and prices. Preserve the purchased Shopify variant and map it to the approved NetSuite representation before any order, fulfillment, or finance process uses it. Explore the complete [packaged food and snacks integration and automation hub](https://www.stacksync.com/industry/cpg/packaged-food-snacks) for the systems and processes around this guide. ![Summary card: Shopify NetSuite sync for snack multipacks and cases](https://www.stacksync.com/images/blog-highlights/icp-shopify-netsuite-sync-for-snack-brands-match-single-units-multipacks-and-cases.webp) ## What this looks like in packaged food and snacks A customer orders two mixed-flavor six-packs. The warehouse stores individual bars and the ERP also has a 24-bar grocery case. A text match on the snack name selects the case SKU, turning twelve bars into forty-eight. The correct design preserves the customer’s two purchased packs and applies the approved component recipe for that exact variant revision. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Shopify variant | Ecommerce | Use the stable variant ID and purchased options, not the current display title, to identify the sellable pack. | | Pack recipe | Product operations | Store component SKU, quantity, effective date, and approval for each mixed pack. | | NetSuite line | ERP operations | Choose whether the accepted order carries a pack item or component lines and retain the original channel line. | | Quantity comparison | Fulfillment | Compare physical units as well as financial totals before accepting the mapping. | ![Record ownership diagram: Shopify variant, Pack recipe, NetSuite line](https://www.stacksync.com/images/blog-diagrams/icp-shopify-netsuite-sync-for-snack-brands-match-single-units-multipacks-and-cases.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 List every sellable level Document individual units, multipacks, variety packs, and retailer cases separately. Identify which exist as ERP items and which require an approved component breakdown. A matching flavor is not sufficient identity. 2. 02 Version the recipe Tie the pack definition to the order’s purchase date or explicit revision. Preserve old recipes so an exchange or return can be interpreted after merchandising replaces a flavor in the current bundle. 3. 03 Validate the order transformation Translate one representative order for each pack type. Compare purchased packs, component units, discounts, and the retained channel reference before allowing the mapped result into ERP order processing. 4. 04 Constrain later edits Allow approved descriptive updates without changing historical quantities. A revised bundle definition should affect eligible future orders, while existing orders need an explicit operational decision before substitution. 5. 05 Test two six-packs, one storefront edit, and one missing component Place a test order for two mixed-flavor six-packs in Shopify and open the NetSuite order it creates. The lines should show twelve component units under the recipe revision in force on the order date. If NetSuite shows a 24-bar case, or any quantity other than twelve, stop the rollout and repair the crosswalk before live orders sync. Then change the bundle's flavor in the Shopify storefront and reopen an order placed last month; its NetSuite lines must still cite the earlier recipe. Last, mark one component out of stock and confirm the order pauses for the fulfillment owner instead of substituting a flavor on its own. ![5-step operating sequence: Shopify NetSuite sync for snack multipacks and cases](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-shopify-netsuite-sync-for-snack-brands-match-single-units-multipacks-and-cases.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### One component is unavailable Route substitution or partial fulfillment to the owner; do not quietly alter the purchased recipe. ### Case conversion is missing Hold the affected line and request the approved pack definition. ### SKU is reused after a redesign Use stable IDs and effective dates to separate the old and new product definitions. ## What to verify before expanding - Two six-packs resolve to twelve component units under the approved recipe. - A historical order retains its original recipe after a storefront change. - A missing case conversion blocks the affected physical-quantity comparison even when the order's monetary totals match. - Reusing a SKU after redesign does not change the approved recipe used to explain an earlier order. ## Connect this process to the rest of your operation [Explore Stacksync two-way sync](https://www.stacksync.com/two-way-sync) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real shopify variant example and the exception your team handles most often, for example one component is unavailable. - [Shopify–NetSuite Integration for Packaged Food and Snack Brands](https://www.stacksync.com/use-case/shopify-netsuite-integration-for-packaged-food-and-snack-brands) - [Amazon–NetSuite Integration for Packaged Food Marketplace Operations](https://www.stacksync.com/use-case/amazon-netsuite-integration-for-packaged-food-marketplace-operations) - [Amazon–NetSuite Sync for Packaged Food Brands: Separate FBA and Merchant-Fulfilled Orders](https://www.stacksync.com/blog/amazon-netsuite-sync-for-packaged-food-brands-separate-fba-and-merchant-fulfilled-orders) - [NetSuite–Postgres Sync for Food Brands: Reconcile Co-Packer Receipts and Finished-Goods Records](https://www.stacksync.com/blog/netsuite-postgres-sync-for-food-brands-reconcile-co-packer-receipts-and-finished-goods-records) - [Packaged Food Promotion Workflows: Coordinate Retail Commitments and Ecommerce Launches](https://www.stacksync.com/blog/packaged-food-promotion-workflows-coordinate-retail-commitments-and-ecommerce-launches) - [Resolve Shopify Order Data Inconsistency with Real‑Time Sync](https://www.stacksync.com/blog/resolve-shopify-order-data-inconsistency-realtime-sync) - [EDI 850 855 856 Automation Challenges and Solutions | Stacksync](https://www.stacksync.com/blog/edi-850-855-856-automation) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync two-way sync quick start](https://docs.stacksync.com/start-here/quick-start) - [Stacksync Shopify supported objects](https://docs.stacksync.com/two-way-sync/connectors/shopify) - [Stacksync NetSuite supported objects](https://docs.stacksync.com/two-way-sync/connectors/netsuite) - [Shopify product variant model](https://shopify.dev/docs/api/admin-graphql/latest/objects/productvariant) FAQ ## Frequently asked questions Can one snack SKU serve every pack size? Only when pack quantity is its own validated field instead of a hint inside the product name. Each variant still needs a stable mapping to its unit relationship, and a flavor match alone says nothing about how many bars the customer bought. Name-based matching is the failure mode this design exists to remove. Does the order land in NetSuite as one pack item or as component lines? Your ERP team decides that once per pack type before the sync goes live; the integration does not infer it order by order. A pack item suits brands that cost and ship the bundle as one unit, while component lines suit brands that pick loose bars. In both cases the Shopify line ID and purchased options travel with the NetSuite record, so support can trace a customer question back to the exact variant. Will a Shopify discount change rewrite the total on an accepted NetSuite order? No. NetSuite owns financial totals once it accepts an order, and the sync carries only the fields assigned to each system. A storefront discount arrives as the purchased line values; NetSuite computes its own totals from the mapped lines. When the two disagree, the quantity comparison raises the difference for a person to review. The sync does not push a corrected amount in either direction. About the author Ruben Burdin Founder & CEO Ruben Burdin is the Founder and CEO of Stacksync, the first real-time and two-way sync for enterprise data at scale. Ruben is a Y Combinator alumni with a strong background in software engineering and business. [All posts by Ruben Burdin](https://www.stacksync.com/blog/author/ruben-burdin) 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 - [integration NetSuite and Shopify integration](https://www.stacksync.com/integrations/netsuite-and-shopify) - [connector Shopify integrations](https://www.stacksync.com/connectors/shopify) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [platform Two-way sync](https://www.stacksync.com/two-way-sync) - [platform CRM synchronization](https://www.stacksync.com/crm) - [platform CRM and ERP integration](https://www.stacksync.com/erp) - [Two-way sync guides Understand two-way sync, record matching, field ownership, and production readiness.](https://www.stacksync.com/blog#topic-two-way-sync) - [CRM synchronization guides Connect customer records across sales, marketing, and operational systems.](https://www.stacksync.com/blog#topic-crm-sync) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [Data engineering Shopify–NetSuite Sync for Beverage Brands: Align Bottles, Cases, and Variety Packs 5 min read read](https://www.stacksync.com/blog/shopify-netsuite-sync-for-beverage-brands-align-bottles-cases-and-variety-packs) [Data engineering Shopify–NetSuite Sync for Household Brands: Map Refills, Concentrates, and Multipacks 5 min read read](https://www.stacksync.com/blog/shopify-netsuite-sync-for-household-brands-map-refills-concentrates-and-multipacks) [Data engineering Shopify–NetSuite Sync for Nutrition Brands: Map Flavors, Serving Sizes, and Bundle SKUs 5 min read read](https://www.stacksync.com/blog/shopify-netsuite-sync-for-nutrition-brands-map-flavors-serving-sizes-and-bundle-skus) ## 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/)