Google Ads Shopping Campaigns Checklist

Use this Google Ads Shopping campaigns checklist before launch, after a feed, catalog, checkout, or bidding change, and during recurring product reviews. Confirm the Merchant Center connection, product data, eligibility, structure, landing pages, purchase measurement, value model, inventory, and rollback owner. The campaign should be evaluated by qualified ecommerce value, not just traffic or headline ROAS.

Google’s Shopping campaign guidance, Merchant Center linking guidance, and product-data requirements are the source references for current fields and eligibility. Campaign type, market, and product program can change the exact setup.

1. Define products and economics

[ ] Products, markets, inventory states, and customer goals are recorded.
[ ] Revenue, margin, discounts, shipping, returns, fulfillment, support, and currency are documented.
[ ] Priority, growth, seasonal, clearance, low-stock, and excluded products are identified.
[ ] Primary outcome, qualified order, value model, and efficiency guardrail are approved.
[ ] Product owner, feed owner, campaign owner, and rollback owner are named.
[ ] Capacity to fulfill and support additional demand is understood.

Do not apply one efficiency target to products with materially different margins or fulfillment constraints.

2. Verify Merchant Center connection

[ ] The correct Google Ads and Merchant Center accounts are open.
[ ] Link status, account access, ownership, country, language, currency, and product destinations are confirmed.
[ ] Feed source, refresh schedule, source version, and owner are documented.
[ ] The catalog is approved for the intended market and surface.
[ ] Product data is not being mixed with the wrong store, pricing, or region.

3. Validate product data

[ ] Titles, descriptions, images, identifiers, availability, price, currency, shipping, condition, brand, category, and applicable attributes are current.
[ ] Disapprovals, warnings, missing attributes, policy status, and feed latency are reviewed.
[ ] Price and availability match the product page.
[ ] Images, variants, landing URLs, and product destinations are valid.
[ ] Feed errors have an owner, correction, refresh expectation, and review date.

4. Choose campaign and product structure

[ ] Product groups follow actionable differences in margin, brand, category, price, inventory, season, market, or strategy.
[ ] Products with different budgets, bids, pages, exclusions, or owners are separated where needed.
[ ] Shared structure is retained where common settings and data are useful.
[ ] Product overlap, shared budgets, and priority-product coverage are checked.
[ ] High-impact boundaries have a purpose and owner.
[ ] The structure is maintainable at the current catalog size.

5. Validate the product experience

[ ] Product, variant, price, availability, shipping, returns, image, and landing page agree.
[ ] Mobile and desktop pages load and support the purchase path.
[ ] Page speed, navigation, checkout, payment, consent, and confirmation are checked.
[ ] Out-of-stock, unavailable, or unfulfillable products follow an approved pause or exclusion process.
[ ] The product page does not promise an offer that the feed or store cannot deliver.

6. Connect purchase measurement

[ ] Purchase events and transaction IDs are captured.
[ ] Currency, value, tax, shipping, discounts, refunds, and cancellations are handled consistently.
[ ] Consent, deduplication, cross-domain checkout, and offline adjustments are checked.
[ ] Platform orders and value reconcile with the commerce system.
[ ] Revenue, qualified order value, contribution margin, returns, and fraudulent orders are distinguished.
[ ] Conversion and refund lag are documented.

Do not optimize to a value that includes canceled or returned orders without a plan to correct it.

7. Set budget, bidding, and review rules

[ ] Budget and bidding match data quality, purchase volume, value reliability, margin, inventory, and capacity.
[ ] The baseline includes spend, impressions, clicks, orders, revenue, margin, returns, refunds, product mix, and feed status.
[ ] Minimum sample, conversion and refund window, guardrail, owner, and rollback condition are defined.
[ ] Feed, product structure, budget, bidding, offer, page, and measurement changes are not bundled without a reason.
[ ] The effective date and previous settings are preserved.

8. Verify after launch or change

[ ] Product eligibility, disapprovals, warnings, feed freshness, and link status are checked.
[ ] Campaign, product group, budget, bidding, shared settings, and scope are reopened and verified.
[ ] Query, product, device, location, audience, and page mix are reviewed.
[ ] Orders, qualified value, margin, returns, refunds, inventory, and service capacity are compared after lag.
[ ] Catalog, price, stock, promotion, checkout, feed, and competitor changes are annotated.
[ ] The decision to retain, narrow, reverse, or expand is recorded.

9. Compact Shopping change ticket

Copy this into a launch or review record:

[ ] Products, markets, and business role:
[ ] Merchant Center account, feed version, and eligibility status:
[ ] Product structure, budget, bidding, and scope:
[ ] Page, checkout, purchase measurement, and value model:
[ ] Baseline, margin guardrail, lag, and capacity:
[ ] Owner, effective time, review date, and rollback:
[ ] Decision: retain / fix / pause / narrow / expand:

For implementation, see how to set up Google Ads Shopping campaigns. The optimization guide covers improvement, how to fix Google Ads Shopping campaigns covers diagnosis, and Google Ads Shopping campaigns best practices provides the broader framework. The adz.so product overview is a truthful evidence-review entry point; it does not create feeds or guarantee Shopping sales.