Amazon's Request a Review button appears 5-30 days after delivery, but when you actually click it affects response rates. Sellers report response rate differences of 2-5 percentage points depending on timing, which compounds significantly across thousands of orders.

How Amazon's Request a Review button timing works

The button becomes available in Seller Central 5 days after the customer receives their order. It remains clickable until day 30 post-delivery, then disappears permanently for that order.

Amazon does not provide data on when customers are most likely to respond. The system simply enforces the 5-30 day window and prevents duplicate requests β€” you get one click per order, and Amazon sends the email within 24 hours of that click.

This creates a testing problem: you must choose a timing strategy without knowing which day produces the highest response rate for your specific products.

What happens when you click the button

Amazon sends a standardized email from [email protected] that asks the customer to rate their purchase and optionally leave a review. The email subject line reads "Did you receive your order?" and includes the product image, name, and direct review submission links.

The customer can respond in three ways:

  • Leave a star rating only β€” appears in your product rating aggregate immediately
  • Leave a star rating plus written review β€” typically appears within 24-48 hours after moderation
  • Ignore the email β€” no response recorded, no second chance to request

You cannot customize the message, resend it, or see open/click rates. Amazon treats it as a compliance-safe review solicitation mechanism, not a marketing channel.

The core timing decision: early window vs late window

Sellers divide into two camps on timing strategy, each with a different theory about customer behavior.

Early window advocates (days 5-7)

This group clicks the button as soon as it becomes available, typically on day 5 or 6 post-delivery.

Theory: The product is fresh in the customer's mind. They have recently unboxed and used it, so recalling the experience requires minimal effort. Faster timing also means fewer days for the customer to encounter problems that might lower their rating.

Best fit for: Consumable products, low-priced impulse purchases, items with immediate use cases. Products where the full value is apparent within 1-2 uses.

Examples: Phone accessories, kitchen gadgets under $25, beauty samples, snack foods, basic office supplies.

Late window advocates (days 14-30)

This group waits until day 14 or later, with some waiting until day 25-28 to maximize the customer's experience time.

Theory: Customers need time to fully evaluate product quality. Requesting too early catches them before they have formed a complete opinion, which increases the likelihood they skip the request entirely. Waiting also filters out customers who will return the product β€” if they have kept it for 14+ days, satisfaction is higher.

Best fit for: Complex products requiring setup, items with learning curves, durability-dependent purchases, higher-priced goods where customers make more thoughtful reviews.

Examples: Electronics over $100, furniture, supplements (where results take 1-2 weeks), apparel (where sizing and comfort emerge after multiple wears), kitchen appliances.

Testing framework: how to find your optimal timing

Since Amazon provides no timing analytics, you must build your own testing system. This requires tracking three data points per order: click date, delivery date, and whether a review appeared.

Step 1: Segment your catalog by product type

Do not test timing across all products simultaneously. Segment first by these characteristics:

Product characteristic Starting timing hypothesis
Price under $30, single-use value Days 5-7
Price $30-$100, moderate complexity Days 10-12
Price over $100 or requires assembly Days 14-20
Consumable with repeat purchase potential Days 7-10
Apparel or size-dependent items Days 10-14

These are starting points, not rules. Your testing will reveal whether these hypotheses hold for your specific products.

Step 2: Create a tracking spreadsheet

You need seven columns:

  1. Order ID β€” from Seller Central order reports
  2. ASIN β€” the product ordered
  3. Delivery date β€” when carrier marked as delivered
  4. Button click date β€” when you clicked Request a Review
  5. Days post-delivery β€” calculation: click date minus delivery date
  6. Review received β€” yes/no, check 14 days after button click
  7. Star rating if received β€” 1-5 stars

Track at least 50 orders per timing window to see meaningful patterns. For lower-volume sellers, this may require 2-3 months of data collection.

Step 3: Run split tests within each product segment

