Skip to main content
Card class: Non-Hero • Category: Ecommerce Platform
% of failed orders that the customer self-recovered (placed a successful order within 30D, joined by lowercased email then customerId). The baseline that defines what’s already being captured without intervention.

​
At a glance

The percentage of failed BigCommerce orders where the customer self-recovered (returned and placed a successful order within 30 days) without any merchant intervention. This is the baseline that defines what is already being captured for free, the floor your tooling investments must clear to be additive.
What it countsrecovered_count ÷ failed_count × 100, where recovered_count = the subset of failed orders whose customer subsequently placed a paymentStatus = captured or paid order within 30 days, joined email-first (lowercased billingAddress.email) with customerId fallback. failed_count = orders with paymentStatus = declined OR status = Incomplete.
VAT / tax treatmentn/a, the rate is derived from order counts. The dollar twin lives at BC Size of the Prize where tax-inclusive total_inc_tax semantics apply.
Shippingn/a, count metric.
Discountsn/a, count metric.
RefundsExcluded. paymentStatus = refunded succeeded first; doesn’t belong in the failure denominator.
Incomplete ordersIncluded. Both Declined and Incomplete failures are summed into the denominator. Incomplete orders typically self-recover at a higher rate (45-60%) than Declined orders (15-30%) because Incomplete is usually a transient UX glitch the customer can retry past.
Cancelled ordersExcluded. Cancelled is a merchant void on a previously-captured order.
30-day recovery windowStrict. A subsequent successful order from the same email more than 30 days after the failure does NOT count as a recovery. This window matches typical abandonment-recovery email cadence. Beyond 30 days the customer either recovered or they walked.
Email-first join semanticsWe lowercase billingAddress.email then look for any subsequent successful order from the same email within 30 days. If the failure had no email (rare guest checkout), we fall back to customerId. We do NOT count cross-email same-customer recoveries (e.g. customer used Apple Pay private email on retry); those are real recoveries we miss, so this rate is a conservative floor.
CurrencyCurrency-agnostic, recovery is matched at the customer-identity layer, not the value layer.
Channels / sourcesNot filtered. All channel_id values contribute. Marketplace channels (Amazon, Facebook) rarely produce failures so they barely affect the rate; the rate is mostly Stencil web behaviour.
Time window30D (the failure-detection period; the recovery-detection window is also 30 days but rolls per-failure)
Alert trigger<35% (poor self-recovery), fires when the store’s organic recovery is below industry baseline, indicating either a checkout that’s so broken customers don’t try again, or a customer base with low brand attachment.
Sentiment keyrecovery_rate
Rolesowner, marketing, finance

​
Calculation

Calculated automatically from your BigCommerce data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

A US homewares brand on BigCommerce Enterprise. The 30-day window covers 14 Mar 26 to 12 Apr 26.
Failure cohortFailed countRecovered countOrganic recovery rate
paymentStatus = declined712839.4%
status = Incomplete41418845.4%
Combined (this card)48521644.5%
Industry comparison:
Store profileTypical organic recovery rateWhat it tells you
Strong brand, repeat-customer base50-65%Customers really want to buy; they retry on their own.
DTC mid-market (this example)40-50%Healthy band. Customers retry but not unconditionally.
Acquisition-heavy store with new traffic25-40%Lots of first-time buyers; if they fail once, half walk.
Low-brand commodity store15-30%No emotional attachment; customers go to a competitor.
Below 15%<15%Either checkout is structurally broken or your customer base has zero loyalty. Investigate immediately.
What’s interesting:
  1. Incomplete recovery (45.4%) is higher than Declined (39.4%). This is consistent across most BC stores. Incomplete is often a transient glitch (network blip, 3DS timing); customers retry seconds later. Declined is structural (insufficient funds, fraud rule); retry alone doesn’t fix it.
  2. A 44.5% combined rate is healthy. Industry baseline for BC Enterprise sits 40-55%. Below 35% triggers the alert because it usually means either (a) the checkout is so broken customers give up, or (b) the customer base has no brand attachment, both serious operational signals.
  3. The remaining 55.5% is your tooling addressable opportunity. Of 485 failures, 216 recovered organically; the other 269 are the Vortex Mind retargeting list. Recovery tooling typically captures 20-40% of THIS sub-population, so realistic incremental capture is ~80-110 additional orders/month, roughly $9-12k of incremental revenue.
  4. Trends matter more than the absolute number. A stable 44.5% is fine; a falling number (44.5% → 38% → 32% over three months) is an emergency. Falling organic recovery often precedes broader checkout-funnel deterioration by 4-8 weeks.
