Returns software should track the item requested, the approved return route, what was received and the resulting authorised resolution. Separate a return request from acceptance, inspection and a confirmed refund or exchange. Partial orders need item-level states so one returned line does not make the whole order appear reversed.
Let’s plan your returns workflow.
Bring your workflow, constraints and open questions. We’ll help you define the requirements and work through a practical next step.
Define policy through responsible owners
Have the business and relevant advisers approve eligibility, deadlines, evidence and financial treatment. This guide describes software states, not consumer-law requirements or a universal returns policy.
For a hypothetical clothing order, a customer may return one size while keeping another item. The product must preserve the original order and explain the specific affected quantity.
Use an item-level lifecycle
| Stage | Record to preserve | Dependency |
|---|---|---|
| Requested | Original line, quantity and stated reason | Eligibility under approved policy |
| Authorised | Permitted route and conditions | Responsible decision |
| In transit | Collection or shipment reference | Provider status and freshness |
| Received | Actual returned identity and quantity | Discrepancy review |
| Reviewed | Approved disposition | Authorised inspection outcome |
| Resolved | Exchange or financial result | Confirmed downstream reference |
Do not describe a refund as completed because a request was sent to a payment provider. Track the provider-supported outcome and unresolved exceptions separately.
Handle exchanges without losing relationships
Link the return and replacement transaction. Recheck replacement stock and applicable pricing under the approved process. A customer choosing an exchange does not guarantee the new variant is still available.
Keep discount and shipping treatment explicit. Finance must define the rule; implementation should not divide totals arbitrarily when only part of an order returns.
Test discrepancies and repeated events
Include the wrong returned item, fewer units than requested, a damaged package and a repeated provider callback. Verify inventory disposition and customer status remain coherent.
Give support a view of unresolved work and a stable reference. Avoid forcing agents to infer resolution from separate courier, warehouse and payment dashboards without a linked record.
Return-workflow questions
Should every requested return immediately restore sellable stock?
No. Receipt, condition and approved disposition determine the stock treatment.
Is an exchange just a negative sale followed by a new sale?
The underlying records may differ by system. Define the business relationship, accounting treatment and user-visible lifecycle explicitly.
Use checkout revalidation for replacement orders, and review the workflow with Drema's ecommerce developers.
