Return triage turns a customer request into a controlled path. It should answer what was purchased, which policy applies, where the product should go, what the customer should expect, and which evidence the receiving team needs. Authorization, physical receipt, disposition and refund are separate events.
Capture the request accurately
Match the customer to the original order, channel, item, quantity and fulfillment record. Record the stated reason using a controlled list plus notes where needed. Keep personal information in approved systems and expose only what the operator needs.
Check the current channel or merchant policy, purchase date, product restrictions and prior resolutions. The triage agent should not invent an exception. Define which requests the frontline team may approve and which require a policy, fraud, product-safety or account owner.
Choose the route
An approved return needs a destination, transport method, authorization reference and time boundary. Route based on product type, origin, destination capability and agreed operating scope. Some items may go to a fulfillment facility; others may require vendor, specialist or local handling.
Tell the customer the next observable event without implying it already occurred. “Your return is authorized” does not mean “your refund is complete.” If a label or pickup is provided, explain what acceptance evidence to retain and how to report a failure.
Receive and inspect
At receipt, match the authorization, item identity and quantity. Record condition, accessories, serial or lot where relevant, and discrepancies. Keep goods unavailable until the required inspection and disposition decision are complete.
Hypothetical example: a customer was authorized to return a blue size-medium garment, but the facility receives a black size-large item without the expected tag. The receiver records an identity exception and photographs it under policy; they do not restock it or silently change the authorization. Customer care and the return owner review the evidence and communicate the next decision.
Work the exception queues
Useful queues include authorized-not-shipped, carrier-stalled, received-unmatched, wrong item, incomplete product, damaged product, inspection-aged and refund-pending. Each needs a clock, owner and escalation threshold defined by current policy.
When a scan or integration is unavailable, create a controlled temporary receipt tied to the physical item, then reconcile it before release. Check retries for duplicate receipts. If an item was mistakenly released, quarantine remaining units, trace allocations and correct inventory with a reasoned adjustment.
Close all three records
A return is operationally closed only when the customer resolution, physical disposition and financial/inventory records are reconciled—or a documented exception remains assigned. Review reasons using comparable sales or return denominators, not raw counts alone.
Use the returns exception playbook, read returned inventory disposition, and visit the returns and CX hub. 1Commerce can support scoped reverse-logistics and customer-experience workflows; exact services, facilities and decision authority depend on agreement.
Explore fulfillment operations or map your return triage with 1Commerce.