On multi-market e-commerce accounts, the most stressful message isn't an ad disapproval — it's a Merchant Center warning. A disapproval stops one ad; an account suspension cuts all Shopping and PMax feed traffic at once. Managing feeds across four countries for brands like Goldia taught me this clearly: the vast majority of suspensions aren't "Google being arbitrary"; they're weeks of accumulating data-quality signals finally coming due.
What the system does: constant comparison
Merchant Center's core job is comparing what your feed declares with what your site actually shows. Automated crawls visit product pages regularly and check three things: does the price match the feed, is availability correct, is the product actually on that page? When the mismatch rate crosses a threshold, item-level disapprovals come first; if it persists, an account suspension follows under the "misrepresentation" umbrella. The system's logic isn't punishment but consumer protection: preventing the experience of seeing ₺899 in the ad and ₺1,099 on the site.
Where mismatches come from
Nobody declares wrong prices on purpose; mismatches always leak in through architecture. The ones I see most: a feed updated once daily while site prices change intraday with promotions (the sale starts, the feed stays on the old price); VAT/currency rounding differing between feed and site; variant confusion — the page's default variant priced differently from the variant the feed sent; "discount in cart" mechanics contradicting the feed price; wrong currency flowing into the wrong country feed in multi-market setups; and inventory sync lag leaving a sold-out product "in stock" for hours. Individually small, these leaks compound into the mismatch rate the crawler sees.
The behaviour that escalates it: mismanaging the warning
Merchant Center rarely suspends out of nowhere; it usually issues a preemptive warning with a grace period. The critical mistake is fixing the symptom and keeping the root: you remove the three flagged products, the warning clears, and because the price-delaying architecture is untouched, the same film restarts three months later with different products. The second critical mistake is requesting the post-suspension review before the problem is actually fixed — review attempts aren't unlimited, and consecutive failures stretch the process. The right order: find the root cause → fix → verify on site and in feed → then request review.
The feed routine I run
First, automatic update layers: structured data (schema.org/Product) correctly implemented on the site and Merchant Center's automatic item updates switched on — even if the feed lags, Google can refresh price/availability from the page; the cheapest insurance against suspension there is. Second, feed frequency matched to reality: if site prices change intraday, the feed updates intraday; on big promo transitions (11.11, Black Friday) the feed push is scheduled to the same minute as the campaign start. Third, a weekly diagnostics routine: the item diagnostics screen plus a manual site-vs-feed comparison of 10 random products — currency, VAT and variants included. Fourth, multi-market hygiene: a separate feed per country, local currency, local shipping/returns info — copying one feed to every country is the guaranteed way to produce mismatches at scale.
In short: a Merchant Center suspension isn't an accident; it's a process with a measurement system. Treat the feed not as a "file you set up once" but as a live mirror of the site's price-and-stock truth, and you'll only ever need this article for other people's accounts.