Shopify–NetSuite Sync for Pet Food Brands: Match Recipes, Bag Sizes, and Variety Packs

What this looks like in pet food and treats

A pet brand sells one recipe in two bag sizes and a trial variety pack containing several recipes. A customer buys the larger bag and a trial pack. Mapping by recipe name alone can select the small bag and erase the trial pack’s components, leaving support unable to explain the exact products purchased.

Records, ownership, and update rules

Work through the process

1. 01
   Review the product matrix

   Enumerate recipe and package combinations, including retired variants needed for historical inquiries. A shared recipe name does not establish the same sellable bag or treat pack.
2. 02
   Approve component relationships

   Define variety-pack contents and the chosen ERP representation. Preserve the original customer line alongside any component breakdown used for operations.
3. 03
   Test mixed purchases

   Use an order containing two bag sizes and a variety pack. Compare physical items, quantities, and accepted totals before relying on the synchronized record for fulfillment.
4. 04
   Preserve downstream references

   Keep order and shipment identities available for later support work. Any lot association must come from approved fulfillment or production evidence rather than the product’s current catalog record.
5. 05
   Place a two-bag order in Shopify and read back the NetSuite items

   Create a Shopify test order with the small bag, the large bag of the same recipe, and one trial variety pack. Open the synced sales order in NetSuite and confirm three separate lines: each bag maps to its own ERP item, and the trial pack keeps its component recipes on the line. Then change the variety pack's composition on the ERP item record and reopen the earlier order. The original components must still be there. If the two bags collapse into one item, or the old order now shows the new composition, stop the rollout and fix the item mapping before enabling any further object.

Handle the exceptions explicitly

Variety pack changes recipes

Version the composition and preserve the purchased definition.

Bag size is renamed

Retain stable identity and review whether the physical package actually changed.

Customer asks for a lot after purchase

Follow the shipment evidence; do not infer the lot from the order date alone.

What to verify before expanding

• Two bag sizes of one recipe remain distinct operational products.
• A variety-pack order retains its original component recipes.
• Changing a variety-pack recipe does not alter the component relationship retained for previously purchased orders.
• A later lot inquiry follows the actual order-to-shipment evidence rather than selecting a batch from the order date.

Technical references

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