3 ways to split commerce reviews data and source ownership

What to take away

How to frame the roles before you hire

Inclusion criteria and geography

Use three tests before you assign anyone. Does the person touch the source directly? Can they change what a shopper sees? Are they accountable for a number in reporting? If the answer is no to all three, they are a stakeholder, not an owner.

UK data protection rules apply across England, Scotland, Wales and Northern Ireland, though some advertising codes are administered differently. The operations and delivery guide sets out the delivery sequence most teams follow.

Apply the same tests to agency and contractor arrangements. An external owner still needs an internal counterpart who signs off changes and holds the register.

The four data sources to allocate

Most retailers draw review content from four places: on-site submission forms, email or SMS requests, marketplace and social imports, and third-party syndication feeds.

Each source has a different refresh rate and failure mode. Email requests fail quietly when consent records are thin, so read the ICO's step-by-step guide to direct marketing for your small business before automating them. Imported feeds fail loudly, usually as duplicate reviews.

Map your own sources before copying a role template. A subscription retailer rarely handles the same mix as a stocked one.

Who owns what, and when

Collection and request ownership

Give one named person the request calendar, suppression rules and sender reputation; they should know which segments were contacted, how often, and what last month's opt-out rate looked like. This role sits close to CRM.

If nobody holds it, requests reach people who already unsubscribed. Document the cadence and wording too, so a replacement inherits the same standard rather than a blank calendar.

Processing and moderation ownership

A second owner handles cleaning, deduplication, language tagging and the moderation queue. They decide what is escalated, rejected or answered. This role keeps user-generated content usable for search and for category pages. Name a backup for the moderation queue, so holiday cover does not stall publication.

Google's crawler overview explains how its crawlers fetch and index pages, which matters when a review widget hides content behind scripts. For the day-to-day sequence, see the operating workflow.

Publication, syndication and reporting ownership

A third owner controls what appears on product pages, which partners receive feeds and which numbers reach the board. They reconcile displayed review counts against the source system monthly. Agree who approves a feed change before partners receive it, as feeds are awkward to recall.

Where paid or sponsored placement is involved, the commercial context matters. The IAB UK's account of its own formation and remit is a reasonable starting point for how UK digital advertising bodies organise themselves.

Worked example and handoff rules

A three-person split with labelled figures

Take an illustrative retailer with 12,000 monthly orders. One coordinator spends about 40% of their time on requests, at a fully loaded cost of roughly £2,800 a month. A content and moderation specialist handles processing at about £2,400 a month.

A part-time analyst owns publication and reporting at about £1,200 a month. Total illustrative cost: £6,400 a month. Outsourcing the same work at an illustrative £9 per processed review would cost £13,500 for 1,500 reviews, more than double.

Handoff rules that survive staff changes

Write four lines per source: owner, backup, trigger and evidence. The trigger starts the handoff, such as a weekly export or a moderation queue above a set size. The evidence proves it happened.

Keep the register beside your review policy so new starters find both. Review it quarterly, and reassign rather than add roles when volumes change. Name a backup person rather than a team, or handoffs stall during leave.

Common questions

Should one person own every review source?

Only in very small teams. Beyond roughly 2,000 orders a month, sending requests and moderating replies start to conflict, because one rewards volume and the other rewards care.

Do we need a dedicated legal reviewer?

No. Build legal checks into each owner's checklist instead, covering consent, disclosure and retention. Escalate edge cases rather than create a permanent post.

How do we know the split is working?

Track three measures monthly: duplicate rate, time from submission to publication, and the gap between displayed and source counts. If all three are stable, the split is holding.

What if we buy customer review software instead of hiring?

The tool changes who does the work, not who is accountable. Name an owner for configuration and an owner for the data leaving the platform.