Abandoned Cart Recovery: The Definitive Klaviyo Guide

How much revenue can an abandoned cart flow recover?

There is no defensible way to estimate recovery from annual store revenue and a generic abandonment rate. The denominator has to be the people who were identified, entered the flow, remained eligible, and received the message. ZHS uses the range below as an operating diagnostic, not an industry guarantee, and compares each program against its own holdout or pre-change baseline whenever possible.

Model the opportunity from observable flow data instead:

eligible recipients × delivered rate × attributed conversion rate × average order value = attributed flow revenue

That result is still attributed, not automatically incremental. Report the trigger, eligibility rules, attribution window, period, and exclusions beside it. Maintain the flow as products, offers, site behavior, and deliverability change.

---

What is the difference between cart and checkout abandonment?

Cart and checkout abandonment are separate triggers that can share reusable creative. Cart abandonment begins with an Added to Cart event. Checkout abandonment begins with a Checkout Started event when the integration has identified the person. Checkout is a later journey stage, not a universal conversion multiplier: report the two cohorts separately and decide their priority from your own identity coverage, margins, and attributed results.

Read this section carefully, because most brands get it wrong. They either build only one of the two, or they waste days designing two different-looking flows when the emails should be nearly identical. The distinction that matters is the trigger, not the artwork.

The two triggers, and why they catch different people

In Klaviyo these are two separate triggers wired to the same creative:

Checkout abandonment fires on the Checkout Started metric. Depending on your integration and checkout behavior, it can provide a later-stage, more identified cohort with cart context. Verify the identity and item data that actually arrive in your account; do not assume this trigger will outperform Added to Cart for every store.

Cart abandonment fires on an Added to Cart event from onsite tracking. It can reach people earlier in the journey, but only when the event and a usable identity have been captured. Audit the event payload, profile identity, consent, and cart block before treating the flow as live.

Criteria	Added to cart	Started checkout
Trigger	Added to Cart event	Checkout Started event
Identity available	Only when onsite tracking has identified the person	Often more complete when checkout identity and cart data are passed
Reporting	Compare as its own cohort	Compare as its own cohort
Creative system	Reuse modules, then test treatment	Reuse modules, then test treatment

Journey-stage comparison, not an intent score or conversion benchmark.

The dedicated checkout-abandonment guide covers the Checkout Started implementation. Here is the Added to Cart build.

---

What emails go in an abandoned cart flow?

The map above is a ZHS starting configuration, not a universal send schedule. It begins with a short first-delay test, separates treatment by purchase history, and gives each follow-up a distinct job. Pair email and SMS only when the person has documented consent, quiet-hour behavior is verified, and the channel will not simply duplicate the prior message. Compare a changed cadence, offer sequence, or branch against a stable cohort before rolling it out.

One useful branch question is: has this person bought before?

Use that question to test appropriate treatment: a returning buyer may need a direct reminder, while a newer buyer may need trust or product context. A discount should be a documented test variable, not an automatic consequence of being new.

Here is what a first email and its follow-up SMS look like in practice.

---

SMS Examples

Examples only: send SMS only to people with the appropriate recorded consent, required disclosures, and eligible local-time behavior. Replace the bracketed offer and expiry language with an approved, accurately represented offer.

1. Hey [Name]! You left something behind. Complete your order: [link]

2. Still thinking about it? Here's [approved offer]: [code]. [Offer terms and expiry]: [link]

---

What can you offer instead of a discount to recover carts?

Test incentives that add value without cutting price, such as free shipping, a gift with purchase, extended returns, loyalty points, or a bundle. Free shipping can address a common checkout objection, but the right option depends on margin, product, and customer context. The same thinking underpins how you drive sales without discounting across the rest of your program. If a code is appropriate, test it in a later follow-up against a no-code control and report both conversion and margin.

Avoid making a predictable discount an automatic reward for abandoning. Watch repeat behavior and margin before expanding any offer treatment.

Try these instead.

Alternative	Why It Works
Free shipping	Removes the #1 objection
Free gift with purchase	Adds value without discounting
Extended returns	Reduces purchase risk
Loyalty points bonus	Builds long-term value
Bundle deal	Increases AOV while providing value

---

What are good abandoned cart flow benchmarks?

Use the canonical ZHS cart-and-checkout recovery benchmark as a diagnostic for eligible recipients, not a universal forecast. Conversion and total attributed revenue change with AOV, product category, identity rate, discounting, attribution settings, and whether cart and checkout triggers are blended.

The detailed scorecard should compare like with like rather than add another set of universal cutoffs:

Metric	Define it before comparing	Compare it with
Delivered rate	Eligible recipients who received the message	Same trigger, provider mix, and period
Click rate	Unique clicks per delivered message	Same message job and audience cohort
Placed-order rate	Attributed orders per eligible recipient	Same attribution window and exclusions
Total attributed revenue	Attributed revenue across a stated eligible-entry cohort	Same trigger, AOV context, offer treatment, and comparison period
Unsubscribes and complaints	Per delivered message	Trend by acquisition source and message type

Treat a meaningful change as a prompt to investigate the cohort, tracking, and customer experience, not a single-send verdict.

---

What are the common abandoned cart flow risks?

The recurring risks are untested timing, automatic discounting, generic treatment, missing product context, and message pressure. Use a documented starting configuration, then test the actual customer path and cohort response before declaring a rule.

1. Untested first-send timing. Start with a documented window, ZHS often begins around 30 minutes after the event, then test against the store’s actual buying cycle.

2. Automatic discounting. Start with a reminder or value case when appropriate, then test an offer deliberately rather than assuming a code is required.

3. One treatment for every customer. Segment by purchase history or another relevant signal when it produces a clearer customer experience.

4. Missing product context. Verify dynamic item details and fallbacks so the reminder reflects the shopper’s actual cart.

5. Uncontrolled message pressure. Check the combined email and SMS experience, account-level pressure settings, and provider signals before increasing frequency.

---

Technical Checklist

Triggers (same creative, two triggers):

• Checkout abandonment on the Checkout Started metric, prioritized only after identity coverage and customer value are assessed
• Cart abandonment on the Added to Cart metric (onsite tracking on)
• First-email delay has a documented test rationale (ZHS starting configuration: about 30 minutes)

Segmentation (one conditional split, not two flows):

• Purchaser vs non-purchaser split by purchase history
• First-timers get the trust block, repeat buyers get the plain reminder

Content:

• Dynamic cart blocks configured
• Product images pulling correctly

Exit Conditions:

• Purchase exits the flow
• Re-entry rules reflect the product cycle and prevent repetitive enrollment
• Smart Sending behavior is deliberate and tested with a real profile
• Re-entry period is documented and reviewed after offer, catalog, or lifecycle changes

---

Get Expert Help

Cart and checkout abandonment flows come with every retention package we run. Our team handles strategy, design, copy, technical setup, and ongoing optimization.

You get the full skill set, live in weeks, without hiring for it.

See our pricing | Apply to work with us