Quick answer
Build the workflow around order facts: delivery status, request window, previous request history, support issues, refunds, returns, cancellations, and account ownership. The operator's job is to send the official Amazon review request for eligible orders and document why anything else was skipped.
Seller Central review request work gets risky when every operator uses a different judgment call. One person checks yesterday's delivered orders. Another checks only large orders. Someone else skips orders that "feel" likely to complain. That is not a workflow.
A cleaner SOP gives the operator a simple decision path: identify orders, remove orders that do not belong in the batch, send the official request where appropriate, and keep a plain record of what happened.
The operator checklist
- Start from delivered orders in the request window used by the seller's account.
- Confirm the order has not already received the official Amazon review request.
- Remove canceled, refunded, returned, pending, and already-handled orders from the batch.
- Route unresolved delivery, item, refund, or service issues to support before review request work.
- Apply the same timing rule across eligible orders.
- Log sent, skipped, failed, and support-routed orders with a short reason.
What operators should check before sending
| Check | Send? | Operator note |
|---|---|---|
| Delivered order inside the seller's review request window | Usually yes, if no other exclusion applies | Use the official Amazon review request workflow and record the result. |
| Already requested | No | Skip it and keep the previous request status visible. |
| Open buyer support issue | Not yet | Route the issue to support. Do not turn a support message into review persuasion. |
| Refunded, returned, canceled, or pending order | No | Keep it out of the review request batch and note the order state. |
| Operator thinks the buyer might leave a negative review | Do not use that as the rule | Review request decisions should come from order facts, not expected buyer sentiment. |
A simple daily or weekly SOP
- Open the seller account or connected tool that shows recent delivered orders.
- Filter to orders old enough for the account's request timing rule.
- Remove orders that are too old, already requested, or no longer eligible for the workflow.
- Check whether any order belongs in support, refund, return, or fulfillment follow-up instead.
- Bulk send official Amazon review requests for the remaining eligible orders.
- Review failures and retry only when the order still qualifies.
- Save the request history so the next operator does not repeat the same work.
Operator rule
The SOP should not ask, "Is this buyer happy?" It should ask, "Is this order eligible, in the right window, not already requested, and free of unresolved support work?"
What the SOP should forbid
- No incentives, coupons, refunds, gifts, or benefits tied to a review.
- No custom language asking for a positive review or preferred rating.
- No skipping eligible orders because the buyer seems unhappy.
- No mixing buyer support messages with review request language.
- No unclear handoff where one operator cannot see what another operator already sent.
How ReviewOps fits
ReviewOps helps sellers and operators run this SOP without living in Seller Central. Teams can find eligible orders, bulk send official Amazon review requests, schedule request windows, and keep a history of sent, skipped, failed, and already-handled orders across connected seller accounts.
Make review request work easier to hand off
ReviewOps helps Amazon sellers reduce manual admin around eligible review requests without incentives, review gating, or custom buyer persuasion.
Open ReviewOpsRelated guides: review request compliance checklist, review request audit trail, and Buyer-Seller Messaging vs Request a Review.