Send the review request to the right order, automatically
Amazon’s “Request a Review” action runs from a rule engine: you decide which orders it fires on and when. The message itself is Amazon’s fixed template — it cannot be customised, and that is the point. One request per order, and any order you want left out goes on a blocklist.
You do not write the message — and you cannot
Amazon’s Solicitations service exposes exactly one action: “Request a Review”. The text the buyer receives is Amazon’s own template, and no word can be added to it.
That is Amazon’s rule rather than a gap in the tool, and it has an upside: there is no way to send wording that breaches policy. The only thing you decide is targeting and timing.
The campaign picks the order
Campaigns run in priority order. Each one collects the orders that match its filters, have not already had a request, and are not on the blocklist.
Amazon is then asked whether the action is available for that order <b>right now</b>. Its eligibility window is not reimplemented here — Amazon answers and the engine follows. Eligible orders fire; the rest wait.
One request per order, with a way back
Amazon allows at most one request per order. That rule is enforced as a database constraint rather than a warning in the interface: a second request for the same order cannot be written at all.
To exclude an order entirely, put it on the blocklist. The reverse exists too — “request now” on the order list skips the campaign filters and checks only Amazon’s live eligibility.
Why this one does not go through the approval queue
AI suggestions in Cirometre are never written to Amazon without your approval. Review requests are the exception, for a specific reason: there is no suggestion of ours involved. The content is Amazon’s template and the only decision is timing.
Unlike a bid or budget change, this action moves no money, no inventory and no ranking, and the blocklist plus pausing a campaign stay in your hands. Putting a risk-free action in the approval queue would dilute what the queue is for.
Frequently asked questions
Can I change the message the buyer receives?
No. The content is Amazon’s fixed template and the API allows no customisation. You decide which orders and when.
Can the same order be asked twice?
No. Amazon allows one request per order and the rule is enforced as a database constraint, so a second record cannot be written.
How do I keep an order out of it?
Put it on the blocklist; it will not enter any campaign.
If it runs automatically, what stays under my control?
Campaign rules, the blocklist and pausing a campaign. It is outside the approval queue because the content is Amazon’s own template and the action moves no money, inventory or ranking.