Every review request tool on the market says it is "100% compliant." Most of them are, because Amazon left them almost nothing to be non-compliant with. The risk is not in the tool; it is in the second message you send.
Review requests are the one part of Amazon operations where the rules are short, explicit and enforced by the system itself, and where sellers still manage to get restricted. This post states the policy first, because everything about automation follows from it, then covers the tools, the timing and the edges where a reasonable-sounding idea becomes a violation.
Evolve Media Agency runs review programs for clients and Bear Basics, the brand I own; we use these tools and are not paid by any of them. Policy statements are from Amazon's Communication Guidelines, the Request a Review help pages and the Selling Partner API documentation as summarized by sources checked September 16, 2026; Seller Central's current text governs. No response-rate statistics are quoted, because published ones are vendor-reported and vary by category; our own experience is described qualitatively. Not legal advice.
The Policy In One Table
| Method | Status | Conditions | Risk |
|---|---|---|---|
| Request a Review button, manual | Permitted | Once per order; 5-30 days after delivery; Amazon writes and sends it | Lowest |
| Automation of the button via the SP-API | Permitted | Tool must call Amazon's Solicitations endpoint, which enforces the same limits; no scraping or browser bots | Low |
| Custom message via Buyer-Seller Messaging | Permitted with conditions | Counts as the one request; no incentives, no steering, no positive-review ask, no marketing, follows formatting rules; not to buyers who opted out | Medium |
| Button plus custom message, same order | Prohibited | Two requests for one order | Reported 30-day proactive-messaging restriction |
| Package insert asking for a review | Permitted | Neutral ask only; nothing conditioned on the experience; no incentive; no diverting unhappy buyers away from reviewing | Low to medium, depends entirely on the wording |
| Warranty or registration insert | Permitted | Collected email may not be used to ask for Amazon-order reviews | Low if the list is kept separate |
| Email outside Amazon about an Amazon order's review | Prohibited | Uses buyer contact information Amazon restricts | High |
| Incentives, discounts, gifts, refunds for reviews | Prohibited | n/a | Suspension and review removal |
| Asking only happy buyers; asking to change or remove a review | Prohibited | n/a | High |
| Friends, family, staff, review groups, purchased reviews | Prohibited | n/a | Account-ending |
The rest of this post is that table expanded. The review strategy guide covers the whole program (Vine, the listing itself, responding to reviews); this post is the request mechanics only.
What The Request A Review Button Is
Request a Review. A button on each order's details page in Seller Central that sends an Amazon-generated, non-editable message to the buyer asking for a product review and seller feedback. Amazon writes the text, translates it into the buyer's preferred language, sends it from Amazon rather than from the seller, and includes no seller contact option. It is available once per order, between 5 and 30 days after the delivery date, and is withheld for cancelled or refunded orders and for buyers who have opted out of unsolicited seller messages. It is the lowest-risk review request Amazon offers because the seller controls nothing but the timing.
Three properties matter for automation. You cannot change the words, so there is no wording risk. Amazon enforces the window and the once-per-order rule at the system level, so an attempt outside them fails rather than violating anything. And the message goes out under Amazon's name, which is part of why buyers respond to it: it reads as the platform asking, which it is.
The API Behind It
The existence of the endpoint is the answer to "is automation allowed": Amazon built the automation path itself. What Amazon did not build is any way to change the message or exceed the limits, and a tool that claims to do either is either lying or doing something you do not want done under your account.
What "Compliant Automation" Means
- Uses the Solicitations API, authorized through an SP-API app you approve in Seller Central, with the messaging permission scope. You can see and revoke it under Manage Your Apps.
- Checks eligibility per order before sending, so cancelled, refunded and opted-out orders are skipped rather than attempted.
- Sends once and records it, so a manual click later on the same order cannot double up (the API would refuse, but the log is how you know).
- Lets you set timing by ASIN or product group within the window, which is the one variable you control.
- Lets you exclude orders by condition: open cases, returns initiated, negative seller feedback already left, specific SKUs.
- Does not also send a custom message for the same order, or offers a custom-message feature with a hard block against sending both.
- Does not touch buyer contact information beyond what the API returns, and does not export it.
Any tool meeting that list is doing what a diligent employee with a spreadsheet would do, at scale. Any tool exceeding it is doing something Amazon's system was designed to prevent.
The Tools That Do It
| Tool | Where It Lives | Fits | Note |
|---|---|---|---|
| Jungle Scout (Review Automation) | Inside the Jungle Scout suite | Sellers already on Jungle Scout | Button automation with timing and exclusions; no custom messaging, which is a feature |
| Helium 10 (Follow-Up) | Inside Helium 10 | Sellers on Platinum or above | Automates the button and can send custom Buyer-Seller messages; use the button mode only, or enforce the one-request rule yourself |
| FeedbackWhiz | Standalone | Higher-volume sellers wanting review monitoring plus requests | Button automation plus review alerts and order-level exclusions |
| SageMailer | Standalone | Small and mid sellers | Button automation and templated messaging; same caution as Helium 10 |
| FeedbackFive (eComEngine) | Standalone | Sellers who also want seller-feedback management | One of the longest-running; button automation with per-SKU rules |
| Sellerboard | Inside the profit tool | Sellers already using it for P&L | Button automation included; convenient if it is already connected |
| Salesbacker | Standalone | Sellers who want only this | Button automation with per-ASIN timing campaigns; simple by design |
They all call the same endpoint and send the same message, so the differences are exclusions, timing controls, reporting, and whether they also offer custom messaging you should mostly ignore. Pick the one already in your stack; there is no data advantage to any of them because the data is Amazon's. Prices are not listed here because they change and because the decision should not turn on a few dollars a month.
Timing: When To Fire The Request
Timing is the only lever, so it gets the most thought. The principle: ask after the buyer has used the product enough to have an opinion, and before they have forgotten the purchase.
The mistake in both directions: day 5 for everything, which asks people to review a box they have not opened, and day 21 for everything, which loses the buyers who would have reviewed on day 8. Per-ASIN timing is the one place the tools earn their fee. For Bear Basics, a balm gets asked at day 6; the client's collagen supplement gets asked at day 18.
Which Orders To Exclude
Amazon excludes cancelled, refunded and opted-out orders for you. The exclusions you add are about not asking someone with a problem to rate you, which is both decent and, since asking only happy buyers is prohibited, a line to walk carefully.
- Orders with an open case or return request. Not because they might review badly, but because the request is tone-deaf while a problem is open. Solve the problem; the tool can re-check eligibility after the case closes if the window is still open.
- Orders where the buyer has already left seller feedback or a review. The request would be redundant.
- Orders with a delivery exception or a very late delivery. Same logic as the open case.
- Specific SKUs you do not want reviewed yet: a listing with a known defect batch, a product being discontinued, a variation being relaunched.
Excluding orders with an open problem is operational courtesy. Excluding orders because a survey, an insert reply or a message suggested the buyer is unhappy, so that only satisfied buyers get asked, is review steering, and it is prohibited whether a tool does it or a person does. The test: are you excluding the order because of a service situation, or because of the buyer's predicted rating? The first is fine. The second is a violation.
Custom Messages: The Narrow Lane
Amazon's Communication Guidelines permit a seller-written review request through Buyer-Seller Messaging, subject to conditions, and that permission is where most restrictions originate. The conditions, in plain terms:
Where Buyer-Seller Messaging remains useful is everything else it is for: answering questions, resolving problems, and sending required information about the order. Keep it for that, and let the button do the asking.
Inserts, Warranty Cards And Off-Amazon Email
"We'd appreciate an honest review on Amazon" is fine. "If you love it, leave 5 stars" is prohibited. "Not happy? Contact us first" is prohibited, because it diverts. A QR code to the product's review page is fine; a QR code to a survey that routes by rating is not.
A free gift, a discount, a warranty extension or a giveaway entry offered for a review, on an insert or anywhere, is the prohibited category Amazon enforces hardest. An extended warranty offered to all buyers with no review condition is fine; tying it to the review is not.
Collecting an email for warranty registration or a how-to guide is allowed. Using that email to ask for a review of the Amazon order is not; it uses contact information the buyer gave for another purpose to do what Amazon restricts. Keep the list for support and your own store's marketing.
Amazon restricts the use of buyer contact information obtained through Amazon orders. An email or text outside Amazon asking for an Amazon review is a violation regardless of how the address was obtained.
The insert is worth getting right because it is the one channel that reaches the buyer at the moment of use, before the button does. The unboxing and packaging playbook covers inserts as a whole; the review ask is one neutral line on it.
What Gets Sellers Restricted Or Suspended
| Behavior | Typical Consequence | How It Usually Happens |
|---|---|---|
| Two requests for one order | Proactive messaging restriction (reported at 30 days) | Tool sends a custom message and a person clicks the button, or two tools connected to one account |
| Messaging opted-out buyers | Messaging restriction; warnings escalate | Custom messages sent outside the API's eligibility check |
| Positive-review asks or steering language | Policy warning, then messaging restriction, review removal | "If you're happy" in a template or insert |
| Incentives | Review removal, listing suppression, account suspension | Insert offering a gift card or free product for a review; giveaway entries |
| Off-Amazon contact for reviews | Policy violation; suspension risk | Warranty email list used for review campaigns |
| Manipulation (friends, family, groups, purchased) | Account termination; funds withheld; legal action in documented cases | Detected through address, payment, IP and behavioral overlap |
| Browser-bot automation of Seller Central | Account access flags; terms violation | A "tool" that logs in as you rather than using the API |
The first two rows are the ones that catch honest sellers, and both come from running a custom-message tool alongside the button. The fix is structural: one tool, button mode only, and nobody clicking manually. The account health guide covers what to do if a warning arrives, and the Section 3 appeals guide covers the serious end of the table.
What To Expect From A Compliant Program
Honest expectations, without a vendor's response-rate chart. A compliant Request a Review program, fired at the right time on every eligible order, reliably raises the share of orders that produce a review compared with doing nothing, and it raises seller feedback more than it raises product reviews, because the message asks for both and feedback is the easier click. In our client work the effect is a few reviews per hundred orders where there were fewer before, the size of the gain depends on the product more than on anything the tool does, and it plateaus: once every eligible order is asked at a sensible time, there is nothing left to optimize in the request.
What moves the number after that is outside the request: a product that surprises people, packaging worth mentioning, an insert that asks neutrally at the moment of delight, and a listing whose claims match the experience so the review is not a correction. The negative review response playbook covers the other half of the program. Review requests are plumbing. Necessary, boring, and not a strategy.
The Ecom Profit Box
Our library of ecommerce growth guides, including the review strategy and account health frameworks behind this post.
Get It FreeAudit Your Review Requests
Bring your messaging setup, your insert and your tool. We will check each against the Communication Guidelines, set timing per ASIN, and remove anything that could earn a restriction.
Book A CallThe Setup Checklist
The counterweight, since we run these programs: this is a settings screen in a tool you probably already pay for, and the whole thing takes an afternoon. Nobody needs an agency to click "enable." What is worth outside help is the product and the listing that make people want to review, and the insert wording that stays on the right side of a line Amazon draws finely. Set the automation up yourself; spend the money on what the buyer sees.
Amazon wrote the message, set the window and built the endpoint. Automation is allowed because it can only do what Amazon already lets you do by hand. Everything you add is where the risk is.
What To Remember
- One review request per order by any method, 5 to 30 days after delivery; Amazon enforces both at the system level for the button and the API.
- Automation is permitted through the Selling Partner API's Solicitations endpoint, which sends the identical Amazon-written message; browser-bot "automation" of Seller Central is a terms violation.
- Every compliant tool sends the same message, so choose by exclusions, per-ASIN timing and what is already in your stack; there is no data advantage.
- Timing is the only lever: about a week for most goods, sooner for consumables, two to three weeks for complex products and supplements with an effect window, never past day 28.
- Exclude orders with open problems; never exclude by predicted rating, because asking only satisfied buyers is review steering.
- Custom messages are permitted in a lane so narrow they add risk without adding words; use the button for asking and Buyer-Seller Messaging for service.
- Inserts may ask neutrally and may not condition, incentivize or divert; warranty emails stay separate; off-Amazon review requests are prohibited; incentives and manipulation end accounts.
Where This Came From
- Amazon Seller Central: Communication Guidelines, the Request a Review help page, the Customer product reviews policies, and the Selling Partner API Solicitations reference (login required; cited by name). Seller Central's current text governs over any summary.
- Keywords.am, July 2026, for the method-by-method compliance table structure, the excluded-order rules and the insert and warranty-list distinctions; a keyword tool vendor. Web Retailer, for the button mechanics, the translation behavior and the reported 30-day messaging restriction for double requests. Seller Labs' knowledge base (May and August 2026) for the 5-30 day window, once-per-order rule and opt-out exclusion; cited by name, as the pages block automated access. SentryKit, for the timing-by-product-type research figures, reported as one vendor's.
- A developer's SP-API write-up, June 2026, for the endpoint path and the 403 behavior outside the window and on repeat calls.
- Evolve Media Agency review-program work for clients and Bear Basics Co., 2020-2026. First-party; the per-ASIN timing defaults, the exclusion line and the qualitative expectations are ours.