Review Gating: Why It's Banned and What to Do Instead

Review gating means steering customers toward different review outcomes based on satisfaction or expected sentiment. The familiar pattern sends happy customers to a public review page and unhappy customers to private support. Amazon's review policies and the FTC's marketer guidance reject selectively soliciting people expected to be positive. Use one neutral path instead.

Review gating: the rule, verbatim

Amazon's official Policy Reminder: Product Packaging and Inserts states:

“Directing customers to contact you instead of leaving a negative review on Amazon is also prohibited.”

Amazon's Customer Product Reviews Policies also prohibit asking for positive reviews, soliciting reviews only from buyers who had a positive experience, asking customers to change or remove reviews, or otherwise attempting to influence them. A recent response from an Amazon community manager specifically warned that a questionnaire filtering or funneling the experience before an Amazon review may be treated as review gating.

The FTC reaches the issue from a consumer-protection perspective. Its guide for marketers says not to request reviews only from customers expected to be positive. The FTC's final Consumer Review Rule summary also addresses specified forms of review suppression and misleading claims about whether displayed reviews represent the submitted feedback. Amazon's platform policy may be stricter or apply differently from federal law, so both must be reviewed.

What's allowed and what's not

Use a neutral process	Avoid a gated process
Give the same review invitation to the defined eligible audience without predicting who will be favorable, subject to Amazon's review policies.	Ask “Are you happy?” and show the Amazon review link only after “yes” or a high rating.
Offer a separate support route to every customer, before and after any feedback request.	Send low-scoring customers to private support while high-scoring customers receive the public-review prompt.
Collect product feedback for improvement without making public-review access depend on the answer.	Require a survey, score, or testimonial screen before revealing the review destination; Amazon's community manager guidance flags this filtering risk.
Measure support resolution and opt-in consent separately from public review activity.	Reward teams or vendors for suppressing negative feedback or increasing ratings through selective routing.

The important unit of review is the complete flow. Button text can be neutral while code makes the outcome conditional. Test every branch using low, middle, and high scores; positive and negative free text; support and no-support choices; and mobile and desktop paths. Record the final destinations. A flow is not transparent if only the designer knows which answers unlock a review request.

Real consequences of review gating

Amazon's current official Product Reviews Policy reminder lists review removal, product delisting, withdrawal of selling privileges, withholding funds, and potential legal action among responses to detected review manipulation. It also says prohibited activity can result in enforcement against reviews, listings, accounts, or brands.

The FTC's Consumer Review Rule Q&A says courts may impose civil penalties for knowing rule violations. Not every instance commonly called review gating necessarily maps to the same provision or consequence; context matters, and FTC staff guidance is not a safe harbor. The correct response is not to promise a particular penalty. It is to eliminate sentiment-based selection and obtain legal review when a business displays, suppresses, or republishes customer reviews.

There is also a data-quality consequence that requires no statistic: a filtered review program cannot faithfully show what the invited customer population said because invitation and destination depend on predicted sentiment. That makes the resulting rating a poor operational signal even before enforcement is considered. Customer support teams lose useful information when negative experiences are treated primarily as ratings to suppress.

How to do this compliantly

Define the eligible audience before looking at sentiment. Use objective criteria tied to the transaction and approved Amazon workflow, not satisfaction scores, support outcomes, customer value, refund history, or language suggesting likely praise. Document exclusions and the reason for each one so reviewers can detect hidden selection.

Create independent lanes. The support lane should be obvious and available to everyone. A separate feedback lane may collect information the brand uses to improve products. If an Amazon review request is used, follow Amazon's approved process and do not condition access on earlier answers. Do not ask a customer to update or remove an existing review after support resolves a problem; Amazon's customer-review policy specifically restricts those requests.

Audit the implementation, not just the mockup. Export decision rules, test every branch, scan every QR code, and inspect automated follow-ups. Confirm that a negative answer does not remove a public-review option that a positive answer receives. Confirm that support agents, agencies, and review tools cannot manually select only satisfied buyers.

For customer ownership, focus on earning a direct relationship through a transparent and separately reviewed consent experience, useful product education, and reliable service. An owned audience should not be built by using private feedback to manipulate Amazon reviews. Keep opt-in status, support history, and review solicitation as distinct records with distinct purposes. That separation makes the journey easier to explain to a customer, an approver, and Amazon.