martech cookbookSearch recipes & patternsSign up
Recipe·Updated 20 May 2026

Cart abandonment recovery basic

A three-message email sequence triggered by abandonment, gated by consent and channel eligibility

01Problem

Roughly half of all carts get abandoned. The exact rate varies by category (apparel runs higher, groceries lower, luxury higher still), but the order of magnitude is the same across consumer ecommerce. A meaningful share of that abandonment is recoverable. The shopper got distracted, hit a checkout friction, wanted to compare on another site, decided to think about it overnight. They had real intent. They just didn't finish.

This is the lowest-readiness recipe in the cookbook because most ecommerce platforms ship cart abandonment recovery out of the box. Shopify Email includes it. Klaviyo has it preconfigured. Bloomreach, Customer.io, Iterable all do. The capability is sitting in the platform. The recipe exists to surface what most teams do wrong with that out-of-the-box capability, which is usually one of three things: never turning it on, turning it on with default settings that condition customers to wait for discounts, or running it without consent and eligibility checks that the platform doesn't enforce by default.

Recovery rates for a competent setup land somewhere between five and fifteen percent of abandoners. That's not a marginal number for a brand with meaningful cart volume. A site doing ten thousand abandonments a month at an average cart value of eighty euros, recovering ten percent, is recovering eighty thousand euros of revenue that would otherwise have walked.

02Outcome

A three-stage email sequence triggered by cart abandonment events, sending at intervals tuned to the brand's purchase cycle, suppressed at send time for customers who completed checkout, gated by consent and channel eligibility. Recovery rate measurable against a holdout cohort that doesn't receive the sequence, so the team knows what's incremental and what's just timing.

03Ingredients
  • Cart events
  • Cart contents
  • Hashed email identifier
  • Consent state flag
04Equipment

An email service provider or platform-native email tool with behavioral triggers (Klaviyo, Customer.io, Iterable, Shopify Email, Bloomreach). A tag manager or storefront integration capturing cart events. A consent management platform if consent isn't carried natively in the ESP. Most platform-native ecommerce setups (Shopify, BigCommerce, WooCommerce) have all of this in one place. Composable setups split it: cart events in the storefront, customer data in the CDP, messaging in the ESP. Both architectures work.

05Staff
  • Marketing ops
    CriticalSequence configuration, content design, timing decisions, suppression logic for completed checkouts
  • Analytics
    SupportingRecovery rate measurement, incrementality check against organic recovery baseline
  • Privacy ops
    SupportingConsent verification for triggered messaging, especially in jurisdictions requiring separate opt-in for behavioral email

Three roles for a basic implementation. Marketing operations owns the sequence: the timing, the content, the suppression rules, the relationship to other lifecycle programs that might be sending in parallel. Analytics runs the measurement, ideally with an incrementality test against a holdout cohort. Privacy operations or legal verifies consent posture before launch, especially for European or California traffic where behavioral triggers may require separate consent from general marketing email.

06Technique
INPUTSPROCESSACTIVATIONCart eventsCart contentsHashed emailidentifierConsent state flagAbandonmentdetectionHoldout assignmentAbandoners segmentEligibility checkEmail sequenceEmail reminderEARLYEmail promptMIDEmail finalLATE

The trigger fires on abandonment. Definitions of "abandonment" vary: some platforms use "cart created but not completed within a defined window" (commonly thirty to sixty minutes); others use "checkout started but not completed." The choice depends on where the most actionable signal lives. Add-to-cart with no checkout-start is a weak signal (the shopper may have been window-shopping). Checkout-start with no completion is a strong signal (the shopper had intent strong enough to begin entering payment details). Pick one definition and stay with it.

The sequence has three stages with different jobs. Stage one, between one and four hours after abandonment, is the reminder. Subject line treats the abandonment as if it might have been accidental ("Your cart is waiting"), shows the cart contents, includes a direct path back to checkout. No discount, no urgency, no marketing language. The customer was just here; they don't need to be sold.

Stage two, between eighteen and thirty hours after abandonment, is the prompt to reconsider. Social proof, scarcity if it's real, a reminder of what's in the cart, possibly a related product if relevant. Still no discount. The customer is now in a different mental state than at abandonment, and the message acknowledges that.

