The output is a promo feed pre-launch checklist. It upgrades pre-campaign QA from “change the sale price” into reviewable product-data evidence: Shopify products, variants, inventory, collections, discounts, Google Merchant Center, Meta Catalog, landing pages, and checkout price must tell the same story.
9 parts · 3 checkpoints · 2 free / 7 member parts →
Five objects carry the fields: Shopify product and variant, sales-channel sync, Merchant Center / Meta Catalog, ad product pool and set, and landing page, cart, and pre-checkout.
How do I run a Shopify product feed QA before a promotion launches?
This lesson turns the promo feed launch checklist into practical questions about the product pool, price, stock, product sets, the shopper path, and the handoff record. Start with the question closest to your situation, then return to the five-step checklist for read-back.
What this lesson answers
- How do I run a promo feed pre-launch checklist?
- Why do Shopify, Merchant Center, and checkout prices mismatch?
- How should I validate sale_price_effective_date, promotion_id, and promotion_effective_dates?
- How do I build Meta Catalog product sets that exclude low-stock or low-margin SKUs?
- What evidence should page, media, and support receive after QA?
Walk the buyer path before launch
Decide whether this feed can launch
Self-check not answered
First confirm the price, stock, and promise match what shoppers see.
Product pool → excluded SKUs → price fields → availability → Catalog / Merchant Center → page and checkout sampling.
- Campaign promise: Clarify why shoppers should pay attention now and where the promise is fulfilled across page, channel, and admin fields.
- Buyer path: Click from ad or email to page, product, cart, and pre-checkout to confirm the price, stock, delivery, and offer promise do not break.
- Admin evidence: Return to Shopify, Feed, GA4, Markets, or ads admin and keep reviewable screenshots and fields.
- Pause line: Write when to narrow, delay, pause, or move into the next lesson.
Understand these fields first
Each field below has an admin location and a check purpose. SKU is the seller’s own item code; variant is the sellable combination of options; product set is the grouped offer; availability is whether checkout can sell it; and sale_price_effective_date is the window in which a sale price applies.
Choose the closest current case
sale_price, compare-at price, and discount stacking
stock and fulfillment promise
product pool boundary
market price and shipping
Free account to read · Parts 3-9 · 7 parts
Members: full exercises and records
This part includes
- Where fields come from
- Official field boundary
- Read feed fields along the buyer path
1 checklist
An account is free; sign in to read this part.
Checking your membership…
No checkpoint finished in this lesson yet. Start with “Go to the exercise”.
Self-check not answered
FAQ
- What does a promo feed pre-launch checklist actually check?
It checks whether the campaign product pool, approved SKUs, excluded SKUs, Shopify PDP price, cart and pre-checkout price, Merchant Center item detail, Meta product set, stock, delivery promise, and page promise agree. The goal is not full feed governance; it is deciding launch, narrow, delay, or pause for this campaign.
- What do sale_price and sale_price_effective_date each control?
sale_price is the platform-readable campaign price. sale_price_effective_date tells platforms when that price starts and ends. Both should match Shopify PDP, cart, pre-checkout, campaign page, and ad timing; otherwise shoppers may see stale, early, expired, or market-mismatched prices.
- Can I launch if Merchant Center price and Shopify page price do not match?
Do not launch the full campaign directly. First check Shopify PDP, cart / pre-checkout, Merchant Center item detail, sale_price, sale_price_effective_date, automatic item updates, and diagnostics status. Before the fix is proven, narrow the product pool, wait for sync, pause budget, or revise the page promise.
After Feed QA, align the creative and landing page
Readable price, stock, and product sets only mean the product facts passed one gate. Before launch, creative, page, and channels still need to carry the same event reason.
Return to the Event Commerce Playbook
- Event creative calendar: turn product facts into a promise: After Feed QA, return to the creative calendar to align the first frame, page handoff, email, and ad promise.
Sources
Sources: 8Last checked
Promotions data specification (Google Merchant Center Help) (opens in a new tab)Checked
Google Merchant Center Help: article 6324471 (opens in a new tab)Checked
Google Merchant Center Help: article 7050148 (opens in a new tab)Checked
Google Merchant Center Help: article 7052112 (opens in a new tab)Checked
Shopify Help Center: Product pricing (opens in a new tab)Checked