Amazon Paid Review Requests: Prep Before Late-October Beta

Paid Ad vs Free Button: What Actually Changed

Review Requests is a paid advertising product with bidding and budget controls. It is not the free Request a Review button. That is the whole headline. The two things do similar jobs but run on different rails.

The free Request a Review button lives in Seller Central. It sends an Amazon-written request one order at a time. No bid, no budget, no targeting. The new paid ad shows a review invitation to recent verified buyers while they browse Amazon's highest-traffic pages. You pay to reach people who already bought from you.

There is a third compliant method worth naming for context. Vine lets you enroll a product that has fewer than 30 reviews and make up to 30 units available to reviewers. Vine covers roughly the first 30 reviews only. So the three tools sit at different stages.

These each have different rules and costs. Confirm the current details for Vine and the Request a Review button on Amazon's own pages before you lean on either, since rules change.

Who Can Run It: Eligibility and the 1,000-Review Ceiling

The beta is open to registered sellers and vendors with an advertising console account in good standing, and the account must have no active policy violations. It is US-only for now.

The product rule is the part you have to watch. Products qualify only while they have fewer than 1,000 total ratings and reviews. Amazon checks eligibility at campaign creation and again during the campaign. Campaigns pause automatically once a product hits the 1,000 threshold.

• Account in good standing with no active policy violations.
• Registered seller or vendor with an advertising console account.
• Product under 1,000 total ratings and reviews at creation and during the run.
• US marketplace only in this beta. Amazon plans more marketplaces and properties in future releases.

Campaigns are created in Amazon's AI chat-style campaign tool, the one introduced at its unBoxed event. They can also be managed through the Unified Campaign Management API. Review Requests campaigns extend existing endpoints on that API, so teams that already automate campaigns have a path in.

What the Buyer Actually Sees: The One-Tap Flow

The buyer sees a module built for speed. Based on Amazon's illustrative mockups, the flow has three steps. Live layout may differ once the beta ships, so treat this as the shape, not the final pixels.

• Step 1. A module titled "How was your purchase?" with a Sponsored label, the product image, a purchase-date badge, and five empty stars.
• Step 2. Tapping a star submits the rating in one tap. The module then shows "Rating submitted" with an Edit link and a "Create review" button.
• Step 3. The optional written review opens a sheet with a star rating, a text box with a character counter, a slot for a photo or video, a required review title, and Submit.

Read the design. A rating is one tap, so more buyers finish it. A written review takes effort, so fewer will bother. That tells you what to expect from the output. Expect more star ratings than detailed written reviews. And the ad does not guarantee anything positive. Customers can leave one star, five stars, or nothing at all.

The Cost Blanks Amazon Left

Here is the honest part. Amazon has not told you what this costs. It said the same bidding and budget controls from other campaign types apply, but it has not published a minimum bid, a pricing benchmark, or an expected volume of invitations.

• No minimum bid disclosed.
• No price benchmark disclosed.
• No expected number of invitations disclosed.
• No detail on which pages carry the ad module, beyond calling them highest-traffic pages.

Do not build a budget on numbers Amazon has not shared. When the beta opens, the cost per rating is the thing to watch first, because that is what decides whether this beats free. Until then, plan around a capped test, not a growth channel.

Why ROAS Math Breaks for a Review Ad

Standard ROAS math does not apply here. You are not buying attributed orders. You are buying a detail-page asset. The reviews live on the product detail page and affect future shoppers who never saw the ad.

That changes how you judge spend. A normal ad either produces a sale you can attribute or it does not. This ad produces a review that sits on your page and nudges conversion for weeks. So the right question is not "what was my return on ad spend this week." It is "what did it cost me to generate one more rating, and did my conversion and review pace improve against a clean baseline."

• Track cost per incremental rating, not attributed order value.
• Expect the payoff to show up in conversion over time, not in the campaign report.
• Set a maximum cost per incremental rating you are willing to test before enabling anything.

Reading the '3x' Claim With Caution

