Google rejected your products. Fix the mismatch before rebuilding the feed.

The feed generates successfully. Merchant Center still rejects products for mismatched prices or availability. Rebuilding the XML may change nothing, because the disagreement is between the feed, product page and checkout.

Pick one rejected item. Check its SKU, website, customer context, currency and variant. Compare the exact values a public visitor sees with the feed and page structured data. A single well-understood mismatch is more useful than changing the whole template blindly.

Price: compare the same offer

A regular price, special price and coupon discount are different things. So are prices before and after tax. A feed for one country pointing to a page showing another currency creates another mismatch.

Check the price fields against Google's price requirements. Then check how your Magento feed obtains them: website scope, guest pricing, tax destination, indexed values and sale dates. A feed generated before a promotion starts can become stale while the product page is already showing the new offer.

Google's price mismatch troubleshooting is the reference for the reported issue. Record the feed timestamp and the page values before requesting another review.

Stock: a parent in stock doesn't make every size available

A configurable product can be salable while one child is unavailable. If the feed represents that child, the landing page must make the advertised option and offer clear. Check backorders separately; do not assume Magento's general stock flag maps to Google's intended availability value.

Test the exact item through checkout. A product page offering purchase followed by an unavailable-item error is a customer problem as well as a feed problem.

Identifiers: don't fill blanks with guesses

Use the manufacturer's correct identifiers where required. A made-up GTIN or a default store brand for third-party products can introduce inaccurate data. Check the requirements for your country, product type and identifiers in Google's product data specification.

For AI-generated feed titles and descriptions, review its structured_title and structured_description requirements too. Generating nicer copy is not enough if the export uses the wrong field for it.

Make the feed testable before it replaces the working file

Our Data Feed Manager provides editable templates, a preview and validation before a generated file replaces the previous one. That helps prevent a template error publishing an empty feed. It cannot correct inaccurate catalogue data or guarantee Merchant Center approval.

The Google template needs review for your store. In particular, check the brand fallback, tax treatment, preorder or backorder handling, and variant landing pages. Guest indexed prices and the store's default tax destination may not represent every market you sell to.

Give the feed a trading schedule

Align generation with stock updates, indexing and promotion starts and ends. Monitor generation failures and Merchant Center diagnostics. Keeping yesterday's file after a failed generation is safer than an empty file, but it can still contain stale offers.

Track eligible products, issue categories and time to resolve them. Do not treat a smaller disapproval count as proof of higher revenue without checking the affected products and campaigns.

For category errors, read Google product category mapping. If updates stop arriving altogether, inspect Magento cron.

Compare the sample output and preview on the Data Feed Manager page with one of your real products. Send us your target market, product types and current diagnostic issue if you want to assess fit. The goal is accurate, timely offers that survive the customer's click.