Merchant Center gives you several kinds of warnings, but they do not all live at the same layer. Treating an account problem like a product problem wastes time; treating a product problem like an account problem creates unnecessary catalog changes.
The three layers to separate
Account and destination
These involve the Merchant Center account, website, policies, shipping, returns, or a destination such as free listings or Shopping ads.
Data source
These concern the connection or file Google uses to read products: authentication, fetch access, format, processing, quotas, or update timing.
Product
These attach to individual products or a group of items with the same data problem: invalid price, missing GTIN, bad category, unavailable page, image issue, or variant mismatch.
Use scope as your first diagnostic
If almost every product became ineligible at the same time, begin with account, destination, and source processing. If a small group shares one field-level warning, inspect the source mapping and affected products.
A safe correction loop
- Capture the issue text and date.
- Determine whether it is account-wide, source-wide, or item-level.
- Choose one representative product or source event.
- Apply the smallest correction at the correct layer.
- Wait for processing and verify the live product.
Use the data source triage workflow when the boundary is unclear, then compare the result with our feed health guide.