How to Set Up Shopping Campaigns and Keep the Merchant Center Feed From Silently Burning Budget

Shopping ads run on Merchant Center product data, not keywords, so most of the budget-burn risk in this campaign type sits in the feed, not the bidding. This page gives the mandatory attributes, the update cadence Google actually enforces, the Standard Shopping vs Performance Max split, and the diagnostics sequence to catch feed problems before they throttle or suspend serving.

Merchant Center Feed: Required Attributes and Disapproval Triggers

Core required fields for every product: id, title, description, link, image_link, availability, and price — always mandatory per the product data specification (https://support.google.com/merchants/answer/7052112?hl=en). brand is also required for new products, with exceptions for movies, books, and musical recordings (same source).

GTIN/MPN

either a GTIN or an MPN is required; GTIN is strongly recommended whenever the manufacturer has assigned one (https://support.google.com/merchants/answer/6324461?hl=en). Acceptable GTIN digit counts are 0, 8, 12, 13, or 14 digits (UPC, EAN, ISBN, or ITF-14 formats); spaces and dashes are accepted but ignored by Google's parser (same source). Products with a missing or incorrect GTIN won't sync to Merchant Center at all (https://support.google.com/merchants/answer/13693497?hl=en), and even when they do sync, incorrect or missing GTIN prevents accurate matching to customer searches, limiting visibility (https://support.google.com/merchants/answer/6324461?hl=en).

Images

current minimums are 100x100 pixels for most (non-apparel) products and 250x250 pixels for apparel; undersized images are a documented common cause of disapproval (https://support.google.com/merchants/answer/13693497?hl=en). A stricter 500x500-pixel minimum for all products is a new requirement Google will start enforcing on January 31, 2027 — not yet in effect, so don't treat it as today's floor.

Availability

must be one of in_stock, out_of_stock, preorder, or backorder and must match the actual stock status shown on your website (https://support.google.com/merchants/answer/7052112?hl=en).

Category and variants

google_product_category is recommended to reduce disapprovals from miscategorization (https://support.google.com/merchants/answer/13693497?hl=en). For apparel in specific countries, age_group, gender, color, and size become required attributes, and item_group_id is required for variants in certain regions — mismatches between variant attributes cause disapprovals (https://support.google.com/merchants/answer/7052112?hl=en).

Price/availability parity with the website

if the price or availability shown on your website differs from what's in the feed, Google treats this as a data-quality violation and disapproves the item — Google's own guidance is explicit that "a person who comes to your website from one of your Shopping ads or listings expects that the price and availability information on your website will be the same" (https://support.google.com/merchants/answer/188489).

Feed Freshness: Update Cadence Google Actually Enforces

The stated minimum is once per day: "at a minimum, you must update your local products feed once a day" (https://support.google.com/merchants/answer/7371671?hl=en). But Google's own high-quality-data guidance frames "once a day" as a floor, not a target — updates should be tied to real product/price changes on your site (e.g. "creating feeds immediately after database updates", "submitting data simultaneously with website changes"), not a fixed interval (https://support.google.com/merchants/answer/188489). Mismatches between the advertised feed and the live website can trigger disapprovals or account suspension (same source).

Automatic item updates let Google re-crawl your product pages and correct feed/website mismatches on its own: an initial check runs within 24 hours, then subsequent checks follow Google's crawl schedule (multiple times daily) (https://support.google.com/merchants/answer/14991445?hl=en). Feed file size is capped at 4 GB, and feed URLs must use http://, https://, ftp://, or sftp:// (same source).

Caveat on the "within minutes" claim

Google's own wording is "we usually update your information for existing products within minutes" (https://support.google.com/merchants/answer/188489), not an "immediately after database updates" guarantee — that phrasing describes when *you* should create your feed relative to your own database changes, not how fast Google ingests it. This is Google's own framing, not independently confirmed in the notes for this page — an industry report from January 2026 claimed real-world feed staleness of 9-10 days against the 24-hour automatic-update promise, but that report is not addressed in any official Google documentation (unverified, reported by third-party industry source, not Google). Treat the "minutes" and "24 hours" figures as Google's stated targets, not a guaranteed SLA, and verify actual sync lag in Diagnostics rather than assuming it.

Standard Shopping vs Performance Max With a Shopping Feed

Shopping ads (keyword-less, driven by Merchant Center data) run through two campaign types with different reach. Standard Shopping campaigns serve only on the Shopping tab, next to main search results, on Google Images, and on Search Partner sites (if enabled) (https://support.google.com/google-ads/answer/2454022?hl=en). YouTube, Gmail, Maps, and the Google Display Network are not reachable from Standard Shopping — they require running the same feed through Performance Max instead (same source).

Standard Shopping keeps spend on the Shopping network alone, with the advertiser manually managing bids, targeting, and settings — there is no keyword layer, since it uses the product data instead (https://support.google.com/google-ads/answer/2454022?hl=en).

Performance Max is a goal-based campaign type that accesses YouTube, Display, Search, Discover, Gmail, and Maps from a single campaign, using Google AI to optimize placement and bidding across all of them (https://support.google.com/google-ads/answer/10724817?hl=en). With a Merchant Center feed connected, Performance Max does not require creative assets to launch, though supplying them is recommended (same source) — see Google Ads Campaign Types: What Each One Is For — Picking the Right Inventory Before You Set Up or Audit an Account for how PMax fits the wider campaign-type roster and How to Launch Performance Max Without Cannibalizing Brand or Wasting Spend for the guardrails needed before turning it on. Google explicitly supports running Standard Shopping vs Performance Max experiments against each other to compare performance before committing budget (https://support.google.com/google-ads/answer/13825980?hl=en).

Reading Diagnostics Before They Throttle Serving

Merchant Center's Issues page distinguishes account-level issues (affect every product in the account) from product-level issues (affect individual items only) (https://support.google.com/merchants/answer/12153802?hl=en). Within that, official documentation describes two severity tiers — Warnings and Disapprovals — not three; a note in the source material that suggested a third "Notifications" tier is not confirmed in Google's own documentation and should be treated with caution.

- Disapproved products stop showing across Google entirely until the issue is fixed. - Warnings don't stop serving yet, but Google's own documentation says they "could negatively impact ad performance and will likely lead to item or account suspensions in future unless resolved" — and separately, products under warning already show with reduced performance (lower impressions and clicks) while unresolved (https://support.google.com/merchants/answer/13693497?hl=en). - Account-level disapprovals suspend the account, disabling all products from appearing on Google (https://support.google.com/merchants/answer/12153802?hl=en).

Preemptive item disapproval (PID)

if price or availability in the feed doesn't match the website, Google proactively disapproves items it judges likely to violate policy, even before a manual review confirms it (https://support.google.com/merchants/answer/13693497?hl=en).

Workflow

start on the "Needs attention" page for account-level issues in summary cards or the Diagnostics tab, then use the Priority fixes feature to filter issues by medium/high performance impact so remediation targets the items actually costing you visibility first (https://support.google.com/merchants/answer/12153802?hl=en).

What Does NOT Work — Common Budget-Burn Failure Modes

- Stale availability data. If the feed's availability field isn't kept in sync with real stock, out-of-stock items keep serving and accepting clicks you pay for (https://support.google.com/merchants/answer/188489). - Price mismatches. A feed price that doesn't match the landing page triggers price-mismatch disapprovals and, if repeated, can escalate to account suspension (https://support.google.com/merchants/answer/188489). - Missing return/refund policy. This is a distinct policy violation (not just a data-quality issue) that triggers account warnings and potential suspension (https://support.google.com/merchants/answer/13693195?hl=en). - Insufficient contact information. Missing or inconsistent legal name, physical address, phone, or email triggers policy warnings on the account (https://support.google.com/merchants/answer/13693195?hl=en). - Misrepresentation — the fast track to suspension. Promoting out-of-stock/unavailable products, or failing to disclose complete pricing (fees, payment models, membership costs), falls under Google's misrepresentation policy, which is explicitly called out as "egregious": serious enough to skip the warning period and suspend immediately (https://support.google.com/merchants/answer/6150127?hl=en). This is the category to check first against Google Ads Policy Taxonomy: What Gets an Ad Disapproved vs an Account Suspended before assuming any violation gets a grace period. - The warning clock. Non-egregious account warnings come with a timeframe to fix the underlying products; if they're removed before the period ends, no further action is taken, but failure to fix in time leads to suspension after review (https://support.google.com/merchants/answer/13693195?hl=en). Appeals typically take 3-7 business days, and repeated unsuccessful appeals trigger progressively longer cool-down periods before you can request review again (same source) — see Account Suspensions: Triggers, Verification, and the Appeal Process — the policy trap that can end a Google Ads account overnight and How to Respond to a Suspension or Disapproval Without Making It Worse — the sequence that avoids turning a fixable violation into a permanent ban for what to do once you're in this state.

Related

- Google Ads Campaign Types: What Each One Is For — Picking the Right Inventory Before You Set Up or Audit an Account — where Shopping and Performance Max sit among the other campaign types, and the funnel-stage/control-vs-automation trade-off that decides which one to run with a given feed. - How to Launch Performance Max Without Cannibalizing Brand or Wasting Spend — once a Merchant Center feed is clean, this is the next decision: whether to run it through Performance Max, and how to stop PMax from eating brand-term Search traffic. - Google Ads Policy Taxonomy: What Gets an Ad Disapproved vs an Account Suspended — the general policy tiers (prohibited content/practices, restricted categories, egregious violations) that the Merchant Center-specific misrepresentation and policy warnings on this page are instances of. - Account Suspensions: Triggers, Verification, and the Appeal Process — the policy trap that can end a Google Ads account overnight and How to Respond to a Suspension or Disapproval Without Making It Worse — the sequence that avoids turning a fixable violation into a permanent ban — what happens after a feed-driven policy warning escalates to an actual suspension: identity verification, appeal timing, and why opening a new account instead makes it worse.