Automate Amazon review requests for every eligible order, within Amazon's rules
Updated · By Ecomsellertool editorial team
To automate Amazon review requests, record every shipped order, wait until 5 days after its earliest delivery date, then ask Amazon's Solicitations API whether a request is allowed and send one if it is. Amazon's window closes 30 days after the latest delivery date, and each order gets one request. Amazon writes the message; you never add incentives, ask only happy buyers or request a positive review.
- Amazon's Solicitations API sends one template-based email that asks for both a product review and seller feedback (checked October 14, 2026).
- Amazon's setup guide allows a request from 5 days after the earliest delivery date to 30 days after the latest delivery date (checked October 14, 2026).
- A second API request for the same order returns a 403 error, and an API request does not flag the order in Seller Central (checked October 14, 2026).
- Both Solicitations operations have a default rate of 1 request per second with a burst of 5 (checked October 14, 2026).
- Amazon's communication policy bars incentives, asking only buyers with a positive experience, and more than 1 request per customer per order (checked October 14, 2026).
The step map: who runs each step
Trigger: Each order that changes to Shipped, then a daily run over every shipped order still inside Amazon's request window.
| Step | What happens | Who runs it |
|---|---|---|
| 1 | When an order changes to Shipped (from Amazon's ORDER_CHANGE notification or a scheduled order pull), the workflow stores its order ID, marketplace ID, earliest and latest delivery dates, and a status of waiting. | Rule |
| 2 | Once a day it selects orders that are at least 5 days past the earliest delivery date, no more than 30 days past the latest delivery date, and not yet marked as requested. | Rule |
| 3 | For each selected order it calls getSolicitationActionsForOrder and continues only if Amazon lists the productReviewAndSellerFeedback action. | Rule |
| 4 | It calls createProductReviewAndSellerFeedbackSolicitation, paced under the default rate of 1 request per second, and logs the response: sent, already requested, not eligible yet or an error to retry. | Rule |
| 5 | When the window closes, any order still not sent is marked closed with the reason, so nothing is retried outside Amazon's time frame. | Rule |
| 6 | A weekly summary lists requests sent, orders Amazon did not offer, and errors; the owner of reviews reads it and acts on product or account problems it points to. | Person |
5 rule steps · 0 AI model steps · 1 person step. A rule follows fixed logic you approve; an AI model handles messy input and its output is checked by rules; a person makes the calls listed below.
What stays with a person
- Choosing one owner for review requests: the workflow or the Request a Review button, never both
- Replies to reviews and to buyers who complain, written and sent by a person
- Product fixes and listing changes when reviews point to a defect
- Any buyer message other than Amazon's template, approved by a person under the communication policy
- Turning the workflow on for each new marketplace or seller account
Which tools can run it
- Amazon's Request a Review button on each order's details page in Seller Central, for low order volume
- A review-request app that you authorize in Seller Central and that uses the Solicitations API
- n8n or another workflow tool with a code step, if you already run your own SP-API app
- Custom code on your accounts, when requests share one order log with your other Amazon workflows
Systems it connects
- Amazon Seller Central
- SP-API Solicitations API
- SP-API Orders API
- SP-API Notifications (ORDER_CHANGE) with Amazon SQS
- A request log (database or spreadsheet)
- Slack or email for the weekly summary
Build size: Small
Two API calls and a date check; most of the work is the app registration, the role and keeping one owner for requests.
Most Amazon sellers know the Request a Review button. Amazon's Customer Reviews tool page puts it on the Order details page in Seller Central (checked October 14, 2026). Clicking it once per order works at ten orders a day. At two hundred, someone spends an hour on it, skips weekends, and misses orders whose window has closed. This recipe sends Amazon's own request for every eligible order through the Selling Partner API, on time and exactly once. It is one page of our automation library.
Which orders can get a review request, and what does the workflow do with each?
This table is the core of the build. Use it today to check a vendor's tool or your own team's habits. Each row is an order state: whether Amazon lets you send a request, the Amazon rule behind that answer, what the workflow does, and what stays with a person. The rules come from Amazon's Solicitations API setup guide, its solicit feedback guide and the Seller Central communication program policy (all checked October 14, 2026).
| Order state | Can you request? | Why (Amazon's rule) | What the workflow does | What a person owns |
|---|---|---|---|---|
| Ordered, not yet shipped | No | The setup guide says to check that the order status has changed to Shipped | Nothing yet; it waits for the Shipped event | Nothing |
| Shipped, less than 5 days after the earliest delivery date | No | The window opens 5 days after the earliest delivery date | Stores the order and its two delivery dates; checks again daily | Nothing |
| Inside the window, and Amazon lists the productReviewAndSellerFeedback action | Yes | The guide says to send only if that action appears in the eligibility response | Sends the request and logs it as sent | Nothing per order; reads the weekly summary |
| Inside the window, but the action is not listed | Not now | Amazon decides eligibility; the guide gives no other route | Logs "not offered" and checks again the next day until the window closes | Looks into it if many orders stay "not offered" |
| Already requested through Seller Central or the API | No | A second API attempt returns a 403 error; the policy allows 1 request per customer per order | Marks the order done and never retries | Decides who sends requests, so the team stops clicking the button |
| A free-form proactive message was already sent for this order | No | The API reference says to send only one review solicitation or free-form proactive message per order | Skips the order if your message log shows one | Keeps a log of buyer messages your team sends |
| Buyer returned the item or complained | Same as any order | You cannot selectively seek positive reviews, and diverting negative reviews away from Amazon is a violation | Treats it like every other order; does not filter out unhappy buyers | Resolves the complaint through normal customer service |
| More than 30 days after the latest delivery date | No | The window closes 30 days after the latest delivery date; calls outside it lead to errors | Marks the order closed with the reason | Nothing |
Two rows deserve a second look. The returned-item row is where well-meant tools break the rules: skipping unhappy buyers looks like good manners, but it is the selective asking Amazon rules out. The already-requested row is where teams trip over themselves. Amazon notes that an API request does not flag the order in Seller Central. If a colleague clicks Request a Review later, Seller Central shows an error saying a review was already requested. One owner, one log.
What may you not do when you ask for Amazon reviews?
The API sends Amazon's wording, so the risk sits around it: what else you send, to whom, and what you offer. These are the lines from Amazon's own pages, checked today. The developer guide's best practices say you cannot selectively seek positive reviews, request changes to existing reviews, or offer rewards or incentives for reviews. The communication policy and the Seller Central customer product reviews policies (checked October 14, 2026) add the rest.
- No compensation, money, gift cards, free or discounted products, refunds, replacements, rebates or future benefits in exchange for a review or feedback.
- No asking for a review only if the buyer had a good experience while telling unhappy buyers to contact you first.
- No sending negative reviews to you or to another feedback channel while positive ones go to Amazon.
- No asking for a particular sentiment or star rating; requests must be for an unbiased review.
- No more than 1 review or feedback request per customer per order.
- No asking a buyer to change or remove a review, before or after a refund.
- No package inserts that ask for a positive review or offer an incentive for one.
- No contacting buyers outside Buyer-Seller Messaging, such as by email, phone or social media.
- No proactive "thank you" or order-confirmation messages.
Amazon's Anti-Manipulation Policy for Customer Reviews (checked October 14, 2026) says Amazon may suspend or end selling privileges, remove reviews and delist products. US law points the same way. The FTC's questions and answers on its consumer reviews rule (checked October 14, 2026) say the rule took effect on October 21, 2024. The FTC adds that asking only customers you think are happy could violate the FTC Act. This page is not legal advice; ask your lawyer about your own messages.
How does the Solicitations API work?
Two calls do the work. getSolicitationActionsForOrder returns the solicitation types available for an order, and today the only type is the product review and seller feedback request. createProductReviewAndSellerFeedbackSolicitation sends it. Each call takes the Amazon order ID and one marketplace ID, nothing else. Both pages list a default rate of 1 request per second with a burst of 5 (both checked October 14, 2026), so a run paced just under one call a second can handle about 3,000 orders an hour without hitting a 429 error.
The Solicitations API overview says one template-based email asks for both a product review and seller feedback, for sellers in the NA, EU and FE regions, and your app needs the Buyer Solicitation or Product Listing role (checked October 14, 2026). The v1 reference adds that buyers cannot reply to these requests, and that they do not appear in the Messaging section of Seller Central (checked October 14, 2026). So you cannot customize the message, and you do not need to.
If you use an AI assistant connected to your account, keep this call behind a fixed rule. Our SP-API MCP server guide puts review requests in the "approval or a fixed rule" group. Our Agent Policy readiness checklist explains why a browser bot pressing the button is the wrong design.
Which tool should send the requests?
At low volume, the button in Seller Central is fine if one person owns it and checks orders every day. Beyond that, an app you authorize in Seller Central that uses the Solicitations API is the usual next step; check that it uses the API and not a logged-in browser. A workflow tool such as n8n can run the schedule if you already run an SP-API app and add a code step for Amazon's sign-in. Custom code on your accounts makes sense when the same order log also drives your other Amazon work, such as restock alerts and reimbursements. It can run on Ecomsellertool Growth OS. For where review requests rank among other Amazon tasks, see our guide to automating Amazon operations.
No AI model is needed to send requests: every step is a date check, an eligibility call or a log entry. Where a model can help is after the review arrives, which is a different workflow. Seller7's review module, shown below, pulls in low-star reviews, sorts them by intent, suggests a next action and drafts a reply. In the workflows we recommend, a person approves and sends every reply.
Negative reviews answered from one screen, with an AI-drafted reply and next action
Read the Seller7 case study ↗What can go wrong, and how do you catch it?
| What goes wrong | How it shows up | The check that catches it |
|---|---|---|
| The button and the workflow both send | Seller Central errors; the API returns 403 | One owner; 403 is logged as "already requested", never retried |
| Calls run outside the window | Unexpected API errors | Dates checked before every call; closed orders are never retried |
| Burst of calls after a big sales day | 429 errors | Calls paced under 1 per second, with back-off on 429 |
| A tool filters out unhappy buyers | Not visible until Amazon acts | The filter is a written rule: every eligible order, no sentiment check |
| Authorization lapses | Every call fails with 403 | Alert when the failure rate jumps, so a person re-authorizes the app |
| A new marketplace is added | Orders missing from the log | The marketplace list is reviewed when you launch a country |
Who builds review-request automation for Amazon sellers?
Ecomsellertool builds Amazon review-request workflows on your own seller account, through the SP-API and within the rules above. We have built software on Amazon's seller APIs since 2017 and shipped 50+ tools for 100+ teams. We start with your order volume, your marketplaces and who owns buyer contact today. Send a project brief below, or read how our workflow automation service works.
The building blocks are work we have shipped:
- Buyer messaging inside a seller app. The Zquared case study lists an autoresponder that sent automated messages to buyers to collect feedback and product reviews, next to its profit dashboard, P&L view and restock alerts. Today we would build that job on the Solicitations API, which sends Amazon's own request.
- Reviews in one workspace. For Seller7 we helped bring orders, shipping, reimbursements, reviews and finance into one connected workspace, including the AI review module above.
Review requests sit next to other buyer-facing work. Our support-ticket triage recipe covers the messages that come back, and the guide to what to automate first helps you rank this against everything else.
Get this workflow built
Send us your version of this workflow
Describe the workflow you want automated. We reply with a written plan: scope, timeline and a fixed price.
Frequently asked questions
Can you automate Amazon review requests?
Yes. Amazon's Selling Partner API has a Solicitations API built for it. Software checks whether an order can receive a request, then sends Amazon's own review and seller feedback email. You need an SP-API app with the Buyer Solicitation or Product Listing role, authorized by the seller account.
Is automating Request a Review against Amazon's rules?
Not when it runs through the Solicitations API, which Amazon provides for this purpose. What breaks the rules is the content and targeting around it: incentives, asking only happy buyers, asking for a positive review, asking twice, or pressing the Seller Central button with a browser bot instead of using the API.
When can I request a review on Amazon?
Amazon's Solicitations API setup guide gives a window from 5 days after the order's earliest delivery date to 30 days after its latest delivery date. Calls outside that window lead to errors. The getSolicitationActionsForOrder call tells you whether a specific order is open for a request right now.
Can I send a review request more than once for the same order?
No. Amazon's communication policy allows one request per customer per order, and the API returns a 403 error on a second attempt for the same order. If someone already clicked Request a Review in Seller Central, the API request fails too, so pick one way of sending.
Can I send review requests only to customers who had a good experience?
No. Amazon's developer guide says you cannot selectively seek positive reviews, and its communication policy bans asking for a review only after a positive experience while sending unhappy buyers to you. Send the request to every eligible order and handle complaints separately.
Can I change the wording of the Amazon review request email?
No. The Solicitations API sends a single template-based email, and the create call takes only the order ID and the marketplace. Buyers cannot reply to it, and it does not appear in the Messaging section of Seller Central. Any custom message is a separate buyer message that must follow Amazon's communication policy.
