--- title: "Shopify NetSuite sync for household refills and multipacks" description: "Map each Shopify variant to the NetSuite refill, concentrate, or multipack item so orders and kits carry physical pack counts instead of advertised yield." canonical: https://www.stacksync.com/blog/shopify-netsuite-sync-for-household-brands-map-refills-concentrates-and-multipacks last_modified: 2026-09-21 --- # Shopify–NetSuite Sync for Household Brands: Map Refills, Concentrates, and Multipacks > 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 Two refills ordered on Shopify stay two concentrate packages in NetSuite, and a starter kit keeps its approved bottle and refill components through fulfillment and returns. Author Ruben Burdin · Founder & CEO Published September 21, 2026 Read time 5 min read DATA ENGINEERING ## The operating decision Household-brand two-way sync should preserve the difference between a refill, concentrate, ready-to-use product, and multipack. Map each Shopify variant to an approved ERP sellable definition. Similar intended use or advertised yield does not establish product equivalence, so keep actual package quantities separate from marketing claims about the amount a concentrate can produce. 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: Shopify NetSuite sync for household refills and multipacks](https://www.stacksync.com/images/blog-highlights/icp-shopify-netsuite-sync-for-household-brands-map-refills-concentrates-and-multipacks.webp) ## What this looks like in household consumables A cleaning brand sells a spray bottle, a concentrate refill, and a starter kit containing both. The storefront emphasizes the finished-use yield, while NetSuite records physical containers. An order for two refills must remain two concentrate packages rather than becoming the number of spray bottles suggested by the marketing description. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Shopify variant | Ecommerce | Preserve the actual purchased variant and pack count rather than deriving quantity from advertised yield. | | ERP item | Product operations | Own the accepted refill, concentrate, or ready-to-use product identity. | | Starter-kit recipe | Product team | Version the physical components and quantities included in each kit. | | Operational quantity | Fulfillment | Reconcile actual packages and components while keeping usage claims outside stock calculations. | ![Record ownership diagram: Shopify variant, ERP item, Starter-kit recipe](https://www.stacksync.com/images/blog-diagrams/icp-shopify-netsuite-sync-for-household-brands-map-refills-concentrates-and-multipacks.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 List physical products Document each sold package and its ERP relationship. Treat concentrate and ready-to-use goods as different products even when they share a scent or product-family label. 2. 02 Separate yield from quantity Retain marketing yield only in its proper descriptive context. Use approved physical units and pack counts for order, inventory, shipment, and return comparisons. 3. 03 Validate kit transformations Test orders containing refills, bottles, and starter kits together. Confirm that the component breakdown preserves the original purchased lines and does not double-count a bottle included in a kit. 4. 04 Govern product changes Version package and kit changes while preserving past purchases. A revised concentration or container size needs product-owner review rather than a silent update to every historical mapping. 5. 05 Run a refill and starter-kit test order through to NetSuite Place a Shopify test order for two concentrate refills and one starter kit, then open the sales order it creates in NetSuite. The refill line should read two of the refill item, with no quantity inferred from how many bottles the concentrate could fill. The kit line should resolve to its approved recipe, one bottle and one refill, without a second bottle appearing because bottles are also sold on their own. Next, change only the yield claim in the Shopify product description. If any NetSuite line quantity moves, or the item record changes before product operations confirms the physical product is the same, stop the rollout and correct the mapping. ![5-step operating sequence: Shopify NetSuite sync for household refills and multipacks](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-shopify-netsuite-sync-for-household-brands-map-refills-concentrates-and-multipacks.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Yield claim changes Do not alter physical order quantities; ask product operations whether the actual item changed. ### Refill packaging is redesigned Review stable item identity and effective mapping before accepting new orders. ### Kit component is replaced Require the approved recipe or substitution decision and preserve the original purchase. ## What to verify before expanding - A refill order maps to physical refill packages rather than implied finished-use volume. - Starter kits preserve their approved component counts. - Changing an advertised dilution or yield claim leaves the physical order and inventory quantities unchanged. - A starter-kit component substitution preserves the purchased recipe and records the separate approved fulfillment decision. ## 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 yield claim changes. - [Shopify–NetSuite Integration for Household Consumable Brands](https://www.stacksync.com/use-case/shopify-netsuite-integration-for-household-consumable-brands) - [Amazon–NetSuite Integration for Household Marketplace Quantities](https://www.stacksync.com/use-case/amazon-netsuite-integration-for-household-marketplace-quantities) - [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) - [Household Product Replenishment Workflows: Prevent Duplicate Wholesale Orders](https://www.stacksync.com/blog/household-product-replenishment-workflows-prevent-duplicate-wholesale-orders) - [Beat Shopify API Rate Limits with Stacksync Real‑Time Sync](https://www.stacksync.com/blog/beat-shopify-api-rate-limits-stacksync-realtime-sync) - [Real-Time Data Integration for Accurate Logistics Ops](https://www.stacksync.com/blog/real-time-data-integration-accurate-logistics-ops) 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 equivalent cleaning yield determine the ERP item? No. Fulfillment and returns require the actual purchased product and package. Yield is not a substitute for stable product identity. Two concentrates that promise the same number of finished bottles can differ in container size, formula, and price, and the warehouse picks a container, not a promise. Does syncing Shopify products into NetSuite also move inventory levels or fulfillments? No. The sync carries product variants, orders, and customers between the two systems, and each field has one owner: NetSuite for item identity and pack count, Shopify for the storefront title and description. Inventory levels and fulfillment status are separate Shopify objects with their own write permission, so decide whether NetSuite should write them at all before the pilot, and keep them out of scope until that decision is signed off. Which product data has to be clean before the first sync run? Every Shopify variant needs a SKU that resolves to exactly one NetSuite item, and every kit needs an approved recipe with an effective date before its first order flows. Variants with no SKU, or with a SKU that two items share, should sit outside the initial scope on a list the product owner works through. Keep marketing yield text in the description field only, never in a field mapped to quantity or unit. 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 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) [Data engineering Shopify–NetSuite Sync for Personal Care Brands: Align Shades, Sizes, and Gift Sets 5 min read read](https://www.stacksync.com/blog/shopify-netsuite-sync-for-personal-care-brands-align-shades-sizes-and-gift-sets) ## 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/)