Shopify–NetSuite Sync for Personal Care Brands: Align Shades, Sizes, and Gift Sets

What this looks like in personal care

A beauty brand offers a shade in travel and full sizes plus a holiday set containing both. The names share a product family, but the physical items and price differ. A loose catalog match can ship the wrong size and later make a partial gift-set return look like a standalone product return.

Records, ownership, and update rules

Work through the process

1. 01
   Enumerate the product matrix

   Review shade and size combinations rather than mapping only product families. Include discontinued variants because customers can return products after the current catalog changes.
2. 02
   Approve set composition

   Record each gift set’s components and effective version. Decide whether the ERP represents the set as a parent item, component lines, or another approved structure while preserving the original purchase.
3. 03
   Test mixed carts

   Use an order with two sizes of the same shade and a gift set. Compare original line references, physical units, and financial totals before accepting the transformed order.
4. 04
   Protect historical meaning

   Treat a packaging or set-content change as a reviewed mapping event. Marketing can improve a display title without altering the product that a historical order represents.
5. 05
   Check two sizes of one shade and a retired set in NetSuite

   Place a Shopify test order with the travel and full size of one shade and open it in NetSuite. Each line must reference a different item record; if both point at the same item, stop and fix the variant mapping. Next, pull a gift-set order from a previous season and confirm the NetSuite lines name the components sold then, not the current assortment. Then rename a shade in Shopify. The NetSuite item should keep its internal ID with only the display name changed. A new item after a rename means identity is keyed on the name, and the rollout pauses until it is keyed on the variant ID.

Handle the exceptions explicitly

Shade name changes

Keep stable identity and review whether the underlying product actually changed.

Set contains a limited-edition item

Require the correct component mapping instead of substituting the nearest permanent item.

Customer returns part of a set

Use the original set context and approved return policy rather than treating it as a standalone sale.

What to verify before expanding

• The same shade in two sizes remains two distinct operational items.
• A historical gift set resolves to its purchased components.
• A partial gift-set return uses the purchased component revision after the current seasonal assortment changes.
• A limited-edition component without an approved ERP match stays unresolved instead of being replaced with a permanent-range item.

Technical references

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