CommerceVigil

Feeds & synchronization

Merchant Center product feed not updating

When Merchant Center appears stale, first identify whether the source failed to send, Google failed to fetch, processing rejected rows, or the same product IDs retained old values. Those failures require different fixes.

Scan your Merchant Center free

No card required · Read-only Google access

Locate the last confirmed update

Open the relevant data source and compare its last attempted update, fetch result, and processing result. For API or platform syncs, inspect the integration's own delivery log. A green storefront update does not prove that a new Merchant payload was delivered.

Next inspect a known changed offer. Compare its source value, submitted ID, processed Merchant value, and update timestamp.

Scheduled source problems

A scheduled fetch depends on a stable URL, credentials when supported, valid file, and cadence that matches catalog changes.

  • The fetch URL redirects, expires, or becomes private.
  • The schedule uses an unexpected timezone.
  • The file was generated successfully but contains yesterday's data.
  • A format error causes rows to be rejected.
  • The source is fetched less often than fast-moving price or inventory changes.

API and platform sync problems

For API integrations, distinguish an accepted request from a processed product. Check authentication, quotas, partial failures, retries, and whether updates target the same account and data source. For platform apps, confirm the connection remains authorized and the intended catalog or market is selected.

IDs and caching can mimic a stale feed

Changing product IDs may create new offers while old ones remain visible. Reusing an ID for a different product can preserve confusing history. Separately, CDN, storefront, integration, or generated-file caches can publish old price and stock even after the commerce admin changed.

Avoid deleting everything as a first response. Preserve the identifiers and find the first layer where the new value disappears.

Verify recovery

After correcting the source or integration, trigger only the supported refresh, then check processing totals and the exact offer's processed values. Product issue reevaluation may occur after the source update itself, so treat those as separate checkpoints.

What CommerceVigil sees

CommerceVigil reads products and diagnostics that Merchant Center exposes and records sync outcomes. It does not operate your feed scheduler or platform plugin and cannot confirm a source value that never reached Google.

Frequently asked questions

Why is the fetch successful but products still old?

The fetched file may itself be stale, rows may fail processing, or the changed product may use an unexpected ID.

Should I create new product IDs to force an update?

No. IDs should remain stable for the same product; diagnose the update path instead.

Can processing take longer than upload?

Yes. Confirm the processed product state rather than relying only on delivery success.

Free Scan

See what Google currently reports for your account.

Inspect current products and issues without changing Merchant data.

Scan your Merchant Center free

No card required · Read-only Google access