Promo Feed Readiness and Seasonal Merchandising
Before a promotion, lock price, inventory, promotion labels, collections, ad product sets, and landing page consistency so the feed does not fail on launch day. This lesson stands on its own and also works as the product-data handoff between Google Ads, Meta Ads, SEO, CRO, and operating reviews.
First, this lesson stands on its own
If you are facing one specific issue, such as a Merchant Center warning, a mismatched Meta product set, or a confusing collection page, you can start here. The key idea is simple: product data is not one file. It is an operating chain that distributes facts into several channels.
PetNest is the case site for this lesson. We will separate the same product across Shopify, feeds, catalogs, search, collections, and structured data so one channel fix does not break another channel during the next sync.
What this lesson solves
Before a promotion, lock price, inventory, promotion labels, collections, ad product sets, and landing page consistency so the feed does not fail on launch day.
The goal is not to fill every possible field at once. The goal is to build a reusable decision order: decide whether the field is required, identify the source, then identify every destination affected by the field. When a new issue appears, the team can fix the root source instead of patching the visible warning only.
- Step one: define the single source of truth so Shopify, feed apps, Merchant Center, and catalog tools do not maintain conflicting versions.
- Step two: assign owner, validation page, and refresh timing so a sync delay is not mistaken for an ads problem.
- Step three: write the fix into the change log so the next similar issue reuses the same path.
Promo readiness board: change QA
This table is the working asset for the lesson. Do not only copy field names. Add the current store owner, validation page, and last updated timestamp to every row.
| Field or node | Recommended source | Owner / use | Governance decision |
|---|---|---|---|
| T-14 | Confirm included and excluded SKUs | Merchandising + ads operations | |
| T-10 | Check price, inventory, and sale date ranges | Operations owner | |
| T-7 | Sync collection, product set, and custom labels | Site operations + ads operations | |
| T-2 | Sample landing page, feed preview, and structured data | QA owner |
Public references: https://support.google.com/merchants/answer/188489?hl=en / https://help.shopify.com/en/manual/online-sales-channels/marketplaces/google/getting-setup/syncing-products. These sources confirm field, sync, diagnostic, or structured-data boundaries. Operating signals should become checklists and owner rules instead of visible source labels.
A promotion is not just a price edit
If the PetNest harness joins a summer sale, sale price, sale_price_effective_date, collection, product set, and home page module all enter the readiness board on the same day.
Turn this decision into the lesson asset, not just a meeting note. Any change that affects price, availability, product title, image, taxonomy, variant ID, or promotion status should trace back to one source field and one owner.
Seasonal merchandising needs exclusion rules
Not every in-stock product belongs in a promotion. Low inventory, high returns, weak images, or unresolved feed warnings should enter the exclusion list first.
Turn this decision into the lesson asset, not just a meeting note. Any change that affects price, availability, product title, image, taxonomy, variant ID, or promotion status should trace back to one source field and one owner.
The first launch hour checks consistency
Do not only watch spend. In the first hour, sample price, availability, landing page, Merchant Center status, and product set matching so budget does not push unavailable or mismatched items.
Turn this decision into the lesson asset, not just a meeting note. Any change that affects price, availability, product title, image, taxonomy, variant ID, or promotion status should trace back to one source field and one owner.
PetNest operating drill
PetNest needs to review 12 SKUs this week. Sample 3 SKUs and compare the product page, Merchant Center preview, Meta Catalog item, collection page, and structured data. Check title, price, availability, image, brand, GTIN, and variant ID consistency.
Execution checks
- Log mismatched fields in the lesson asset, not in a temporary chat thread.
- Mark impact scope: ads serving, organic search, on-site search, collections, dynamic ads, or monthly review.
- Give every fix an owner, deadline, and validation method.
- After the fix, wait for one sync cycle and save the updated channel state.
Cross-series handoff
This lesson connects pricing, ads, and inventory. After the campaign, it hands off to lesson eight for review.
If you arrived from ads, SEO, CRO, or operating review work, keep this boundary clear: this series makes product facts trustworthy. Later series decide budget, page design, creative scripts, or profit tradeoffs.