Most Merchant Center suspensions I see do not start with a policy violation. They start with a data mismatch that Google reads as misrepresentation, and the one that comes back the most is availability.
The pattern: your feed and your product's structured data say InStock, but the actual product page shows sold out (or the other way around). Google crawls the landing page, compares it to the feed, sees they disagree, and treats it as the store misrepresenting the product. That is a suspension trigger even though nothing about your business is dishonest. It is usually just an app or a theme that updates one place and not the other.
Where the mismatch tends to hide:
- A product hidden or sold out on the page while the feed still lists it available.
- Structured data (Product/Offer availability) not refreshing when stock hits zero.
- Variants: the product shows available because one variant is, but the specific one in the feed is out.
The fix is making availability agree across the feed, the schema, and the visible page. Has a mismatch like this ever bitten anyone here, and did you catch it before or after the suspension email?
After. Of course.
A sold-out variant was still marked available in the feed. Took a suspension to catch it.
Now I check schema availability, not just the feed. My app writes the feed fine but the theme's Product schema lagged on variant stock.
First thing I look at when Merchant Center acts up.