Shopify–NetSuite Sync for Snack Brands: Match Single Units, Multipacks, and Cases

What this looks like in packaged food and snacks

A customer orders two mixed-flavor six-packs. The warehouse stores individual bars and the ERP also has a 24-bar grocery case. A text match on the snack name selects the case SKU, turning twelve bars into forty-eight. The correct design preserves the customer’s two purchased packs and applies the approved component recipe for that exact variant revision.

Records, ownership, and update rules

Work through the process

1. 01
   List every sellable level

   Document individual units, multipacks, variety packs, and retailer cases separately. Identify which exist as ERP items and which require an approved component breakdown. A matching flavor is not sufficient identity.
2. 02
   Version the recipe

   Tie the pack definition to the order’s purchase date or explicit revision. Preserve old recipes so an exchange or return can be interpreted after merchandising replaces a flavor in the current bundle.
3. 03
   Validate the order transformation

   Translate one representative order for each pack type. Compare purchased packs, component units, discounts, and the retained channel reference before allowing the mapped result into ERP order processing.
4. 04
   Constrain later edits

   Allow approved descriptive updates without changing historical quantities. A revised bundle definition should affect eligible future orders, while existing orders need an explicit operational decision before substitution.
5. 05
   Test two six-packs, one storefront edit, and one missing component

   Place a test order for two mixed-flavor six-packs in Shopify and open the NetSuite order it creates. The lines should show twelve component units under the recipe revision in force on the order date. If NetSuite shows a 24-bar case, or any quantity other than twelve, stop the rollout and repair the crosswalk before live orders sync. Then change the bundle's flavor in the Shopify storefront and reopen an order placed last month; its NetSuite lines must still cite the earlier recipe. Last, mark one component out of stock and confirm the order pauses for the fulfillment owner instead of substituting a flavor on its own.

Handle the exceptions explicitly

One component is unavailable

Route substitution or partial fulfillment to the owner; do not quietly alter the purchased recipe.

Case conversion is missing

Hold the affected line and request the approved pack definition.

SKU is reused after a redesign

Use stable IDs and effective dates to separate the old and new product definitions.

What to verify before expanding

• Two six-packs resolve to twelve component units under the approved recipe.
• A historical order retains its original recipe after a storefront change.
• A missing case conversion blocks the affected physical-quantity comparison even when the order's monetary totals match.
• Reusing a SKU after redesign does not change the approved recipe used to explain an earlier order.

Technical references

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