Returns processing from eligibility to refund or exchange
Use a returns processing checklist to check eligibility, verify what came back, calculate refunds and exchanges, and draft a customer reply.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What returns processing is
Returns processing is the work of deciding what your store can do about a customer's request to send back or exchange an item. You match the item, apply the governing return policy and check what happened to the goods and payment. The result is a decision a store owner can review, along with the exact quantity and amount the records support and a draft reply that explains the next step.
One order can have several requests against the same item. A payment may have been refunded before any goods came back, or another case may already reserve the last unit eligible for return. Start from the current order and refund history, then account for only the new action being proposed. Keep policy or legal disputes with the qualified owner.
What it does for the business
- Keep a second refund from slipping throughA queue that shows existing case IDs and payment history gives the reviewer a place to check before approving money movement. Customer service and finance can follow up using the same reference.
- Give the warehouse a clear inspection requestA hold can name the exact variant, quantity and condition evidence you need. The warehouse can report what arrived against the right order line so support can update the customer.
- Offer an exchange you can fulfillA dedicated reservation shows which size or model the owner can offer this customer. The owner can also see whether the replacement leaves a refund or a balance to collect before deciding what to communicate.
- Handle exceptions with a consistent recordCiting the policy clause and the evidence behind each decision lets the owner compare similar cases. Repeated holds for missing delivery dates or unclear fees also show where to improve order records or clarify the policy customers read.
Returns processing, step by step
Match the request to the order and policy
A return decision starts with the exact item and the policy clause that governs the case.
What to do
- Set a cutoff for the review and identify the selling entity. Gather requests, order lines, fulfillment records, receipts, delivery events and the policy versions that could apply.
- Match each request to its order, line and purchased variant using recorded IDs. Use proof of purchase tied to the transaction and keep customer details to the minimum needed.
- Find the rule that picks the policy version and the event that starts the return window. Record the relevant dates separately, including when the order was placed and when the customer received it.
- Read the terms for the product and region. Record the customer's reason, any final-sale restriction, evidence of item condition, required inspection and any documented exception with its approver.
Why
A receipt can establish the purchase date while leaving the delivery date unknown. If the policy counts from delivery, the receipt alone cannot establish whether the request arrived in time. For an unopened-item rule, keep the customer's account and the warehouse inspection as distinct records. Write a specific hold question when either date or condition remains unclear. Route contested policy, warranty or consumer-rights claims to a qualified owner for review.
Reconcile units, payments and open returns
Goods received and money refunded each need their own evidence.
What to do
- Start with fulfilled quantity for the exact order line. Deduct completed physical returns and quantities reserved on open returns once each, based on distinct current records.
- Check for duplicate provider events and superseded revisions before adding quantities or amounts. Keep separate returns on the same line when the records show they are distinct.
- Look for an active record for the same request. Carry its return authorization or refund reference into a follow-up and use that record to check the current status.
- Record the exact quantity received for this request and the current financial limits. Check the remaining item credit and how much cash is still refundable on the order after posted and pending refunds.
Why
An order can have a cash refund for an item the customer kept, and a return can be open while the parcel is still in transit. Treating either event as evidence of the other risks issuing excess credit or booking inventory that never arrived. If two new requests share the same remaining units, use the supplied review order and record how much each supported proposal reserves on your worksheet. Keep a proposed reservation separate from a reservation already recorded in the store.
Calculate the supported refund or exchange
Every amount in a proposal needs a traceable source and room within the current balance.
What to do
- Use the item's recorded tax-inclusive credit after actual discounts. For a uniform per-unit credit, multiply that value by the supported return quantity to get the gross item credit.
- Subtract the documented fee and, for an exchange, the recorded total for the replacement. Use the positive balance as the proposed refund or the absolute value of a negative balance as the amount to collect.
- Tie the exchange allocation, a stock commitment for a specific replacement, to the intended variant, location and exact quantity. Check that the same reservation is free of other commitments.
- Send uncertain fees, shipping adjustments, mixed currencies and discounts with unclear item allocations to the owner for an exact calculation. When goods are still in transit, record what is pending before assigning a ready refund amount.
Why
A partial refund is limited by both the credit left on the item and the cash still refundable on the order. Dividing an order total evenly across items can misstate the credit when the items had different prices, discounts or taxes. Flag any amount between the currency's supported increments for owner review. Check shared balances again after adding each supported proposal.
Prepare the decision queue and customer drafts
Each case needs a clear decision, an owner and a specific next action.
What to do
- Put supported proposals, existing-record follow-ups and cases awaiting evidence in one review queue. Show the order line, policy basis, quantity, amount and owner action on each row.
- Use documented response commitments and verified case dates to set the review order. Keep cases with unknown timing visible and label any part of the queue that is shown only in the full export.
- Draft the customer reply with the item, proposed outcome and next step. For a hold, ask for the one fact that can move the case forward, such as the date the parcel arrived.
- Give the owner the provider record needed to confirm each action. Track the replacement reservation, payment, stock decision and customer contact with the evidence appropriate to each.
Why
A customer who is waiting for an exchange needs to know whether to send the item, wait for an inspection or confirm a replacement. A reply that implies a refund has cleared can create a second dispute if the owner has yet to execute it. Mark drafts as pending execution and use an existing contact reference when following up. For a possible decline or exception, give the qualified reviewer the policy clause and the facts still in doubt.
Review the evidence before anyone acts
The reviewer should be able to reconstruct the decision from the records in the case.
What to do
- Trace each consequential proposal to the applicable policy version, timing event, exact variant, inspection and latest payment and return records.
- Check quantities across the full queue and compare refund and collection amounts to the source-backed calculation. Check fees, the currency and the evidence for each replacement.
- Review the customer draft alongside the queue row and remove any promise the record cannot support. Confirm that held cases name the evidence or decision required.
- On a later run, compare each stable case ID to the new records. Recheck approval when the policy, quantities or amounts have changed, and keep a case open for verification if it disappears from the export.
Why
A proposal can be correct when you prepare it and become stale after a teammate posts a refund or reserves a replacement. Retain approvals and execution receipts with their dates so a later reviewer can tell what happened. A refund receipt verifies the payment action. Warehouse receipt, exchange shipment and customer contact each need their own confirmation before you mark those steps complete.
Common mistakes
- Starting the window from the invoice dateUse the policy's named event and record a verification question if the corresponding date is missing.
- Counting the same return twiceReconcile repeated provider events and keep completed returns distinct from quantities reserved on open requests.
- Estimating item credit from the order totalUse the recorded line credit after tax and discounts and send unclear allocations for owner calculation.
- Promising a replacement from general stockVerify an allocation tied to the request and the exact variant before offering a ready exchange.
- Treating a draft as a completed actionKeep proposals, approvals and execution records distinct so a later run can use current facts.
What a good result looks like
- Each case names the purchased variant and cites the policy clause and event date that govern eligibility.
- Completed and active returns reconcile to fulfilled quantity, with the current request isolated from prior records.
- Every proposed amount traces to the item credit, documented fee, exchange total if applicable and remaining balance.
- Any unresolved case names a precise question and identifies who can answer it.
- Draft replies describe the supported next step and stay unsent pending owner action.
And then what? Using the result
- Assign eligible cases to the owners who can confirm reservations, issue refunds or arrange exchanges, and record their decisions.
- Ask for the missing evidence listed on held cases, starting with known customer response commitments.
- Match execution receipts to the approved request and record the actual quantity and amount before refreshing the queue.
- Send the reviewed customer reply after checking that its wording matches what has happened and what the customer should do next.
- Use repeated holds to identify which purchase, delivery or inspection records your team needs to capture more consistently.
When to run it
- After a batch of returns arrivesMatch warehouse receipts to specific requests and compare received quantities with what the customer asked to return.
- When one order has several open requestsReconcile the shared item and payment limits before an owner approves another case against the order.
- After a return policy changeKeep the effective dates and policy versions on hand so you can check requests for purchases made under earlier terms.
- When a customer asks about an existing casePull the original return or refund record and use it to prepare a status update with the next concrete step.
Questions people ask
How does returns processing work?
Match the request to the purchased item, verify eligibility and condition, reconcile prior returns and refunds, then prepare a supported proposal for owner review. Include the evidence and a customer reply that reflects the next action.
When does the return window start?
It starts from the event named in the applicable return policy. If the rule uses delivery or customer receipt, get credible evidence of that date and hold the timing decision while it remains unresolved.
How do you calculate a partial refund?
Start with the recorded credit for the eligible quantity and subtract any exact applicable fee, subject to the remaining item credit and refundable order balance. If item discounts or taxes make the allocation unclear, ask the owner for the source-backed amount.
What evidence do you need to approve an exchange?
Verify that the requested item qualifies, the original goods meet the required receipt and condition checks, and the exact replacement is reserved for this case. Confirm any difference to refund or collect from the recorded item credit, fees and replacement total.
What should you do if a return is already open?
Follow up on the existing record using its original ID. Check its status and any related payment or warehouse events before drafting the next update.
Who reviews a disputed return decision?
A qualified owner should review disputed eligibility, warranty claims or claims that depend on local consumer rights. Give them the applicable policy text, evidence and specific point to decide before communicating a final outcome.
More jobs in E-commerce
Prepare return and exchange decisions, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac