Returns Processing Checklist

Per-return workflow for an e-commerce returns coordinator: receive the RMA, inspect the unit, determine refund vs. exchange vs. reject, restock or dispose, and update reason-code reporting. Built for DTC and marketplace sellers using a returns platform like Loop or AfterShip.

4 sections 12 steps Collects data
1

Receiving and Inspection

  1. Match the parcel to its RMA

    • Scan the inbound tracking or RMA barcode in Loop / AfterShip Returns / Returnly to pull up the original order. Reject parcels with no RMA on file — drop-shipped returns or wrong-address returns are common at high volume and shouldn't be processed blind.

    Collects text Collects text Collects list
  2. Inspect the unit against return-window policy

    • Confirm the return is within the policy window (typically 30 or 60 days from delivery). Check tags, hygiene seals, original packaging, and accessories. Flag worn / washed apparel, opened consumables, or missing pack-ins for the next decision step.

  3. Photograph damage or discrepancies

    • Photos protect against chargeback disputes and feed the quality team's defect tracking. Capture the SKU label, the damage area, and any signs of customer use. Attach to the RMA record so the dispute team has evidence if the customer claims they returned it new.

    Collects image
  4. Tag the return reason code

    • Use a consistent reason taxonomy (sizing, defect, not-as-described, changed mind, damaged in transit, wrong item shipped). Reason-code discipline is what lets the merchandising team find the SKU driving a returns-rate spike from 3% to 12%.

    Collects list
2

Resolution Decision

  1. Determine the resolution path

    • Apply the policy matrix: refund to original payment if within window and unworn, store credit for late returns, exchange if requested and stock available, reject if outside policy or clearly used beyond inspection. Escalate fraud-pattern customers (serial returners, wardrobing) to the CX lead.

    Collects list Collects paragraph
  2. Issue the refund in the payment processor

    • Refund through Shopify Payments / Stripe / PayPal so the funds return to the original payment method — never via a separate gift card unless the customer explicitly requested store credit. Confirm the refund amount nets restocking fees if your policy applies them.

  3. Notify the customer of the rejection

    • Send a Gorgias / Zendesk macro citing the specific policy reason (outside 30-day window, clear signs of wear, missing original packaging) with the inspection photos attached. Offer a goodwill option (10% off next order) when appropriate to avoid a public review escalation.

3

Disposition and Inventory

  1. Grade the unit for disposition

    • Grade A goes back to sellable stock; Grade B routes to the open-box / outlet channel; Grade C is liquidation or B-stock pallets; Grade D is destroy / recycle. Apparel returned without tags but unworn typically grades B regardless of policy — don't recirculate as new.

    Collects list
  2. Update on-hand in the OMS

    • Increment sellable stock in Cin7 / SkuVault / NetSuite for Grade A units; route Grade B/C to the appropriate location code so they don't show as available on the storefront. Multi-channel sellers must verify the update propagates to Amazon, eBay, and Walmart inventory feeds.

  3. Pick and ship the exchange unit

    • Generate the exchange order in ShipStation with the original order referenced. Push tracking back into Loop / AfterShip so the customer's return portal shows the outbound. Exchanges past day 1 of receipt drive the bulk of negative reviews on the returns experience.

    Collects text
4

Reporting and Trend Review

  1. Log the return in the weekly dashboard

    • Push the closed RMA to the returns dashboard (Triple Whale, Glew.io, or a Sheets pull from Loop). Per-SKU returns rate, reason mix, and resolution-cost-per-return are the three numbers the merchandiser needs at the Monday review.

  2. Flag SKUs over the returns-rate threshold

    • Any SKU above 8% returns rate over a rolling 30 days goes on the merchandising review list. The product manager investigates root cause: sizing chart wrong, PDP images misleading, manufacturing defect batch, or marketing claim mismatch. Sustained spikes warrant pulling the listing until corrected.

    Collects paragraph

Use this template

Copy it to your account, customize the steps, and run it with your team in minutes.

Use this workflow Start free trial
Sections 4
Steps 12
Category E-commerce
Price Free to start
Need a different process

Browse hundreds of free templates across every team and industry.

Back to template library

Related templates

More workflows your team can run.

E-commerce

CRM Setup Checklist

View
E-commerce

E-commerce Expense Management Checklist

View
E-commerce

Live Chat Operations Checklist

View
E-commerce

Daily Operations Checklist

View

Run Returns Processing Checklist with your team

Customize the steps, assign roles, set a schedule, and keep a complete record for every run.

Use this workflow Start free trial