Pick two timing windows to test first. Common starting comparisons:

  • Day 6 vs Day 14
  • Day 5 vs Day 20
  • Day 10 vs Day 25

Alternate between the two windows for consecutive orders of the same ASIN. If you fulfill 10 units of Product X this week, click the button on day 6 for orders 1, 3, 5, 7, 9 and day 14 for orders 2, 4, 6, 8, 10.

This controls for seasonal variation, inventory batch differences, and listing changes that might affect review rates independent of timing.

Step 4: Calculate response rate by timing window

After 14 days from your last button click, calculate:

Response rate = (Reviews received / Button clicks) Γ— 100

Compare the two timing windows. A difference of 2+ percentage points typically indicates a meaningful pattern. For example:

  • Day 6 clicks: 47 reviews from 200 button clicks = 23.5% response rate
  • Day 14 clicks: 58 reviews from 200 button clicks = 29.0% response rate

In this scenario, day 14 outperforms by 5.5 percentage points β€” a substantial and actionable difference.

Step 5: Implement the winning window, then test variations

Once you identify a higher-performing window, use it as your baseline for 30 days while testing minor variations. If day 14 won your initial test, compare day 12 vs day 14 vs day 16 in the next round.

This progressive testing approach prevents you from missing a local maximum. The best timing for one product may be day 13, even if your initial test showed day 14 beating day 6.

Timing patterns by product category

While every catalog is different, certain patterns appear across seller reports and testing discussions in Amazon seller communities.

Electronics and tech accessories

Lower-priced accessories (cables, cases, screen protectors) tend to perform best at 5-8 days post-delivery. Customers evaluate these products on immediate functionality β€” does the cable work, does the case fit β€” and form opinions quickly.

Higher-priced electronics benefit from 12-18 day windows. Customers spend more time testing features, comparing to previous products, and forming detailed opinions worth writing about.

Home and kitchen products

Single-use items like cleaning supplies or food storage containers: 5-7 days.

Appliances and cookware: 14-21 days. Customers need time to use these products multiple times and evaluate durability, which heavily influences their satisfaction.

Apparel and accessories

The 10-14 day window balances two opposing pressures. Waiting past day 7 lets customers wear the item multiple times and wash it once (revealing fit and fabric quality issues). But waiting past day 18 increases the chance they have already moved on mentally and will ignore the request.

For seasonal apparel (swimwear, winter coats), timing should align with actual use. A winter coat delivered in November gets reviewed after 2-3 weeks of wear. The same coat delivered in March may not get worn at all, making timing largely irrelevant to response rates.

Supplements and consumables

Products where results take time (vitamins, protein powders, skincare) show higher response rates at 14-21 days. Customers who review after 5 days often comment that it is "too early to tell," which provides limited value to future buyers.

Consumables with immediate sensory feedback (snacks, coffee, tea) perform well at 7-10 days β€” enough time to finish the initial quantity and form a taste preference.

FBA vs FBM timing differences

The 5-30 day window runs identically for both fulfillment methods, but FBM sellers face an additional variable: shipping time accuracy.

Amazon calculates the window from the delivery date, not the ship date. If you mark an order shipped on Monday but it does not deliver until Friday, the button appears 5 days after Friday.

This creates two FBM-specific timing considerations:

Carrier delays push your window later. If you planned to click on day 6 but a carrier delay extends delivery by 3 days, the button does not appear when expected. You must manually track delivery confirmation dates, not your ship dates.

Faster shipping shortens the evaluation period. If a customer receives an FBM order in 2 days instead of the promised 5, clicking on day 6 post-delivery means they have had only 6 days with the product. For FBA, day 6 post-delivery is typically day 7-8 post-order, providing slightly more evaluation time.

FBM sellers using regional carriers or freight shipping should add 2-3 days to their target timing windows compared to FBA equivalents. A product that would get clicked on day 10 for FBA might perform better at day 12-13 for FBM.

