--- title: "Zendesk NetSuite Extensiv returns workflow for beauty sets" description: "A Zendesk return ticket recovers the purchased shade, size and set from NetSuite, then waits for Extensiv receipt and finance evidence before closing." canonical: https://www.stacksync.com/blog/personal-care-returns-workflows-across-zendesk-netsuite-and-extensiv last_modified: 2026-09-21 --- # Personal Care Returns Workflows Across Zendesk, NetSuite, and Extensiv > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Support, warehouse receipt, disposition and refund stay as separate states with separate owners, so a closed ticket never stands in for a completed return. Author Ignacio Malpartida · GTM Engineer Published September 21, 2026 Read time 4 min read APP TIPS ## The operating decision Connect personal-care return conversations to the original shade, size, set, and approved remedy. A workflow should keep support authorization, warehouse receipt, disposition, and finance completion separate. It must not assume that returned personal-care goods can be restocked or that a closed ticket proves a refund was accepted. Explore the complete [personal care integration and automation hub](https://www.stacksync.com/industry/cpg/personal-care) for the systems and processes around this guide. ![Summary card: Zendesk NetSuite Extensiv returns workflow for beauty sets](https://www.stacksync.com/images/blog-highlights/icp-personal-care-returns-workflows-across-zendesk-netsuite-and-extensiv.webp) ## 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 | Record | Owner | Operating rule | | --- | --- | --- | | Return ticket | Support | Retain original order and line, reported issue, requested shade, and proposed remedy. | | Purchased configuration | Order operations | Recover the historical set and component relationship used for the sale. | | Warehouse disposition | Authorized receiving owner | Own the observed item, condition, and approved disposition. | | Financial remedy | Finance | Record the accepted credit, refund, or exchange treatment and destination reference. | ![Record ownership diagram: Return ticket, Purchased configuration, Warehouse disposition](https://www.stacksync.com/images/blog-diagrams/icp-personal-care-returns-workflows-across-zendesk-netsuite-and-extensiv.webp) *Define the record owner and the rule before enabling updates.* ## 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. ![5-step operating sequence: Zendesk NetSuite Extensiv returns workflow for beauty sets](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-personal-care-returns-workflows-across-zendesk-netsuite-and-extensiv.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## 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. ## Connect this process to the rest of your operation [Explore Stacksync workflows](https://www.stacksync.com/workflow-automation) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real return ticket example and the exception your team handles most often, for example returned shade differs from the order. - [Sample and Tester Fulfillment Automation for Personal Care Brands](https://www.stacksync.com/use-case/sample-and-tester-fulfillment-automation-for-personal-care-brands) - [Personal Care Sample and Tester Workflows: Track Requests Through Warehouse Fulfillment](https://www.stacksync.com/blog/personal-care-sample-and-tester-workflows-track-requests-through-warehouse-fulfillment) - [AI Agents for Personal Care Retailer Onboarding: Assemble Product and Packaging Documents](https://www.stacksync.com/blog/ai-agents-for-personal-care-retailer-onboarding-assemble-product-and-packaging-documents) - [Conflicting Product Sheets and Missing Packaging Data: Personal Care Agent Exceptions](https://www.stacksync.com/blog/conflicting-product-sheets-and-missing-packaging-data-personal-care-agent-exceptions) - [Manage Shopify Exchanges Through Zendesk and NetSuite](https://www.stacksync.com/blog/manage-shopify-exchanges-through-zendesk-and-netsuite) - [Product Exchange Checks: Refunds, Stock, and Customer Choice](https://www.stacksync.com/blog/product-exchange-checks-refunds-stock-and-customer-choice) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync Workflows quick start](https://docs.stacksync.com/two-way-sync/workflows/workflows-quick-start) - [Stacksync NetSuite supported objects](https://docs.stacksync.com/two-way-sync/connectors/netsuite) FAQ ## Frequently asked questions Does the workflow decide whether returned goods are resaleable? No. It records and carries the authorized disposition decision. The product and receiving owners determine the applicable policy. Do agents see warehouse and finance progress inside Zendesk? Yes, as read-back fields on the ticket rather than editable values. Each stage writes its reference and timestamp to the ticket once the owning system confirms it: the Extensiv receiver ID when goods are checked in, the NetSuite document number when finance records the remedy. Agents can quote those fields to the customer but cannot set them, which keeps the ticket honest about what has and has not happened. Should the exchange ship before or after Extensiv confirms the return? That is a policy choice you set per remedy, not something the workflow assumes. Some brands release the replacement shade as soon as support approves the remedy; others wait for Extensiv to confirm receipt and condition. Configure the trigger explicitly for each remedy type and keep the two events as separate states. The one thing the workflow will not do is release an exchange because a ticket was closed. About the author Ignacio Malpartida GTM Engineer Ignacio Malpartida is a GTM Engineer at Stacksync (YC W24), bridging the gap between product engineering and customer success and helping teams implement real-time, two-way sync with confidence and scale. [All posts by Ignacio Malpartida](https://www.stacksync.com/blog/author/ignacio-malpartida) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [connector Zendesk integrations](https://www.stacksync.com/connectors/zendesk) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [connector Extensiv (3PL Central) integrations](https://www.stacksync.com/connectors/extensiv-3pl-central) - [platform Integration architecture](https://www.stacksync.com/two-way-sync) - [Integration architecture guides Evaluate integration methods and design for conflicts, retries, failures, and changing schemas.](https://www.stacksync.com/blog#topic-integration-architecture) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips Personal Care Sample and Tester Workflows: Track Requests Through Warehouse Fulfillment 4 min read read](https://www.stacksync.com/blog/personal-care-sample-and-tester-workflows-track-requests-through-warehouse-fulfillment) [App tips Manage Shopify Exchanges Through Zendesk and NetSuite 8 min read read](https://www.stacksync.com/blog/manage-shopify-exchanges-through-zendesk-and-netsuite) [App tips Product Exchange Checks: Refunds, Stock, and Customer Choice 7 min read read](https://www.stacksync.com/blog/product-exchange-checks-refunds-stock-and-customer-choice) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)