--- title: "Household product return workflow with Zendesk and Extensiv" description: "Zendesk return claims, Extensiv receiving counts, and NetSuite remedies stay linked so damaged household goods never re-enter stock via a ticket update." canonical: https://www.stacksync.com/blog/household-product-return-workflows-route-damaged-and-unsellable-goods-for-review last_modified: 2026-09-21 --- # Household Product Return Workflows: Route Damaged and Unsellable Goods for 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 A leaking case returned by a distributor is counted and dispositioned before any credit or stock movement, with support, warehouse, and finance each owning their own step. Author Ignacio Malpartida · GTM Engineer Published September 21, 2026 Read time 5 min read APP TIPS ## The operating decision Connect household-product returns to the original sold pack, actual receiving evidence, and approved disposition and remedy. A customer’s damage report starts a case; it does not establish returned inventory or a completed credit. Keep warehouse condition decisions and finance authorization separate so damaged goods do not automatically re-enter available stock. Explore the complete [household consumables integration and automation hub](https://www.stacksync.com/industry/cpg/household-consumables) for the systems and processes around this guide. ![Summary card: Household product return workflow with Zendesk and Extensiv](https://www.stacksync.com/images/blog-highlights/icp-household-product-return-workflows-route-damaged-and-unsellable-goods-for-review.webp) ## What this looks like in household consumables A distributor returns a case containing leaking refills and intact outer cartons. Support approves review, while the warehouse receives fewer usable packages than the original case count. The workflow must preserve the actual contents and disposition rather than add one complete case back to stock because the return reference says case. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Return claim | Support | Record original order, affected item, reported condition, quantity, unit, and requested remedy. | | Receiving count | Warehouse | Own the physical items received and their observed condition. | | Disposition decision | Authorized operations owner | Approve the treatment of damaged, unsellable, or acceptable goods. | | Finance remedy | Finance | Link the authorized adjustment to the original sale and accepted outcome. | ![Record ownership diagram: Return claim, Receiving count, Disposition decision](https://www.stacksync.com/images/blog-diagrams/icp-household-product-return-workflows-route-damaged-and-unsellable-goods-for-review.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Recover the original pack Identify the purchased refill, concentrate, multipack, or case and its effective definition. A returned carton may no longer contain the full quantity that was originally shipped. 2. 02 Authorize the return path Apply the business’s policy and obtain required evidence before issuing instructions. Keep the requested remedy separate from the approved warehouse and finance actions. 3. 03 Capture actual receipt Record received item quantities and condition at the appropriate unit level. Confirm the supported warehouse action and preserve its reference rather than assuming a return authorization changed stock. 4. 04 Close the approved remedy Reconcile the disposition and accepted financial result. Support should communicate what actually completed, including any unresolved quantity difference, instead of closing all states from a single ticket update. 5. 05 Close a Zendesk ticket early and confirm nothing moved in stock Use a returned case that holds leaking refills alongside intact cartons of a different product. Let the warehouse record the item-by-item count in Extensiv, then have support close the Zendesk ticket before operations enters a disposition. In NetSuite, on-hand inventory for both items should be unchanged and no adjustment should exist against the original sale. Only after the disposition owner marks the intact cartons acceptable and the leaking refills unsellable should the adjustment appear, and it should cite the return authorization and the accepted quantities. Available stock rising on ticket closure, an adjustment without that reference, or a receipt logged as one whole case stops the rollout. ![5-step operating sequence: Household product return workflow with Zendesk and Extensiv](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-household-product-return-workflows-route-damaged-and-unsellable-goods-for-review.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Carton contains mixed products Count and identify actual items before disposition or financial reconciliation. ### Received quantity differs from authorization Route the discrepancy to the owner and preserve both values. ### No return is required by policy Record the explicit decision without creating a fictional warehouse receipt. ## What to verify before expanding - Unsellable goods cannot become available stock through ticket closure. - The finance remedy references the approved and accepted return outcome. - A mixed-product return retains separate observed item quantities before disposition or financial calculation. - A no-return policy decision creates no fictional receipt, while a received-count mismatch remains visible against the authorized quantity. ## 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 claim example and the exception your team handles most often, for example carton contains mixed products. - [Wholesale Replenishment Automation for Household Brands](https://www.stacksync.com/use-case/wholesale-replenishment-automation-for-household-brands) - [Household Product Replenishment Workflows: Prevent Duplicate Wholesale Orders](https://www.stacksync.com/blog/household-product-replenishment-workflows-prevent-duplicate-wholesale-orders) - [AI Agents for Household Brands: Investigate Refill and Case-Quantity Disputes](https://www.stacksync.com/blog/ai-agents-for-household-brands-investigate-refill-and-case-quantity-disputes) - [Missing Conversions and Mixed Pack Sizes: Exceptions for Household Order Agents](https://www.stacksync.com/blog/missing-conversions-and-mixed-pack-sizes-exceptions-for-household-order-agents) - [How to Sync Zendesk with Salesforce: A Two-Way Integration Guide](https://www.stacksync.com/blog/how-to-sync-zendesk-with-salesforce) - [Beat Shopify API Rate Limits with Stacksync Real‑Time Sync](https://www.stacksync.com/blog/beat-shopify-api-rate-limits-stacksync-realtime-sync) 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 a return authorization increase inventory? No. It authorizes a process. Actual receiving and approved disposition establish the operational outcome, and any inventory action must be verified separately. Until the warehouse posts a receipt in Extensiv against that authorization, NetSuite should still show the goods as sold, and an authorization that never turns into a receipt should lapse with no stock or credit effect. When does the Extensiv receiving count reach NetSuite? After the warehouse has counted and graded the contents, not when the carton is scanned at the dock. The receipt carries item, quantity, and observed condition at the pouch or bottle level, and NetSuite records it against the return with unsellable units kept out of available stock. Finance sees the same receipt reference on the adjustment, so a count posted before grading is a defect to fix, not a timing preference. Who can override the warehouse condition finding? No one in support or finance. The receiving count and observed condition belong to the warehouse, and the disposition owner decides what to do with what was found; neither role edits the other's record. If a customer disputes the count, support opens a discrepancy on the case and the warehouse recounts. Any override happens in the open, as a new decision with a name on it, not as an edit to the receipt. 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 Household Product Replenishment Workflows: Prevent Duplicate Wholesale Orders 5 min read read](https://www.stacksync.com/blog/household-product-replenishment-workflows-prevent-duplicate-wholesale-orders) [App tips Household Products EDI: Connect Distributor Purchase Orders to Case-Level Shipments 5 min read read](https://www.stacksync.com/blog/household-products-edi-connect-distributor-purchase-orders-to-case-level-shipments) [App tips AI Agents for Household Brands: Investigate Refill and Case-Quantity Disputes 5 min read read](https://www.stacksync.com/blog/ai-agents-for-household-brands-investigate-refill-and-case-quantity-disputes) ## 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/)