Increase repeat purchases by making the first product outcome successful, identifying a realistic replenishment or next-use moment, segmenting customers by actual behavior, and sending useful consented communication. Separate transactional updates from marketing and suppress messages when the product, timing, inventory, or customer status is no longer eligible.
- Retention starts with the first product and fulfillment outcome.
- Replenishment timing should reflect real product use.
- Transactional and marketing consent remain separate.
- Repeat revenue must be net of refunds and message cost.
Find the exact failure before choosing a fix
Build purchase cohorts by product, first-order date, acquisition source, market, discount, fulfillment, return, and support outcome. Compare time to second order and category migration. Review whether low repeat behavior reflects product lifecycle, poor first experience, unavailable replenishment, irrelevant messaging, or naturally infrequent purchase.
Use a segmented funnel rather than a storewide average. Compare product, variant, device, market, traffic source, new versus returning shopper, and purchase stage. Preserve counts and denominators, and inspect real sessions or support evidence before treating a correlation as a customer reason.
A practical, low-risk improvement plan
Fix first-order quality and service before increasing message frequency. Use expected product life only as a starting hypothesis, let customers express a preferred future condition, and keep marketing optional. Make opt-out, pause, and preference controls work across every channel.
- Measure second-order timing by product cohort.
- Suppress customers with returns, complaints, or ineligible inventory.
- Keep service updates separate from promotional consent.
- Test relevance and net margin, not email clicks alone.
Where conditional demand adds useful evidence
BuyWhen can record a shopper's future stock, quantity, timing, service, or product condition and notify them only within the approved workflow. It is not a general-purpose loyalty program and should not turn a transactional request into an unrestricted marketing subscription.
BuyWhen should not interrupt a shopper who can already complete the normal purchase. It is a secondary path for an unresolved condition, with explicit contact permission, merchant control, expiry, and live checkout validation. A request remains potential demand until it is qualified and never becomes guaranteed revenue merely because it was submitted.
Measure paid outcomes and guardrails
Measure cohort repeat rate, time to second paid order, net sales, contribution margin, returns, support contacts, sends, opt-outs, complaints, and holdout lift. Avoid crediting BuyWhen for normal repeat behavior unless the evidence and comparison support that claim.
Track the complete path from eligible visit to interaction, request, merchant response, checkout, paid order, refund, cancellation, and contribution outcome. Separate direct orders, attributed recovered orders, and experimentally estimated incremental orders. Record the attribution window and exclusions so the report can be audited later.
Frequently asked questions
How often should a Shopify store email past customers?
There is no universal frequency. Use consent, product lifecycle, customer preference, engagement, complaint risk, and incremental value to set bounded frequency rules.
Is a replenishment reminder transactional?
It depends on the customer's explicit request and applicable rules. Treat optional promotional or cross-sell content as marketing and keep its consent separate from necessary request updates.
Sources and further reading
Product guidance is grounded in BuyWhen's documented behavior. The broader commerce and search principles in this guide also reference these primary sources: