Google Merchant Center’s 2026 product data changes carry actual deadlines, not just recommendations, and the enforcement dates don’t all land on the same day. The minimum image resolution requirement started showing warnings on April 14, 2026, with enforcement beginning January 31, 2027 — which sounds distant until you account for how long a full-catalog image re-shoot or re-export takes for a store with thousands of SKUs. Treat this as a feed compliance project with a real timeline, not a someday task.
What’s Changing and When
| Requirement | Key Date | What It Means for Your Feed |
|---|---|---|
| Minimum image resolution (raised standard) | Warnings from April 14, 2026; enforcement from January 31, 2027 | Images below the new minimum will eventually cause disapproval, not just a warning — audit your full catalog now, not close to the deadline |
| New video attribute | Available now, not yet mandatory for most categories | Adding product video where you have it is a low-cost improvement while it’s still a differentiator rather than a baseline requirement |
| Alcohol subscription products under “Alcoholic Beverages” (ID 99676) | Effective March 31, 2026 | US merchants selling recurring alcohol products (wine clubs, etc.) must use this specific category and add the subscription_cost attribute to serve compliantly |
| Feed update frequency expectations | Ongoing — daily is now the practical minimum | High-volume stores should be moving toward real-time or near-real-time sync (roughly every 15–60 minutes), not a once-daily batch job |
An Audit Sequence That Catches Problems Before Google Does
- Pull your current feed’s image dimensions in bulk rather than spot-checking — a script that reads image_link and checks actual served resolution against the new minimum, since a CDN or theme can silently serve a downscaled version even if the source file is compliant.
- Flag every subscription product and confirm it carries the subscription_cost attribute where required, and specifically confirm alcohol subscription products use Google product category 99676 rather than a general beverage category — using the wrong category here is a compliance issue, not a cosmetic one.
- Check your feed’s actual update cadence against real-time expectations. A once-daily cron job was adequate a few years ago; for a store with frequent price or stock changes, daily updates now read as stale to Google’s freshness signals, which affects Shopping placement independent of any outright disapproval.
- Add video attributes opportunistically where you already have product video assets — this isn’t a compliance deadline yet, but early adopters typically see the benefit before a requirement forces universal adoption and removes the differentiation.
- Re-run the audit on a quarterly cadence, not once — Merchant Center requirements have moved multiple times in 2026 alone, and a feed that passed an April audit isn’t guaranteed to pass one in Q4 without a recheck.
The Cost of Waiting Until the Enforcement Date
Re-shooting or re-exporting product imagery at scale is a production-and-approval cycle measured in weeks, not a config change. Waiting until close to the January 2027 enforcement date to discover which SKUs fail the new resolution standard turns a manageable, staged project into a scramble that risks a period of mass disapprovals right when you can least afford lost Shopping visibility.
