How much is your post-purchase CX leaking?
Put in your real numbers. We'll show your annual recoverable contribution across every post-purchase leak: checkout, fulfilment, experience and retention. Directional estimate, confirm with your data.
Directional starting points - overwrite with the client's actuals.
Business
Checkout & payment
Fulfilment leak
Experience
Retention leak (cohort)
Engagement
Checkout & payment
India cart/checkout abandonment runs ~68–72%; payment failure is the top cause (~35%). Fixing payment, hidden costs and forced sign-up recovers 15–25% of abandoned carts, plus 5–10% with WhatsApp/SMS. Sources: Razorpay, Shiprocket 2025. Confidence: High.
Fulfilment — RTO, NDR & failed delivery
India D2C RTO averages 20–30% (COD-heavy up to ~40%); below 12% is operationally excellent. Automated NDR workflows recover 30–50% of at-risk orders within the 24–72h window. Sources: GoKwik, ClickPost 2025–26. Confidence: High.
Experience — accuracy, damage & efficacy
Wrong/missing/damaged fulfilment defects typically run 1–3% of orders; efficacy-driven refunds run higher in wellness/Ayurveda. Reducing avoidable refunds protects margin and reviews. Directional — confirm with client WMS/returns data. Confidence: Med.
Retention — repeat & replenishment
DTC repeat-purchase averages 25–30% over 12 months; consumables 35–45%, beauty 30–40%. Replenishment timed to 70–80% of the consumption cycle converts 8–15% vs 1–3% generic. Sources: finsi.ai, Swell 2025–26. Confidence: High.
Assumptions & methodology
Leak 1 — Checkout & payment. (Orders ÷ completion now) × (target − current completion) × contribution per order × 12 × realization factor.
Leak 2 — Fulfilment. Orders × COD share × (current − target RTO) × (contribution + 1 shipping leg) × 12 × realization factor.
Leak 3 — Experience. Orders × (current − target refund rate) × (contribution + 1 shipping leg) × 12 × realization factor.
Leak 4 — Retention. (Target − current repeat rate) × new customers × 12 × extra orders per retained customer × contribution per order × realization factor.
Realization factor. Conservative 0.6 · Base 0.8 · Aggressive 1.0 - discounts gross upside for real-world execution drag.
Directional estimate from inputs the client confirms, not a guarantee. Replace benchmark defaults with their actuals. Benchmarks are current as of the build month and should be refreshed quarterly.
