Students in front of large screen. In the foreground a closed laptop. Most likely qualitative data analysis in a spreadsheet, but it could also be any other kind of debriefing.
Photo by Kalsau on Wikimedia Commons, CC BY 2.0

Operations

Part of Plan shopping feeds operations before peak season

When to trust a shopping feeds launch review and its sources

How to read a shopping feeds launch review: what gets assessed, what vendor claims are worth, and which independent sources support a decision.

What to take away

  • Recent launches lean on platform documentation rather than independent testing, so reviews increasingly quote vendor material instead of measuring it.
  • Google's mobile guidance is a public rule you can check yourself, making it a useful benchmark for claims about feed quality.
  • Data protection duties are assessable too: the ICO offers a self-assessment route for smaller organisations and lawful basis guidance for customer data used in feeds.
  • Anything a review cannot evidence, such as performance figures or support response times, belongs in your own evaluation.

What does a shopping feeds launch review actually assess?

A review like this assesses documentation, published rules and the claims a provider makes about them. It does not assess live performance in your account, and no supplier account was accessed for this piece.

Platform requirements are published, so a claim about feed formatting or landing page quality can be traced to its source. Google's guidance on optimising your website for mobile sets out expectations for the pages a feed points to, and it applies whether or not a vendor repeats it.

What cannot be checked is anything account-specific: your feed error rates, your approval times, your return on ad spend. Those depend on your catalogue and your team. The shopping feeds operations and delivery guide covers workflow and ownership in more depth.

Are vendor claims evidence?

Vendor claims are a starting point, not evidence. A supplier saying its tool fixes feed errors is describing capability, not your outcome. Reviews should label that material clearly.

A worked example: a vendor claims its tool makes product pages mobile compliant. Google's guidance on optimising your website for mobile is the published rule for those pages. The claim can be checked against that rule, which does not certify the tool or guarantee approval.

Vendor claims vs independent evidence

Vendor claim

Published
Often
Dated
Rarely
Checkable by non-seller
No
Survives vendor exit
No

Independent evidence

Published
Yes
Dated
Yes
Checkable by non-seller
Yes
Survives vendor exit
Yes

Independent evidence has three useful properties: published, dated, and checkable by someone who does not sell the product. Platform documentation and regulator guidance meet all three.

The practical test: ask which sentence would survive if the vendor disappeared tomorrow. If only the vendor's own copy would, the claim is marketing.

Which independent sources support a launch decision?

Regulators and official statistics give you fixed reference points. The Information Commissioner's Office publishes advice for small and medium organisations, including a self-assessment that helps a retailer judge how it handles customer data before adding a new feed channel.

If a feed sends customer data to a platform or an agency, you need a lawful basis. The ICO's lawful basis guidance explains the options and when each applies, which is more reliable than a vendor's summary. The ICO's Guide to the UK GDPR, which applies from 1 January 2021, is a dated reference point for those duties.

Statutory service standards are another fixed point. Our explainer on shopping feeds service standards in England sets out which duties apply where, so you can tell a legal requirement from a commercial preference.

Checklist for reading a launch review

  • Identify what was assesseddocumentation, a demo account or a live catalogue.
  • Note what was not assessed, including performance, support and integration depth.
  • Mark every vendor claim and check whether a published source confirms it.
  • Confirm the date of each source, because platform rules and guidance change.
  • Check whether data protection duties were considered, not just feed formatting.
  • Look for a named test period and named metrics; without them, the review is commentary.
  • Decide which claims you will verify before committing budget.

For example, a named test period would read: 1 September to 30 September 2025. Named metrics would include feed error rate, product approval rate and return on ad spend, reported weekly.

Common questions

Can a review tell me whether a tool will work for my catalogue?

No. A review can tell you what a supplier documents and which public rules apply. Only a trial against your own product data shows whether error rates and approval times improve.

Why do so many reviews rely on vendor material?

Independent testing is expensive and hard to repeat. Platform documentation is public and stable, so reviewers quote it.

What should I check before signing?

Check the lawful basis for any customer data you send, confirm the feed meets published platform requirements, and agree who owns feed quality internally. A short written brief beats a long demo.

How often should a launch review be revisited?

Revisit it when the platform rules or the supplier's documentation change. Treat any review older than a year as a prompt to recheck the original sources.

More in Operations