Text version of this lessonExpand
Event Commerce Playbook · Lesson 6
This lesson produces a promo feed launch gate. Before launch, you will sample SKUs and variants, check sale price, sale_price_effective_date, availability, product set scope, page promise, and checkout proof, then decide Go, Delay, Narrow, or Pause.
Launching the Page Is Not Launching the Campaign
Many teams treat an event launch as a page update: the banner changed, the PDP says sale, and the email is scheduled. But buyers do not stay on one page. They move between Google Shopping cards, PMax product cards, Meta Catalog ads, email CTAs, collections, PDPs, cart, and checkout. If one key promise conflicts, the buyer starts doubting the click, the price, the stock, or the store.
The corrected model is system promise consistency. The product shown in ads, the fields read by feeds, the price shown on the page, availability, checkout total, and shipping promise must say the same thing. This lesson is not a full feed governance manual. It is the pre-event launch gate.
Theoretical Starting Point: Promise Consistency, Trust Breakdown, and System Friction
Promise consistency explains why a small field mismatch can become a conversion problem. During events, buyers compare more alternatives and tolerate less friction. If the ad price is low but the page price is high, they feel baited. If the page has a discount but the Shopping card still shows the old price, the promotion feels unreliable. If the hero variant is out of stock, the store looks unprepared.
System friction is often not a strategy mistake. It is a reading mistake: sale price did not enter the feed, sale_price_effective_date was not checked by market, Meta product set included low-margin or out-of-stock SKUs, availability lagged real inventory, or page copy, structured data, feed fields, and checkout price contradicted each other.
Terms to Clarify
- SKU: the store-owned product or inventory identifier. SKU sampling tells you which exact product is being promoted.
- Variant: a buyable option such as color, size, or bundle configuration. A red 20oz tumbler and black 20oz tumbler can have different stock risk.
- Sale price: the promotional price platforms read. Discount copy in a theme does not mean Merchant Center or ad platforms read the sale price field.
- sale_price_effective_date: the start and end window for the sale price. Multi-market campaigns must check timezone, page countdown, and email timing.
- Availability: the sellable status platforms see. Available does not always mean a promoted variant has enough stock for high-budget promotion.
- Product set: a group of products included or excluded in an ad platform such as Meta Catalog. A broad product set can promote low-margin, out-of-stock, or non-event SKUs.
The Six Pre-Launch Gates
Price gate: check Shopify product or variant price, Merchant Center item detail, landing page price, and checkout price. If ad or feed price conflicts with landing or checkout price, delay high-budget Shopping or PMax.
Date gate: check sale_price_effective_date, page deadline, email send window, and market timezone. Do not use strong deadline copy without a real end window.
Inventory gate: check Shopify inventory, fulfillment lead time, and promoted variant samples. Thin-stock SKUs should not lead the creative or product set.
Product set / collection gate: check Meta product set, Google product group, and Shopify collection. Campaign scope must exclude low-margin, out-of-stock, and non-event products.
Landing page promise gate: check PDP, collection, landing page, shipping, and returns copy. Page promises must match offer, stock, and fulfillment capacity.
Checkout confirmation gate: run a cart or checkout sample to confirm total, shipping, tax, and discount do not undermine the advertised offer.
Worked Example: BFCM 2-Pack Tumbler Bundle
The main market is the USA, with Canada and the UK as secondary markets. The offer is the 2-pack tumbler bundle from the previous lessons: page and email say “$72 ends Sunday,” creative highlights the red 20oz variant, and the team plans Google Shopping / PMax plus Meta Catalog promotion.
Error A: the page has the sale price, but Merchant Center still reads the old price. The PDP shows $72, while the Google Shopping card still shows $80. Likely causes include a missing sale price field, incomplete feed processing, structured data or landing price mismatch, or a price that was only changed in theme copy. Decision: Delay high-budget Shopping / PMax, sample 5-10 hero SKUs, and keep Merchant Center item detail, landing page, and checkout price evidence.
Error B: a thin-stock hero SKU is inside a high-budget product set. The red 20oz variant has only 12 units left, the Meta product set includes every color, and creative highlights red. Decision: Narrow the product set, remove or downgrade the red variant from hero creative, promote colors with enough stock, and write the inventory pause item into copyable lesson notes.
Error C: multi-market dates are misaligned across time zones. The USA page says 12 hours remain, UK buyers see the promotion as ended, and the Canada email CTA still points to the old landing page. Decision: Pause multi-market expansion, sample one SKU per market, check page, feed, email CTA, and checkout, and avoid strong deadline copy in unverified markets.
How to Use the Interactive Practice: EvidenceStack + GateMap
In the integrated practice, choose one gate: Price, Date, Inventory, Product set, Page promise, or Checkout. The right side shows what the buyer sees, what backend evidence says, common failure, and the recommended status. Do not trust the page view alone. Check fields platforms read: Shopify product or variant, Merchant Center item detail, Meta Catalog item or product set, landing page, checkout test, and campaign product group.
GateMap has four outcomes. Go means the evidence aligns. Delay means the scope is correct but sync, processing, or evidence is incomplete. Narrow means a smaller verified SKU, market, or color scope can launch. Pause means price, date, stock, or checkout promise is materially wrong.
Stop / Go Decision
Go: price, date, inventory, product set, page promise, and checkout evidence align; sampled SKUs have proof; campaign scope is controlled; the next step can be paid media pacing.
Delay: feed processing, Merchant Center item detail, or Meta Catalog sync is not complete, but SKU scope and offer are correct.
Narrow: some SKUs, colors, markets, or product sets are unsafe, but a smaller verified scope can launch.
Pause: price, date, inventory, shipping, or checkout promise conflicts materially, or critical evidence is missing. Do not let ad budget pay for system errors.
Copyable Lesson Notes
- Event product scope:
- Sample SKUs:
- Variant risk:
- Sale price field:
- Promotion dates:
- Inventory status:
- Product set / collection:
- Backend evidence:
- Pause items:
- Next route: paid-media-pacing-during-high-noise-events
Boundary With Adjacent Series
This lesson owns the pre-event launch gate. It does not replace the Product Data Feed series for full feed governance, GTIN, structured data, or long-term item issue debugging. It also does not replace Google Ads or Meta Ads campaign setup and budget optimization, or Shopify Ops inventory and fulfillment systems. The next lesson discusses paid media pacing only after the verified launch scope is clear.