Shopify–NetSuite Sync for Beverage Brands: Align Bottles, Cases, and Variety Packs

What this looks like in beverages

A beverage store sells a twelve-bottle variety pack containing three flavors. NetSuite has individual bottles and full single-flavor cases. A customer buys two variety packs. The integration must retain two purchased packs and the approved twenty-four-bottle component recipe, while avoiding a substitution with two cases of one flavor.

Records, ownership, and update rules

Work through the process

1. 01
   Map the physical meaning

   Document each bottle size and sellable pack. A twelve-pack of small bottles and a six-pack of large bottles may have similar total volume but are different products and fulfillment instructions.
2. 02
   Approve variety components

   Record the flavor and quantity of every component. Keep the recipe available for the order’s purchase date so a seasonal mix change does not rewrite an earlier customer commitment.
3. 03
   Reconcile a mixed cart

   Test a cart containing a single bottle, a standard case, and a variety pack. Verify the original lines and the intended ERP representation before relying on the data for fulfillment.
4. 04
   Control product updates

   Permit approved catalog changes while protecting stable identity and historical pack definitions. Recheck mappings when a bottle size, case count, or product formulation actually changes.
5. 05
   Test a two-variety-pack order in NetSuite before widening the sync

   Place a Shopify test order for two twelve-bottle variety packs and open the resulting NetSuite sales order. It should carry two pack lines, and the approved recipe should expand to twenty-four bottles with each flavor's count visible on the line detail rather than folded into a total. Then repeat the order while one flavor is out of stock. The expected result is a substitution request routed to the merchandising owner with the original pack intact. Stop the rollout if the order arrives as two single-flavor cases, if a flavor count is missing, or if the sync swapped the flavor on its own.

Handle the exceptions explicitly

One flavor is unavailable

Route the substitution decision to the authorized team rather than silently changing the variety pack.

Pack name remains but contents change

Create a new effective recipe and preserve prior order interpretation.

Warehouse reports cases instead of bottles

Apply only the approved unit conversion and retain the original warehouse quantity.

What to verify before expanding

• Two twelve-bottle packs resolve to the intended twenty-four bottles.
• Flavor-level component quantities remain visible for a variety pack.
• Changing variety-pack contents preserves the purchased recipe on earlier orders, even when the marketing name stays unchanged.
• A warehouse quantity in cases remains visible alongside the bottle conversion, allowing a reviewer to reproduce both totals.

Technical references

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