You changed a price this morning. Two hours later Merchant Center still shows the old value, your Shopping ads still bid on the old value, and nothing anywhere is flagged. From Google's side nothing is wrong. Every stage did its job on its own schedule, and your edit is still in the queue.
What you'll take away
- Four stages sit between your edit and the ad — fetch, processing, item review, serving. Each has its own clock.
- Three of them publish a timestamp — the stuck stage is identifiable in a few minutes of clicking.
- Diagnose top down — a delay upstream looks exactly like Google being slow downstream.
- Most gaps are stage one — a fetch schedule that never lined up with when your file regenerates.
Why isn't my product feed updating in Google Merchant Center?
Because one of four sequential stages is lagging: the scheduled fetch has not run or failed silently, the downloaded file has not finished processing, the changed items have re-entered review, or the serving layer is still working from cached data. Merchant Center publishes a timestamp for three of the four, so the stuck stage is identifiable without guessing.
Where the lag lives, and where its timestamp is
The stages run strictly in order. Each one only starts when the one before it finishes, which is why a scheduling gap at the top produces a symptom that looks like slowness at the bottom.
| Stage | What it does | Where the timestamp lives |
|---|---|---|
| 1. Fetch | Downloads your file on the feed's schedule | Products > Feeds > your feed > Processing |
| 2. Processing | Parses and validates the file row by row | The same Processing tab, with error counts |
| 3. Item review | Approves new and substantially edited items | Status column in Products, plus item detail |
| 4. Serving | Picks up approved data for ads and free listings | No timestamp. Diagnosed by elimination |
Stage 1: the fetch schedule
Google downloads your feed file only at the interval set in the feed's fetch schedule. Set it to daily, edit your source this morning, and the change waits for tonight. Fetching is also the most common failure point because it fails quietly. A moved URL, a server returning errors, a robots.txt rule blocking Google's fetcher, expired credentials: they all produce the same outcome, which is Merchant Center continuing to serve the last version it downloaded successfully.
Stage 2: processing
A downloaded file is not a live feed. Google parses and validates it row by row, and until that pass finishes the previous parsed version keeps serving. Large feeds take longer. Malformed rows, encoding problems, and schema mismatches slow the pass or drop items entirely, and a run can complete successfully with fewer items than you submitted.
Stage 3: item review
Processed is not approved. New products sit in review before they can serve, and substantial edits to existing ones can send them back: a new title, a new image, a changed category. Price and availability changes on already-approved items usually serve without a full re-review, which is why a price edit and a title edit in the same upload behave differently.
Stage 4: the serving cache
Shopping ads and free listings do not read your processed feed in real time. They serve from a layer that picks up approved data on its own cadence, so Merchant Center can show the new price while the auction still carries the old one. If the data inside Merchant Center is already right, this is the only lag left, and there is nothing to fix.
A successful fetch means the file arrived
It does not mean your change was in it. Feed apps and export scripts regenerate on their own schedule, so Google can download a perfectly healthy file that still holds this morning's stale price.
What order should I run the checks in?
Top down, stopping at the first broken stage. Working backwards means debugging symptoms while the cause sits untouched upstream.
Six checks, in order, stopping at the first failure
Check which system you're actually looking at
Google Ads reports and serves on its own lag behind Merchant Center. Before concluding that an update is stuck, confirm the screen in front of you. Merchant Center is the source of truth for feed state.
How do I stop updates getting stuck next time?
Align the two schedules that are easy to leave misaligned: how often your source file regenerates, and how often Google fetches it. If the file rebuilds hourly and the fetch runs daily, every update waits a day no matter what else you fix. Match fetch frequency to how fast your prices and stock actually move, and keep stage one boring.
If your pattern is repeated fetch failures rather than scheduling gaps, the problem is usually hosting: the URL itself, or the firewall and CDN rules sitting in front of the file.
Common questions
How long does a Google Merchant Center feed take to update?
It depends on which of the four stages you are waiting on. The fetch runs on the schedule you set, processing follows the download, item review applies to new and substantially changed products, and the serving layer picks up approved data on its own cadence. A price edit on an approved item is the fastest path through all four.
Why does Merchant Center show a successful fetch but the old price?
Because the fetch succeeded on a file that still contained the old price. Feed apps and export scripts regenerate on their own schedule. Load the feed URL directly and read the row yourself before assuming Google is at fault.
Can I force Merchant Center to refresh a feed immediately?
You can trigger a manual fetch from the feed's Processing tab, which skips the wait for the next scheduled run. It does not skip processing or item review, so a manual fetch shortens stage one only.
Why do my Google Ads and Merchant Center show different data?
They run on separate cadences. Merchant Center reflects the processed feed, while Google Ads serves and reports on its own lag behind it. Treat Merchant Center as the source of truth for what the feed currently says.
Free tool
Not sure if your feed has errors?
Run your Google Shopping, Meta, or TikTok product feed through our free validator and get a prioritized error report before channels reject your products.
Editorial note
Written by Muhammad Norafif
This article was published on August 24, 2026 and last updated on August 24, 2026. NextFeed builds product feed management software for Shopify, Google Shopping, Meta, and other commerce channels.