Supplement Return Workflows: Connect Zendesk Requests to Warehouse and Finance Review

What this looks like in nutrition and supplements

A customer reports receiving the wrong tub size and asks for a replacement. Support finds the order, but the warehouse has not received anything back. The workflow must distinguish the reported issue, approved remedy, physical return, and any finance action instead of treating a closed support ticket as proof that all four happened.

Records, ownership, and update rules

Work through the process

1. 01
   Locate the exact sale

   Match the request to the original variant, package, and order line. A customer’s current account or product nickname is not enough to identify the item sold.
2. 02
   Apply the approved policy

   Route replacement, refund, inspection, or additional-information decisions to the authorized owner. Keep a customer request distinct from the accepted remedy and avoid implying that opened goods are automatically resaleable.
3. 03
   Coordinate the handoffs

   Use verified warehouse and finance actions for the authorized path. Preserve each destination reference and wait for actual receipt evidence where the policy requires it.
4. 04
   Reconcile the customer outcome

   Confirm which remedy completed and what remains pending. Support should communicate the accepted state, not infer a refund from a warehouse receipt or infer receipt from a shipping label.
5. 05
   Book a mismatched return in Extensiv and check every state

   Approve a return for the wrong-size tub, then have the warehouse receive a different product against it in Extensiv. Check four places: the Zendesk ticket should show the authorization but not a closed status, Extensiv should show the receipt with disposition pending rather than the item in sellable stock, NetSuite should have no credit memo yet, and the return authorization should show the mismatch awaiting the owner. Stop the rollout if the receipt alone flipped the item to resaleable, if NetSuite posted a refund before the disposition decision, or if closing the ticket in Zendesk cleared any of the other three states.

Handle the exceptions explicitly

Returned item differs from the order

Hold disposition and ask the owner to review the mismatch.

Replacement already shipped

Check prior remedy references before issuing another replacement or refund.

No physical return is required

Record that explicit policy decision instead of creating a fictional receiving event.

What to verify before expanding

• The ticket, authorization, receipt, and financial outcome have separate states.
• An item is not marked resaleable solely because a return arrived.
• An existing replacement reference is checked before another replacement or refund can be approved for the same request.
• A policy-approved no-return remedy completes without creating a warehouse receiving event or returned-stock increase.

Technical references

• Stacksync Workflows quick start
• Stacksync NetSuite supported objects