Merchant Center alerts that lead to action

A current issue list is a snapshot. An operational alert describes a transition: a new issue appeared, an existing issue affected more products, a product became disapproved, impact increased, or Google reported recovery. The destination, severity, affected set, and detection time should remain visible.

Not every product warning should interrupt a team immediately. Alert policy should distinguish critical changes from items suited to a grouped digest.

Supported product-status push notifications can reduce detection delay, but they are not a complete replacement for regular account checks. Scheduled reconciliation catches broader account state, missed events, and full affected-product changes. A reliable monitor uses both and deduplicates repeated delivery.

• Acknowledge authenticated, valid push events quickly.
• Deduplicate repeated event identifiers or equivalent state changes.
• Run targeted refreshes without inventing product issues.
• Keep a scheduled full reconciliation as the safety net.
• Record failures operationally rather than silently dropping them.

Google severity should influence urgency, while affected products, recent impressions, and recent clicks can add commercial context. Clicks generally carry more weight than impressions, but traffic evidence belongs in an alert only when the performance row matches the exact product deterministically.

If identity is ambiguous or performance is absent, say so. No recent performance data is more accurate than a fabricated zero or an arbitrary variant choice.

Group the same issue across affected products and report lifecycle changes rather than sending one message per offer. Apply customer notification preferences and digest cadence while preserving genuinely critical alerts under the product's current rules. One transient sync failure should not look like a broken Google connection.

Open the direct Merchant issue, confirm the affected country and destination, inspect representative products, and correct the actual source. After Google processes the change, verify the issue has resolved instead of closing work merely because a feed upload succeeded.

CommerceVigil combines supported near-real-time product-status events with scheduled reconciliation, issue lifecycle, internal alerts, email delivery for eligible plans, and deterministic traffic prioritization. It remains read-only and does not edit products or guarantee Google recovery.