Personal Care Returns Workflows Across Zendesk, NetSuite, and Extensiv

What this looks like in personal care

A shopper returns one item from a gift set and requests a different shade. Support sees the current product catalog, while the ERP records the original set. The process must recover the purchased configuration and apply the approved partial-return policy before warehouse or finance actions occur.

Records, ownership, and update rules

Work through the process

1. 01
   Recover purchase context

   Use the original order line and historical set definition. Current catalog contents may differ and should not overwrite the item relationship needed to assess the request.
2. 02
   Authorize the remedy

   Apply the business’s policy for partial sets, shade changes, and item condition. Keep the customer’s requested outcome separate from the accepted remedy.
3. 03
   Coordinate physical and financial work

   Use confirmed warehouse and finance actions and store their references. Wait for the evidence required by the policy without inventing a receiving event when no return is required.
4. 04
   Close the loop accurately

   Tell support which steps completed and which remain pending. A received parcel, approved exchange, and accepted refund are different states with different owners.
5. 05
   Close a Zendesk ticket early and confirm NetSuite stays untouched

   Open a Zendesk ticket for one item returned from last season's gift set. The workflow should attach the NetSuite order line and the set revision sold at the time; if it shows the current set contents instead, stop and fix the lookup. Then close the ticket before the parcel arrives. Nothing should change in NetSuite or Extensiv: no credit memo, no receipt, no stock movement. Any of those appearing on closure means the workflow treats a support status as evidence, and the rollout pauses. Have the warehouse record a different shade than the ticket names. The original sale line must remain as sold, with the mismatch queued for review.

Handle the exceptions explicitly

Returned shade differs from the order

Route the mismatch for review rather than updating the original sale to fit the return.

Set definition has changed

Use the purchased revision and preserve the difference from today’s catalog.

Goods cannot be restocked

Record the approved disposition and avoid increasing available inventory automatically.

What to verify before expanding

• Partial-set returns preserve the original component relationship.
• Ticket closure cannot imply warehouse or finance completion without evidence.
• Receiving goods with a different shade preserves the discrepancy and cannot rewrite the original purchased item to make it match.
• A non-restockable disposition produces no available-stock increase, regardless of ticket closure or the financial remedy.

Technical references

• Stacksync Workflows quick start
• Stacksync NetSuite supported objects