An Amazon hazmat review happens when catalog information, whether it's a description, bullet point, or image, signals that a product may qualify as a dangerous good.
Amazon's dangerous goods team then pauses the listing until documentation proves otherwise, and sellers typically have a narrow window, often two to four business days depending on the trigger, to submit a safety data sheet or an exemption sheet.
Most sellers treat this as a paperwork problem, something to hand off to whoever answers email fastest, but a hazmat flag is a signal that your catalog data has a structural gap, and if that gap isn't fixed, the same ASIN or its variations will get flagged again.
This article breaks down what actually happens during a review, why the SDS-versus-exemption sheet decision carries more weight than sellers expect, and how to stop the cycle before it drains a full quarter of sales velocity.
It is important to understand that Amazon does not physically inspect your product before flagging it, that would be impossible with all the products that are in their catalog, but the dangerous goods team relies almost entirely on catalog information, meaning your product description, bullet points, data on the backend, and images are the actual inputs into the classification engine.
This is the detail sellers consistently underestimate. A vague description doesn't reduce scrutiny, it increases it, because Amazon's system defaults to caution when it can't confirm what a product is or isn't.
Three patterns show up most often.
Related: Amazon Stranded Inventory — Merchant Fulfilled (DG info required)
External resources:
Once a review starts, the timeline is unforgiving, and it does not pause for weekends or your team's bandwidth. Amazon's stated Service Level Agreement (SLA) is two business days for products with complete and accurate documentation, but that clock only starts once you've submitted something reviewable.
.png)
Additionally, rejected documents restart this clock entirely, so every resubmission requires another full two-business-day review, and a single formatting error in your SDS can cost a seller a week or more of paused fulfillment.
And if inventory is already sitting in a fulfillment center when the flag hits, Amazon gives you 14 business days to respond before disposing of the stock at your expense.
An SDS, or Safety Data Sheet, is required if your product is or might be classified as dangerous goods, and it must be issued within the last five years and include a product name that matches your listing exactly.
Note: An exemption sheet is the correct path only when the product genuinely contains no harmful chemicals or is a battery-powered item that qualifies for exemption.
The trap is assuming the exemption sheet is the easier option.
In practice, an exemption sheet requires a full ingredients list, and sellers sourcing from trading companies or overseas manufacturers often find their supplier doesn't have one, particularly when the supplier is reselling rather than manufacturing.
At that point, the only route forward is a paid lab analysis, which adds weeks and real cost to a problem that started as a documentation gap.
Sellers also assume their manufacturer can produce an SDS on demand. Many can't, particularly trading companies that resell rather than manufacture, and by the time this gets discovered mid-review, there usually isn't enough runway left to source one before the deadline hits.
Once documentation clears review, Amazon assigns one of three outcomes, and each carries a different operational cost.
The P&L impact compounds fastest with Restricted DG, because sellers frequently discover their hazmat storage allocation is already consumed by other ASINs, and expanding that limit through Seller Central Support is not guaranteed, requests from larger sellers tend to get approved more often than requests from smaller catalogs.
External resources:
It is important to know that once a product has undergone classification, it remains subject to re-review indefinitely, and a new review can be triggered simply because another seller on the same listing submitted conflicting ingredient information.
This means a variation, a co-listing seller, or even an outdated bullet point buried in an old flat file can reopen a case you thought was finished months ago, and this is where catalog structure and hazmat exposure intersect directly.
Poorly managed variations, orphaned child ASINs, or inconsistent flat file data across a catalog create multiple points of failure, any one of which can trigger a new review cycle. A seller managing this reactively, one flagged ASIN at a time, will always be a step behind. A seller who audits catalog consistency across the full listing family closes those failure points before Amazon finds them.
Documentation is only one side of hazmat compliance since Amazon also requires specific prep standards for anything classified or suspected as hazmat, and getting this wrong at the warehouse level creates a second failure point separate from the classification review itself.
For example:
Note: Amazon recommends sellers validate packaging with a three-foot drop test, five consecutive drops onto concrete, covering the top, bottom, largest side, a bottom corner, and the longest bottom edge, because Amazon will not run this test on your behalf, and if your packaging fails in the field instead, expect refusal, return, or repackaging fees charged back to your account, plus new prep requirements applied retroactively.
The sellers who handle hazmat reviews without losing weeks of sales velocity share one trait, they treat it as a catalog issue. That means maintaining current SDS documentation for every chemical- or battery-adjacent SKU before listing, keeping ingredient and battery language consistent across all variations, and knowing in advance whether a supplier can produce compliant documentation on a four-day clock.
For sellers managing this without dedicated backend support, the pattern is predictable: a flag hits, someone scrambles to find the right internal contact at the supplier, documentation comes back incomplete or mismatched, and the resubmission clock resets.
Multiply that across a catalog with dozens of hazmat-adjacent SKUs, and the lost fulfillment time adds up to real revenue, not just an administrative headache.
This is the exact gap Online Seller Solutions closes for sellers. Our Amazon Pay-Per-Project Service covers the full scope of what a hazmat cycle actually requires, correcting the backend catalog data that triggers repeat reviews, restructuring variations so orphaned child ASINs stop reopening closed cases, and recovering suppressed listings fast within Amazon's existing review windows instead of restarting the clock.
An Amazon hazmat review is rarely about the product itself, it's about whether your catalog data gives Amazon a reason to ask questions. Sellers who treat documentation as a one time task keep getting pulled back into the same cycle, a flag, a scramble, a partial fix, and a reopened case months later.
The pattern is predictable because the underlying cause never gets addressed.
A resubmitted SDS fixes one ASIN for one review cycle, but it doesn't address inconsistent bullet points, mismatched flat-file data, or orphaned variations elsewhere in the catalog that will eventually trigger the next flag. Sellers who only respond to the ASIN in front of them are managing symptoms, not the source.
The sellers who stay ahead of it build consistent, accurate catalog data across every variation and keep compliant documentation ready before Amazon ever asks. They also know their supplier's documentation capabilities before a deadline forces the question, and they track dangerous goods storage utilization before it becomes a bottleneck during a launch.
That shift, from reactive to structural, is what protects sales velocity and keeps a hazmat flag from becoming a quarter long distraction. It's also the difference between a seller who resolves a hazmat review in days and one who loses a full sales cycle untangling the same issue for the third time.