A pricing error took your listing inactive
This is the inactive listing that confuses people most, because the stock is there, the product is fine, and nothing about the error mentions price unless you go looking.
Four separate gates can deactivate a listing over price: your own minimum and maximum settings, a low-price check, a high-price check, and the fair pricing policy. The listing shows as inactive with stock intact, which is why it reads as a mystery. Check your own min and max settings first, because they are the most common cause and the only one entirely within your control.
- The stock is untouched. Only the offer is switched off, which is why it looks inexplicable.
- Check your own minimum and maximum price settings before anything else.
- A price inherited from a bulk upload in the wrong column is a frequent cause.
- Reactivating without changing the price usually just deactivates it again.
- Repricer software and a manual edit fighting each other produces a flapping listing.
An inactive listing with full stock sends sellers to the inventory, which is the one place the answer is not. Price has its own set of gates, and each of them can switch an offer off without saying much about why.
Your own settings, which people forget they set
Amazon lets you define a minimum and a maximum price per listing, and an offer priced outside that band is not shown. These are usually set once, often long ago, sometimes by a tool rather than by hand, and then forgotten. A cost increase that pushes your price above an old maximum deactivates the listing with no policy involved at all.
This is the first thing to check because it is the most common and the easiest to fix, and because the other three causes are all about Amazon's view of your price rather than your own constraint.
The low-price gate
A price far below what Amazon's systems expect for the product triggers a check, on the reasoning that an implausibly low price is more often an error than a bargain. The classic version is a decimal point or a unit mistake, where a price meant per pack arrives per piece.
A bulk upload is the usual vector. A price column that landed one position out, or a figure that arrived as text, produces a value nobody intended, and the listing is switched off before any buyer sees it. That is the system working correctly, even though it feels like an obstruction.
The high-price gate and the fair pricing policy
A price far above the usual range triggers the opposite check. Amazon also operates a fair pricing policy, which compares your price against external references and recent history, and an offer judged materially out of line can be deactivated.
The important practical difference is that your own min and max are a constraint you set, while these are judgements Amazon makes against information you cannot see. You can price back into the acceptable range, but you cannot read the threshold, so the honest approach is to price by your own economics and treat a deactivation as a signal that something is far out rather than marginally so.
The two tools fighting each other
A repricer adjusting prices automatically, plus a manual edit, plus a bulk upload on a schedule, will contradict one another. The symptom is a listing that goes inactive and active repeatedly with nobody obviously doing anything, because each system is correcting what it sees as the other's mistake.
If a listing flaps rather than failing once, stop looking for a policy cause and find out how many things are authorised to write a price. The answer is usually more than one and often more than two.
Working through it in order
First, read your own minimum and maximum settings on that listing. Second, look at the price that is actually live rather than the one you believe you set, because a bulk upload may have changed it. Third, compare it against what the same product sells for elsewhere, which tells you whether you are far out or marginally out. Fourth, count the systems that can write a price.
Reactivating without changing anything is the one step worth skipping. If the gate deactivated it once on that price, it will do so again, and each cycle makes the history harder to read.
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, how to list your products the one publicly readable Amazon.in page that states listing figures: title 200 characters, images 500x500 or 1,000x1,000. Read 16 October 2026.
- 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. Read 16 October 2026.
- Amazon India seller forums where the failure shapes described here are reported by sellers. Read 16 October 2026.
Not legal or tax advice. Amazon changes fees, windows and policies without notice, and the detailed style guides and account-health thresholds 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 first.
Questions sellers ask
Because price has its own gates, separate from inventory. Four of them can switch an offer off: your own minimum and maximum price settings, a low-price check, a high-price check, and the fair pricing policy. The stock is untouched, which is why the inventory is the one place the answer is not.
Your own minimum and maximum price settings on that listing. They are the most common cause, they are entirely within your control, and they are usually set once and forgotten, so a cost increase that pushes your price past an old maximum deactivates the listing with no policy involved.
Because an implausibly low price is more often an error than a bargain, so Amazon checks it. The usual vector is a bulk upload where the price column landed one position out or a figure arrived as text, producing a value nobody intended. The listing is switched off before a buyer sees it, which is the system working.
You can, and if the price has not changed the same gate will deactivate it again, while each cycle makes the history harder to read. Find out which gate caught you and change the input rather than re-enabling the output.
Almost always more than one system is authorised to write a price: a repricer, a manual edit and a scheduled bulk upload will contradict each other, each correcting what it reads as the other's mistake. If the listing flaps rather than failing once, count the writers before looking for a policy cause.
Related seller guides
More on the operations, money and claims that decide whether a marketplace catalogue actually makes money.
Amazon low price error and what actually triggers it
A low price error is usually a unit mistake rather than a pricing decision. The four input mistakes that cause it, and why reactivating without a change fails.
Amazon high price error, and the cost increase behind it
A high price error often means your costs moved and the listing did not. What triggers it, why a stale maximum setting makes it worse, and what to check.
Amazon minimum and maximum price settings, and the trap in them
These two fields are the most useful pricing protection Amazon gives you and the commonest cause of a listing nobody can explain. How to set them so they age well.
Amazon listing uploaded with no error and showing nowhere
A clean processing report does not mean a live listing. The six states an uploaded listing sits in while buyers cannot see it, and how to tell them apart.
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.
Amazon main image rules, white background and what breaks it
The main image carries stricter rules than the rest, and breaking them gets a listing suppressed rather than flagged. What is settled, what is convention, and how to diagnose a rejection.
Amazon Easy Ship label printing and what goes wrong
Most Easy Ship label problems are a browser, a printer driver or a scale issue rather than Amazon. The order to check them in, and the one that risks a rejected handover.
Amazon error 8541, your attributes match an existing ASIN
Error 8541 is often not an error. Amazon found the product already in its catalogue. How to check whether you are already live on that page.