Book a live demo — see your catalog's review coverage →
Blog

Borrowed trust: the compliance rules every team should know before syndicating reviews

Displaying another company's reviews is legitimate. Doing it without permission, attribution, or an audit trail is not. A plain-language guide to the boundaries.

Trust
Compliance
Retailers
Aug 21, 2026 · 8 min read

By Tony Chiappetta, Founder

Borrowed trust: the compliance rules every team should know before syndicating reviews

This is not legal advice, and your counsel gets the final word. It is a plain-language summary of the boundaries we designed REVEX around, and the questions any retailer or brand should be able to answer about their own review program.

Regulators in the US, UK, and EU have all sharpened their focus on consumer reviews in recent years. The consistent theme is not "syndication is bad." It is that reviews must be genuine, must be about the product being sold, and must not be presented in a way that misleads a shopper about their origin or their representativeness.

Syndication satisfies all three — if you build it correctly.

The four questions to be able to answer

1. Do you have the right to display this content?

Reviews are user-generated content. The company that collected the review typically holds a license to it through their terms of service, and that license is what makes onward distribution possible. If you are the retailer, your right to display flows from the brand, not from the fact that the content is publicly visible on the internet.

"It was on their website" is not a permission. Scraping a brand's PDP and reposting the content is a rights problem regardless of how the review reads.

What good looks like: an explicit, recorded, revocable grant from the review owner that names what may be displayed and where. When the grant ends, the content comes down automatically.

2. Is the reader told where the review came from?

Attribution is the single most important display decision. A shopper reading a review on your product page reasonably assumes it was written by one of your customers unless you tell them otherwise.

Show, next to syndicated content: the source organization, the collection date, and — where you can — how the review was verified (verified purchase, invited buyer, unverified). Do not describe a syndicated review as a verified purchase from your store. That is the specific misrepresentation that turns a legitimate program into a deceptive one.

3. Is the review about the product on this page?

Google's review snippet guidance and general advertising law converge here: the review must reflect a genuine opinion about the item being sold. Aggregating reviews across different products to inflate a rating is a problem twice over — a search-quality violation and a consumer-deception risk.

Two rules follow. Match at the correct granularity, and be explicit when you roll model-level reviews up to a colorway page. A line reading "Reviews for all colorways of this model" is honest and costs you nothing.

4. Can you prove any of this later?

Compliance is mostly an evidence problem. If a review's authenticity is challenged — by a competitor, a regulator, or a shopper — you want to produce a record, not a recollection.

The record should include: where and when the review was collected, whether the reviewer was verified, whether it was invited or incentivized, what permission allowed it to appear on this page, and every edit or moderation action taken since. Immutable is better than editable: the original content should be preserved even when a display version is moderated.

This is why REVEX writes a provenance receipt for every syndicated review and exposes a public verifier. If someone doubts a review, they can check it themselves rather than take your word.

Practices to avoid

  • Incentivized reviews without disclosure. Discounts or free product in exchange for a review are permissible in most jurisdictions when clearly disclosed. Undisclosed, they are deceptive.
  • Suppressing negative reviews. Filtering out one-star reviews while displaying the rest misrepresents the distribution. Moderate for policy violations — abuse, PII, off-topic content — never for sentiment. Write your moderation rules down, apply them symmetrically, and log every action.
  • Stale content after revocation. If a brand ends a partnership, their reviews must come off your pages. A program that cannot revoke cleanly is a liability.
  • Review gating. Asking customers about their experience and only routing happy ones to the public review form manufactures a false distribution.
  • Uncontrolled AI-assisted review text. Summaries generated from real reviews are fine when labeled as summaries. Generated content presented as a customer's own words is not.

A short internal checklist

Run this once a quarter:

  1. For every source of review content on our PDPs, can we name the permission that allows it?
  2. Does every syndicated review display its source and collection date?
  3. Does our structured data describe exactly what a human sees on the page?
  4. Can we produce the full history of any single review in under five minutes?
  5. Are our moderation rules written down, and are they applied to positive and negative reviews identically?
  6. If a partner revoked today, how long until their content is off our site?

If you can answer all six, syndication is one of the safest things in your marketing stack — the content is real, it is attributed, and it is auditable. If you cannot answer them, the risk was already in your program before syndication entered the picture.