How can I recover abandoned carts with Klaviyo?
A relevant reminder instead of blanket vouchers: how we connect store data, Klaviyo filters and useful messages for unfinished purchases.
AI-generated image- 1Quick answer
- 2Key takeaways
- 3When does a cart reminder make sense?
- 4Which event should trigger my Klaviyo flow?
- 5What should I check in the PrestaShop integration?
- 6How do I prevent reminders after a customer has ordered?
- 7Can I automatically email every captured contact?
- 8How many messages and how much discount do I need?
- 9Which scenarios should I test before launch?
- 10How can I tell whether the flow really helps?
- 11How can sjmedia help with cart recovery?
- 12Sources & further reading
- 13Cite this article
- 14Authors & technical review
Quick answer
A Klaviyo flow can remind suitable contacts who started a purchase and are eligible to receive the message. First verify store events, purchase exclusion filters and the route back to the cart. Begin with a limited sequence and assess relevant orders and commercial impact. A discount is not automatically necessary.
A full cart is not yet an order. Sometimes the shopper was interrupted, sometimes information is missing, and sometimes checkout does not work as expected. A reminder can help, but it cannot resolve every cause. At sjmedia, we would first establish whom you can appropriately contact and whether the store data identifies an actual abandonment. Only then would we plan the message and timing in Klaviyo.
Key takeaways
- Verify checkout events and completed purchases before launching the flow.
- Send targeted reminders only to appropriate, legally eligible contacts.
- Evaluate orders and commercial impact rather than open rates alone.
When does a cart reminder make sense?
A reminder makes sense when a reachable contact who is eligible for that message has started but not completed a purchase, and the message offers a useful route back. We would start with a clearly defined audience. Treating every store visitor as a cart abandoner would distort the starting point.
A technical failure needs a different response from a forgotten purchase. If a payment provider regularly returns errors, checkout should be repaired first. Our guide to reducing checkout abandonment in PrestaShop covers those causes. This article addresses subsequent recovery through an appropriate message.
Which event should trigger my Klaviyo flow?
Klaviyo distinguishes events such as adding a product to a cart and starting checkout. A checkout-based flow uses the relevant event with a delay, while a filter excludes completed purchases. The exact event name depends on the integration. Source: Klaviyo abandoned cart flows.
We first examine a real test profile. When does the event appear, which products does it contain, and is the contact identified correctly? A library template does not replace this check. A guest entering an email address late in checkout may be captured differently from a signed-in customer. Planning should follow your store's verified data flow rather than an assumed default feature.
- Orientation
- Understand the product
- Build confidence
- Review the order
What should I check in the PrestaShop integration?
For PrestaShop, Klaviyo documents checkout-event data including cart contents, language and a cart recovery link. Order events depend on the configured order-status mapping. Source: PrestaShop data reference. We would therefore test that mapping alongside the actual ordering process.
A completed purchase must become recognisable in time. The return route from the email matters too: does it open the correct cart, use the right language and show products that can still be ordered? When prices or availability change, the message must not make a promise the store can no longer fulfil.
This is where we connect PrestaShop support with Klaviyo setup. For Shopify and Shopware, we examine the relevant integration and its events separately. We would not transfer a working PrestaShop flow unchanged to another platform.
How do I prevent reminders after a customer has ordered?
The filter logic must account for completed purchases. For the usual workflow, Klaviyo recommends excluding contacts who have placed an order since entering the flow. Profile filters are checked before individual messages. Source: Klaviyo triggers and filters.
If a reminder still arrives after purchase, we first examine the order events and their timestamps. A delayed event can affect the flow's decision. Klaviyo explicitly describes this scenario in its metric-triggered flow troubleshooting guide. Increasing the delay repeatedly without that investigation would not address the underlying issue properly.
We also coordinate the flow with other messages. A contact should not receive the same purchase prompt from several automations simultaneously. We would document which workflow takes priority and when re-entry is appropriate.
Can I automatically email every captured contact?
Having an email address does not automatically authorise a send. Before activation, the audience, consent records and legal requirements applicable to your situation need to be established. We would implement the legally agreed requirements as traceable flow conditions. Klaviyo also advises legal review for these automations. Source: Klaviyo privacy requirements.
Technical acceptance testing therefore includes contacts without the required permission and contacts who have unsubscribed. Removing a suppression is not a substitute for documented permission. Your legal advisers should assess the requirements for your recipients; we implement the agreed technical rules.
How many messages and how much discount do I need?
We would initially test a useful reminder without a blanket voucher. It can provide a route back to the cart and a real contact option for unanswered questions. Whether another message is worthwhile depends on the buying cycle, product range and results. There is no universally best sending time for this planning exercise.
A hypothetical example: a merchant sells spare parts whose compatibility customers often need to confirm. A reminder offering access to a knowledgeable contact may be more useful than an immediate discount. Everyday consumables may present a different situation. This illustrates a possible decision, not a measured customer case study.
We would use discounts only where they are commercially sustainable and appropriate to the offer. Their conditions must also be clear. Regularly rewarding every abandoned purchase may encourage customers to wait for a voucher. That is a possible behaviour to consider in evaluation, not an inevitable outcome.
Which scenarios should I test before launch?
We would test more than the appearance of an email preview. Acceptance should cover the entire journey from the store event to the next purchase:
- An eligible contact starts checkout without initially placing an order.
- The same contact purchases before the scheduled reminder.
- A purchase after the first message prevents further reminders.
- A contact without the required permission receives no marketing message.
- The cart link works on a smartphone in the correct language.
- An unavailable product or changed price is handled without a misleading promise.
For each case, we record expected and actual behaviour. Skipped recipients are not automatically a problem: recognising a completed purchase should cause the reminder to be skipped.
How can I tell whether the flow really helps?
We examine reached contacts, clicks, orders and the commercial contribution after discounts and returns. Revenue attributed by a platform is not automatically all incremental revenue. A customer might have purchased without the reminder. Open rates alone cannot answer that question either.
With enough data, a carefully designed comparison group can help. Klaviyo offers global holdout groups, among other options; these affect marketing across multiple messages and do not provide isolated proof for one flow. Source: Klaviyo holdout groups. We would choose the measurement approach for the actual question and avoid overinterpreting small samples.
How can sjmedia help with cart recovery?
Through our Klaviyo services, we would first examine store events, the audience and existing automations. We then develop a limited sequence, suitable content and documented test cases. Where data is missing or checkout problems emerge, we coordinate the required technical work with store support.
After launch, we assess both results and side effects: relevant orders alongside unsubscribes, complaints and maintenance effort. If delivery problems arise, our guide Why does my newsletter land in spam? supports further diagnosis. The objective is a helpful return to purchase, not the largest possible volume of automated messages.
Sources & further reading
Cite this article
Johann Nehrlich (sjmedia GmbH, Kuppenheim): How can I recover abandoned carts with Klaviyo?. 17 Nov 2026. https://www.sjmedia-consulting.de/en/wissen/e-commerce-strategie/klaviyo-warenkorbabbrecher-zurueckgewinnen
Author & technical review
Related to this topic.
Questions about this topic? Let’s talk about it.
I’ll listen to your situation and discuss which next steps suit your store.



