Skip to content

Household Product Return Workflows: Route Damaged and Unsellable Goods for Review

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
Read time
5 min read
Household Product Return Workflows: Route Damaged and Unsellable Goods for Review
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 for the systems and processes around this guide.

Summary card: Household product return workflow with Zendesk and Extensiv

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

RecordOwnerOperating rule
Return claimSupportRecord original order, affected item, reported condition, quantity, unit, and requested remedy.
Receiving countWarehouseOwn the physical items received and their observed condition.
Disposition decisionAuthorized operations ownerApprove the treatment of damaged, unsellable, or acceptable goods.
Finance remedyFinanceLink the authorized adjustment to the original sale and accepted outcome.
Record ownership diagram: Return claim, Receiving count, Disposition decision
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
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.
Book a demo for household consumables integration and automation

Connect this process to the rest of your operation

Explore Stacksync workflows and scope the records and actions against your actual systems. Book a demo with a real return claim example and the exception your team handles most often, for example carton contains mixed products.

The shared architecture guide covers record matching, ownership, and recovery across systems.

Technical references

Book a demo for household consumables integration and automation

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
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

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.

Coworkers laughing in front of a laptop in a casual office setting

You just read how it should work.
See it run on your own data.