Amazon ran a closed-beta test from June 3 to June 21, 2026 and claims it produced about 3x more ratings and reviews per week. That number sounds great. Read it carefully before you plan around it.

• The 3x is an internal closed-beta claim attributed to Amazon, not a forecast for your catalog.
• The comparison is each product's own prior pace, not a controlled comparison against a holdout.
• Amazon did not disclose the number or type of products, the spend, the bid amounts, the shopper frequency, or whether a randomized control group existed.

A claim with that many unknowns is a reason to test small, not a reason to go big. Your product, your buyer cohort, and your price point will move this number. Prove it on your own catalog with your own baseline.

You may also see third-party promos quoting figures like 24% or 23.8% conversion lift from listing video. Those come from a third-party promotional insert and are not about Review Requests. Do not mix them into your decision.

Staying on the Right Side of Amazon's Review Policies

The ad itself is compliant by design. Amazon controls the invitation and limits it to recent buyers, which separates it from off-platform review clubs. The ad asks verified purchasers for authentic feedback, and it does not buy positive ratings.

The risk is what you do around it. If you follow Amazon's invitation with your own message that asks only happy buyers to review, that is review gating. Review gating is a policy problem even if the ad is fully compliant. Do not pair the campaign with your own gating messages.

• Let Amazon's invitation stand on its own.
• Do not steer customers to review only if they are happy.
• Do not pair the campaign with a discount or free product in exchange for a review.

If you want to clean up reviews the right way, the compliant path is removal of rule-breaking reviews, not gating. We cover that in Amazon review removal and the escalation most sellers skip.

Baseline Before You Bid: How to Measure It

Because the ad builds a page asset instead of attributed orders, you need a clean before-picture. Record your baseline before you launch anything. If you skip this, you will never know if the spend worked.

Export these per eligible ASIN before launch:

• Weekly review count and written-review share.
• Average rating.
• Refund rate and customer contact rate.
• Conversion rate.
• Current ad and promotion spend.

Then pick a comparable eligible ASIN that is not running the campaign as a control. Run a fixed test period. Compare the test ASIN against its own prior period and against the control ASIN. That is how you separate the ad's effect from normal seasonality.

A This-Week Checklist Before the Beta Opens

You have until late October to get ready. Here is the short list. Do it now so you can decide fast when the beta goes live.

• Confirm your advertising console account is in good standing with no active policy violations.
• Identify eligible ASINs under 1,000 total ratings that have accurate detail pages and available inventory.
• Pick a stable product with a large recent-order cohort for a capped test, not just your lowest-review ASIN. The invitation goes to recent buyers, so a bigger recent cohort gives the test room to work.
• Export baseline metrics for each test ASIN before launch.
• Choose a comparable eligible ASIN as a control.
• Set a maximum cost per incremental rating you will accept before enabling anything.
• Set and cap the budget, and keep this spend separate from proven acquisition campaigns.
• Document who can create campaigns and change bids.
• Avoid pairing the invitation with any review-gating message.
• Plan a fixed test period and the exact comparison you will run after.

One more thing. Before you send any buyer back to a detail page, make sure the page earns the click. If you want a refresher on what moves conversion there, read how customer reviews affect Amazon SEO rankings.

Conclusion

Review Requests is a paid version of a thing you could already do for free, with wider reach and a one-tap rating flow. The reach is the selling point. The cost is the open question, and Amazon has not answered it. So the smart play is simple. Get your account and your eligible ASINs ready now, record a clean baseline, cap a small test, and judge it on cost per incremental rating, not on ad report ROAS.

Do not gate reviews around it, and do not plan a budget against Amazon's 3x claim. Test it on your own catalog against a control. If the cost per rating is lower than the value of a review to your conversion, keep it. If not, the free button and Vine are still there. For more on the review system itself, see how Amazon's review system works for sellers, and if you are chasing early reviews, start with compliant ways to increase reviews on your listing.

Frequently Asked Questions

References

1. Amazon Ads: Get product reviews faster with Review Requests
2. Amazon Vine program overview
3. Amazon Seller Central: review and feedback policy reference
4. Amazon Ads: improve your products for advertising