Shopify marketing stack for discount strategy

Stack execution playbook

Discount strategy on a marketing stack is not a coupon code generator — it is governance across capture, lifecycle, SMS, loyalty, and winback layers. When every tool defaults to 10–15% off, shoppers learn to never buy full price. Full-price purchase ratio is the leading indicator of stack health.

Segment by discount sensitivity: full-price loyalists (3+ orders no code), moderate (occasional code), cold (never purchased). Full-price loyalists get early access and proof — never same coupons as bargain hunters.

One offer per intent window documented in collision calendar: popup session → welcome → browse → cart → SMS → loyalty cannot stack same afternoon. Max depth per segment row in calendar.

Proof-first paths reduce discount dependency — browse and cart email one without code for consideration categories. Incentive only when proof path fails or segment is cold/discount-sensitive.

VIP and high-AOV segments: financing and warranty before discount. Jewelry, furniture, commercial equipment train wait-for-sale with aggressive cart incentives.

Replenishment full-price default — discounting every reminder destroys consumable margin. Winback education before incentive for 90–120 day lapsed.

BFCM exception planning: deeper discounts allowed but collision calendar still applies — VIP early access before sitewide, recent full-price buyer exclusions, sunset unengaged first.

Marsello double-points same day as 20% sale email = stacked incentive. Loyalty promotional calendar syncs with email promotional calendar.

Analytics: full-price order %, discount redemption rate, margin after all incentives, repeat purchase without discount. Weekly full-price ratio review.

Popup default is the training wheel — Privy 15% sitewide trains behavior before lifecycle even starts. Quiz and value-exchange popups outperform discount wheels for replenishment LTV.

Merchant scenarios

Full-price loyalist: Early access, new arrivals, proof — zero discount in cart/browse/winback.

Cold subscriber: Welcome modest incentive email three only if popup did not deliver. Cart tiered.

High-AOV cart: Financing email one, 5% max email three discount-sensitive only.

BFCM week: Calendar max depth 25% VIP early -24h, general 20%, exclude recent full-price 14d.

Stack checklist

• Collision calendar published with max depth per segment
• Full-price loyalist segment defined and excluded from promos
• Popup default audited — not 15% sitewide without strategy
• One offer per intent window rule documented
• Cart/browse proof-first for consideration categories
• Replenishment full-price default
• Loyalty promo sync with email calendar
• VIP exclusion from sitewide blasts
• Weekly full-price ratio tracked
• Margin after discount on recovered carts
• Winback education before incentive branch
• BFCM exception rows in calendar

Exclusions (non-negotiable)

• Recent discount redeemers
• Full-price loyalists
• Customers in other offer flows

Metrics that prove quality

• Full-price order percentage
• Discount redemption rate
• Margin after all incentives
• Repeat purchase without discount

Common mistakes

• Default 10% on every automation
• Stacking popup + cart + winback discounts
• No full-price segment treatment

Discount governance across stack layers

Timing and trigger governance

Default: full-price first for engaged and loyalist segments.

Incentive escalation only on touch 3+ for cold segments.

BFCM: calendar overrides with documented max depth.

Post-peak: return to full-price-first within 7 days.

Measurement across the stack

Full-price order percentage weekly.

Discount redemption rate by segment.

Margin after all incentives.

Repeat purchase without discount within 90 days.

Related playbooks

Governance: cross-channel coordination.

Flows: cart, winback.

Vertical: high-AOV discount restraint.

Stack coordination for discount strategy

discount strategy is not an email template problem — it is a stack handoff problem. Trigger: Segment by discount sensitivity, order history, and engagement Timing: Full-price first for engaged segments; graduated discounts for cold segments; never stack with active promos 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 use incentives without training every shopper to wait, margin after discount matters more than attributed revenue.

Capture defaults: Sets first-touch discount expectation. Playbook fit: Quiz/value exchange over sitewide 15%. Failure mode: Aggressive wheel trains coupon hunters. Operator test: 90-day LTV popup vs quiz source.

Lifecycle incentives: Tiered branches by segment sensitivity. Playbook fit: Proof-first paths default. Failure mode: 10% on every automation touch. Operator test: Full-price ratio trend weekly.

SMS offers: Same caps as email — no deeper SMS discount. Playbook fit: One offer per intent window. Failure mode: SMS 20% + email 15% same day. Operator test: SMS/email offer collision audit.

Loyalty promos: Double-points days sync with email calendar. Playbook fit: No loyalty + sale email same day. Failure mode: Stacked loyalty and promo. Operator test: Collision calendar includes loyalty row.

Analytics: Full-price %, margin after incentives. Playbook fit: Finance weekly review. Failure mode: Revenue up, full-price ratio down unnoticed. Operator test: Full-price ratio above target band.

Scenario — Full-price loyalist: Early access, new arrivals, proof — zero discount in cart/browse/winback. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).

Scenario — Cold subscriber: Welcome modest incentive email three only if popup did not deliver. Cart tiered. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).

Scenario — High-AOV cart: Financing email one, 5% max email three discount-sensitive only. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).

Scenario — BFCM week: Calendar max depth 25% VIP early -24h, general 20%, exclude recent full-price 14d. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).

Checklist execution notes

Collision calendar published with max depth per segment — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.

Full-price loyalist segment defined and excluded from promos — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.

Popup default audited — not 15% sitewide without strategy — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.

One offer per intent window rule documented — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.

Cart/browse proof-first for consideration categories — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.

Replenishment full-price default — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.

Loyalty promo sync with email calendar — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.

VIP exclusion from sitewide blasts — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.

Weekly full-price ratio tracked — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.

Margin after discount on recovered carts — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.

Winback education before incentive branch — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.

BFCM exception rows in calendar — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.

FAQ deep dives

Default 10% on all automations? No — trains discount waiting. Proof-first, segment-tiered incentives. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.

Collision calendar what? Shared doc: which layers can offer what depth when — one offer per intent window. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.

Full-price loyalist definition? Typically 3+ orders without code redemption — segment and exclude from promos. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.

Popup discount strategy? Value exchange and quiz over sitewide 15% — improves LTV on consumables. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.

BFCM deeper discounts OK? Yes with calendar rules — exclusions, VIP sequencing, post-peak reset. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.

Loyalty + sale same day? Avoid — stacked incentive erodes margin and confuses. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.

Measure discount strategy? Full-price ratio weekly, margin after incentives, repeat without discount. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.

High-AOV discount? Restraint — financing/proof before discount. Max depth lower than impulse DTC. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.

Replenishment discount? Full-price default — incentive only non-responders email two. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.

Who owns calendar? Growth lead with lifecycle, capture, SMS owners — weekly review slot. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.

Shopify automatic discounts? Sync with email codes — avoid surprise stacking at checkout. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.

Biggest mistake? Independent 10% defaults in Privy, cart, winback, SMS same week — trains perpetual waiting. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.