How to use this card:
  1. Set your tooling capture-rate expectations based on the inverse of organic recovery. If 45% recover organically, your tooling is competing for the remaining 55%.
  2. Compare cohorts, declined vs incomplete recovery rates often differ by 10-20 points. Tooling investment should target the lower-recovering cohort first.
  3. Watch the trend, not the level, even a 60% organic recovery rate doesn’t mean “we don’t need tooling”, it means “tooling needs to clear a higher bar to be additive”. A drop in trend tells you something is breaking before the failure rate itself moves.

​
Sibling cards merchants should reference together

CardWhy pair it with Organic Recovery Rate
BC Size of the PrizeThe dollar twin. Multiplying failed_value × (1 − organic_recovery_rate) gives the addressable-opportunity dollars.
BC Failed Orders CountThe denominator. A 45% organic recovery on 485 failures means 269 unrecovered customers.
BC Decline RateThe trend signal. Rising decline rate + falling recovery rate = compounding revenue loss.
BC Incomplete RateSame dynamic for the UX-side population. Incomplete recovery is usually higher; if it falls below decline recovery, your checkout has a structural problem.
BC Repeat Failure CustomersCustomers who failed multiple times and never recovered, the 100%-tooling-needed cohort.
BC Top Unrecovered TodayThe daily action list of the largest entries in the unrecovered cohort.
Customer SegmentsCross-reference: high-LTV customers usually have higher organic recovery than first-timers. The mix shifts the headline.
Repeat RateStores with high repeat-customer rates show higher organic recovery, brand attachment drives both.

​
Reconciling against the vendor’s own dashboard

Where to look in BigCommerce Control Panel: BigCommerce does not surface this metric natively. Organic recovery rate requires a customer-level join between failed orders and subsequent successful orders, BC’s reporting layer doesn’t compute it. To partially verify:
  1. Filter Orders by status Declined and Incomplete for the period; export the customer email list.
  2. For each email in the export, manually query subsequent orders within 30 days, count successes.
  3. Compute successful_followups ÷ total_failed_emails. The number should approximate this card to within ±5% (rate divergence comes mostly from email-normalisation differences).
Other BC views that look adjacent but miss the point:
  • Customers → Customer groups: doesn’t track recovery flows.
  • Analytics → Insights → Cohort report: tracks lifetime cohort retention, not failure-to-success conversion.
  • Storefront → Abandoned carts: tracks pre-checkout abandonment recovery, different stage of the funnel.
  • Channel Manager → Customer activity: per-channel customer events, doesn’t compute recovery rate.
Why our number may legitimately differ from a manual computation:
ReasonDirection
Email-first join semantics. We lowercase, then fall back to customerId. Manual exports often use customerId only, missing logged-out shoppers who retry under the same email.Vortex IQ HIGHER recovery rate (catches more recoveries)
30-day strict window. Manual analysis often slides the window or uses 14 days; we use a strict 30.Vortex IQ HIGHER if the manual window is shorter
Email normalisation. We treat J.Smith@example.com and j.smith@example.com as the same customer; BC stores them case-sensitively.Vortex IQ slightly HIGHER recovery rate
Cross-email recoveries excluded. Customer who failed under one email and succeeded under another (e.g. Apple Pay private email) doesn’t count as a recovery, so we under-count.Vortex IQ LOWER bound on actual recovery
Time zone. UTC vs store.Marginal
Cross-connector reconciliation: This card is a derived ratio with no direct cross-connector equivalent. The components reconcile through:
CardExpected relationshipNotes
stripe.stripe_decline_rateStripe-side decline rate is the lower bound on the failure denominatorStripe sees only Stripe-routed failures.
klaviyo.klaviyo_recovery_attributed_revenueKlaviyo flow attribution lets you split organic recovery from email-driven recoveryThis card is the organic baseline; Klaviyo’s attribution is the tooling-driven lift. The gap is your tooling’s true contribution.
The recovery-join semantics are BC-specific in our current build. Equivalent organic-recovery cards on Shopify and Adobe Commerce are tracked on the CONNECTOR_BACKLOG.

​
Known limitations / merchant FAQs

