A return moves through several decisions: whether it is accepted, where the product goes, whether it can be resold, what the customer receives and how the records reconcile. Treating those decisions as one status hides work and creates avoidable confusion.
You will finish with: a workflow map and an owner for each decision. Use this guide with customer experience, warehouse, channel operations and finance. Apply your published policies and applicable channel requirements; this guide does not define them for you.
1. Identify the order and request
Connect the request to the original order, product, quantity and selling channel. Record the customer’s reason in a consistent format. Protect personal information by keeping the working record in your approved systems rather than a public shared document.
Decide who can authorize the return and which exceptions need approval. Do not assume every channel uses the same authorization process.
2. Give the customer a clear next step
Confirm the destination, packaging instructions and expected next event. Explain who will provide updates. If a return label or collection is required, assign the owner and a way to detect when the handoff fails.
Customer communication should reflect actual status. “Received” and “refund approved” are different events; a customer should not have to infer the distinction.
3. Receive and inspect
The warehouse checks the item against the expected return, records its condition and identifies discrepancies. Returned stock should remain unavailable for sale until the required inspection is complete.
Define how to handle the wrong item, missing accessories, damage or an unidentified return. Keep an evidence trail appropriate to the product and policy. An operator should not need to guess which queue owns the exception.
4. Decide disposition
Typical operational decisions include restock, repair or refurbishment, return to vendor, disposal or further review. The options depend on your product and agreements.
Record who has authority to choose and how the decision changes inventory. A refund does not prove that an item is resellable. Conversely, a resellable item does not automatically establish that the refund has been completed.
5. Reconcile the customer and stock records
Confirm the refund or replacement action in the relevant selling channel. Check the inventory movement and the financial treatment against the same order and item.
Assign unresolved differences to an owner. Useful exceptions include a received return with no refund decision, a completed refund with missing goods, and inspected stock that has not reached the correct available balance.
6. Turn reasons into improvements
Review return reasons alongside listing content, variant mappings, packing errors and delivery damage. Use defined denominators and equivalent time windows. A high raw count can simply reflect higher sales.
Choose an action supported by the evidence. Unclear size information may call for catalog work. Repeated transit damage may call for packaging review. A long refund queue may call for clearer decision ownership.
A working ownership map
| Event | Decision owner | Evidence of completion |
|---|---|---|
| Request received | Customer experience | Order match and reason |
| Return authorized | Policy owner | Authorization and instructions |
| Product received | Warehouse | Receipt and identity check |
| Inspection complete | Returns operations | Condition and disposition |
| Refund or replacement | Authorized channel operator | Channel acknowledgment |
| Stock and cost reconciled | Inventory and finance | Movement and cost records |
These roles are examples. Replace them with named people or queues in your operating model.
Where 1Commerce can help
1Commerce can orchestrate configured returns workflows, with responsibilities for reverse logistics, inspection, disposition, restocking and customer communication agreed during scoping. Customer-care operations are optional, and return, refund and restocking turnaround commitments depend on the approved operating design and service agreement. Confirm the selected responsibilities and systems so the physical return and the customer conversation remain connected.
Explore fulfillment operations, read managed commerce vs software only, or map your returns handoffs with our team.