Short version: Item disapprovals are product-level problems in an otherwise healthy Merchant Center account, and they need a completely different response from an account suspension. Each disapproved item is one product Google will not show, and the damage compounds quietly: every percent of the catalog that is disapproved is inventory your Shopping and Performance Max campaigns cannot sell, which caps scale without ever tripping an alarm. The errors cluster into a few families, and price or availability mismatch between the feed and the landing page is the biggest by a distance, usually caused by sales, currency handling, or a delayed feed refresh rather than anything exotic. The workflow that works is the same every time: read the item issues in the Products tab, prioritize by affected products and margin, and fix each issue at its source in the platform or feed rules instead of hand-editing products one by one.
Before anything else, confirm which problem you actually have. If the account itself is suspended, every product stops at once and you receive a policy notice naming the account; that is a different and more serious situation, covered in our guide to fixing a Merchant Center suspension, and the advice below does not apply to it. Item disapprovals look different: the account is fine, most products serve, and a subset shows "Disapproved" or carries warnings in the Products tab. That subset is what this guide is about, because it is common, it is fixable, and left alone it grows.
Why feed errors compound quietly
An account suspension announces itself. Item disapprovals do not. Shopping and Performance Max keep running on the products that remain approved, revenue continues, and nothing in the campaign interface says that a fifth of the catalog is sitting out. The account simply behaves like a store with a smaller catalog: fewer queries matched, fewer products with impression share, less room for the algorithm to find winners. Teams then respond to the symptom, raising budgets or loosening targets, when the actual constraint is that the machine has less inventory to work with than anyone realizes.
The second compounding effect is trust in the feed itself. Items that flip between approved and disapproved, prices that mismatch for a day after every sale starts, and identifiers that conflict all degrade how confidently Google serves the products that are approved. A clean feed is not just about the disapproved items coming back; it is about the approved items being served harder. That is the same reason feed work is the highest-leverage neglected task in ecommerce accounts, a case we make in full in the product feed piece.
Decoding the item issues
Open Merchant Center, go to the Products section, and look at the item issues list rather than individual products. Every issue row tells you three things: what rule is violated, how many products it affects, and whether it is a disapproval or a warning. The families below cover the large majority of what ecommerce stores see.
Price and availability mismatch, the big one
Google crawls your landing pages and compares what it finds against the feed. When the page says one price and the feed says another, or the page shows out of stock while the feed says in stock, the item is disapproved for mismatch. The causes are almost always timing and configuration rather than carelessness: a sale starts on the site but the feed refreshes tomorrow morning; a currency conversion rounds differently on the storefront than in the feed; structured data on the page carries an old price the theme never updated; a flash sale ends and the feed lags behind again on the way out. The durable fixes are structural. Refresh the feed more often or on sale events rather than on a fixed daily schedule, make sure the structured data on product pages is generated from the same source as the displayed price, and turn on automatic item updates in Merchant Center so Google corrects small drifts from your structured data instead of disapproving the item. If mismatches spike every time you run a promotion, that is a pipeline problem with a permanent fix, not a recurring emergency.
Missing or invalid GTINs
Products that have a manufacturer barcode need it in the feed, and an invalid, reused, or placeholder GTIN is worse than a missing one. Stores inherit this problem from suppliers who provide wrong codes, from platform defaults that copy one GTIN across variants, and from teams filling the field with internal SKUs to make an error disappear. If the product genuinely has no GTIN, custom or handmade goods for example, set the identifier attributes to say so honestly rather than inventing one. Correct identifiers do more than clear disapprovals; they let Google match your product to its catalog, which affects which queries you can appear on at all.
Image policy: overlays, watermarks, placeholders
Promotional text on the image, percentage-off badges, watermarks, logos stamped over the product, and placeholder images all trigger image disapprovals. The image policy wants the product, on a clean background, with nothing added. The one-by-one fix is replacing images manually; the source fix is finding where the overlays come from, usually an app or theme feature adding badges automatically, and excluding the feed image from it or pointing the feed at the original unbadged asset.
Incorrect identifiers and mismatched product data
Beyond GTINs, items get flagged when brand, GTIN, and MPN disagree with each other or with Google's catalog: a brand name spelled differently from the registered brand, an MPN copied across products that are not the same, condition set wrong, or an identifier that belongs to a different product entirely. These matter because they are misrepresentation in miniature, and a feed full of them starts to look like a data quality problem rather than a set of typos.
Shipping and tax misconfiguration
Every country you target needs a shipping service configured, and for the US, tax settings as well. Items get disapproved wholesale when a store starts feeding a new country before configuring shipping for it, or when shipping rates in Merchant Center contradict what checkout actually charges. This family is the easiest to fix because it is pure configuration, and one correction typically restores every affected item at once.
Limited performance warnings versus hard disapprovals
Not every issue row is a disapproval. Warnings, missing recommended attributes, and "limited performance" flags mean the item still serves but with reduced eligibility or weaker matching. They are tempting to ignore because nothing is visibly broken, but fixing them expands where and how often approved products show. Triage disapprovals first, then work the warnings on your highest-margin products.