Stack execution playbook
Post-purchase education is the stack moment that reduces returns, support tickets, and buyer remorse — while setting up replenishment and cross-sell with correct timing. Pushing another sale before delivery on furniture, jewelry, or supplements increases returns and chargebacks.
Immediate confirmation: order summary and expectation setting. Fulfillment: shipping notification. Education: delivery +2 days for usage, assembly, or routine guidance. Cross-sell: delivery +14 days for home goods, day 14 for consumables, day 7 for digital activation.
Gift vs self-purchase branches mandatory — gift buyers get packaging and care content, not "buy another for yourself." Shopify gift order properties or recipient-detected heuristics gate branches.
Yotpo review request timing: delivery +5 to +14 days depending on category — after return window assessment for high-return SKUs. Experience language in supplements; fit and comfort in apparel.
Marsello loyalty enrollment on second order or post-purchase email three after positive experience — not day-zero points pitch competing with product education.
Recharge subscription first orders get onboarding education, not cross-sell conflicting with upcoming shipment. Subscription suppressions on replenishment promos in post-purchase path.
AfterShip or Shopify delivery events gate cross-sell for home goods and high-AOV — cross-sell before delivery is top mistake in furniture stacks.
Digital products: post-purchase IS activation — access link immediate, day 1/3/7 check-ins. No shipping modules. See digital vertical guide.
SMS: delivery notification and delivery-day confirm for perishables — Postscript with opt-in. Not promotional cross-sell SMS.
Analytics: review submission rate, second order within 60 days, support ticket reduction, cross-sell attach rate — each measured separately not blended.
Merchant scenarios
Beauty routine post-purchase: Usage education day 2 → review day 7 → replenishment preview day 14 → loyalty enroll on 2nd order.
Furniture delivery-gated: Assembly email on delivered → review day 14 → cross-sell room completion day 21.
Gift jewelry order: Packaging care email → no cross-sell to gift buyer → recipient-focused content only.
Digital course: Access immediate → module 1 day 1 → stall help day 3 → no physical-product modules.
Stack checklist
- Gift vs self branch configured
- Delivery-gated cross-sell for bulky SKUs
- Review request timed post-delivery appropriately
- Subscription first-order separate path
- Loyalty not in email one
- Education before cross-sell
- AfterShip trigger verified if used
- Support FAQ link in email one
- Replenishment preview timing documented
- SMS delivery-only if applicable
- Return window considered for review ask
- Second-order 60d metric tracked
Exclusions (non-negotiable)
- Gift purchasers (different messaging)
- Subscription first orders
- High-return SKUs needing fit guide first
Metrics that prove quality
- Review submission rate
- Second order within 60 days
- Support ticket reduction
- Cross-sell attach rate
Common mistakes
- Pushing another sale before delivery
- Same post-purchase for gifts and self-purchases
- No product-specific education
Five-layer post-purchase stack map
Lifecycle orchestration: Sequenzy
Branched post-purchase by category and order type.
Education → review → cross-sell sequence.
Failure mode: Cross-sell before delivery.
Operator test: Cross-sell timestamp after delivery event.
Delivery intelligence: AfterShip, Shopify
Delivered trigger for timing accuracy.
Furniture and bulky goods cross-sell gate.
Failure mode: Ordered-event triggers cross-sell.
Operator test: 100% bulky cross-sell post-delivery.
Proof layer: Yotpo
Timed review requests and UGC follow-up.
Category-specific review timing.
Failure mode: Review ask before arrival.
Operator test: Review rate by timing variant.
Loyalty enrollment: Marsello
Second-order or post-experience enrollment.
Not competing with education email one.
Failure mode: Points pitch day zero.
Operator test: Enrollment on 2nd order rate.
Analytics: Shopify
Second order 60d, tickets, review rate, cross-sell attach.
Separate metrics per post-purchase email.
Failure mode: Blended post-purchase ROI.
Operator test: Weekly metric dashboard exists.
Timing and trigger governance
Confirmation: immediate.
Education: delivery +2 days or digital day 1.
Review ask: delivery +5 to +14 by category.
Cross-sell: delivery +14 bulky, day 14 consumables.
Loyalty enroll: second order trigger only.
Measurement across the stack
Review submission rate.
Second order within 60 days.
Support ticket volume per 100 orders.
Cross-sell attach rate post-delivery.
Return rate on post-purchase-influenced orders.
Related playbooks
Next: replenishment for consumables.
Proof: reviews and UGC.
Vertical: home goods delivery gating.
Stack coordination for post-purchase education
post-purchase education is not an email template problem — it is a stack handoff problem. Trigger: Order placed and payment confirmed Timing: Confirmation immediate; shipping at fulfillment; education at delivery +2 days; cross-sell at day 14 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 reduce buyer anxiety and set up the next purchase, margin after discount matters more than attributed revenue.
Lifecycle orchestration: Branched post-purchase by category and order type. Playbook fit: Education → review → cross-sell sequence. Failure mode: Cross-sell before delivery. Operator test: Cross-sell timestamp after delivery event.
Delivery intelligence: Delivered trigger for timing accuracy. Playbook fit: Furniture and bulky goods cross-sell gate. Failure mode: Ordered-event triggers cross-sell. Operator test: 100% bulky cross-sell post-delivery.
Proof layer: Timed review requests and UGC follow-up. Playbook fit: Category-specific review timing. Failure mode: Review ask before arrival. Operator test: Review rate by timing variant.
Loyalty enrollment: Second-order or post-experience enrollment. Playbook fit: Not competing with education email one. Failure mode: Points pitch day zero. Operator test: Enrollment on 2nd order rate.
Analytics: Second order 60d, tickets, review rate, cross-sell attach. Playbook fit: Separate metrics per post-purchase email. Failure mode: Blended post-purchase ROI. Operator test: Weekly metric dashboard exists.
Scenario — Beauty routine post-purchase: Usage education day 2 → review day 7 → replenishment preview day 14 → loyalty enroll on 2nd order. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).
Scenario — Furniture delivery-gated: Assembly email on delivered → review day 14 → cross-sell room completion day 21. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).
Scenario — Gift jewelry order: Packaging care email → no cross-sell to gift buyer → recipient-focused content only. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).
Scenario — Digital course: Access immediate → module 1 day 1 → stall help day 3 → no physical-product modules. Map this scenario to your vertical guide at /for if category-specific suppressions apply (Recharge tags, wholesale accounts, gift buyers).
Checklist execution notes
Gift vs self branch configured — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Delivery-gated cross-sell for bulky SKUs — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Review request timed post-delivery appropriately — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Subscription first-order separate path — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Loyalty not in email one — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Education before cross-sell — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
AfterShip trigger verified if used — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Support FAQ link in email one — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Replenishment preview timing documented — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
SMS delivery-only if applicable — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Return window considered for review ask — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
Second-order 60d metric tracked — assign a named owner and add to collision calendar if the checklist item touches offers across capture, email, SMS, or loyalty.
FAQ deep dives
When post-purchase cross-sell? After delivery +14 days bulky goods; day 14 consumables; never before customer has product for furniture. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Gift order handling? Separate branch — packaging/care for gift buyer, no recipient cross-sell to purchaser. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Review request timing? Delivery +5 to +14 depending category; after return window for high-return SKUs. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Loyalty in post-purchase? Enroll on second order or email three — not day zero. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Subscription first order? Onboarding education — not cross-sell conflicting with subscription shipment. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Best stack tools? Sequenzy sequences, AfterShip triggers, Yotpo reviews, Marsello loyalty timing. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Digital post-purchase? Activation not shipping — access immediate, progress check-ins. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
SMS post-purchase? Delivery notification perishables only — not cross-sell SMS. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Metrics? Review rate, second order 60d, support tickets, cross-sell attach, returns. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Biggest mistake? Cross-sell before delivery on bulky goods — increases returns and support load. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
AfterShip required? High ROI for furniture/home — optional for small parcel consumables. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.
Education content who owns? Ops/product with compliance review supplements — Sequenzy executes approved blocks. Stack operators should document this answer in internal runbooks — not rely on tribal knowledge when agencies turn over.