Shopify Promo Feed: Promotions, Sale Price, and Product Sets
Promo feed readiness catches price, stock, promotion-date, and product-set errors before launch, then decides what can scale from field and platform evidence.
Author
Ranfeng WeiPublished
Updated
Last reviewed
Review note: Established a verifiable publication, modification, and maintenance-review baseline.
Review scope Reviewed against Shopify, Google Search, ads, analytics, and ecommerce operating workflows.
Public preview
Understand what this lesson solves
A promotion is not a last-minute price edit. Before budget scales, sale price, effective dates, eligible products, inventory, product sets, collection pages, landing-page promises, and platform state need to be locked together. Otherwise the campaign is not buying growth. It is amplifying wrong prices, stockouts, bad product pools, and support problems.
It is July 21, 2026, and NorthPaw is preparing a US Summer Travel Weekend from July 24 at 09:00 through July 27 at 23:59 America/Toronto. The 20oz Trail Bottle drops from $24.99 to $19.99. The unit discount is $24.99 − $19.99 = $5.00 , and $5.00 ÷ $24.99 ≈ 20.0% . Page, feed, promotion data, ad creative, and checkout must describe the same amount and window.
The previous lesson closed the material-field change, but it did not approve a promotion. The governed base pool contains 21 qualified items. Promotion review excludes three low-stock variants, two low-margin bundles, and one item with an unresolved availability warning, leaving 21 − 3 − 2 − 1 = 15 for the first release. Catalog-ready is a base qualification. Promo-ready also requires price, window, inventory, margin, mapping, and checkout promise.
Lesson outline
- 1Work through the NorthPaw promotion first: 21 governed items do not mean all 21 should join
- 2Eight-step release route
- 3Completed PD-007 promo feed readiness gate
- 4Write the static conclusion before using the workbench
- 5Lesson output: Promo Feed Readiness Gate
- 6If you came from Event Commerce, continue here for field and platform evidence
Public core framework
- Lock scope. Start from the field version closed in PD-006; record US market, 15 included, six excluded, base/sale price, and the full time-zone window.
- Calculate exclusions. In Shopify/product master, lock price source, availability, variant ID, and margin tier; calculate inventory and profit exclusions before mapping.
- Create the promotion. In the promotions source, create NORTHPAW_SUMMER20_2026 with specific_products/no_code, effective dates, destination, and an accurate long_title.
- Map products. Add the exact promotion_id to the 15 eligible items. Export included/excluded lists; stop unless counts are 15/6.
- Sample at T-2. Read nine boundary SKUs through PDP → cart/checkout → feed → promotion preview → ad creative. Wrong price, code, buyability, or pool is blocking.
- Repair and rerun. Keep Hold at the first 8/9, repair 20oz/Navy, and rerun all nine. Set the first budget cap only at 9/9.
Example or scenario from the lesson
This is not a sitewide promotion. Use case-sensitive, space-free NORTHPAW_SUMMER20_2026 with product_applicability=specific_products . The 15 eligible items map to that promotion_id in product data, and offer_type=no_code . The feed sale_price_effective_date is 2026-07-24T09:00-0400/2026-07-27T23:59-0400 . A campaign page may appear early, but sale price applies only inside the effective window, and price restoration needs evidence at the end.
Public questions and answers
Why is promo feed readiness not just a last-minute price edit?
Because platforms read more than PDP copy. They read promotion_id, product_applicability, offer_type, promotion_effective_dates, sale_price, sale_price_effective_date, availability, product sets, collection pages, and landing-page promises. Before Black Friday or a 20oz summer promo, price, inventory, promotion fields, and product sets need to pass the Promo Feed Readiness Gate together.
What does the 20oz promo feed release-decision practice train?
It trains you not to treat the campaign calendar as budget approval. If the T-2 nine-SKU sample for a 20oz summer tumbler finds the PDP at 29.99 and feed at 39.99, or inventory, promotion_id, coupon code, or product set is not ready, pause budget or narrow the product pool first.
Why does the Promo Launch pressure-check practice look at schedule, preview, and total inventory?
Because a correct calendar, approved preview, or enough total stock does not prove the promo can scale. You still need SKU-level availability, sale_price_effective_date, promotion_effective_dates, price and availability consistency, product-set scope, support risk, and launch-hour war room readings.
Sources cited in the previewed lesson
Member lesson
Sign in or upgrade to read the full lesson
Checking membership access for this account.
Share this lesson with your reviewer
Share it with the copyable lesson notes so everyone reviews the same evidence, decision line, and next action.