Independent verification layer

Catch Shopify ↔ Google Merchant Center drift before it costs you sales

Your Shopify store can be healthy. Your Google Merchant Center can show “Connected.” And your product data can still be wrong.

One complete scan, free. No feed changes. Nothing is modified.

  • Read operations only
  • No Google Ads changes
  • No product edits
  • No feed modifications
Latest scan23 issues found

Checked

247

Healthy

224

Issues

23

  • Missing from Google7
  • Price mismatches5
  • Availability mismatches6
  • Ghost products3
  • Stale products2

The gap nobody watches

Connection health is not data correctness

Every part of the chain reports that it is fine. None of them is actually comparing the two catalogues, product by product, to see whether they still agree.

ShopifyAll good

Product is active, in stock, priced at $24.00.

Your feed appAll good

Sync successful. Last run 2 hours ago.

Merchant CenterAll good

Account connected. Products: 1,204.

Reality

Google is serving $19.99 for that product, and 7 of your active products are not in Merchant Center at all.

Check my catalogue

What it finds

Real differences, graded by what they cost you

Findings are separated into critical, warning and informational — because a product that vanished from Google is not the same as a formatting nit.

Critical

Active products missing from Google

Products that are live and in stock in Shopify, but that Google Merchant Center has no record of at all.

Critical

Stale prices

Google serving a price your store no longer charges — the most common cause of price-mismatch disapprovals.

Critical

Incorrect availability

In stock in Shopify but out of stock on Google (invisible to shoppers), or the reverse (clicks that cannot convert).

Critical

Ghost products

Archived, drafted or deleted in Shopify, yet still live in Merchant Center and still taking clicks.

Warning

Missing variants

The product is there, but sizes or colours quietly stopped being submitted.

Warning

Silent catalogue mismatches

GTIN and SKU differences, and products where Google is holding an older version of your data.

Evidence, not alarms

Every finding shows both sides

For each affected product you see the Shopify value next to what Google currently sees, with only the differing fields highlighted. No jargon, no root-cause guessing — just what the two systems disagree about, and when it started.

  • First detected and last detected timestamps
  • Whether the issue is new, persistent or resolved
  • Per-product scan history
  • A clear “we could not verify” state when an API is unavailable
Field
Shopify
Google sees
Product
Navy Hoodie — M
Navy Hoodie — M
SKU
HOO-014-M
HOO-014-M
Price
68.00 USD
59.00 USD
Availability
In stock
Out of stock
Status
Active · Published
Present · Approved
First detected 6 days ago · still present · matched on SKU (90% confidence)

How it works

Three minutes to your first real answer

  1. 01

    Connect Shopify (read-only)

    A single read_products scope. No write access is requested, so the app cannot change anything even in principle.

  2. 02

    Connect Merchant Center

    One Google permission for Merchant Center content, used for reads only. No Google Ads scope is ever requested. Pick the account if you have several.

  3. 03

    Run the scan

    We read both catalogues, match products across SKU, GTIN, offer id and variant id, and show you exactly where they disagree.

Where it fits

We don't manage your feed. We verify it.

Feed management tools like Simprosys and DataFeedWatch are good at building and sending your feed. Merchant Center diagnostics are good at telling you what Google rejected. Neither of them answers the question this product exists for.

Feed managers

Build and send the feed. They report on their own sync — the same system doing the work is grading the work.

Merchant Center diagnostics

Report what Google rejected. Silent divergence between two accepted states is invisible to them by design.

FeedParity

Reads both catalogues independently and compares them. Works alongside whatever feed tool you already use.

Keep your feed tool. Keep your agency. This is the second opinion that reads both systems directly and tells you whether they still agree.

Pricing

Start free. Keep watching for $19/month.

The free scan shows every finding in full. We do not hide your problems to sell you the fix.

Free scan

$0one scan

One complete verification of your catalogue.

  • One full Shopify ↔ Google comparison
  • Every finding shown in full — nothing hidden behind a paywall
  • Side-by-side evidence for each affected product
Run free scan

Monitor

Recommended

$19/month

Daily verification, history, and alerts when something changes.

  • Automatic daily scan
  • Email alerts for new drift
  • Price, availability, missing and ghost product alerts
  • Drift history and resolved-issue tracking
  • Unlimited manual re-scans
Start monitoring

Common questions

Will this change anything in my store, feed or ads?+

No. FeedParity only performs read operations. Shopify is connected with the read_products scope alone, and the grant is refused outright if it comes back containing any write scope. Google offers a single Merchant Center permission that is technically read/write — there is no read-only variant — so we are explicit about it: our Google client has no write method, and no Google Ads scope is ever requested.

Do I have to stop using my feed app?+

No — and you should not. This is a verification layer that sits alongside whatever builds your feed. It has no opinion on which tool you use.

What happens if an API is down during a scan?+

The scan is marked “could not verify” and reports nothing. A failed read must never look like catalogue drift, so absence-based checks are suppressed whenever a catalogue was only partially readable.

How do you avoid false alarms?+

Values are normalised before comparison — currency formats, decimal precision, stock wording, casing, UPC vs EAN barcodes, active sale prices, multi-country feeds. Products whose identifiers are ambiguous are reported as unverifiable rather than guessed at.

What data do you store?+

Account details, encrypted OAuth tokens, scan results, and product snapshots only for products involved in a finding. You can disconnect and delete everything from the settings page at any time.

Find out what Google actually sees

One free scan of your whole catalogue. If everything matches, you will know that too — and that is worth something.

Run free scan