Refunded Orders
Track and analyze all refunded orders, monitor incoming returns with carrier tracking, and understand your refund trends with detailed breakdowns.
Difficulty: 🟡 Intermediate · Reading time: ~15 min
Open this page in your dashboard: Go to Refunded Orders →
📋 Overview
The Refunded Orders page gives you full visibility into every return and refund across your Amazon accounts. Track the financial impact, monitor in-transit returns with carrier tracking, analyze refund reasons, and export data for reporting.
Returns are an unavoidable part of selling on Amazon, but they do not have to be a black box. This page transforms raw refund data into actionable intelligence, helping you reduce return rates, recover costs where possible, and catch product or listing issues before they escalate.
📊 Key Performance Indicators
Net Impact
Total refund cost minus any reimbursements received
Your true bottom-line loss from returns
Label Costs
Shipping and return label expenses
Reveals the hidden cost beyond product refund value
Items Refunded
Total number of items returned
Tracks return volume independently of financial impact
Avg Value Per Return
Average cost per refund transaction
Identifies whether high-value or low-value products drive most returns
Reading the KPI Cards
Each card shows the current value for your selected date range plus a comparison percentage against the previous equivalent period. For refund KPIs, remember:
Net Impact going up = more money lost to refunds (bad)
Label Costs going up = shipping costs for returns are increasing (bad)
Avg Value Per Return going up = your more expensive products are being returned more often (investigate immediately)
Warning: Do not look at Net Impact in isolation. A Net Impact increase could simply mean your sales volume grew (more sales = more returns in absolute terms). Always check your refund rate alongside Net Impact to distinguish between volume growth and a genuine quality problem.
Pro tip: Set a personal threshold for each KPI. For example: "If Net Impact exceeds 4% of revenue or Avg Value Per Return exceeds EUR 25, I investigate immediately." Having predefined thresholds prevents you from normalizing gradually worsening numbers.
📈 Charts
Refund Volume Trend
A line/area chart showing refund volume over time, helping you identify trends, seasonal spikes, or issues with specific products.
What to look for:
Gradual upward trend: May indicate a slow-developing quality issue, or could simply track with sales growth. Check the percentage rate, not just absolute numbers.
Sudden spikes: A spike 2-3 weeks after a product launch often points to listing inaccuracy (customer expectations vs. reality mismatch).
Seasonal patterns: Returns typically spike in January (post-holiday), and after Prime Day. These are expected and normal.
Day-of-week patterns: Some categories see higher Monday returns (customers returning weekend impulse purchases).
Context matters: Amazon's return window is typically 30 days. A spike in refunds today may relate to orders placed 2-4 weeks ago. Always look back at your order data for the corresponding period.
Return Reasons Distribution
A bar chart breaking down returns by reason category. Available for FBM orders where return reason data is provided by Amazon.
Common return reason categories and what they signal:
Not as described
Listing does not match product reality
Audit listing images, bullet points, and A+ content
Defective / Does not work
Product quality issue
Contact supplier, check batch quality, review QC process
Wrong item sent
Fulfillment or labeling error
Audit FNSKU labels and fulfillment workflow
No longer needed
Impulse purchase or buyer's remorse
Generally not actionable; monitor for unusual volume
Better price found
Competitive pricing issue
Review pricing strategy and competitor landscape
Arrived too late
Shipping or delivery delay
Check carrier performance and shipping SLA compliance
Unauthorized purchase
Potential fraud or shared account purchase
Monitor for patterns; may warrant fraud investigation
Note: Return reasons are only available for FBM (Fulfilled by Merchant) orders. FBA return reasons are managed by Amazon and visible in Seller Central's FBA returns report. SellerMagnet pulls what Amazon's API makes available.
Pro tip: If "Not as described" accounts for more than 20% of your returns, this is a high-priority fix. Improving listing accuracy is one of the highest-ROI actions you can take, it simultaneously reduces returns, improves reviews, and boosts conversion rate.
Incoming Returns (FBM)
For FBM orders, a dedicated Incoming Returns section shows returns currently in transit back to your warehouse.
Each incoming return card displays:
Order ID and date
Status badge (Incoming, etc.)
Product preview: Image, title, SKU (Stock Keeping Unit)
Carrier badge: Branded carrier icon (DHL, UPS, FedEx, DPD, Hermes, GLS, etc.)
Tracking number and a Fetch live status button (see Live Carrier Status below)
📡 Live Carrier Status
Live carrier tracking is wired into three places on the Refunds surface, and every one of them opens the same shared Live carrier status modal (marked Beta). The button only appears on rows that already carry a tracking number; the modal queries the carrier on demand (it does not auto-fetch) when you click Fetch live status.
Incoming Returns card
A full-width Fetch live status button on each return parcel in transit
Refunds Table row
A compact Fetch live status button in the Carrier cell
Detail side panel
A Fetch live status button on the Live status row inside Return Shipment Details
Whichever entry point you use, the modal shows the same live read of the return shipment:
Status badge
Current carrier status: Delivered, In transit, Out for delivery, Undelivered, Exception, Info received, Pending, Expired, or Not found
Delivery verdict
A plain-language read of on-time-vs-late - Delivered on time, Delivered late (by N days), Delivered, or Awaiting delivery confirmation
Tracking number
The tracking ID in monospace
Route
Origin → destination with country flags
Date tiles
Carrier, service, transit days, and shipped / delivered dates when available
Tracking timeline
A chronological checkpoint list (event, date/time, and location) so you can follow the return's journey
Coverage: Live tracking spans 1,600+ couriers worldwide. If a return has no tracking number yet, the row shows an Awaiting tracking placeholder instead - the live status activates as soon as the buyer ships the return.
Supported Carriers
SellerMagnet automatically detects and displays branded badges for 20+ carriers:
Pan-European
DHL, UPS, FedEx, DPD, GLS
Germany
DHL, Hermes, DPD, GLS
UK
Royal Mail, Hermes/Evri, DPD UK, Yodel
France
La Poste, Colissimo, Chronopost, Mondial Relay
Italy
Poste Italiane, BRT, SDA
Spain
Correos, SEUR, MRW
Netherlands
PostNL, DHL Parcel NL
Poland
InPost, Poczta Polska
Pro tip: Check the Incoming Returns section daily if you manage FBM orders. Knowing when a return will arrive lets you plan inspection, restocking, and inventory adjustments. Products returned in sellable condition can be relisted faster, reducing your out-of-stock window.
Incoming Returns Workflow
Automation idea: If you consistently receive returns in non-sellable condition from a specific product, consider tagging it with a "High Return Risk" tag (see Product Tags) so your team knows to inspect it carefully before restocking.
Refunds Table
Where to focus first: Sort by Return Reason. Reasons like "Not as described" or "Defective" point to listing or product quality issues you can fix. Reasons like "No longer needed" or "Better price found" are normal, every seller gets these.
The main data table provides a detailed, sortable, and filterable view of all processed refunds.
Marketplace
Country flag
Refund Date
When the refund was processed
Order ID
Clickable Amazon order identifier
Products
Number of products in the return
Status
Incoming, Processed, or Label Only
Carrier
Carrier badge with tracking number and a Fetch live status button
Return Reason
Reason provided by buyer (FBM) or Amazon (FBA)
Net Impact
Financial impact in your account currency
Actions
View full details in side panel
Status Definitions
Incoming
Amber
Return is approved/in transit or awaiting delivery: a label exists but no product refund has posted yet
Refunded / Processed
Green
A product refund has posted (the return has been settled)
Label Only
Indigo
Only a return label or adjustment cost exists, with no product refund (the buyer may not send the item back)
Quick win: Filter the table by "Label Only" status periodically. These are cases where the customer requested a return but may not have sent the item back. Amazon may still have issued a refund. If the return window has passed and no shipment was made, you may be eligible for a reimbursement through Amazon's SAFE-T claim process.
Detail Side Panel
Click any row to open a detailed breakdown. The panel stacks several cards, each answering a different question about the refund - from "what shipped back" to "what did this actually cost me."
Return Shipment Details: Order ID, date, status, and a Live status row with the Fetch live status button
Order Overview: Original sale vs. refund, line by line (see below)
Net Impact: Your real economic loss, with the sellable/damaged split (see below)
Cash Flow Details: The full per-item breakdown of every credit and charge (see below)
Timeline History: Animated timeline showing each step of the return process (return initiated -> label created -> shipped -> delivered -> refund processed)
📦 Items Recovered vs. Items Written Off
The plain-English version: A returned unit that comes back Damaged can't be sold again, so you lose what you paid for it - its cost (COGS) is written off as a real loss. A unit that comes back Sellable goes back on the shelf to sell again, so there is no COGS write-off. Same refund to the customer either way; the difference is whether you also lost the product.
The heart of the panel is the distinction between units that came back sellable (recovered to inventory) and units that came back damaged (written off as a loss). SellerMagnet splits each refunded line into:
Items recovered (sellable): These units returned to your inventory and can be sold again. Their cost (COGS) is not written off.
Items written off (damaged): Amazon returned these as damaged. Their cost is lost, so it counts against your Net Impact.
Each line shows a source badge indicating where the sellable/damaged decision came from, resolved in this priority order:
Manual
You set the disposition by hand using the override control (below)
FBA scan
Amazon's FBA returns scan reported the unit's condition (e.g. sellable, customer-damaged, carrier-damaged, defective)
SKU default
A per-SKU "returns sellable" default you configured on the product
Project default
Your project-wide default, used when nothing more specific applies
Override control (Auto / Sellable / Damaged)
Each refunded line that has a linked cost batch carries an Override sellable / damaged control with three options:
Auto
Follows the automatic resolution (FBA scan → per-SKU default → project default). The currently active source is shown in parentheses next to the option, e.g. Auto (FBA scan)
Sellable
Forces all refunded units on this line to count as recovered - COGS is not written off
Damaged
Forces all refunded units to count as written off - COGS is lost
Why set an override? The override changes the refund's Net Impact - but only when the project setting "Include COGS in refund Net Impact" is on. With that setting on, units marked Damaged add their cost to your loss, while units marked Sellable do not. Use the override when you know better than the automatic source: for example, Amazon's scan flagged a unit as damaged but you inspected it and it is perfectly resellable (set it Sellable to stop overstating your loss), or a unit was returned "sellable" but arrived broken (set it Damaged to capture the real loss).
No cost batch, no override. The override only appears on lines that have a cost batch linked on the Products page. Without a linked cost, there is no COGS to write off, so the toggle would have no effect and is hidden. If you see "Inventory loss not tracked," add a cost batch to that product to start counting it.
Order Overview card
This card lays out the original sale against the refund so you can see exactly what the customer paid, what came back, and what they kept. It is a four-column table (Original, Refunded, Kept) with these rows:
Items (net)
Item price excluding VAT
VAT on items
VAT charged on the items
Shipping (net)
Shipping charge excluding VAT
VAT on shipping
VAT charged on shipping
Gross total
Sum of the above
A coverage pill below the table summarizes whether this was a Full refund, Partial refund, or No refund yet, alongside how many units of the order were refunded.
Net Impact card
This card is the headline summary - your real economic loss from this refund. It walks through each component so you can trace the math:
Items written off
COGS of the damaged units (carries the source badge). Shows a zero/placeholder when COGS is excluded by your project settings or no cost batch is linked
Amazon's net fees
The net of Amazon's fee adjustments on the refund (labelled "Amazon's net fees (gross)" when a VAT-reclaim line is present)
VAT reclaim on Amazon fees
The reclaimable VAT portion of Amazon's gross fees, shown only when applicable - it is not a real P&L cost, so it offsets on your VAT return
Other adjustments
Any remaining credits or charges
Total Net Impact
The bottom-line figure
Why the cash refund is excluded: A discreet "Customer refund (cash only)" line shows the cash paid back to the buyer, but it is excluded from Net Impact. It reverses the original sale revenue and the VAT pass-through (which offsets on your VAT return), so only your real out-of-pocket losses are counted in the total.
Cash Flow Details card
The final card is the full per-item breakdown - every credit and charge that makes up the refund, humanized into plain labels (for example, Items refunded (net), VAT / Tax refunded, Referral fee refund, Return label postage). Each refunded line shows its Items recovered (sellable) and/or Items written off (damaged) split with the COGS write-off, the override control, and a Return label & adjustments section for shipping and label charges. Use this card when you need to reconcile the Net Impact figure down to the individual line items.
Using the Detail Panel for Investigations
When investigating a specific return:
🔍 Filters
Marketplace
All Marketplaces, or multi-select specific ones
All
Date Range
Today, Yesterday, L7D, L30D, MTD, YTD, L6M, L12M, Last Year, Custom
Last 30 days
Custom Dates
Calendar picker with range selection
:
Pro tip: Use the Custom Dates filter to isolate refunds from a specific product launch window. For example, if you launched a new product on March 1st, set the date range to March 1-31 to see the first-month return profile. A return rate above 8% in the first month is a red flag worth investigating.
📤 Export
Click Export CSV to download all refund data matching your current filters, including marketplace, dates, products, reasons, carrier info, and financial impact.
The export includes these columns:
Marketplace, Refund Date, Order ID
Product Name, SKU, ASIN (Amazon Standard Identification Number), Quantity
Return Reason, Status, Carrier, Tracking Number
Refund Amount, Label Cost, Net Impact
Use case: Export your refund data monthly and import it into a spreadsheet to build a rolling 12-month return analysis. This makes quarterly business reviews and supplier negotiations much more data-driven.
Scenario: Your Return Rate Suddenly Jumped 15%
You open the Refunded Orders page and notice your refund rate has increased from 4% to 4.6% (a 15% relative increase). Here is a systematic investigation workflow:
Step 1: Determine the Scope
Filter by marketplace: Is the spike across all markets or isolated to one?
Check the date range: When did the spike start? Narrow down to the exact week.
Step 2: Identify the Cause Products
Sort the Refunds Table by product: Are 1-2 products responsible for most of the increase?
Check the Return Reasons chart: Has a specific reason category grown?
Step 3: Investigate Root Cause
One product drives 70%+ of new returns
Product quality or listing issue
Pull the listing, inspect inventory, fix listing
"Not as described" spiked
Recent listing change
Revert listing changes made in the past 2 weeks
"Defective" spiked
Bad batch from supplier
Quarantine current inventory, contact supplier
Returns spread across many products
Shipping/fulfillment issue
Check carrier delays, packaging quality
Spike only in one marketplace
Market-specific issue
Check local reviews, competitor activity
Step 4: Take Action and Monitor
Implement the fix
Set a calendar reminder to check the refund rate again in 7 and 14 days
If the rate has not returned to baseline within 2 weeks, escalate the investigation
Warning: Do not ignore a 15%+ refund rate increase even if absolute numbers seem small. Amazon monitors return rates at the ASIN level, and a high return rate can lead to listing suppression, removal of the "Fulfilled by Amazon" badge, or in extreme cases, ASIN deactivation.
Weekly Refund Review Process
Follow this template every week to stay proactive about returns:
Monday Review (15 minutes)
Open Refunded Orders, set filter to L7D
Check KPI cards: Compare Net Impact and Items Refunded against last week
Scan the Refund Volume Trend: Any unusual spikes mid-week?
Review Return Reasons chart: Any category growing disproportionately?
Check Incoming Returns: Are there deliveries expected this week?
Monthly Detailed Analysis (30 minutes)
Set filter to L30D
Export CSV and calculate refund rate per SKU
Rank products by return rate: Flag anything above 5%
Cross-reference top returners with customer reviews: Are reviews mentioning the same issues as return reasons?
Calculate label cost trends: Are shipping costs per return increasing?
Update product tags: Tag products with "High Return Rate" if above threshold (see Product Tags)
Quarterly Business Review Data
Total refund Net Impact as a percentage of revenue
Top 5 returned products with root cause analysis
Return reason distribution trend (quarter over quarter)
Label cost trend
Actions taken and their impact
🔄 Before & After: Systematic Refund Management
Before (Reactive Approach)
A seller checks refunds only when they notice a cash flow issue. By the time they investigate, a defective product batch has been selling for 6 weeks. Result: 340 returns, EUR 8,500 in refund costs, 47 one-star reviews, and a listing health warning from Amazon.
After (Proactive Weekly Review)
The same seller implements a weekly Monday review using SellerMagnet's Refunded Orders page. In week 2 of the same scenario, they spot a "Defective" return reason spike for one ASIN. They immediately:
Pull 120 remaining units from FBA inventory for inspection
Contact the supplier with defect evidence
Pause PPC for the affected ASIN
Result: 45 returns (vs. 340), EUR 1,100 in refund costs (vs. EUR 8,500), 8 negative reviews (vs. 47), and no listing health warning. The supplier covered the defective batch cost.
⚠️ Common Mistakes to Avoid
Mistake 1: Ignoring "Label Only" refunds
When Amazon issues a returnless refund or the customer gets a label but never ships, you lose the product AND the money. Regularly filter for "Label Only" status and file SAFE-T claims for items never returned after the return window closes.
Mistake 2: Not tracking label costs separately
Label costs add up quickly, especially for heavy or oversized items. A EUR 15 product with a EUR 6 return label effectively has a 40% return cost overhead. Factor label costs into your product profitability calculations.
Mistake 3: Treating all returns as equal
A return for "no longer needed" is fundamentally different from "defective." The first is normal buyer behavior; the second is a quality alert. Separate your analysis by return reason to avoid false alarms or missed real problems.
Mistake 4: Not correlating returns with listing changes
If you updated product images, titles, or bullet points recently and returns spike with "not as described," the listing change likely created a mismatch between customer expectations and reality. Always note listing change dates and check returns 2-4 weeks later.
Mistake 5: Forgetting FBA reimbursement claims
Amazon sometimes damages returned inventory or loses it in the warehouse. Check your FBA reimbursement reports regularly. SellerMagnet's Net Impact calculation accounts for reimbursements, so if your Net Impact seems high relative to refund volume, you may have unreimbursed losses.
## 🔧 Troubleshooting
No refunds showing in the table
No refunds in selected period or marketplace
Expand date range; check marketplace filter
Carrier badge shows "Unknown"
Carrier not recognized from tracking number format
The tracking link still works; badge is cosmetic only
Return reason shows blank
FBA order (reasons managed by Amazon)
Check Amazon Seller Central FBA Returns report
Net Impact seems too high
Reimbursements not yet processed by Amazon
Wait 5-7 business days; Amazon processes reimbursements in batches
Incoming Returns count does not match table
Incoming section shows FBM only
FBA returns are managed by Amazon and may not show as "incoming"
Export CSV is empty
Filters too restrictive
Reset filters to All Marketplaces + L30D and try again
Timeline in side panel is incomplete
Return still in progress
Check back later; timeline updates as events occur
❓ FAQ
How quickly do refunds appear after Amazon processes them?
Refund data typically appears within 2-4 hours of Amazon processing the refund. The Incoming Returns section updates more frequently as carrier tracking data changes.
Can I dispute a return through SellerMagnet?
SellerMagnet is an analytics and tracking tool. To dispute a return or file a SAFE-T claim, you need to do so through Amazon Seller Central. However, SellerMagnet provides all the data you need to build your case (order details, tracking info, timeline).
Why does my refund rate differ from Amazon Seller Central?
SellerMagnet calculates refund rate as (refunded orders / total orders) for the selected period. Amazon may use different calculation methods or timeframes. Small differences (under 1 percentage point) are normal.
Are partial refunds included?
Yes. Partial refunds appear in the table with the actual refunded amount. The Net Impact KPI reflects the true financial impact including partial refunds.
Can I see which warehouse received the return?
For FBM returns, the return destination is your configured return address. For FBA returns, Amazon manages warehouse routing and this information is available in Seller Central's FBA inventory reports.
How do I track refunds for multi-pack or bundle products?
Refunds are tracked at the order item level. If a customer returns one item from a bundle, it shows as a partial return with the corresponding refund amount. The product breakdown in the side panel shows exactly which items were returned.
Is there a way to get alerts for high refund rates?
Automated alerts are on the roadmap. In the meantime, we recommend the weekly Monday review process described above. You can also tag high-risk products using Product Tags for easy filtering.
💡 Tips
Pro tip: Monitor your refund rate KPI closely. A sudden increase may indicate a product quality issue, listing inaccuracy, or shipping problem that needs immediate attention. Set your personal red-flag threshold at a 10% relative increase week-over-week.
Use the Return Reasons chart to identify the most common reason for returns. If "Not as described" is high, review your product listings for accuracy. This single action can reduce returns by 20-40% for affected products.
Pro tip: When negotiating with suppliers, export your refund data for their products and present the defect return rate. Concrete data strengthens your position for quality improvement demands, cost credits, or improved QC processes.
Seasonal awareness: Return rates naturally increase in January (post-holiday returns) and after Prime Day. Do not panic if your January refund rate is 1-2 percentage points above normal. Compare against the same period last year for a fair benchmark.
➡️ What's Next?
Orders AnalyticsProducts ManagementLast updated