Stage three, between sixty and ninety hours after abandonment, is the last attempt. This is where some brands deploy a discount and others don't. The discount is a powerful lever and a dangerous one. It recovers customers who otherwise wouldn't return, but it also conditions repeat customers to abandon strategically because they've learned the discount is coming. Brands that send a discount at stage three for every abandonment, every time, are training their customer base to abandon as a price negotiation tactic. The defensible posture is to use the discount selectively (high-value carts, lapsed customers, never on repeat-abandoners) or to skip it entirely and accept the lower recovery rate.

Suppression at send time is the non-negotiable part. Before each stage sends, the system checks whether the customer has completed checkout in the interim. If yes, the rest of the sequence cancels. Without this check, a customer who returned and bought thirty minutes after the stage-one email still receives stages two and three, which is the most obvious failure mode in cart recovery. Most platforms handle this automatically; verify rather than assume.

Channel eligibility is the second non-negotiable. Each stage checks at send time whether the customer is still subscribed to behavioral or marketing email, whether their consent is current, whether they're in a jurisdiction that requires special handling. Customers who unsubscribed yesterday should not receive the sequence today, even if the trigger already fired.

07Gotcha
Failure 01

The discount-conditioning trap is the most common one. A team turns on stage-three discount sends with no segmentation. Recovery rate goes up. Six months later, repeat customers are abandoning their carts intentionally and waiting for the discount email. Average order value drops. Margin drops. The team can't easily unwind the program because customers have learned the pattern. The fix is to either never send discounts at stage three or to limit them to specific cohorts (new customers, high cart values, lapsed buyers) and exclude repeat-abandoners.

Failure 02

Anonymous-cart abandonment is where the recipe quietly fails to work for most ecommerce sites. The recipe needs an email to send to. If the shopper added to cart but never entered their email or logged in, there's no recipient. The platform might capture the event, but the customer is unreachable. Browser-resident cart-restore (a "your cart is still here" prompt when the visitor returns to the site) is the only available channel. Some brands address this by collecting email earlier in the checkout flow (before payment, on cart view). Doing so is a tradeoff between abandonment intervention and a more aggressive collection that some shoppers find friction.

Failure 03

The over-firing trap catches teams running multiple lifecycle programs without clear precedence. A customer abandons a cart, gets a stage-one recovery email, opens a separate welcome series the same day, gets a browse-abandonment email from a different program, gets a low-stock notification, and so on. Each program is well-meaning. The customer experience is harassment. A program hierarchy or send-frequency cap, set at the platform level, prevents the pile-on. Define which program wins precedence and configure the platform to enforce it.

Failure 04

Consent timing trips a lot of European implementations. Customers consent to "marketing email" at signup, which feels broad enough to cover cart recovery. Some regulators read it more narrowly: behavioral triggers based on browsing or cart activity may require separate consent from general marketing communications. The implementation question is whether your consent capture explicitly mentions behavioral triggers, and whether the consent record can support that distinction at audit. Most ecommerce sites don't get audited on this. Some do.

WorkshopFor your stack·The questions this recipe raises

Eight questions this recipe raises for your stack.

The Workshop works out with your team which of these matter for your stack right now, and what to do first: a 90-minute session with the people who own the decision.

  1. 01Cart event schema and tag manager configurationWhich add-to-cart and checkout-start fields the trigger actually needs, and where they break.
  2. 02Three-stage sequence template by categorySubject lines, send times, and content jobs per stage, tuned to the purchase cycle.
  3. 03Send-time suppression and channel eligibility checksCatching the customer who bought, or unsubscribed, after the trigger fired.
  4. 04Discount logic and margin thresholds by cart-value tierWhen stage three earns a discount, and the cohorts that must never get one.
  5. 05Anonymous-cart handling and the email-capture tradeoffWhat you can do for the shopper who never left an address, and what it costs.
  6. 06Cross-session cart reconstructionReassembling the cart a returning visitor abandoned across separate sessions.
  7. 07Holdout methodology for incrementalitySeparating recovered revenue from sales that would have happened on their own.
  8. 08Send-frequency caps and program precedenceStopping the pile-on when welcome, browse, and recovery all fire the same day.

If cart recovery is the most sophisticated lifecycle program you're running and you're starting to feel the limits of the platform defaults, the Workshop is where we work out what the next layer looks like.

Most teams find that the gap between basic cart recovery and full lifecycle orchestration is bigger than they expected, and the bridge is usually a CDP rather than a more sophisticated ESP.

take this to the martech workshop→

Did this recipe match your situation?Anonymous response. Sign up to leave a longer note tied to your account.

Related recipes