Google Merchant Center 2026 spec changes: April 14, June 30, January 31 2027 deadlines

Google Merchant Center is in the middle of its biggest product-data spec update in years. Three deadlines between April 2026 and January 2027 reshape what your Google Shopping feed has to look like. Some of the changes are additive — new optional attributes you can opt into for richer SERP treatment. Some are enforcement — minimum image dimensions that have been "warning only" for years and now actually disapprove products.

This is a field reference. Each deadline gets the date, the actual change, and what you need to ship before it lands.

April 14, 2026 — three new attributes go live

Three new attributes are added to the product data spec. They're optional initially, but products that include them get richer SERP treatment.

handling_cutoff_time

The cutoff time of day at your warehouse — orders placed before this time ship same-day. Combined with handling time and shipping time, it lets Google show "Order in the next 4 hours for delivery Tuesday" prompts on Shopping listings.

Format: HH:MMin your warehouse's local timezone, plus a separate handling_cutoff_time_zone attribute. e.g. 16:00 with Europe/Prague.

minimum_order_value

The smallest cart total your store accepts (or the smallest cart total qualifying for free shipping, depending on the use case). Surfaces in Shopping ads as "Minimum order €30 for free shipping" when relevant.

Format: number + ISO 4217 currency code, same as price.

video_link

URL to a product video. Optional now, eligible to display on Shopping listings starting June 30 (next deadline). Supports MP4, WebM, MOV, AVI, FLV, MPEG.

Plus loyalty program sub-attributes (loyalty_program_label, loyalty_tier_label) for stores running points programs that affect price or shipping.

EU/UK note

In the UK and EEA specifically, minimum_order_value and pickup-cost attributes are subject to a stricter mandatory rollout in some flows. If you sell in those regions, treat the April deadline as serious, not aspirational.

June 30, 2026 — video display eligibility

Products that submitted video_link in April become eligible to actually display videos in Shopping listings. Quality and policy validation begins at this point — videos with watermarks, urgent text overlays, or copyrighted background music get rejected the same way images do today.

Action item before June 30: if you want to compete on video, get product videos shot or rendered, set video_link before April 14 ideally, and let the validation cycle finish before June 30 so eligible videos start showing as soon as Google flips the switch.

January 31, 2027 — 500×500 image minimum enforced

This is the big one. Google Merchant has had a 500×500 minimum image size as a recommendation for years. From January 31, 2027 it's enforced — products with images below 500×500 get disapproved, not warned.

The previous floors:

• Non-clothing categories: 100×100 px
• Clothing/apparel categories: 250×250 px

Both go away. The new universal minimum is 500×500 across all categories.

Warnings already started on April 14, 2026 — meaning Merchant Center will surface the issue in your diagnostics for nine months before it actually disapproves products. Use the warning period.

Other changes worth knowing

IPTC DigitalSourceType for AI images (already in effect)

Not new in 2026 — this became mandatory in February 2024— but worth flagging if you haven't updated. AI-generated product images submitted to Merchant Center must include IPTC DigitalSourceType metadata with one of: TrainedAlgorithmicMedia, CompositeSynthetic, or AlgorithmicMedia.

Applies to image_link, additional_image_link, and lifestyle_image_link. Tools like Emberfeed automatically tag images they generate; if you're using a different AI image tool, verify it sets the metadata.

identifier_exists is now warning-only

Since late 2023, missing GTIN/MPN combined with identifier_exists=falseno longer triggers disapproval — it surfaces as a "Limited performance" warning. Your products keep serving; visibility in Shopping results is just downgraded. Worth knowing because it's the highest-volume warning in Merchant Center diagnostics.

structured_title and structured_description

Alternative attributes that satisfy title /descriptionrequirements with structured data — useful for AI-driven product surfaces. Increasingly important as Google Shopping moves toward AI Overviews and structured comparisons in SERPs. Worth adding now even though they're not strictly required.

What to ship and when

1. Right now:Audit Merchant Center diagnostics for the "Image too small" warning. Plan the remediation. Get IPTC metadata correct on any AI images you're generating.
2. Before April 14, 2026: Add handling_cutoff_time, minimum_order_value, and video_link to your feed. Get product videos created if you want to compete on that surface.
3. Before June 30, 2026: Watch your Merchant Center diagnostics for video rejections. Fix anything flagged before video display goes live.
4. Before January 31, 2027: Resolve every "Image too small" warning. Worst case: 9 months to either update the source assets or flip your feed through a tool like Emberfeed that renders at the higher resolution.

The Emberfeed shortcut for catalog-wide changes

Field rules let you make catalog-wide changes once and have them apply to every product. Specifically for the 2026 spec:

• Add handling_cutoff_time as a default value (your warehouse cutoff is the same for every product) — one rule, every product gets it.
• Set minimum_order_value conditionally per category if your store has different thresholds — one rule with a category condition.
• Render images at 1500×1500 by default through Emberfeed's template — guarantees you're above the 500×500 floor without touching source assets.
• Validate against Google's live spec in real time so warnings surface in the Emberfeed UI before they appear in Merchant Center.

For the full reference of every Google Merchant required field and rule, see our GMC image requirements 2026 spec page. For specific rejection codes, the catalog rejection database covers each error individually.