A Shopify store selling consumer electronics runs Google Shopping ads. Their feed syncs once per day via a plugin — standard setup, nothing unusual. On Tuesday morning, they run a flash repricing to match a competitor's sale: 40 products drop in price, some by 15–20%. The repricing executes at 9am. Prices update in Shopify. The store is now competitive.
By Tuesday afternoon, Google is still showing their pre-sale prices in Shopping results. Competitors who updated their feeds that morning — including the one they were trying to match — are showing the cheaper prices in the same row. The store's impression share drops steadily through the afternoon as shoppers click the cheaper-looking listings next to theirs. Cost per click stays the same. Conversions don't improve.
By the time the feed refreshes overnight, the competitor's sale is long over. The store paid for 8 hours of traffic disadvantage and gained none of the visibility benefit they'd priced for. The flash sale achieved almost nothing in Google Shopping — and they had no idea.
This is what Google Merchant Center feed pricing divergence looks like in practice. It's not a dramatic failure. It's a quiet, consistent drain on your Google Shopping performance that most store owners never directly attribute to their feed.
What the Google Merchant Center Feed Actually Is
The Google Merchant Center product feed is a structured data file — typically submitted via Google's Content API or a scheduled feed URL — that tells Google what you sell, at what price, and whether it's in stock. Google uses this data to populate both paid Shopping ads and free product listings in the Shopping tab.
The critical thing to understand: the feed is not live. It's a snapshot. Google ingests a version of your product data and uses that version until it refreshes. How often it refreshes depends entirely on how your feed is configured.
For stores using a feed file URL (the most common plugin-based setup for Shopify and WooCommerce), Google typically re-crawls the feed once per day — and sometimes less frequently. The schedule is set in your Merchant Center account and controlled by Google's crawl bot. You can request an immediate resync, but it's still not instantaneous.
For stores using the Google Content API for Shopping, the situation is entirely different. API-based updates are processed in near real-time — typically within minutes. A price change pushed via the API is reflected in Shopping results far faster than a file-based feed waiting on Google's crawl schedule.
Most mid-sized Australian e-commerce stores are on the file-based feed path. Which means there's a window — sometimes 24 hours or more — between when your prices change and when Google knows about it. In a competitive Google Shopping environment, that window is costly.
The Four Ways Feed Pricing Goes Wrong
1. Feed sync delay
Your store price changes but the feed updates on a 24-hour schedule. During that window, Google shows your old price. If your old price was higher than your new (repriced) price, shoppers see a misleadingly expensive listing in Shopping results and click elsewhere. The sale you engineered to win clicks doesn't win them, because Google is still advertising the price you had yesterday.
The reverse is equally damaging: if you raise a price and the feed still shows the old lower price, Google will crawl your landing page and find a mismatch — the page price is higher than the feed price. This triggers a price mismatch disapproval (covered in detail below), and the product stops appearing in Shopping entirely until you fix it.
2. Sale price not propagated to feed
You run a sale on your website — you've applied a discount in Shopify or created a sale event in Neto. The store shows the sale price correctly. But your feed plugin only reads the regular price field, not the sale price. Google's feed shows $129. Your landing page shows $89. Shoppers who find your listing in Shopping see $129, click through expecting to save, and arrive at a page showing $89 — which is actually a positive surprise, but it damages trust in the data consistency of your listings.
More importantly: the proper way to signal a sale in Merchant Center is via the sale_price and sale_price_effective_date fields. Products with these fields set correctly get a strikethrough display in Shopping results (showing both the original price and the sale price), which is a significant click-through advantage. Stores whose feed plugins don't populate these fields miss that visual treatment entirely.
3. Price mismatch disapprovals
Google periodically crawls your product landing pages and compares the price it finds on the page to the price in your feed. If they differ beyond a small tolerance threshold, the product is flagged for "price mismatch" and disapproved. Disapproved products don't show in Shopping results — not in ads, not in free listings. They simply vanish from Google Shopping until the issue is resolved.
For stores that reprice frequently and whose feed syncs infrequently, this is a persistent problem. Every time a price changes in your store, there's a window where the landing page price and the feed price diverge. If Google crawls a landing page during that window, the product gets disapproved.
4. Currency and tax errors
Australian merchants must submit prices inclusive of GST in their Merchant Center feed. This is a hard requirement for Australian Shopping surfaces. Stores that submit prices exclusive of GST — perhaps because their internal product database uses ex-GST pricing — create a systematic mismatch: the feed shows $90.91, the landing page shows $100.00. Every single product in the catalogue has a price mismatch. Google's crawler will flag each one.
This is an easy mistake for stores migrating from a B2B or wholesale operation where ex-GST pricing is the norm internally. The feed submission layer needs to handle the GST-inclusive conversion explicitly — it can't be assumed the plugin handles it correctly without verification.
These four failure modes don't stay isolated. A store with a 24-hour feed sync delay, a plugin that doesn't read sale prices, and GST confusion in their pricing data can end up with 30–40% of their catalogue either misrepresented or disapproved in Google Shopping — without any single alert telling them it's happening.
The Price Mismatch Disapproval Problem in Detail
Price mismatch disapproval deserves its own section because it's simultaneously the most common and the most invisible problem in Merchant Center management. Stores lose Shopping visibility without any notification sent to their inbox. The products just quietly disappear from Google Shopping results.
Here's the mechanism: Google operates a dedicated crawl that visits your product landing pages independently of its main search crawl. This crawl is specifically looking for the price displayed to the user on the page. It then compares that price to the price field in your feed. If the difference exceeds a small threshold — commonly observed to be around 5%, though Google does not publish an exact figure — the product is flagged.
The flag shows up in Merchant Center under Products → Diagnostics. Look for "Price mismatch" in the item disapprovals section. You'll see a count of affected products and, if you drill in, the specific SKUs. Most stores that check this for the first time find far more disapprovals than they expected.
The fix sounds simple: get your feed in sync. If you're using a plugin, force a resync immediately. If you're using the Content API, push a price update for the affected items. But the underlying fix is making sure the price mismatch opportunity can't keep recurring — which means either faster feed sync intervals or a workflow that updates the feed whenever the store price changes.
A store with 500 SKUs in Google Shopping and 15% of them disapproved for price mismatch is effectively running Shopping ads on 425 products while paying for 500. The disapproved products generate impressions that never convert — they don't even show. The spend gets redistributed to the remaining products, raising their frequency. Cleaning up disapprovals regularly is one of the highest-ROI maintenance tasks in Google Shopping management.
Keep Your Merchant Center Feed in Sync Automatically
PriceSpy pushes price updates to your product feed immediately after repricing — so Google always shows your current prices, not yesterday's.
How Repricing Breaks Your Feed (and How to Fix It)
Dynamic repricing introduces a specific and underappreciated failure mode: every time your repricing tool changes a price, the feed and the store diverge by definition — until the feed catches up. If your feed syncs once per day and your repricing tool adjusts prices 30 times per day (common for busy catalogues in competitive categories), you have a near-constant state of divergence.
The sequence looks like this:
- Repricing tool detects a competitor has dropped their price at 10:15am
- Your repricing rule triggers — your store price updates from $149 to $144
- Google crawls your landing page at 11:30am and finds $144
- Your feed still shows $149 (last sync was 2am)
- Price mismatch: product disapproved
- Feed syncs at 2am the next day — product is re-approved
- By 2am, your repricing tool has changed the price again — the cycle starts over
For stores with aggressive intraday repricing and a daily feed sync, this cycle can mean products are in a near-permanent state of price mismatch disapproval during business hours. They show in Shopping briefly overnight after the feed sync, then get disapproved again as repricing resumes in the morning. The store's Shopping impression data looks erratic and hard to explain.
The architectural fix is clear: the repricing workflow and the feed update must be coupled. When a price changes in your store, the feed must be updated as part of the same action — not hours later on a scheduler. This requires either a repricing tool that triggers a Content API push when it updates a price, or a near-real-time webhook integration between your store and Merchant Center.
PriceSpy handles this as part of its core repricing workflow. When a price update is applied to your Shopify, Neto, WooCommerce, or Magento store, the Merchant Center feed update is triggered in the same pipeline. The store price and the feed price stay in sync. The Google Shopping listing reflects your actual competitive position — which is the whole point of repricing in the first place. You can see this in action in the live demo.
See the full list of PriceSpy's feed integration capabilities — including the supported platforms and how the real-time sync is implemented.
Supplemental Feed Best Practices for Australian Merchants
Beyond fixing the sync problem, there are several feed configuration decisions that have an outsized impact on Google Shopping performance for Australian stores specifically.
Use the Content API for high-velocity products
Not all products in your catalogue are equally price-sensitive or equally reprice frequently. For products where you reprice multiple times per day — typically your highest-volume, most competitive SKUs — switching to Content API-based updates for those specific items is worth the setup cost. The near-real-time update speed means your repricing actually reaches the shopper-facing price comparison in Shopping, rather than being invisible until tomorrow's feed sync.
Always submit GST-inclusive prices
For Australian Shopping surfaces, Google requires tax-inclusive pricing. Submit the price that appears on your landing page — including GST. If your store's pricing database stores ex-GST amounts internally, the feed submission layer needs to handle the conversion explicitly. Verify this is correct in your current feed by spot-checking 5–10 products: compare the price in your Merchant Center product list against the price shown on the landing page. They should match exactly.
Use sale_price and sale_price_effective_date
When you run a promotion, don't just drop the regular price field — add the sale_price and sale_price_effective_date fields. Products with these fields correctly populated display a strikethrough price in Shopping results (showing "was $X, now $Y"), which consistently outperforms plain price listings in click-through rate. If your feed plugin doesn't support these fields, this is a strong reason to switch to one that does.
Include GTINs wherever available
Products with valid Global Trade Item Numbers (GTINs — barcodes) get better product matching quality scores in Merchant Center. Google uses GTINs to confidently match your product to the same product listed by competitors, which is how the Shopping comparison view is built. Products without GTINs may be matched incorrectly or not matched at all, which affects your position in the comparison. For products where the GTIN is available from your supplier or the manufacturer, include it in your feed.
Check the Price Competitiveness report regularly
Merchant Center includes a Price Competitiveness report (the navigation path varies depending on whether your account is on classic Merchant Center or Merchant Center Next — search for "Price Competitiveness" within your Merchant Center account to find it). This report shows, for each of your products, how your feed price compares to the benchmark price across other Google Shopping merchants. Products where your feed price is above benchmark are losing clicks to cheaper-priced competitors on the same Shopping page. This report is one of the most actionable pieces of data in your entire Google Shopping setup — and most store owners never look at it.
Monitoring Competitor Feed Prices (Not Just Site Prices)
Here's a distinction that matters more than most store owners realise: your competitor's Google Shopping price is not necessarily the same as the price on their website.
Some competitors maintain Shopping-specific pricing — slightly lower than their website price — specifically to win clicks in the Google Shopping comparison. Their website might show $149 for a product, but their Google Shopping feed shows $139. If you're monitoring their website to benchmark your own pricing, you're comparing against the wrong number. Your repricing rule fires at $148 to beat their "website price" of $149 — but Google Shopping is still showing their $139 feed price next to your $148. You've repriced, you've updated your feed, and you're still losing the click.
PriceSpy monitors the prices that actually appear in Google Shopping results — the feed prices that Google displays to shoppers — not just the prices on competitor websites. This gives you an accurate picture of your competitive position where it actually matters: in the comparison row that shoppers see before they decide where to buy.
Combined with human-verified product matching — ensuring you're comparing against the correct variant, model, and configuration of a product — this is the foundation of genuinely accurate competitive intelligence for Google Shopping. Automated matching that conflates different-spec products produces repricing decisions based on bad data, which is often worse than no repricing at all.
A competitor's price for a 64GB version of a product and their price for a 128GB version can differ significantly. If your monitoring matches your 128GB SKU against their 64GB listing because both are returned for the same search term, your repricing is responding to the wrong data point. See our earlier post on variant-level matching for a detailed breakdown of why this problem is more common — and more costly — than most stores realise.
Your Feed Is Your Google Shopping Storefront
Your Google Merchant Center feed is not a background administrative task. It's the live representation of your store inside Google Shopping — the price every shopper sees before they decide whether to click your listing or your competitor's. When that representation is out of date, inaccurate, or structurally incorrect, your Google Shopping performance suffers in ways that don't show up cleanly in your ad platform dashboards.
Keeping your feed accurate, in sync, and competitively priced is not a set-and-forget task. It's an ongoing operational requirement — and if your repricing tool isn't designed to keep the feed in sync as part of the same workflow, you're spending money on Google Shopping ads that are systematically undermined by your own data.
If you've never audited your Merchant Center disapprovals or checked how many products have price mismatches right now, that's the place to start. Open Merchant Center, go to Products → Diagnostics, and find out what Google actually knows about your prices. The number is usually surprising.