Stack execution playbook
Product launch on a full stack is a timed coordination play — VIP early access, waitlist fulfillment in signup order, general launch, and inventory-synced variant accuracy. Fashion drops, beauty shade launches, POD trend releases, and food limited flavors share launch architecture with different urgency windows.
VIP access 24h before general launch for qualified RFM segment — Klaviyo predictive CLV or order-count threshold. VIP email must not leak codes to bargain segment before general launch window.
Waitlist fulfillment: Privy tags by variant → Sequenzy sends in waitlist order on restock → never full list for six-unit restock. Postscript VIP SMS 2h before email for drop-native brands.
Inventory sync mandatory — launch email with sold-out variant destroys trust. Shopify inventory check before every launch and back-in-stock send.
Suppress recent purchasers of same or adjacent SKU from launch promo — they already bought.
Sold-out variants excluded from dynamic product blocks — fallback creative when inventory zero.
Collision calendar: launch week pauses winback and conflicting promos. Loyalty double-points not same day as launch blast.
Yotpo UGC from beta or early buyers embedded in general launch email two for social proof.
Analytics: 48h sell-through, waitlist conversion, VIP vs general revenue split, false alert rate if OOS again.
POD and food: 48h sell-through window. Beauty shade: back-in-stock variant. Fashion drop: full collection launch with size-level accuracy.
Merchant scenarios
Fashion drop: Privy waitlist by variant → VIP SMS 2h early → Sequenzy waitlist order → Klaviyo general 2h later → inventory gates.
Beauty shade launch: Waitlist by shade → VIP early → proof UGC in email two → suppress recent shade purchasers.
POD viral design: 48h sell-through focus → margin cap → waitlist order only → no sitewide discount launch.
Food limited flavor: Waitlist → regional availability check → shipping cutoff in launch SMS.
Stack checklist
- Waitlist tags by SKU/variant
- VIP segment defined with exclusion rules
- VIP timing 24h before general documented
- Inventory check pre-send automated
- Waitlist fulfillment order not full blast
- Recent purchaser suppression
- Sold-out variant fallback creative
- SMS VIP early access if drop brand
- Collision calendar launch week rows
- 48h sell-through tracking
- Post-launch sold-out handling
- Holdout on launch incrementality optional
Exclusions (non-negotiable)
- Customers who already purchased
- Sold-out variants
- Markets where product unavailable
Metrics that prove quality
- Launch sell-through in 48h
- Waitlist conversion rate
- VIP vs general revenue split
- Inventory accuracy in emails
Common mistakes
- Sending launch to entire list including recent buyers
- No inventory sync on variants
- VIP and general list same timing
Launch stack coordination map
Waitlist capture: Privy
Variant-level waitlist tags and position.
Ordered fulfillment handoff to Sequenzy.
Failure mode: Full list blast on 6-unit restock.
Operator test: Waitlist conversion vs cold list.
Lifecycle launch: Sequenzy
VIP, waitlist, general sequences timed.
Inventory gate on every send.
Failure mode: OOS variant in launch email.
Operator test: Zero OOS launch sends last 90 days.
VIP segmentation: Klaviyo
RFM and CLV early access qualification.
VIP revenue split tracked.
Failure mode: VIP and general same timing.
Operator test: VIP early access revenue % documented.
SMS drop urgency: Postscript
VIP early text before email wave.
2h early access for drop brands.
Failure mode: SMS full list promo on scarce SKU.
Operator test: SMS opt-out on launch week under 2%.
Analytics: Shopify
48h sell-through, waitlist conversion, VIP split.
Launch retrospective within 7 days.
Failure mode: Celebrating send volume not sell-through.
Operator test: 48h sell-through rate per launch.
Timing and trigger governance
VIP: -24h general launch (or -2h SMS for drop brands).
Waitlist: immediate on restock in signup order.
General: go-live at inventory confirmed.
Expire waitlist offer after 48h scarcity window.
Pause conflicting promos launch week.
Measurement across the stack
48h sell-through rate.
Waitlist conversion %.
VIP vs general revenue split.
Inventory accuracy — false alert rate.
Unsubscribe spike launch day.
Related playbooks
Related: back-in-stock.
Governance: seasonal campaigns.
Stack coordination for product launch campaigns
product launch campaigns is not an email template problem — it is a stack handoff problem. Trigger: New product live, waitlist signup, or VIP segment qualification Timing: VIP access 24h early; general launch at go-live; waitlist fulfillment in order Every layer must read the same customer state: capture tags from Privy, lifecycle execution in Sequenzy, proof modules from Yotpo, loyalty tier from Marsello, SMS consent from Postscript. When coordinate drops, waitlists, and VIP early access, margin after discount matters more than attributed revenue.
Waitlist capture: Variant-level waitlist tags and position. Playbook fit: Ordered fulfillment handoff to Sequenzy. Failure mode: Full list blast on 6-unit restock. Operator test: Waitlist conversion vs cold list.
Lifecycle launch: VIP, waitlist, general sequences timed. Playbook fit: Inventory gate on every send. Failure mode: OOS variant in launch email. Operator test: Zero OOS launch sends last 90 days.
VIP segmentation: RFM and CLV early access qualification. Playbook fit: VIP revenue split tracked. Failure mode: VIP and general same timing. Operator test: VIP early access revenue % documented.
SMS drop urgency: VIP early text before email wave. Playbook fit: 2h early access for drop brands. Failure mode: SMS full list promo on scarce SKU. Operator test: SMS opt-out on launch week under 2%.
Analytics: 48h sell-through, waitlist conversion, VIP split. Playbook fit: Launch retrospective within 7 days. Failure mode: Celebrating send volume not sell-through. Operator test: 48h sell-through rate per launch.
Scenario — Fashion drop: Privy waitlist by variant → VIP SMS 2h early → Sequenzy waitlist order → Klaviyo general 2h later → inventory gates. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).
Scenario — Beauty shade launch: Waitlist by shade → VIP early → proof UGC in email two → suppress recent shade purchasers. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).
Scenario — POD viral design: 48h sell-through focus → margin cap → waitlist order only → no sitewide discount launch. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).
Scenario — Food limited flavor: Waitlist → regional availability check → shipping cutoff in launch SMS. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).
Checklist execution notes
Waitlist tags by SKU/variant — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
VIP segment defined with exclusion rules — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
VIP timing 24h before general documented — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Inventory check pre-send automated — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Waitlist fulfillment order not full blast — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Recent purchaser suppression — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Sold-out variant fallback creative — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
SMS VIP early access if drop brand — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Collision calendar launch week rows — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
48h sell-through tracking — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Post-launch sold-out handling — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Holdout on launch incrementality optional — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
FAQ deep dives
Launch to full list? No for scarce SKU — waitlist order and VIP early access. Full list only broad availability launches. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
VIP early access timing? 24h before general typical; drop brands SMS 2h before email. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Inventory check? Mandatory pre-send — variant-level Shopify sync. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Waitlist order? Privy signup order via Sequenzy — not simultaneous blast. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Recent buyers? Suppress launch promo if purchased same/adjacent SKU recently. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Best launch stack? Privy waitlist, Sequenzy fulfillment, Klaviyo VIP, Postscript drop SMS, Yotpo proof. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
POD launch specifics? 48h sell-through, margin cap, waitlist only, community content. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Collision calendar? Pause winback and conflicting promos launch week. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Metrics? 48h sell-through, waitlist conversion, VIP split, false alerts. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Sold out mid-launch? Pause sends, update creative, waitlist for next restock — no false urgency. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Shopify Email launches? Insufficient VIP branching, waitlist order, inventory gates. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Biggest mistake? Full list blast on limited restock — burns list and VIP trust. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.