> For the complete documentation index, see [llms.txt](https://docs.sellermagnet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sellermagnet.com/selling-tools/review-requester-overview.md). # Review Requester Automate Amazon review requests with SellerMagnet. Send compliant review solicitations to buyers, track response rates, and boost your product ratings across all marketplaces. {% hint style="info" %} **Difficulty:** ๐ŸŸข Beginner ยท **Reading time:** \~10 min {% endhint %} {% hint style="success" icon="rocket" %} **Open this page in your dashboard:** [**Go to Review Requester โ†’**](https://dashboard.sellermagnet.com/review-request) {% endhint %} ## ๐Ÿ“‹ Overview The **Review Requester** automates the process of sending Amazon-compliant review request emails to your buyers. More reviews mean better product rankings, higher conversion rates, and stronger Buy Box competitiveness. SellerMagnet handles the timing, targeting, and tracking so you never miss an opportunity to collect feedback. The tool uses Amazon's official "Request a Review" mechanism, ensuring full compliance with Amazon's Terms of Service. Every request sent through SellerMagnet is identical to clicking the "Request a Review" button in Seller Central, but automated across your entire order history. {% embed url="" %} *** ## ๐ŸŒŸ Why Reviews Matter
Search rankingProducts with more reviews rank higher in Amazon search results
Conversion rateListings with 50+ reviews convert 2-3x better than those with 5
Buy Box eligibilitySeller feedback score influences Buy Box allocation
Customer trust93% of consumers read reviews before purchasing
Advertising efficiencyHigher conversion rates lower your ACoS (Advertising Cost of Sale) on Sponsored Products
{% hint style="success" icon="rocket" %} **Pro tip:** Amazon allows one review request per order, and buyers are most receptive once the product has arrived and been used. SellerMagnet holds every order for a **5-day eligibility floor** before it can be requested, then sends at the **daily send time** you choose, so requests land while the purchase is still fresh but the buyer has had time with the product. {% endhint %} *** ## ๐Ÿ“‹ Dashboard Overview The Review Requester page is divided into three main areas: {% tabs %} {% tab title="Statistics Panel" %} Four KPI metrics at the top show your review request activity: | KPI | Description | | ------------------- | ---------------------------------------------------------- | | **Sent Today** | Number of review requests sent in the current calendar day | | **Sent YTD** | Total requests sent year-to-date | | **Sent (30d)** | Requests sent in the last 30 days | | **Sent (All Time)** | Lifetime total across all marketplaces | These four tiles give you the headline counts, **today**, the **last 30 days**, **year-to-date**, and **all time**, at a glance. Below the KPIs, a **daily send-rate trend chart** plots how many requests went out on each of the **last 30 days**. This is the detail behind the tiles: it lets you confirm automation is firing every day, spot gaps where sending stalled, and see whether your volume is rising or falling over the month. {% endtab %} {% tab title="Latest Seller Reviews" %} A slider panel showing your most recent seller feedback across marketplaces. The panel header carries three controls: | Element | Description | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------ | | **All marketplaces (N)** | A badge that appears when you have **two or more** connected marketplaces, showing how many are represented | | **View all reviews** | Opens the **Seller Review Details** modal with every connection's marketplaces merged into one cross-account view | | **Default marketplace** | A chip noting that the carousel shows feedback for your **default marketplace**; click it to change the default under **Settings โ†’ Connections** | Each seller card shows your store name, star rating (with a visual bar), total reviews, seller feedback **Score** percentage, and a **View Details** button. The inner slider shows individual reviews with star ratings, dates, and buyer comments. **Seller Review Details modal.** Opening **View Details** (or **View all reviews**) surfaces a deeper breakdown: * A **feedback distribution** across four periods, **30 days / 90 days / 365 days / Lifetime**, split into positive, neutral, and negative counts. * A recent-feedback filter bar with **Sentiment** (All / Positive / Neutral / Negative), an **ASIN** filter, and a **Sort** control (Newest / Oldest / Most Negative). When two or more marketplaces are represented, a per-marketplace filter also appears. * Per-negative-review actions: **Open Seller Central case**, **Open Reimbursements**, and **Tag investigated** (a browser-local marker, stored in localStorage). {% endtab %} {% tab title="Order Queue" %} The main section displays your orders grouped into three accordion sections by review request status. Each section header carries a **count badge** and expands to reveal a table. | Section | Description | Badge Color | | ------------- | ------------------------------------------------------------------------ | ----------- | | **Waiting** | Orders placed less than 5 days ago, not yet inside the eligibility floor | Blue | | **Ready** | Orders that pass our eligibility checks and can be requested now | Green | | **Requested** | Full history of every order a request has been sent for | Grey | {% hint style="info" %} **Ready is a best-effort estimate.** SellerMagnet marks an order **Ready** using the public rules it can see (past the 5-day floor, no prior request, refund status). Amazon still enforces additional per-order rules that are not visible through the API, invoice-required marketplaces, customer opt-out flags, account-age limits, and message-policy checks. If a specific **Ready** order is declined when you click Request, that is Amazon enforcing a private rule, not an error in the list. The page shows this same disclaimer as a banner at the top of the **Ready** section. {% endhint %} {% endtab %} {% endtabs %} *** ## Order Table Columns | Column | Description | | --------------- | -------------------------------------------------------------------------------------------------------- | | **Checkbox** | Select orders for bulk actions | | **Fulfillment** | FBA or FBM badge | | **Order** | Order ID, date, and marketplace | | **Products** | Product name, ASIN (Amazon Standard Identification Number), and thumbnail image | | **Unit Price** | Price per unit | | **Units** | Quantity ordered | | **Gross** | Order total including tax | | **Net** | Order total excluding tax | | **Status** | Review request status pill (see below) | | **Active** | Per-order auto-eligibility toggle: eligible for automatic requests, flip off to skip this specific order | | **Manage** | Manual **Send Request** button | ### Status Pills The **Status** column shows one of the following pills per row: | Pill | Meaning | | -------------------- | ---------------------------------------------------------- | | **Review Requested** | A request has been sent for this order | | **Not Requested** | Eligible, no request sent yet | | **Skipped** | Marked skipped from the queue (browser-local, see below) | | **Failed** | A request attempt failed | | **Pending...** | A request is in flight | | **Limit reached** | Your plan's request limit is reached; upgrade to send more | *** ## ๐Ÿ” Filters and Controls Above the order queue you have: | Control | What it does | | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Refresh** | Reloads the queue and counts | | **Marketplace** | Dropdown to filter by a specific Amazon marketplace (default: All Marketplaces) | | **Filters** | A popover to filter by **Fulfillment**, FBA or FBM | | **ASIN filter** | A free-text box that narrows the rendered rows to a matching ASIN (this is the only free-text filter on the page, there is no generic search or tag filter) | | **Status** | A dropdown to filter by All Statuses / Requested / Not Requested / Failed | Each accordion section is **paginated at 25 orders per page** (the server caps the page size at 100). *** ## Sending Review Requests ![SellerMagnet Review Requester](https://4139654583-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fih2knSvVpBcq5rIeXVjM%2Fuploads%2Fgit-blob-0e08755ae1b697a24296bcc461bb44bbfb704fc9%2Freview-request.png?alt=media) ### Manual (Individual) 1. Find the order in the **Ready** section. 2. Click the **Send Request** button in the Manage column. 3. Confirm the action in the popup. 4. On success the order's status pill flips to **Review Requested** and it moves into the **Requested** history. ### Bulk Requests 1. Select multiple orders using the checkboxes. Hold **Shift** and click, or **click-and-drag** down the checkbox column, to select a range at once. 2. Click the **Bulk** button in the toolbar. 3. Confirm the batch action. 4. All eligible selected orders receive review requests. ### Bulk Actions on Selected Orders Once you tick one or more checkboxes, the toolbar exposes three organizing actions alongside **Bulk**. They let you manage large order lists without sending anything you did not intend to: | Action | What it does | | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Tag** | Attaches a short label to the selected orders so you can group and find them later. Enter a name in the popover and click **Apply**. **Tags are browser-local**, stored in localStorage per project, they are not saved on the server. | | **Skip** | Marks **just the selected orders** as skipped, flipping their status pill to grey **Skipped**. **Skip state is browser-local** too, kept in localStorage per project. The Skip endpoint is an acknowledgement stub that validates and echoes the order list; it does not persist the skip server-side. | | **Exclude** | Takes the products behind the selected orders and adds them to your **automation exclusion list**. The tool de-duplicates the ASINs, resolves each to its SKU, and files them under the correct marketplace connection, so those products are never sent an automatic request on that store again. Products already on the list are reported as duplicates rather than added twice. | {% hint style="info" %} **Skip vs Exclude, which one do I want?** * **Skip** is per **order** and lives only in your browser. Use it when a handful of specific orders should not surface (for example a problem order or a test purchase). Because it is stored locally, it clears if you switch browsers or clear site data, and it does not stop server-side automation. * **Exclude** is per **product** and is saved server-side per connection. Use it when an entire ASIN/SKU should be left out of automation going forward, regardless of order. It adds the product to the same per-marketplace exclusion list you manage under the **Automatic** panel. In short: Skip hides the orders in front of you (in this browser), Exclude stops the product from automatic requests for good. {% endhint %} ### Automatic Requests 1. Click the **Automatic** button in the toolbar (you can also deep-link straight to it with `/review-request#manage-automatic-review-requests`, which the Settings page uses). 2. The automation panel opens with a **separate settings card for each connected marketplace**, so you can run different rules per store. For every connection, you can configure: | Setting | Description | | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Automation** | The master on/off switch for automatic requests on that connection | | **Daily Send Time** | The time of day requests go out, chosen from a **whole-hour** dropdown set in **GMT/UTC** (default **2 PM**). A live **local time** readout shows the equivalent in your own timezone so there is no guesswork | | **Enable Scheduling** | A toggle that turns the daily send-time schedule on or off. The time dropdown and its **Save** button are disabled until scheduling is enabled | | **Include Refunded Orders** | A toggle that decides whether refunded orders also receive a request. **Off by default** (recommended), with an inline warning, since requesting reviews on refunded orders tends to attract negative reviews | | **Exclude Specific Products** | A search-and-select list of products to skip when sending automatically (see below) | {% hint style="success" icon="rocket" %} **Pro tip:** Set the daily send time to a point in the buyer's afternoon or early evening in their local market, that is when "Request a Review" emails are most likely to be opened. Use the local-time readout to convert from UTC. {% endhint %} #### Excluding Specific Products from Automation Within each connection's automation card, the **Exclude Specific Products** section lets you pick individual products that should **never** receive an automatic review request, while every other qualifying order still does. * **Search and select** products by ASIN or SKU and add them to the exclusion list. * **Import CSV** to bulk-add exclusions from a file with `asin`/`sku` columns, and **Export CSV** to download your current exclusion list. * Excluded products are saved per connection, so you can exclude an item on one marketplace while still requesting reviews for it on another. {% hint style="info" %} **When to use this:** Exclude products with known quality issues, items under active complaint, or low-margin SKUs where extra reviews are not worth the risk, all without turning off automation for the rest of your catalog. {% endhint %} *** ## Compliance and Amazon Policies {% hint style="danger" %} **Important:** SellerMagnet uses Amazon's official "Request a Review" API, which is fully compliant with Amazon's Communication Guidelines. However, you should be aware of these rules: * You may only request a review **once per order** * Requests are eligible between **5 and 30 days** after delivery, on Amazon's side * You **cannot** incentivize reviews (no discounts, coupons, or gifts in exchange) * You **cannot** ask for only positive reviews * You **cannot** contact buyers who have opted out of seller messages {% endhint %} SellerMagnet holds every order for a **5-day eligibility floor** before it can be requested, and never sends more than one request per order. It does **not** hard-block requests at the 30-day upper bound: orders past the window can still appear as **Ready** on a best-effort basis, but Amazon rejects any request that falls outside its own eligible window. The **Ready** disclaimer explains that Amazon has the final say per order. *** ## ๐ŸŽฏ Realistic Example **Scenario:** You sell across Amazon.de, Amazon.fr, and Amazon.it and want to maximize review collection without spending time in Seller Central. **Setup:** 1. Open the **Automatic** panel. 2. On each connection card, turn the **Automation** master toggle **on**. 3. Turn **Enable Scheduling** on and set the **Daily Send Time** (whole-hour, GMT/UTC), leaving the **2 PM** default or shifting it toward your buyers' local afternoon. 4. Leave **Include Refunded Orders** **off** so refunded orders never get a request. 5. Add any problem or low-margin SKUs to **Exclude Specific Products**. **How it flows:** * New orders sit in **Waiting** until they clear the 5-day eligibility floor. * Once eligible, they move to **Ready** and are sent automatically at your daily send time (subject to Amazon accepting each order). * Every sent order lands in the **Requested** history, and the KPI tiles and trend chart update so you can confirm automation is firing daily. Without automation, sending the same requests one at a time would mean thousands of individual clicks in Seller Central. *** ## Tracking Results | Where to Look | What It Shows | | ------------------------- | ----------------------------------------------------------------------------------------------------------- | | **Statistics Panel** | Volume of requests sent over time | | **Trend Chart** | Daily sending patterns to confirm automation consistency | | **Section Count Badges** | How many orders sit in Waiting, Ready, and Requested | | **Latest Seller Reviews** | Your overall seller rating and recent feedback, with the Seller Review Details modal for a deeper breakdown | | **Amazon Seller Central** | Product review count changes (cross-reference with requests) | ***
โš ๏ธ Common Mistakes to Avoid | Mistake | Why It Hurts | | --------------------------------------- | ---------------------------------------------------------------------------------- | | Including refunded orders in automation | Refunded buyers are the most likely to leave negative reviews, keep the toggle off | | Not enabling automation | You manually forget to send requests and miss thousands of reviews | | Treating a Ready order as guaranteed | Amazon can still decline it for per-order rules SellerMagnet cannot see | | Relying on Skip or Tag to persist | Both are browser-local, use **Exclude** for a product you want kept out for good | | Not monitoring the trend chart | You miss automation failures or disruptions |
## โœ… Best Practices 1. **Enable automation on day one:** Set it and forget it. Every eligible order should receive a review request. 2. **Use the local-time readout:** Convert the UTC send time to your buyers' local afternoon or early evening for the best open rates. 3. **Monitor your seller feedback score weekly:** A declining score may indicate a product quality issue that review requests are surfacing. The Seller Review Details modal breaks feedback down by 30 days / 90 days / 365 days / Lifetime. 4. **Exclude the right products, not orders:** Use **Exclude** (server-side, per product) for anything you want kept out of automation permanently; reserve **Skip** for one-off, in-browser tidying. 5. **Cross-reference requests with reviews:** Track your review request volume against new review count to estimate your response rate. Industry average is 3-8%. *** ## โ“ FAQ
Is using the Review Requester against Amazon's Terms of Service? No. SellerMagnet uses Amazon's official "Request a Review" API, which is the same mechanism as the button in Seller Central. It is fully compliant.
Can I customize the review request message? No. Amazon's "Request a Review" sends a standardized email from Amazon. You cannot modify the content, subject line, or branding. This is by design to prevent manipulation.
What is a good review response rate? Industry average is 3-8%. Response rates vary by product category, price point, and marketplace. Higher-priced products and consumables tend to have higher response rates.
Why does an order show as Ready if Amazon still rejects it? SellerMagnet marks an order **Ready** using the public rules it can see, past the 5-day floor, no prior request, and refund status. Amazon enforces extra per-order rules that are not visible through the API (invoice-required marketplaces, customer opt-out, message-policy flags, account age). SellerMagnet does not hard-block at the 30-day upper bound, so Ready is a best-effort estimate and Amazon decides each request when you send it.
Are Skip and Tag saved to my account? No. Both **Skip** and **Tag** are stored in your browser's localStorage, scoped per project, so they clear if you switch browsers or clear site data. The Skip endpoint only acknowledges the request; it does not persist the skip server-side. To keep a product out of automation permanently, use **Exclude**, which is saved server-side per connection.
Does the review requester work for both product reviews and seller feedback? Yes. Amazon's "Request a Review" email asks the buyer for both a product review and seller feedback in a single message.
What happens if a buyer has already left a review? Amazon prevents duplicate requests. If a buyer has already reviewed the product, the request is simply not sent (or is ignored by Amazon's system).
Can I exclude specific products from automated review requests? Yes. Open the **Automatic** panel and, in the connection's **Exclude Specific Products** section, search and select the products you want to skip (or bulk-import them from a CSV with `asin`/`sku` columns). Excluded products are saved per connection and are never sent an automatic request, while every other qualifying order still is.
*** ## โžก๏ธ What's Next? {% content-ref url="/pages/VXlGkA4PfkAz77id3Txp" %} [Listing Optimizer](/selling-tools/listing-optimizer-overview.md) {% endcontent-ref %} {% content-ref url="/pages/YtBP2GSz5q83gTVW9tOI" %} [Product Sourcer](/selling-tools/product-sourcer-overview.md) {% endcontent-ref %}