--- title: "Zendesk to Extensiv returns workflow for supplements" description: "Carry a supplement return from the Zendesk ticket to the authorized remedy, Extensiv receipt and NetSuite credit, with each stage holding its own state." canonical: https://www.stacksync.com/blog/supplement-return-workflows-connect-zendesk-requests-to-warehouse-and-finance-review last_modified: 2026-09-21 --- # Supplement Return Workflows: Connect Zendesk Requests to Warehouse and Finance Review > 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 Wrong tub size reported, nothing back at the warehouse yet: the workflow keeps the ticket, the authorization, the receipt, and the credit as four separate facts. Author Ignacio Malpartida · GTM Engineer Published September 21, 2026 Read time 5 min read APP TIPS ## The operating decision Connect a supplement return request to the original order, authorized return decision, actual receipt, and finance outcome. Support owns the customer conversation, receiving owns what physically arrives, and the approved policy determines disposition and refund. Do not equate a ticket status with returned stock or a completed financial adjustment. Explore the complete [nutrition and supplements integration and automation hub](https://www.stacksync.com/industry/cpg/nutrition-supplements) for the systems and processes around this guide. ![Summary card: Zendesk to Extensiv returns workflow for supplements](https://www.stacksync.com/images/blog-highlights/icp-supplement-return-workflows-connect-zendesk-requests-to-warehouse-and-finance-review.webp) ## 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 | Record | Owner | Operating rule | | --- | --- | --- | | Support request | Customer support | Capture original order and line, reported issue, requested remedy, and available photos or evidence. | | Return authorization | Policy owner | Record the permitted remedy and conditions before instructing warehouse or finance actions. | | Receiving result | Warehouse | Own actual product, quantity, package condition, and approved disposition status. | | Financial outcome | Finance | Link the accepted credit or refund evidence to the original transaction and approved remedy. | ![Record ownership diagram: Support request, Return authorization, Receiving result](https://www.stacksync.com/images/blog-diagrams/icp-supplement-return-workflows-connect-zendesk-requests-to-warehouse-and-finance-review.webp) *Define the record owner and the rule before enabling updates.* ## 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. ![5-step operating sequence: Zendesk to Extensiv returns workflow for supplements](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-supplement-return-workflows-connect-zendesk-requests-to-warehouse-and-finance-review.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## 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. ## 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 support request example and the exception your team handles most often, for example returned item differs from the order. - [Wholesale Sample Automation for Nutrition Brands](https://www.stacksync.com/use-case/wholesale-sample-automation-for-nutrition-brands) - [Wholesale Sample-to-Order Workflows for Nutrition Brands Using HubSpot and NetSuite](https://www.stacksync.com/blog/wholesale-sample-to-order-workflows-for-nutrition-brands-using-hubspot-and-netsuite) - [AI Agents for Nutrition Brands: Assemble Product and Batch-Document Requests](https://www.stacksync.com/blog/ai-agents-for-nutrition-brands-assemble-product-and-batch-document-requests) - [Missing COAs and Batch Mismatches: Exception Handling for Nutrition Brand Agents](https://www.stacksync.com/blog/missing-coas-and-batch-mismatches-exception-handling-for-nutrition-brand-agents) - [NetSuite Returns Dashboard via SuiteQL Query](https://www.stacksync.com/blog/netsuite-returns-dashboard-via-suiteql-query) - [Automating Quote-to-Cash Between HubSpot and NetSuite](https://www.stacksync.com/blog/automate-hubspot-netsuite-quote-to-cash) 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 make product-quality decisions? No. It carries the approved policy and named owner's decision. Product condition and quality judgments belong to the responsible team. Can support trigger the refund from inside Zendesk? No. The agent can record the requested remedy and see the authorization status, but the refund is posted in NetSuite by finance once the policy conditions are met, and the workflow only reads that result back to the ticket. This keeps a ticket macro from becoming a payment instruction. A support lead who wants faster refunds should change the policy thresholds, not the write permissions. What order data does Zendesk need before the workflow can locate the sale? The ticket needs the order number or the email used at checkout, and the workflow looks up the order line in NetSuite from there. Support should also collect the tub size printed on the label when the complaint is about the wrong product, because that is what receiving will compare against. If neither identifier is present, the workflow parks the ticket in a needs-information state instead of guessing from the customer's recent orders. 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 EDI for Supplement Brands Entering Retail: Validate Item Numbers and Pack Configurations 4 min read read](https://www.stacksync.com/blog/edi-for-supplement-brands-entering-retail-validate-item-numbers-and-pack-configurations) [App tips Wholesale Sample-to-Order Workflows for Nutrition Brands Using HubSpot and NetSuite 5 min read read](https://www.stacksync.com/blog/wholesale-sample-to-order-workflows-for-nutrition-brands-using-hubspot-and-netsuite) [App tips AI Agents for Nutrition Brands: Assemble Product and Batch-Document Requests 5 min read read](https://www.stacksync.com/blog/ai-agents-for-nutrition-brands-assemble-product-and-batch-document-requests) ## 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/)