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.