Skip to content

Shopify–NetSuite Sync for Household Brands: Map Refills, Concentrates, and Multipacks

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
Read time
5 min read
Shopify–NetSuite Sync for Household Brands: Map Refills, Concentrates, and Multipacks
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 for the systems and processes around this guide.

Summary card: Shopify NetSuite sync for household refills and multipacks

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

RecordOwnerOperating rule
Shopify variantEcommercePreserve the actual purchased variant and pack count rather than deriving quantity from advertised yield.
ERP itemProduct operationsOwn the accepted refill, concentrate, or ready-to-use product identity.
Starter-kit recipeProduct teamVersion the physical components and quantities included in each kit.
Operational quantityFulfillmentReconcile actual packages and components while keeping usage claims outside stock calculations.
Record ownership diagram: Shopify variant, ERP item, Starter-kit recipe
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
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.
Book a demo for household consumables integration and automation
Book a demo for household consumables integration and automation

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
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

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.

Coworkers laughing in front of a laptop in a casual office setting

You just read how it should work.
See it run on your own data.