Read the status before prescribing a fix
Merchant Center's Products overview distinguishes approved, limited, not approved and under-review items. Inspect the detail for the intended country and destination. A product eligible for one surface is not automatically eligible for every other surface, and a warning does not always mean the whole catalog is blocked.
Disapproved or not-approved items need the specific cause investigated. Limited items require you to identify what is restricted. Under review means the current state may still be processing; repeated unrelated edits are not a diagnosis. An approved product can still have little exposure because eligibility and performance are separate questions.
Use the issue detail, not just the summary count. Record representative item IDs, variants, affected markets and source. Check account-level policy concerns before spending hours on individual attributes. If an issue suddenly affects the entire catalog, a shared configuration or account change may be more informative than one product description.
Prioritize impact, not whichever warning is easiest
Start with customer-facing contradictions and blockers affecting commercially important products. Commercial importance comes from your own store knowledge and authorized data, not a made-up revenue estimate. An error on an unavailable seasonal item may matter less than an eligibility block on a core stocked range.
Then separate scope from severity. A widespread account issue can outrank many small product improvements. A single variant with a price mismatch still deserves careful handling because it misrepresents the offer. Do not use a simple count of warnings as a substitute for investigation.
Create a queue with one owner and one verification condition per issue. Where the cause is uncertain, investigate rather than guessing. Mark whether a fix belongs in Shopify product data, the Google channel configuration, Merchant settings or a policy review. The same symptom can arise in more than one place.
Merchant Issue Prioritization Table
This table supplies investigation starting points, not guaranteed causes. The official issue details and requirements for your product and market take precedence. Work from the submitted item back to the authoritative source so an apparent correction is not overwritten at the next synchronization.
Business impact below describes the type of risk, not a measured loss. You need your own evidence to rank products commercially. Avoid attributing a sales decline to a warning merely because both happened in the same week.
| Symptom | Likely causes | Investigate | Impact | Next action | Verify |
|---|---|---|---|---|---|
| Price mismatch | Variant, currency, sale or stale source | Shopify offer, checkout, markup, submitted item | Affected offer may be blocked | Align the actual prices | Google submitted value and status |
| Availability mismatch | Stock state or old sync | Variant inventory and source | Incorrect purchasable offer | Correct true availability | Landing page, checkout and processed item |
| Missing attributes | Category or identifier requirements | Product data and specification | Affected products limited/blocked | Supply real required data | Attribute accepted and issue cleared |
| Image issue | Overlay, quality or inaccessible URL | Original image and submitted URL | Affected listing eligibility | Use a compliant accurate image | Image loads and issue processed |
| Shipping/returns | Missing or conflicting market settings | Shopify configuration and Merchant policies | Market or account scope | Align actual checkout and policy | Target-country requirements satisfied |
| Account concern | Policy or business-information issue | Merchant account issue details | Potential catalog-wide impact | Resolve documented cause; use review process | Recorded review outcome |
| Sync issue | Permissions, source or market changes | Google channel and data-source history | Missing/stale items | Repair the confirmed connection/configuration | Correct item IDs and refreshed data |
Trace price and stock through the same variant
Compare the submitted item with its landing page, checkout and structured data where present. Use the same variant, country and currency. A parent product's starting price can differ from the selected variant; checking only the first visible price can conceal the mismatch.
For availability, distinguish an actual stock update from using availability to suppress a listing. Google explicitly warns against marking items out of stock merely to pause them. Keep the submitted offer truthful. Review the appropriate destination or pause controls if the commercial intention is to stop serving an otherwise available product.
After correcting the source, confirm the Google channel has refreshed and Merchant Center shows the intended value. Document processing state and follow the issue's guidance rather than promising a universal resolution time. A manual Merchant edit may not be durable if the connected source remains wrong.
Identifiers, images and policies need real information
Required attributes vary by product and market. Follow the current specification rather than assuming every category has identical requirements. Use manufacturer-assigned identifiers where applicable. Do not invent a Global Trade Item Number, or GTIN, or a Manufacturer Part Number, or MPN, to make a validation check pass.
Check that the main image accurately depicts the product, loads publicly and follows the image rules. Google distinguishes the main product image from additional and lifestyle images. A promotional overlay or broken image URL requires an image fix, not a broad SEO rewrite.
Shipping and return configuration should reflect what customers can actually receive and the policies they can inspect. Review target-country requirements and whether Shopify's automatic shipping import supports your setup. Account-level concerns need the documented Google process; this article cannot promise account reinstatement or substitute for policy review.
A hypothetical price mismatch after a sale
Imagine a mug variant normally costs $32, a promotion changes checkout to $28, and the submitted item still shows $32. These figures and the scenario are illustrative, not a real merchant incident. First verify exactly where the mismatch occurs; do not assume the sale itself violates policy.
Check regular and sale values, effective dates where applicable, currency, selected variant and rendered markup. Correct the source that owns the inconsistent value. Record the change and verify the submitted product after processing. Changing titles, images and shipping simultaneously would make the diagnosis less clear.
If the same symptom appears across many items after a market or source change, inspect the shared configuration and source history. A feed migration can alter the troubleshooting context, but do not declare it the cause without account evidence. Scope directs investigation; it does not prove causation.
One focused fix, one observable verification
Keep a change log: item, issue, source value, action, owner, timestamp and verification result. Escalate when the documented cause is resolved but the issue persists through the relevant processing or review guidance. Supply precise evidence instead of repeatedly resubmitting unrelated changes.
BluePocket Growth brings available Google product and search evidence into a connected-data workflow. Its public plan does not promise automatic feed repair, direct Shopify synchronization or guaranteed approval. Make corrections in the system that owns the data and verify outcomes in Merchant Center.
An eligible feed is a prerequisite for some visibility, not a sales commitment from Google. Once blockers are resolved, move to impressions, relevance and offer performance. The weekly two-dashboard guide helps keep that next investigation separate from organic Search Console indexation and ranking.