The Amazon cancellation rate counts yours, not the buyer's
This is the account-health metric with the simplest cause and the most confusion around it, because sellers assume every cancellation counts and only one kind does.
The cancellation rate counts orders you cancelled before dispatch, not orders the buyer cancelled. That makes it an inventory accuracy metric wearing a fulfilment name: nearly every seller cancellation happens because the listing sold something the shelf did not have. Fix the count, not the cancelling.
- A buyer cancelling before dispatch does not count against you. Yours does.
- So it is really a stock accuracy metric, not a fulfilment one.
- Multi-channel selling without a shared stock count is the usual root cause.
- Cancelling to avoid a late dispatch trades one metric for a worse one.
- The threshold everyone quotes is convention; the dashboard is authoritative.
Of the account-health metrics this one has the clearest mechanism, and sellers still misread it, because the word cancellation covers two very different events and only one of them is counted.
Only seller cancellations count
If a buyer changes their mind and cancels before dispatch, that is not a defect and it does not feed the metric. If you cancel, it does. The rate is a measure of how often you accepted an order and then could not or would not fulfil it.
That distinction is worth checking in your own reports before concluding the metric is unfair, because a seller convinced that buyer cancellations are the cause is looking at a number that does not include them.
Which makes it a stock accuracy problem
Almost every seller cancellation comes from the same place: the listing offered something the shelf did not have. The order was legitimate and acceptance was legitimate; the count was wrong. So the lever is the accuracy of the quantity you publish, not the diligence with which you cancel.
The common sources of an inaccurate count are selling the same stock on more than one marketplace without a shared figure, a manual count updated on a cadence slower than orders arrive, damage or shrinkage that was never deducted, and a single unit held back for a photograph and never returned to the count.
Multi-channel selling, the dominant cause in India
A seller listing the same stock on Amazon, Meesho and AJIO with three independently maintained quantities will oversell, and the only question is how often. The arithmetic is unforgiving: three channels each believing they hold the last unit produces a cancellation roughly whenever two of them sell it.
The structural answers are a single source of truth that all channels read, or a deliberate buffer that keeps each channel's published quantity below the real one. A buffer wastes some availability and it is cheap compared with an account-health problem.
The trade sellers make by accident
Faced with an order it cannot ship on time, a seller sometimes cancels rather than dispatch late, reasoning that one metric is better than another. That reasoning is backwards. A late dispatch is recorded and recoverable; a cancellation is a defect on a metric with a lower tolerance, and the buyer is left without the thing they bought either way.
If the stock genuinely does not exist then cancelling is the only honest option and the metric is correctly recording a real failure. The point is that cancelling to protect the dispatch number is choosing the worse of the two.
What to actually do this week
Pull your own cancellations for the last month and sort them by cause rather than by date. In most catalogues they concentrate on a handful of SKUs, usually the fastest-moving ones shared across channels, and that list is the whole project.
The threshold at which this metric becomes dangerous is widely quoted and not published on any Amazon.in page you can open; the seller-performance and account-health paths both returned 404 when checked on 14 October 2026. Your Account Health dashboard shows the target for your account.
Where this sits in the rest of your Amazon operation
Robnu is read-only on Amazon today: orders, returns, payouts and inventory sync so you can see and reconcile them, and it cannot accept Amazon orders or make their labels. Order processing is live for AJIO and Meesho. Related reading:
Sources & further reading
- Amazon India seller performance page checked 14 October 2026 and it returns 404, as does the account-health path. No public Amazon.in page states these thresholds, which is why they are described here as market convention.
- Amazon India Seller University the public training hub. It serves, and it does not publish the account-health thresholds.
- Amazon listing and image style guides login-gated. It redirects to Amazon sign-in, so the detailed rules it holds are not quoted here and are described as market convention instead.
Not legal or tax advice. Amazon changes fees, windows and policies without notice, and the detailed style guides sit behind a Seller Central login, so any figure quoted here as convention is not Amazon-published. Check anything you plan to act on against your own Seller Central account or flat-file processing report first.
Questions sellers ask
No. The metric counts orders you cancelled before dispatch, not orders the buyer cancelled. A seller convinced that buyer cancellations are driving the number is looking at a figure that does not include them, which is worth checking in your own reports before concluding the metric is unfair.
Because it is really a stock accuracy metric. Nearly every seller cancellation happens because the listing offered something the shelf did not have, so the lever is the accuracy of the quantity you publish rather than the care you take when cancelling.
Selling the same stock across Amazon, Meesho and AJIO with independently maintained quantities. Three channels each believing they hold the last unit will oversell, and the only question is how often. The answers are a single shared stock figure or a deliberate buffer below the real quantity.
No, and this is a common reversal. A late dispatch is recorded and recoverable; a cancellation is a defect on a metric with a lower tolerance, and the buyer goes without either way. If the stock genuinely does not exist, cancelling is the honest option, but cancelling to protect the dispatch number is choosing the worse outcome.
Not published on any Amazon.in page you can open. The seller-performance and account-health paths both returned 404 when checked on 14 October 2026 and the detail sits behind a Seller Central login, so quoted figures are market convention. Your own Account Health dashboard shows the target that applies to you.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
Amazon late dispatch rate and the handling time trap
Most late dispatch problems are a handling time set optimistically rather than a warehouse that is slow. What the metric measures, and the settings that quietly cause it.
AJIO order cancellations: types, costs and prevention
Buyer, seller and system cancellations decoded, what each one costs, the stale-stock root cause behind most of them, and the discipline that keeps your rate down.
Amazon bullet points, how many and how long each should be
Amazon's public page states no bullet count and no character limit at all. What it does say, what the category guides hold, and how to write bullets that answer the objection instead of listing features.
What goes in an Amazon description when you have A plus content
The description and A plus content overlap, and which one a buyer sees is not always your choice. What to put where, and what Amazon publishes about limits, which is nothing.
Amazon order defect rate, what counts and what does not
ODR is three separate things counted as one, and sellers usually watch the wrong one. What feeds it, the lag that makes it look wrong, and why the threshold is not publicly citable.
Meesho bulk label download: 100 orders labelled in minutes
Downloading Meesho labels one order at a time does not scale. Here is the batch dispatch workflow, bulk-select ready-to-ship orders, generate labels and invoices as one merged PDF, print, and manifest without touching each order.
Bulk Invoice Download on Amazon: Generate GST Invoices at Scale
Downloading Amazon GST invoices one order at a time does not scale. Here is how bulk invoice generation works, why it matters for GST filing, and how Robnu handles it end to end.
Meesho orders stuck in pending: what it means and how to clear them
Blocked does not mean paused, the dispatch clock usually keeps running. The four causes, which two you can fix yourself, and what to document when you cannot.