You set up the product feed once, exports ran on schedule, and for a while everything looked fine. Then one morning half your Google Shopping items are disapproved, the ad team is asking why spend dropped, and nobody can pinpoint when it started.
What you'll take away
- Feeds decay — catalogs change constantly and a static export will fail.
- Synchronize first — price and availability mismatches cause the most disapprovals.
- Validate before sending — catch errors before the channel rejects them.
- Make it channel-specific — Google, Meta, TikTok and Amazon have different requirements.
Here is the belief that causes the most damage: a product feed is a setup task. Configure it once, point Google Merchant Center at the URL, and let the nightly export handle the rest. This works for a week or two. It works right up until it stops working.
The mechanism that kills it is simple. Your ecommerce catalog is not static. Prices change when you run a promotion. Inventory sells out. Products are added for a new season. Variants get renamed. Items are discontinued and removed from the store but not from the feed. Each of these changes creates a gap between what your store shows and what your feed claims. Google's crawler finds the gap. Items get disapproved. Spend drops.
None of that is random. It is predictable.
What does a healthy feed-management process actually include?
A healthy feed-management process includes four things: automated synchronization of source data, validation of that data against channel requirements, continuous monitoring for errors and disapprovals, and periodic optimization of titles, categories, and identifiers. The feed is not an export. It is a controlled system that takes source data, validates it, transforms it where necessary, and delivers the right information to each destination.
Think of feed management the way you think of plumbing in a building. The pipes do not work because someone installed them once. They work because there is a pump maintaining pressure, a valve preventing backflow, a gauge showing the reading, and a maintenance schedule that catches corrosion before it leaks. A product feed is the same. The export is the pipe. Automation is the pump. Validation is the valve. Monitoring is the gauge. Optimization is the maintenance schedule. Skip any one and the system fails silently until the damage is visible.
The feed is a system, not a file
Every channel expects current, valid, transformed product data. A nightly CSV export with no validation step is a file. A feed process is the pipeline that ensures correctness before delivery.
Why do price and availability mismatches cause the most disapprovals?
Price and availability mismatches cause the most disapprovals because channels compare your feed data against your live store in real time. Google Merchant Center crawls the landing page and checks whether the price and availability shown there match the feed. If they do not, the item is disapproved. This is the single most common error source.
The mismatch usually happens because the feed export runs on a schedule but the store updates in real time. A customer buys the last unit at 10:14 AM. The store marks it out of stock immediately. The feed still says in stock because the next export runs at 2:00 AM the following day. For nearly sixteen hours, your feed claims something your store cannot deliver.
From the trenches — One merchant ran a flash sale, dropped prices 40% for 24 hours, then raised them back. The feed exported at midnight during the sale. Google Merchant Center showed sale prices for two days after the sale ended. Every item was flagged for price mismatch. The fix was not faster exports. It was triggering an export when prices change.
The fix is event-driven synchronization. Instead of exporting on a fixed schedule, export when something changes. If your platform supports webhooks or real-time inventory updates, use them. If it does not, shorten the interval and accept that some latency is unavoidable. Read more about sync timing and refresh rates to understand the trade-offs.
How do you catch feed errors before the advertising team does?
You catch feed errors by running validation against channel requirements before the feed is delivered, then monitoring the channel's diagnostics dashboard daily. Validation means checking every required field, every format constraint, and every policy rule the channel enforces. Monitoring means watching for disapprovals and acting on them within hours, not days.
Most merchants discover feed errors when the performance dashboard shows a drop in impressions or clicks. By then the error has been live for days. The ad team has spent budget on fewer items. The campaign has underdelivered. Someone has to explain why.
How a feed failure unfolds
The gap between step 1 and step 4 is where you lose money. Validation and monitoring compress that gap to hours instead of days.
| Stage | What you lose by waiting | What checking early saves |
|---|---|---|
| Before export | Nothing. Error never leaves your system. | Zero disapprovals from that issue. |
| After export, before delivery | Time spent re-exporting after fixing. | The channel never sees the bad data. |
| After delivery | Impressions, clicks, and spend on a broken item. | Catch it before the ad team opens the dashboard. |
| After disapproval | Budget, trust, and time explaining the drop. | Nothing. The damage is already done. |
What should you validate in a product feed before sending it?
Validate every required field for the destination channel, every format constraint, and every policy rule. For Google Merchant Center, that means checking that titles are under 150 characters, GTINs are present where required, prices include currency, availability uses accepted values, and image URLs resolve to valid images. For Meta, the requirements differ. For TikTok Shop, they differ again.
Validation is not optional. It is the difference between finding a problem in your own dashboard and finding it in Google Merchant Center's diagnostics tab. Use the free product feed validator to check your feed before delivery.
When should you exclude products from a channel feed?
Exclude products when they cannot meet the channel's requirements, when their margins do not support advertising spend, or when their inventory is too thin to sustain consistent availability. Exclusions are a tool for protecting spend and avoiding disapprovals, not for laziness.
Products with missing GTINs, broken image URLs, or prices below your advertising threshold should be excluded. So should products that go out of stock frequently. Google Merchant Center penalizes inconsistent availability. If an item flips between in stock and out of stock every few days, it harms your account-level data quality score. Exclude it until supply stabilizes.
Use feed rules to automate exclusions. A rule that says "exclude items where inventory is less than 5 units" prevents thin-stock items from entering the feed. A rule that says "exclude items where margin is less than 15%" prevents unprofitable spend. These rules run before delivery, so the channel never sees the excluded items. Read more about handling out-of-stock products in feeds.
Exclusions are a strategy, not a workaround
Excluding products that cannot meet channel requirements protects your account-level quality score and your ad spend. The goal is not to send everything. The goal is to send what performs.
Why does the same feed need different data for Google, Meta, and TikTok?
The same feed needs different data for each channel because Google Merchant Center, Meta Commerce Manager, and TikTok Shop have different required fields, different format rules, and different policies. Google requires GTINs for most products. Meta requires a content category from its own taxonomy. TikTok requires specific product type classifications. Sending identical data to all three guarantees that some items fail on at least one platform.
This is why a single CSV export cannot serve all channels. The source data is the same. The delivery is different. A proper feed process transforms the source into channel-specific outputs. Learn more about multichannel feed management and the specific TikTok Shop feed requirements.
How often should you review titles, categories, and product identifiers?
Review titles and categories at least once per quarter and after any major catalog change. Product identifiers like GTINs should be checked whenever a supplier changes packaging, discontinues a variant, or updates a barcode. Titles and categories drift over time because search behavior changes and channels update their taxonomies.
A title that performed well in January may underperform in July because competitors have improved their titles, because Google has updated its relevance model, or because seasonal search terms have shifted. Reviewing titles is not about rewriting them constantly. It is about checking whether they still match how shoppers search.
Before
Blue T-Shirt M
After
Gildan Men's Short Sleeve Cotton T-Shirt, Navy, Medium
The difference is specificity. "Blue T-Shirt M" tells the shopper nothing. "Gildan Men's Short Sleeve Cotton T-Shirt, Navy, Medium" includes brand, gender, sleeve length, material, color, and size. Google Merchant Center can match that title to a wider range of search queries. Read the full guide on optimizing product titles for Google Shopping.
Categories need the same attention. Google's product taxonomy is updated periodically. A category that was correct last year may be too broad or too narrow this year. Review your Google product categories quarterly.
What does a worked example of feed cost look like?
Consider a catalog of 2,000 products exported nightly to Google Merchant Center. Suppose 5% of those products have a price mismatch on any given day because the store updated prices after the export ran. That is 100 items with incorrect prices. Google disapproves them. Those 100 items stop receiving impressions.
If those 100 items previously averaged 50 impressions per day each at a cost per click of $0.75, and 2% of impressions converted to clicks, that is 100 items times 50 impressions times 2% click-through rate times $0.75. The daily cost of those disapprovals is $75 in lost clicks. Over a month, that is approximately $2,250 in lost ad spend efficiency. Over a quarter, nearly $6,750. This is illustrative. Your numbers will differ. But the mechanism is real: every disapproved item is a hole in your spend.
Common questions
How often should I update my product feed?
Update your product feed whenever catalog data changes, or at minimum daily if your platform does not support event-driven updates. Price and availability should synchronize in near real time. Full catalog exports can run daily, but any change to price, availability, or product status should trigger an immediate update to prevent mismatches.
What causes the most feed disapprovals?
Price and availability mismatches between the feed and the landing page cause the most disapprovals. Google Merchant Center crawls your product pages and compares them to feed data. When the price or availability does not match, the item is disapproved. Other common causes include missing GTINs, broken image URLs, and policy violations.
Should I use the same feed for Google Shopping and Facebook ads?
No, you should not use the same feed for Google Shopping and Facebook ads without transformation. Google Merchant Center and Meta Commerce Manager have different required fields, different category taxonomies, and different policy rules. Use a feed process that takes your source catalog and transforms it into channel-specific outputs for each destination.
How do I monitor my feed for errors?
Monitor your feed by checking the diagnostics dashboard in Google Merchant Center daily, running pre-delivery validation against channel requirements, and setting up alerts for disapprovals. Do not wait for the ad team to notice a spend drop. Use a feed validator tool to catch errors before the channel sees them.
What products should I exclude from my feed?
Exclude products with missing required identifiers, broken images, margins too thin for advertising, or inventory that fluctuates too frequently. Use feed rules to automate exclusions based on inventory thresholds, margin minimums, and data completeness. Excluding weak products protects your account-level quality score and concentrates spend on items that perform.
Feed management is not a setup task. It is ongoing work. The merchants who avoid disapprovals are not the ones who configured their feed perfectly once. They are the ones who validate before delivery, monitor after delivery, and optimize on a schedule. Build the system. Then maintain it.