Automate Merchant Center disapproval alerts and send each issue to the person who fixes it
Updated · By Ecomsellertool editorial team
To automate Google Merchant Center disapproval alerts, read product and account issues from the Merchant API on a schedule, subscribe to its product status change notifications, and run each issue through an alert rule table. The table names who fixes it, whether it pages someone now or waits for a daily digest, and how the workflow re-checks the product until Google approves it again.
- Google says the Content API for Shopping was sunset on August 18, 2026, and that its requests see progressive errors from September 1, 2026; status checks now belong on the Merchant API (checked October 20, 2026).
- In the Merchant API, each product's productStatus lists itemLevelIssues with a severity of NOT_IMPACTED, DEMOTED or DISAPPROVED, plus the attribute and reporting context affected.
- A PRODUCT_STATUS_CHANGE subscription pushes a message to your HTTPS callback when a product's approval status changes, for example from approved to disapproved.
- Account issues come from accounts.issues.list with a severity of CRITICAL, ERROR or SUGGESTION; Google describes CRITICAL as an issue that causes offers to not serve.
- Google says product and account reviews can take up to 7 business days, and a failed account review can start a cool-down period that Google support cannot shorten.
The step map: who runs each step
Trigger: A Merchant API product status change notification, plus a scheduled pull of product issues, account issues and aggregate counts every few hours and right after each feed or catalog sync.
| Step | What happens | Who runs it |
|---|---|---|
| 1 | A scheduled job reads every product's status and issues from the Merchant API, the account's issues, and the aggregate counts of active, pending, disapproved and expiring products per country and surface. | Rule |
| 2 | Status change notifications arrive at a callback between pulls; the job orders them by event time and fetches the full issue list for each product that changed. | Rule |
| 3 | Each issue is compared with the last run, so only new, worsened or cleared issues move on, and each one is matched to a row of the alert rule table by issue, attribute and severity. | Rule |
| 4 | An AI model reads the issue detail next to the product's Shopify data and drafts a one-line likely cause for the owner, such as a sale price that ended on the site but not in the feed. It never edits a product. | AI model |
| 5 | The row decides the route: an instant message to the owner for account issues, top sellers and sudden spikes, or a line in the daily digest grouped by issue and owner. | Rule |
| 6 | The owner fixes the data at its source, usually the Shopify product or the feed, not the Merchant Center copy, and marks the alert as fixed. | Person |
| 7 | The workflow re-reads the product after the next sync and keeps checking until the issue clears or the row's wait time runs out, then escalates. | Rule |
| 8 | For policy and account issues, a person reads the fix list, decides when to request a review in Merchant Center and records the date, so nobody requests a second review too early. | Person |
5 rule steps · 1 AI model step · 2 person steps. A rule follows fixed logic you approve; an AI model handles messy input and its output is checked by rules; a person makes the calls listed below.
What stays with a person
- Requesting a review or disagreeing with an issue in Merchant Center, which has limited attempts and cool-down periods
- Any change to the refund policy, contact details or business information on the website
- GTIN values: a person confirms the manufacturer's barcode instead of guessing one
- Price and availability fixes where the website, not the feed, is wrong
- Changes to the alert rule table, the owners and the instant-alert thresholds
Which tools can run it
- Merchant Center's product data alert emails and Shopify's Google & YouTube product errors, for a small catalog checked by hand
- Zapier, Make or n8n calling the Merchant API on a schedule and posting to Slack or email, for one store and one country
- Custom code on your accounts, for push notifications, several countries or stores, issue diffs, digests and re-check clocks
Systems it connects
- Google Merchant Center
- Merchant API: products, accounts, issues, notifications
- Shopify Google & YouTube channel
- Shopify products and inventory
- Slack or email
- Task tracker or helpdesk
Build size: Medium
Reading the statuses is simple; the work is diffing issues between runs, routing each one to a named owner and re-checking until Google approves the product again.
A product goes from approved to disapproved on a Monday because a sale ended on the site but not in the feed. Nobody looks at Merchant Center until the weekly ads review, when someone asks why Shopping clicks fell. By then a few dozen products have been out of Google for days, and the warning email sits in a shared inbox nobody owns. This recipe closes that gap: the workflow reads every product and account issue, sends each one to the person who can fix it, and keeps checking until Google approves the product again. It covers the stretch between product data leaving your store and the product being approved in Merchant Center, and it is one page of our automation library.
Which Merchant Center issues should alert someone, and who fixes each one?
Write the rule table before you connect anything. Each row is an issue a brand actually meets, where the signal comes from, who owns the fix, how fast they hear about it and how the workflow checks the fix. Issue names are Google's own, from its Merchant Center Help pages (checked October 20, 2026). The owners and wait times are illustrative: set them for your team.
| # | Issue (Google's name) | What it does to the product | Where the signal comes from | Who owns the fix | Instant or digest | Re-check step |
|---|---|---|---|---|---|---|
| 1 | Limited performance due to missing value: GTIN | Keeps showing, "may have limited visibility" | Merchant API item-level issue on the gtin attribute; Shopify's "Missing GTIN or MPN" error on the product | Catalog owner: the manufacturer's barcode in the Shopify product, or brand and MPN for products without one | Digest | Re-read after the next sync; the issue can take some time to leave Needs attention |
| 2 | Inaccurate price status due to inconsistency between feed and landing page | Products preemptively disapproved, or an account warning | Item-level issue on the price attribute; an account-level warning when Google warns the account | Pricing owner; a developer when the page's structured data is wrong | Instant | Resubmit the data, then a person selects "I fixed the issue"; the review takes 7 business days |
| 3 | Mismatched product availability | Stops showing; too many can lead to account suspension | Item-level issue on the availability attribute; a jump in disapproved counts | Inventory or operations owner, often a sync timing problem | Instant above your threshold, digest below | A person requests a website check, which can take up to 12 hours |
| 4 | Image too small | Disapproved | Item-level issue on the image attribute | Creative or content owner | Digest, instant for top sellers | Re-read after 24 to 72 hours |
| 5 | Text on image (promotional text or watermarks) | Disapproved until the image is updated | Item-level issue on the image; Shopify's "Promotional overlay on image" error | Creative owner | Digest, instant for top sellers | Re-read after the new image link syncs |
| 6 | Unavailable landing page, missing description or missing image (Shopify's error names) | Product not approved for Google | Shopify's Google errors on the product; item-level issues in the Merchant API | Store admin: make the product available to both Online Store and Google & YouTube, then add what is missing | Digest | Re-read after the next sync |
| 7 | Misrepresentation and other policy issues on the account | Warning with 7 or 28 days to fix, or immediate suspension for egregious cases | accounts.issues.list (severity CRITICAL or ERROR); the banner and email in Merchant Center | Founder or operations lead, with whoever edits the website's policies and contact page | Instant, always | Fix everything first; a person requests one review and the workflow tracks the 7-business-day wait |
| 8 | A sudden drop in active products | Many products gone at once, often a feed or sync failure | Aggregate counts per country and surface; Merchant Center's default product data alert email | Developer or whoever runs the feed | Instant | Compare counts on the next run; close only when they recover |
| 9 | Products expiring or with no destination status | Removed from Merchant Center if nothing refreshes them | Product status dates and empty destination statuses in the Merchant API | Developer or whoever runs the feed | Digest | Confirm the next sync refreshed them |
Three choices make the table work. Every row names one owner, not a team, because an alert sent to everyone is fixed by no one. Fixes happen at the source, the Shopify product or the feed, because the store's data is what the next sync sends to Google again. And the review buttons stay with a person: Google limits how often you can request a review, so the workflow tracks the wait but never clicks.
When should an issue page someone, and when can it wait for the digest?
Use one short rule. Send an instant alert when the issue can cost the whole account or a real share of sales today; put everything else in a daily digest. In practice that means four triggers for instant alerts:
- Any account issue with a severity of CRITICAL or ERROR, or any warning with a deadline
- A product that becomes disapproved and is one of your top sellers or carries ad spend
- A jump in disapproved or a drop in active products above your threshold in one run, for example 5% of the catalog
- A price or availability mismatch above a set count, because those can turn into account warnings
Everything else goes into one morning digest, grouped by issue and owner, with the count, the products and the likely cause. Limited-performance warnings, single disapprovals on slow sellers and image issues on long-tail products are digest items. The 5% threshold and the top-seller list are examples for your brand to set. The point is that the instant channel stays quiet enough that people still read it when the account warning arrives.
Where does the workflow read the signals?
From the Merchant API now, not the Content API. Google's migration guide says the Content API for Shopping was sunset on August 18, 2026, and that its requests see progressive errors from September 1, 2026 (checked October 20, 2026). Any old script that read productstatuses there needs to move.
In the Merchant API, each product's status sits in its productStatus field: destination statuses with approved and disapproved countries, and a list of itemLevelIssues (checked October 20, 2026). The products reference gives each issue a code, a severity, a resolution, the attribute, the reporting context and the countries it applies to. Severity is NOT_IMPACTED for a warning, DEMOTED for limited performance and DISAPPROVED for a disapproval. Google notes that a change can take several minutes to appear on the processed product, and that products with no destination status are removed after about a week.
Between pulls, a notification subscription sends a base64-encoded message to an HTTPS callback you host (checked October 20, 2026). The product status change event, PRODUCT_STATUS_CHANGE, carries the old and new status (approved, pending or disapproved), the region, the reporting context and an event time to order messages by. It tells you that a status changed, not why, so the workflow fetches the issues next.
Account issues come from accounts.issues, each with a title, a severity of CRITICAL, ERROR or SUGGESTION, the destinations it affects and a link to Google's help. The aggregate product statuses give active, pending, disapproved and expiring counts per reporting context and country, which is what row 8 watches.
What do Merchant Center and Shopify already tell you?
More than most teams use. Google says product-level issues show on the Needs attention tab and account-level issues show in a banner, that disapproved products stop showing across Google, and that unresolved warnings can lead to disapprovals (Issues in Merchant Center, checked October 20, 2026). Its product data alerts email you by default when it detects a significant drop in active products for a country and surface. They are a good backstop, but they go to whoever set up the account, not to the person who fixes a GTIN.
In Shopify, the Google & YouTube channel shows the errors per product: open the product and click Google in its Sales channels section (Syncing your products, checked October 20, 2026). Shopify lists errors you fix in Shopify, such as a missing GTIN or MPN, a missing description or image, an unavailable landing page and a promotional overlay. It also says Google reviews new products within 3 to 5 business days of the first sync and applies a 30-day expiry to synced data, which the channel refreshes. For suspensions, Shopify's disapprovals and warnings page says to contact Google, and that review requests can take up to seven days.
How does the re-check work after a fix?
The alert stays open until Google agrees. When the owner marks a fix done, the workflow waits for the next sync, re-reads the product and checks that the issue has gone. Each row has its own wait: Google says image changes can take 24 to 72 hours to show, a website check for availability can take up to 12 hours, and a product review can take up to 7 business days (Request a review of your issues, checked October 20, 2026). If the issue is still there when the wait runs out, the alert goes back to the owner with the new status.
Account issues need more care. Google allows one courtesy review during a warning period of 7 or 28 days, you may get only one chance to disagree with an issue, and a cool-down period can start after failed reviews that Google support cannot shorten. So the workflow keeps the full fix list, the date of every review request and the cool-down end date in one place, and a person decides when the account is ready for review. For price mismatches, Google's price inconsistency page says a failed review places the account in a 7-business-day cool-down.
Who builds Merchant Center disapproval alerts for ecommerce brands?
Ecomsellertool builds workflow automation on your own Shopify store and Google accounts. We have built software on Amazon's seller APIs since 2017 and shipped 50+ tools for 100+ teams. For Merchant Center we write the alert rule table with you first, then connect the Merchant API, the digest and the re-check clocks, with routine routing done by rules. Send a project brief or read how our workflow automation service works.
The building blocks are work we have shipped:
- Listing alerts, as rule-based automation we built. For AccountDr we built push and email notifications that tell Amazon sellers about listing faults, suppressed buy boxes, ASIN changes and performance metrics.
- Listings tracked for a whole client base. For Little Owl, a 3PL and FBA prep center, we built software that tracks listings, inventory and discrepancies across the sellers it serves.
If your catalog feeds several channels, the listing and catalog agent keeps one product record that Merchant Center reads from, and our guide to AI shopping agent-ready listings covers the product data Google's Shopping Graph uses. Stock that drifts between channels is the usual cause of row 3, which our multichannel inventory sync recipe addresses. The alerts can run on Ecomsellertool Growth OS beside your other catalog workflows, and our guide to what Shopify Flow automates explains where Shopify's own automation stops.
Get your disapproval alerts built
Send us your Merchant Center setup and who fixes what
Describe the workflow you want automated. We reply with a written plan: scope, timeline and a fixed price.
Frequently asked questions
How do I get notified when a product is disapproved in Google Merchant Center?
Merchant Center emails product data alerts by default when it detects a significant drop in active products for a country and surface. For each disapproval, use the Merchant API: subscribe to the PRODUCT_STATUS_CHANGE event, which pushes a message to your HTTPS callback when a product's approval status changes, and read the product's itemLevelIssues to see why. A workflow then sends that issue to the person who fixes it.
What is the difference between a disapproved product and a warning in Merchant Center?
Google says disapproved products stop showing across Google until the issue is fixed, while products with warnings keep showing but may have limited performance. Unresolved warnings can lead to disapprovals. In the Merchant API, the issue's severity tells you which one it is: DISAPPROVED, DEMOTED or NOT_IMPACTED.
Does the Content API for Shopping still work for product statuses?
Not for long. Google's migration page says the Content API for Shopping was sunset on August 18, 2026 and that requests see progressive errors from September 1, 2026. Any script that reads productstatuses through the Content API should move to the Merchant API, where the status sits in the product's productStatus field.
How long does Google take to re-approve a product after I fix it?
It depends on the issue. Google says a product review can take up to 7 business days, and that changes for issues such as image size may take 24 to 72 hours to show on the Needs attention page. For an availability mismatch you can request a website check, which can take up to 12 hours. The workflow keeps re-checking the product and escalates when the wait runs out.
Where do I see Google errors for a product in Shopify?
Open the product in the Shopify admin and click Google in its Sales channels section. Shopify lists errors you can fix there, such as a missing GTIN or MPN, a missing description or image, an unavailable landing page and a promotional overlay on an image. Account-level suspensions and reviews are handled with Google, not Shopify Support.
Should every Merchant Center issue send an instant alert?
No. Instant alerts are for account issues, sudden drops in approved products and disapprovals on products that sell or carry ad spend. Everything else, including most limited-performance warnings, belongs in a daily digest grouped by issue and owner. Too many instant alerts get muted, and then the account warning is missed too.