My organic recovery is 65%, do I need recovery tooling at all? Probably yes, but the math is different. A 65% organic rate means tooling is competing for the remaining 35%; if tooling captures 30% of that residual, you gain 10.5 percentage points (so combined recovery moves from 65% to 75.5%). At a 675kannualisedfailed−valuebase,that′s675k annualised failed-value base, that's 71k of additional captured revenue per year. Tooling cost of 30−50k/yearstillreturnspositiveROI.Thedecisionpivotsonwhetheryou′dratherinvestthe30-50k/year still returns positive ROI. The decision pivots on whether you'd rather invest the 50k elsewhere; for most stores recovery tooling is still in the top 5 highest-ROI investments. My organic recovery is 25%, what’s wrong? Three usual causes, in order of likelihood: (1) Checkout is so broken customers don’t try again. Audit your checkout page, look for slow tax calc, geo-IP redirects, 3DS configuration issues. (2) High-acquisition mix, lots of first-time visitors with no brand attachment. Repeat customers recover at 60%+; first-timers at 15-25%. Check your Repeat Rate. (3) High-funnel-cost categories (e.g. luxury, regulated goods) where customers comparison-shop and don’t return after one failure. Less fixable, but worth knowing. Why doesn’t this card count post-30-day recoveries? By 30 days, most realistic recovery has already happened. A customer who comes back on day 45 to retry was likely going to come back regardless of the failure (they’re just a returning customer with intent). Counting day-31+ recoveries would inflate the rate without giving the merchant actionable signal. The 30-day window is the canonical recovery-tooling timeframe and matches industry benchmarking. Does this rate include cross-method recoveries (failed on PayPal, succeeded on credit card)? Yes. As long as the customer email matches and the recovery is within 30 days, it counts regardless of which payment method they used the second time. This is the realistic merchant view, the customer recovered, the merchant got the revenue, the method swap is operational detail. Why is my Incomplete recovery rate higher than my Declined recovery rate? Different failure types, different fix paths. Incomplete is usually a transient UX glitch (network drop, 3DS timeout, browser closed); the customer reloads and retries within minutes. Declined is structural (insufficient funds, fraud rule); the customer has to change something to succeed (different card, top up funds, contact the bank), most don’t bother. A widening gap between Incomplete and Declined recovery often signals a fraud-rule misconfiguration; tighten or loosen Stripe Radar / processor rules accordingly. My number jumped 8 percentage points overnight, did something improve? Could be real (a checkout fix landed, customers can now self-retry past a previously-blocking issue), could be noise (small denominator on a quiet day produces volatile rates). Check the absolute failure count first, if it’s <50 for the period, the rate is too noisy to read precisely. Wait for a 200+ failure base before trusting a single-period number. Should I treat this as a KPI for the operations team? Yes, but as a trend KPI, not a target. Setting “achieve 50% organic recovery” as a goal incentivises checkout-team behaviour you don’t want (e.g. relaxing fraud rules to let more retries through, increasing successful failures-then-recoveries while inflating fraud loss). Track the trend; investigate dips; do not target a number. Multi-currency stores: does the rate look different by currency? Yes, but the rate is computed currency-agnostic in this card. Per-currency organic recovery cards are on the BC roadmap. Until then: customers transacting in their home currency tend to recover at higher rates than customers transacting in a foreign currency (FX confusion + bank-side blocking). If your multi-currency store has a low headline rate, slice by currency directly in OpenSearch to find the broken-currency segment. How does this rate compare across BC plan tiers? Plan tier matters less than store age and brand. Larger Enterprise stores tend to have more repeat customers and higher organic recovery; smaller Plus stores often have more new-acquisition traffic and lower recovery. Don’t benchmark against your plan tier; benchmark against your repeat-customer-rate cohort. The Vortex Mind cohort report includes recovery-rate-by-customer-segment. Is high organic recovery good or just the sign of a good checkout? A bit of both. High recovery means customers are willing to come back, which reflects brand strength AND checkout usability (they got close to paying once; they trust they can complete it on retry). It’s a genuinely positive signal. The risk is complacency, “high recovery so we don’t need to fix the checkout”, missing the tooling opportunity on the unrecovered residual.

​
Tracked live in Vortex IQ Nerve Centre

Organic Recovery Rate is one of hundreds of KPI pulses Vortex IQ tracks across BigCommerce and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.