Shopify–NetSuite Two-Way Sync for CPG Brands Selling DTC and Wholesale

What this looks like in consumer packaged goods

A CPG brand sells single units online and cases to distributors. A Shopify order contains a promotional bundle, while NetSuite holds the components and a separate wholesale customer hierarchy. Finance receives a channel total, operations receives units to fulfill, and sales needs the right account context. Copying the order total into a second system does not explain which products should move or which customer owes money.

Records, ownership, and update rules

Work through the process

1. 01
   Choose the business grain

   Decide whether the integration represents each order line as a sellable pack or its components. Preserve the original line even when fulfillment requires an approved component breakdown. Never infer a wholesale case quantity from a similar DTC title.
2. 02
   Map identity before values

   Create stable channel-to-ERP customer and product references. Validate known customers, new shoppers, bundles, and canceled lines independently. Record whether a field may be edited by commerce, finance, or neither.
3. 03
   Separate receipt from fulfillment

   Move a valid order into a received state, then check finance and fulfillment rules before release. The presence of a synchronized order is not permission to allocate stock, capture payment, or mark it shipped.
4. 04
   Reconcile the full order

   Compare line quantities, discounts, tax, shipping, and currency before accepting the ERP result. A header total may match even when a bundle was expanded incorrectly, so inspect both money and physical units.
5. 05
   Prove one bundle order lands on one NetSuite reference

   Place a test Shopify order for a promotional bundle and follow it into NetSuite. Open the created sales order and confirm it carries a single external reference back to the Shopify order ID, then compare its lines against the storefront: component quantities, discount, tax and currency must add back to the channel total. Next, place a guest order using the email of an existing distributor. In NetSuite that order must sit against a separate shopper identity, with the conflict raised for review. Stop the rollout if the bundle creates two sales orders, if the components round to a different amount, or if the guest order attaches to the distributor account.

Handle the exceptions explicitly

Guest customer shares an email

Resolve the channel identity without silently attaching the order to a distributor account. Escalate conflicting legal entities.

Bundle changes after purchase

Retain the purchased bundle revision and its component evidence; do not apply today’s recipe to an older order.

Cancellation after ERP posting

Route a controlled cancellation or credit process to finance; do not delete the posted transaction through a field update.

What to verify before expanding

• One Shopify order resolves to one approved NetSuite business reference.
• Bundle components reconcile to the original channel quantities and amount.
• A guest order and a distributor account sharing an email retain their separate customer identities after reconciliation.
• An older bundle order retains its purchased components after the current storefront recipe changes.

Technical references

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