An ecommerce returns workflow connects a customer’s item-level request with the merchant’s policy decision, physical return and financial resolution. Treat request submitted, return approved, goods received and refund completed as separate states. Each needs its own evidence, owner and customer explanation; progress in one state does not prove another is complete.
Translate your policy into review inputs
Identify the item, quantity, reason, request date and reference date used by your published policy. Record condition requirements, excluded categories and permitted resolution paths. Distinguish a standard request from damage evidence or an exception needing human review. Ask the responsible team to confirm market requirements and policy wording; do not let an illustrative rule become a customer promise.
Keep a partial return tied to the right item
Suppose a customer buys a jacket and a shirt, then requests to return only the jacket. The request should preserve the jacket’s item reference, quantity and reason while leaving the shirt unchanged. Give the return its own reference linked to the order. A submitted request should show that review is pending, rather than presenting the whole order as returned.
Agree approval and the physical route
Name who reviews the request and supplies return instructions. Confirm destination, shipping method, label responsibility and any documents with your logistics team for the relevant market. Explain what approval permits and what still needs checking. If no physical return is required under your policy, document that decision rather than inventing a warehouse receipt to advance the process.
Reconcile receipt with the separate resolution
The warehouse should record what arrived, the quantity and any condition discrepancy against the return reference. Finance or the responsible team then records the approved financial outcome in its own process. If the parcel is received but the refund remains unresolved, keep both facts visible. Give support an owner and next review instead of a generic completed status.
Merchant returns checklist
For JetonTrack, confirm the available request, review and integration scope. Label issuance, warehouse updates and payment actions require explicit production agreements.
- Test a standard request, a partial return and an excluded item.
- Keep request, approval, receipt and resolution statuses distinct.
- Assign support, logistics, warehouse and finance handoffs.
- Check the message and evidence required at each decision.
- Define who resolves mismatched quantities or financial statuses.
Common questions
Does receiving a return mean a refund is complete?
No. Receipt confirms a physical event. Record the separate inspection and financial outcome according to your agreed process and communicate the actual status.
Should every return use the same warehouse and method?
Not by default. Review the item, market, reason and your logistics arrangements. Make the approved instructions clear for that request.