Common timing mistakes that lower response rates

Clicking too early after a known delivery issue

If tracking shows "attempted delivery" or "left at door" with a customer message stating they did not receive it, do not click the button the moment it becomes available. Wait until you have confirmed successful receipt, even if that pushes you to day 10-12.

Requesting a review when the customer is still resolving a delivery problem guarantees either no response or a negative review about the delivery experience (which Amazon allows since the request asks about the overall order, not just the product).

Ignoring seasonal use patterns

Products with seasonal use cases need timing adjustments based on purchase date. A snow shovel purchased in July will not be used for months, making any timing within the 5-30 day window equally ineffective. A snow shovel purchased in December should be reviewed around day 14-20, after the first major snowfall.

For highly seasonal products, some sellers skip the review request button entirely for off-season orders and focus their efforts on peak-season deliveries.

Using identical timing across all ASINs in a catalog

Standardizing timing to "always click on day 7" simplifies workflow but ignores product-level differences. A catalog containing both $12 phone cables and $200 headphones needs split timing strategies.

Group ASINs into 3-4 timing tiers based on price and complexity, then set timing windows accordingly: tier 1 at day 6, tier 2 at day 12, tier 3 at day 18. This takes minimal additional effort but prevents systematic under-optimization.

Automating timing without violating Amazon's review policy

Amazon prohibits automated review requests sent outside the Request a Review button. You cannot use third-party tools to email customers directly.

However, you can automate the button-click process itself using workflow tools that interact with Seller Central. These tools do not send messages β€” they click the button on your behalf at your specified timing.

Acceptable automation approach:

  1. Pull your order report daily via Amazon's API or manual download
  2. Filter for orders where current date = delivery date + your target days (6, 12, 18, etc. depending on ASIN tier)
  3. Use a browser automation tool (Selenium, Puppeteer) to log into Seller Central and click the button for those order IDs
  4. Log each click in your tracking spreadsheet

This keeps the review request mechanism within Amazon's system while removing the manual workload of checking orders daily.

Alternatively, some all-in-one seller tools include compliant review request automation as a feature. Verify that any tool only interacts with Amazon's official button and does not send external emails before using it.

When timing matters less than other factors

Optimal button timing improves response rates by several percentage points, but it cannot overcome fundamental product or listing issues.

Timing becomes irrelevant when:

  • The product has consistent quality defects. A well-timed review request for a defective product accelerates negative reviews.
  • Listing images or descriptions create false expectations. Customers who receive something different from what they expected will leave detailed negative reviews regardless of when you ask.
  • Competitors have 4.7+ star averages and hundreds of reviews. Late-entering products with under 50 reviews struggle to convert browsers into buyers, which reduces total order volume and thus total review opportunities. Timing optimization happens downstream of the traffic problem.
  • Your review request button access is restricted due to policy violations. Amazon disables the button for sellers with recent intellectual property complaints, inauthentic review activity, or other policy strikes. Fix the policy issue before testing timing.

Start timing optimization after confirming that your product quality, listing accuracy, and policy compliance are solid. Timing is a 3-7% improvement lever, not a 50% improvement lever.

Tracking long-term timing performance

Once you establish baseline timing windows for your catalog, review performance quarterly to catch shifts in customer behavior.

Two scenarios require timing adjustments:

Product maturity changes. A newly launched product with under 15 reviews benefits from aggressive 5-7 day timing to build initial social proof quickly. The same product at 200+ reviews can shift to 12-16 day timing to prioritize review quality over speed.

Market saturation increases. As product categories become crowded with competitors, customers receive more similar products simultaneously. A customer who orders three phone cases in one week may only review the one they like most. Later timing (day 18-22) gives your product more standalone use time before competing products arrive.

Set a calendar reminder every 90 days to pull your review response rates by ASIN and timing window. If response rates for a previously strong window drop by 3+ percentage points, rerun a timing test for that product tier.