Ungating on Amazon: The Process and the Evidence It Wants

What ungating actually is, mechanically

Amazon restricts selling in certain categories and under certain brands by default — not because the product is banned, but because the category or brand carries a higher risk of counterfeit, safety, or authenticity problems. Ungating is the approval process that removes that restriction for your specific account, for that specific category or brand. It's account-specific and, importantly, not automatic: getting ungated in one category doesn't ungate a different one, and a brand approval through Brand Registry doesn't automatically ungate you for other brands you may also sell.

The restriction shows up in two forms worth telling apart: a category-level gate, applied broadly to a product type regardless of brand, and a brand-level gate, tied specifically to one brand's products across categories. Which one you're facing changes what evidence actually clears it, so identify which type is blocking the listing before gathering documentation.

The evidence Amazon actually checks, in detail

The core requirement across most ungating requests is the same, whether the category is toys, jewelry, automotive parts, or a restricted brand under Brand Registry: an invoice or receipt from an authorized source — a manufacturer, an authorized distributor, or in some cases a wholesaler — dated within the last 90 to 365 days depending on category, showing your business name matching your seller account, the specific product or a close match, and a quantity consistent with commercial selling rather than a single retail purchase. Amazon's automated and manual reviewers are checking whether the supply chain is real and traceable back to a legitimate source, not whether the product itself is good. A single invoice for one unit from a marketplace reseller typically doesn't satisfy this; a purchase order or invoice from the brand or an authorized distributor usually does.

A worked example of a request that gets approved

Take a seller applying to sell in a gated category with an invoice from a regional distributor showing 200 units purchased under an account name that matches the seller's business name exactly, dated four months prior. That request typically clears review without much friction, because every element checks out against what the reviewer is verifying: matching name, plausible commercial quantity, recent date, and a source Amazon can independently confirm is authorized to distribute that brand or category. Compare that to a request submitted with a personal credit card receipt for three units from a general retailer — same category, same seller, but none of the verification elements are present, and it typically comes back denied even though the products themselves are identical.

What separates these two outcomes isn't the product — it's entirely the paper trail behind it. That's genuinely worth internalizing before ever applying: the review is a documentation check first, and a product-quality argument, however true, doesn't substitute for it.

The common mistake: applying before the paperwork exists

The most common reason an ungating request fails isn't a policy problem — it's applying before securing the right invoice. Sellers sourcing from a marketplace themselves, or from a supplier that won't issue a business-name invoice, apply anyway hoping the request gets approved on the strength of the product listing alone. It usually doesn't. The fix is sequencing: confirm your supplier can issue a proper invoice — business name, product, commercial quantity, recent date — before submitting the request, not after a denial reveals the gap. This is slower up front and faster overall, because a denied request that gets reapplied with the same weak documentation just produces the same denial.

The arithmetic makes the sequencing worth it: a request submitted with a weak invoice that gets denied, then reapplied with a corrected invoice two weeks later because the supplier needed to reissue it, costs two full weeks of not selling in that category. The same two weeks spent confirming the supplier can issue proper paperwork before the first submission produces an approval on the first try, at the same total elapsed time but without a denial on the account's request history.

What to do when a request is denied

A denial notice usually names what was missing — most often "insufficient invoice information" or a mismatch between the invoice name and the account name. Read it literally: if the account name doesn't match, that's a legal-entity or DBA mismatch worth fixing with your supplier before resubmitting, not a reason to argue. If the quantity looks too low, request a consolidated invoice covering a larger recent purchase rather than resubmitting the same document. Reapplying with the identical invoice that was already flagged doesn't produce a different outcome — the fix has to close the specific gap the denial named, and most denials do name it.

If your business operates under a legal name different from the name your customers or suppliers know you by, resolve that mismatch once, in writing with your supplier, rather than repeatedly explaining it case by case — it's a recurring, avoidable friction point across ungating requests, invoice-based reimbursement claims, and most other document-checked processes on the account.

Where ungating sits inside broader case management

Ungating requests are casework in the same sense as a suspension appeal — diagnosis of what's actually required, evidence gathering, filing through the right channel, and escalation if the first attempt is denied. Full Circle has managed more than $500M in Amazon spend across 100+ brands, and the pattern across that book is consistent: requests fail on documentation, not on eligibility, far more often than sellers expect. Dr. Shield runs ungating requests as part of its case-management work — first 30 days free, priced on the call — diagnosing what a specific supplier's paperwork needs to look like before a request goes in, not after it comes back denied.

Strong documentation improves the odds of a fast, favorable review; it doesn't remove Amazon's discretion. Every request is still reviewed and decided against Amazon's own criteria for that specific category, and a genuinely ineligible or unverifiable supply chain won't clear approval no matter how carefully or persuasively the request itself is written.