---
title: "Shopify NetSuite sync for nutrition flavors and bundle SKUs"
description: "Map Shopify variant IDs to approved NetSuite items so flavor, tub size, serving count and bundle revision stay distinct through orders and returns."
canonical: https://www.stacksync.com/blog/shopify-netsuite-sync-for-nutrition-brands-map-flavors-serving-sizes-and-bundle-skus
last_modified: 2026-09-21
---

# Shopify–NetSuite Sync for Nutrition Brands: Map Flavors, Serving Sizes, and Bundle SKUs

> 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

Why a title match picks the wrong tub, and how an approved variant-to-item crosswalk keeps flavors, sizes, and kit revisions distinct in NetSuite.

Author

Ruben Burdin · Founder & CEO

Published

September 21, 2026

Read time

5 min read

DATA ENGINEERING

## The operating decision

Nutrition-brand two-way sync should identify the exact sold variant: flavor, package size, serving count, and bundle revision. Map Shopify variant IDs to approved NetSuite item representations, retaining those distinctions even when marketing names look similar. Product identity must be correct before an order or return can be reconciled.

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: Shopify NetSuite sync for nutrition flavors and bundle SKUs](https://www.stacksync.com/images/blog-highlights/icp-shopify-netsuite-sync-for-nutrition-brands-map-flavors-serving-sizes-and-bundle-skus.webp)

## What this looks like in nutrition and supplements

A store sells vanilla powder in two tub sizes and a starter kit with a shaker. The ERP uses different items for each tub and component. A title match sees only vanilla protein and selects the smaller tub. The error changes both physical fulfillment and the meaning of a later customer return.

## Records, ownership, and update rules

| Record | Owner | Operating rule |
| --- | --- | --- |
| Shopify variant | Ecommerce | Preserve variant ID, selected options, and original order-line description as purchase evidence. |
| ERP item | Product operations | Own the accepted item relationship and package definition used by order processing. |
| Bundle recipe | Product operations | Version component items and quantities independently from the storefront marketing name. |
| Order comparison | Operations | Compare the sold package and component quantities before accepting the ERP representation. |

![Record ownership diagram: Shopify variant, ERP item, Bundle recipe](https://www.stacksync.com/images/blog-diagrams/icp-shopify-netsuite-sync-for-nutrition-brands-map-flavors-serving-sizes-and-bundle-skus.webp)

*Define the record owner and the rule before enabling updates.*

## Work through the process

1. 01

   Enumerate the variants

   List every flavor and size combination actually sold, including discontinued variants needed for historical returns. Distinguish net package quantity from marketing serving count; neither should be inferred from a shortened title.
2. 02

   Approve the crosswalk

   Map each stable Shopify variant to the correct ERP item or component recipe. Have product operations review confusing combinations such as the same flavor in two container sizes.
3. 03

   Test mixed orders

   Use an order containing a small tub, large tub, and kit. Confirm that each retains its identity and that the kit does not become a single unit of an arbitrary component.
4. 04

   Preserve history

   When formulas, package sizes, or bundle contents change, version the affected mapping. Existing orders must remain interpretable under the product definition that was actually sold.
5. 05

   Rename a flavor in Shopify and check the NetSuite item holds

   Take the two vanilla tubs and rename the flavor label on the smaller one in Shopify. Open the NetSuite sales order for a pre-rename purchase of that tub and confirm it still points to the same item, with package size unchanged. Then look up a return against an older starter-kit order and confirm NetSuite resolves it to the kit revision that shipped, not the current recipe. Stop the rollout if the renamed variant now lands on the larger tub's item, if the two sizes have merged into one NetSuite item, or if the return references today's kit contents. Any of those means the crosswalk matched on text.

![5-step operating sequence: Shopify NetSuite sync for nutrition flavors and bundle SKUs](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-shopify-netsuite-sync-for-nutrition-brands-map-flavors-serving-sizes-and-bundle-skus.webp)

*Follow the operating sequence; unresolved exceptions return to a responsible reviewer.*

## Handle the exceptions explicitly

### Flavor label is renamed

Retain the stable variant relationship and review whether the actual product changed.

### Serving count differs across documents

Ask product operations for the approved definition rather than rewriting the ERP item from marketing text.

### Kit component is substituted

Require the approved fulfillment decision and preserve the original purchased configuration.

## What to verify before expanding

- Similar flavor names cannot collapse distinct package sizes.
- Historical returns resolve to the originally sold variant and bundle revision.
- Renaming a flavor without changing the product preserves the stable variant-to-item relationship for existing orders.
- A changed serving-count description cannot silently change ERP package quantity; the product owner must approve its physical meaning.

## 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 flavor label is renamed.

- [Shopify–NetSuite Integration for Nutrition and Supplement Brands](https://www.stacksync.com/use-case/shopify-netsuite-integration-for-nutrition-and-supplement-brands)
- [Amazon–NetSuite Integration for Supplement Marketplace Sales](https://www.stacksync.com/use-case/amazon-netsuite-integration-for-supplement-marketplace-sales)
- [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)
- [Wholesale Sample-to-Order Workflows for Nutrition Brands Using HubSpot and NetSuite](https://www.stacksync.com/blog/wholesale-sample-to-order-workflows-for-nutrition-brands-using-hubspot-and-netsuite)
- [Syncing Custom Fields From a Legacy NetSuite to HubSpot](https://www.stacksync.com/blog/sync-netsuite-custom-fields-to-hubspot)
- [Automating Quote-to-Cash Between HubSpot and NetSuite](https://www.stacksync.com/blog/automate-hubspot-netsuite-quote-to-cash)

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 serving count be the product identifier?

No. It is a useful attribute, but stable variant and ERP item references must establish identity. Different products can share the same serving count.

Which fields should Shopify own once the sync is live?

Keep the storefront in charge of what customers see: variant title, option labels, and images. NetSuite item definitions, package quantity, and component recipes are write-scoped to product operations, so a merchandiser editing a Shopify title cannot alter what the warehouse picks. Decide this field ownership per column before the first order flows, and record it where both teams can read it.

What has to be cleaned up in Shopify before the crosswalk is approved?

Duplicate variants left behind by earlier catalog edits are the usual blocker. Merge or archive variants that represent the same physical tub, give every live variant a SKU that differs by package size, and make sure discontinued flavors still needed for returns are archived rather than deleted. Product operations then reviews one row per variant, which keeps the approval to a single pass instead of a rolling cleanup.

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