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

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

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.

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.

Technical references

• Stacksync two-way sync quick start
• Stacksync Shopify supported objects
• Stacksync NetSuite supported objects
• Shopify product variant model