Operations
Part of What commerce reviews operations means for retail feedback teams
Seven steps to a commerce reviews operating workflow
A seven-step commerce reviews operating workflow for retail teams in England, covering consent, crawlability, moderation, ownership and a short glossary of terms.
What to take away
- Most teams fail because they collect reviews before agreeing who owns consent, moderation and takedown decisions.
- Seven steps is enoughrequest, capture, moderate, publish, respond, report, review.
- Each step needs one named owner and one written rule, or the workflow collapses when someone leaves.
- Consent and opt-out records sit under data protection rules, not under marketing preference alone.
- Crawlability and structured data decide whether the reviews you gather are ever found.
Set the workflow scope
Write down which products, markets and languages the workflow covers before anyone sends a review request.
Decide where reviews live. A retailer selling through its own site, a marketplace and a social channel needs one master record and three publication routes. For the wider delivery picture, the operations and delivery guide for 2027 sets out how these choices fit together.
Name owners and roles
Give every step an owner. A typical mid-sized retailer needs a request owner, a moderation lead and a reporting analyst, even if one person holds two of those hats part time. You can compare typical splits in the commerce reviews team roles guide.
Ownership matters most at the edges: who approves a negative review response, who decides a review is fake, and who signs off a takedown. If those three questions have no owner, moderation becomes a queue nobody clears.
Run the seven steps
- Request. Trigger a review request after delivery, not after checkout.
- Capture. Store the rating, the text, the date and the order reference together.
- Moderate. Check for personal data, profanity and incentives before publication.
- Publish. Push the approved review to every channel from one source.
- Respond. Reply to negative reviews within an agreed window.
- Report. Track volume, average rating and response time weekly.
- Review. Revisit the rules each quarter and retire what no longer works.
Steps three and five carry the most risk. A moderation rule that removes every critical review damages trust; one that publishes everything unread exposes you to complaints.
| Step | Owner | Rule |
|---|---|---|
| 1 Request | Request owner | After delivery |
| 2 Capture | Request owner | Rating and order ref |
| 3 Moderate | Moderation lead | Remove personal data |
| 4 Publish | Moderation lead | One master record |
| 5 Respond | Moderation lead | Reply in window |
| 6 Report | Reporting analyst | Weekly volume and rating |
| 7 Review | Workflow lead | Revisit each quarter |
Worked example: one coat order.
Request: two days after delivery. Capture: four stars and a sizing note. Moderate: no personal data. Publish: product page and marketplace. Respond: answered in two days. Report: counted that week. Review: rule unchanged.
One Master Record, Three Routes
- Own site: publication route one
- Marketplace: publication route two
- Social channel: publication route three
- One master review record
- Edit once, audit trail intact
Handle consent properly
The Information Commissioner's Office publishes a direct marketing checklist covering consent, opt-out and record keeping. Review requests sent by email sit close to that territory, so treat the checklist as your baseline for wording and for how you log refusals.
Who Owns The Edge Cases
Who approves a negative review response?
named approver clears it
moderation queue stalls
Keep two records: the basis for contacting the customer, whether consent or legitimate interest, and their separate choice about publishing their words. A customer can agree to be contacted and still refuse publication.
For example, a shop sending 5,000 requests a month might see 600 responses and 40 refusals to publish. Honour those refusals without deleting the underlying order data.
Make reviews crawlable
If search engines cannot reach your review pages, the content earns nothing. Google's documentation on how it interprets the robots.txt specification explains the directives that block or allow crawling, which is the first thing to check when review pages stop appearing in search results.
Test after every platform migration. A staging rule left in place is a common cause of missing review pages, and it is invisible until traffic drops.
Publish and respond
Paid placement of review content and UGC follows the CAP Code enforced by the Advertising Standards Authority (ASA), alongside the ICO's data protection rules. LinkedIn's getting started guide for advertising covers campaign setup and targeting if you plan to amplify customer stories beyond your own site.
Keep the workflow rule simple: no paid amplification of a review until the moderation lead confirms it is genuine, current and disclosed as a customer review.
Common questions
Who should own the review workflow?
One named person should own the end-to-end workflow, even if individual steps sit with other teams.
How long should review data be kept?
Set the retention period from your stated purpose, your contract terms and any limitation period for complaints. Document it and delete data once that purpose ends.
Do review requests need consent?
It depends on the basis you rely on and how you contact the customer.
How often should the workflow be reviewed?
Quarterly is workable for most teams.
