Every eligible order asked, without clicking a single button.

Sellerbud watches your delivered orders, works out which ones Amazon will accept a review request for, and asks — nightly, in bulk, through Amazon’s official Request a Review. No buyer emails, no third-party messaging. You set the delivery window and the switch; every run logs what it found, what it asked, and what Amazon said back.

  • Every order sorted into Eligible, Requested, Returned, Cancelled or Not Eligible — click a card to filter the list.
  • One request per order, enforced at the database, inside the window you set and never before the marketplace's floor: 10 days after delivery on Amazon.in.
  • Every run keeps a record of each order it asked and what Amazon answered, with a plain-English reason on a refusal.

Illustration with sample data

Review automations

Amazon already has a button for this. Sellerbud presses it, every night.

Request a Review is one click per order, buried a page deep in Seller Central, valid inside a window that opens and closes without telling you. Five things turn that into something that runs itself — and keeps a receipt for every request it makes.

01 / 05Every order, in one state

Kalpavriksha Home & Living10,668 orders
Order book
Requested5,822
Not Eligible3,885
Returned820
Eligible78
Cancelled63
78
eligible nowthe queue the next run works through

Illustration with sample data

  1. Five states, one order book

    Every order in the marketplace is sorted into exactly one of Cancelled, Returned, Requested, Eligible and Not Eligible. The five counts are the filters, and the number on the Eligible card is the queue the next run will work through, each order checked with Amazon before it is asked.

  2. A window you set, on a floor you cannot cross

    One switch and two numbers: the earliest and the latest day after delivery you are willing to ask on. Underneath, the minimum is floored at 10 days on Amazon.in, so Sellerbud never asks for a review on a sale that could still come back.

  3. Nightly, or right now

    Leave the switch on and one run is created for the marketplace each day. Not willing to wait: Trigger Now starts a batch on the spot, and the Send icon on any eligible row asks for exactly that order. Only one batch can be in flight at a time.

  4. Every attempt, with Amazon’s own answer

    Open a run and you get every order it touched: when it was requested, whether Amazon accepted, and on a refusal a plain-English reason. A failed order stays re-eligible for later runs until it has been refused 3 times.

  5. One request per order, ever

    Once Amazon accepts a request, the order moves to Requested and no later run looks at it again. Two runs racing for the same order cannot both succeed, because only one successful request per order can be saved, and asking for one by hand is refused with the date of the earlier request.

Worked example

One night, nobody at the keyboard.

A single Amazon.in marketplace, from the order book to the requests Amazon accepted, across the sweep that ran at 01:00 this morning. Illustrative figures — the arithmetic is the product’s, the numbers are an example.

Automatic run · Amazon.in68d3e0b95a71c4d3220f8e1710,668 orders in the book · window 10–30 days after delivery · ran in 6m 14s
01

The book, as it stands now

Five states, one order each, decided server-side with fixed precedence. What is left is the queue the next run will take — small, because this morning’s already ran.

Orders in the book
10,668
Cancelled
−63
Returned
−820
Already requested
−5,822
Not eligible
−3,885
Eligible now78
02

What the 01:00 sweep did

Requests are paced 1 per second through Amazon’s own Request a Review endpoint, scoped to this seller so another account’s batch cannot throttle it. The whole sweep finished inside the worker’s 480-second budget.

Eligible when it started
356
Attempted
356
Refused by Amazon
−31
Successful325
03

The day, added up

Every accepted request is on the run ledger by order id, whether the nightly rule or a person started it, so a retry or a second run cannot ask the same order again.

Accepted in the 01:00 sweep
325
One order asked by hand
1
Refused, each with its reason
31
Reviews requested today326

Nobody opened the console. The switch was set once and the window was set once; overnight 325 delivered orders were asked for a review through Amazon’s own endpoint, 31 were refused with a reason, and every one of them is on the ledger by order id. The only manual act in the whole night was the single order someone asked for by hand this morning.

FAQ

The questions sellers actually ask.

Is this actually allowed?

It is Amazon’s own button. Every request is a call to the Solicitations API — the same “Request a Review” action in Seller Central, which sends Amazon’s own template from Amazon. Sellerbud never emails a buyer, never sees a buyer’s name or address, and cannot change a word of the message. Requests are paced through a dedicated rate limiter at one per second, scoped to your seller account, so a large batch behaves the way Amazon expects it to. One thing worth saying plainly: this feature asks for reviews and stops there. It does not read, display, rate or reply to the reviews that result, and it does not track star ratings or review counts.

When exactly does it ask?

You set the window as two numbers — the earliest and latest day after delivery — and the daily sweep only picks up orders inside it. Underneath, the effective minimum is floored at 10 days on Amazon.in (5 elsewhere, Amazon’s own earliest day), so anything you enter below that has no effect; the settings form will accept it, and eligibility will ignore it. Two more conditions apply and neither is negotiable: the order must not be cancelled, returned or refunded — by its settlement or by Amazon’s own order status — and it must not already have a successful request. Within a run, the orders closest to your maximum day are asked first, so nothing ages out while something newer jumps the queue.

What happens when Amazon refuses one?

Nothing is hidden. The attempt is written to the run as a Failed row with its reason — already requested, outside Amazon’s window, buyer opted out — and Amazon’s own text on hover. Where a retry can change the answer, Retry re-issues it there and then. A failed order stays eligible and is picked up by later runs until it has been refused 3 times, after which Sellerbud stops asking. Before each request Sellerbud asks Amazon whether the order can be asked yet; one it cannot is skipped, not counted, and simply comes up again in the next run.

Can the same order be asked twice?

No, and not as a matter of good behaviour — as a storage constraint. A partial-unique index on the marketplace and order id, filtered to successful solicitations, means a second successful request for one order cannot be written even if two runs race for it. A successful order is then permanently outside eligibility, so no later sweep will look at it again. Ask for one by hand and the request is refused with a pointer to the earlier one, including its date.

What does it take to run nightly?

One switch, and it is off by default. The automatic run happens once a day and picks up a marketplace only when its switch is on; with the switch off, Trigger Now and single requests still work. At most one automatic run happens per marketplace per UTC day, and only one batch can be in flight at a time; if the automatic run fails, a manual trigger is what recovers the same day.

Which marketplaces does it work on?

Every marketplace you have connected. Everything is scoped to one marketplace: the switch, the window, the runs and the counts are all per marketplace, and there is no cross-marketplace roll-up screen.

Know your numbers. Grow your store.

Connect your first marketplace in about two minutes, pick the plan that fits your store — and move up when the numbers earn it.

We use cookies for analytics, to improve Sellerbud, and for marketing, to measure our ads and the links we send. If you say no, we keep only what this visit needs. Privacy policy