Recover abandoned carts with email and SMS in WooCommerce

How To Implement

• 1 Choose the right WooCommerce route first

  If you need cart recovery, product/browse abandonment and SMS with the least custom work, Klaviyo and Omnisend are the strongest off-the-shelf options from the sources reviewed. Klaviyo’s WooCommerce extension syncs checkout starts and viewed products in real time and is HPOS-compatible; Omnisend’s WooCommerce route supports abandoned cart, abandoned checkout, product abandonment and browse abandonment; FunnelKit, AutomateWoo and Retainful are strongest when you want more of the automation to live inside WordPress.

• 2 Check whether you are on classic checkout or Cart and Checkout Blocks before touching consent fields or capture

  On the Checkout Block, older extensibility like woocommerce_checkout_fields does not apply in the same way; WooCommerce’s own developer docs say the previous pattern is intentionally not the path for the new block checkout. If you need to add or move extra consent fields on Blocks, use the newer block extensibility path rather than assuming classic hooks will work.

• 3 If you use Klaviyo, install and connect it from the WooCommerce side, then enable checkout consent capture

  The current path is WooCommerce → Extensions → search Klaviyo for WooCommerce → activate the plugin → Marketing → Klaviyo → Connect Account. In Klaviyo’s WooCommerce integration settings, you can enable the checkout email consent checkbox, select the list to add subscribers to, and add mobile consent options such as Text Message for checkout capture. Klaviyo says consent is sent after the shopper places the order, and its WooCommerce extension is HPOS-compatible.

• 4 Build the abandoned-cart flow in Klaviyo with the right trigger and safety filter

  Klaviyo’s standard WooCommerce abandoned-cart flow uses Started Checkout by default, not just Added to Cart. The core safety filter is Placed Order zero times since starting this flow, so buyers who return and convert are skipped automatically. Klaviyo’s pre-built flow includes a four-hour first delay by default, but timing can be changed by category and buying cycle.

• 5 Use actual rebuild or recovery links, not generic store links

  In Klaviyo WooCommerce, the cart rebuild URL is {{ organization.url|trim_slash }}/cart?wck_rebuild_cart={{ event.extra.CartRebuildKey }}. In Omnisend abandoned-cart emails, the recommended pattern is to show the abandoned items and add a separate button linked to “, because the product block’s default button goes to the product page rather than the full saved cart.

• 6 Add SMS as a branch, not a duplicate blast

  In Klaviyo, add a conditional split after the first delay so only contacts who can receive SMS go down the SMS path, and keep quiet hours on. In its SMS-specific guidance, Klaviyo recommends putting the split after the first delay and notes that the delay should still be within 48 hours of the trigger. In FunnelKit, the current documented route is Cart Abandoned event → delay → Send SMS via Twilio or Bulkgate, using merge tags for first name and the recovery link.

• 7 If you use Omnisend, start with the pre-built WooCommerce workflows and separate the funnel stages clearly

  The documented path is Automation → Create workflow → choose Cart Abandonment for add-to-cart without checkout, Abandoned Checkout for checkout starters, Product Abandonment for viewed product pages without add-to-cart, and Browse Abandonment for broader page views such as homepage, category or sale URLs. Omnisend explicitly recommends using exit conditions and Skip Contacts to stop people receiving multiple abandonment flows at once.

• 8 Use Product Abandonment, not generic Browse Abandonment, when you want viewed-product content in Omnisend

  Omnisend’s current docs say Browse Abandonment does not capture product names, images, prices or a page-specific return URL. Product Abandonment does capture the specific product viewed, can display it in the message, and can link SMS back to that product. For a WooCommerce store, that is usually the better “browse-abandonment” layer if the real goal is reminding people about specific products they inspected.

• 9 Set frequency caps before going live

  Omnisend’s Abandoned Cart and Abandoned Checkout workflows are frequency-limited to once every 24 hours by default, and its Browse and Product Abandonment guidance recommends a 10–15 day re-entry restriction plus Skip Contacts. That avoids over-messaging frequent visitors and makes later reporting cleaner. Measurement note: frequency settings also block retests, so record your test settings and restore them before launch.

• 10 If you prefer WordPress-native automation, build inside AutomateWoo, FunnelKit or Retainful with realistic expectations

  In AutomateWoo, carts become abandoned after 15 minutes of inactivity by default or whatever you set at AutomateWoo → Settings → Carts, and you can view them at AutomateWoo → Carts. Guest email capture is checkout-first by default, but you can enable capture JavaScript on all pages and tag extra fields with automatewoo-capture-guest-email if you want earlier email capture. On block checkout, AutomateWoo currently captures billing email and name, while classic checkout can capture the fuller billing detail. In FunnelKit Automations, enable cart tracking in FunnelKit Automations → Settings → Cart. Its documented settings include Enable Cart Tracking, Wait Period, Cool-off period and Lost Cart, plus a GDPR notice option to inform shoppers their email and cart data will be saved for abandonment reminders. Build the flow at Automations → Create Automation, starting with the Cart Abandoned event. In Retainful, the official docs reviewed focus on email-based abandoned-cart sequences. You can enable explicit marketing consent at WooCommerce → Retainful → Settings, control abandoned-cart timing in Retainful’s general settings, and build a first reminder, second incentive email and final urgency email inside the automation builder.

• 11 Sequence the messages so the first one reminds, the later ones persuade

  Klaviyo’s general abandoned-cart guidance supports a delay before the first message; Retainful’s documented sequence is particularly clear for WooCommerce-style execution: first reminder within an hour, second reminder about 24 hours later with the coupon, and a final urgency email around 48 hours after that. That is a sensible default for a store without heavy in-house testing capability, and it aligns with the wider “don’t train people to abandon for a coupon” principle.

• 12 Respect UK consent and tracking rules even if the app lets you send more aggressively

  Some platforms technically allow abandoned-cart messages to non-subscribed contacts or present these flows as “transactional”. For a UK WooCommerce store, do not assume the vendor setting settles the legal question. The ICO says marketing emails and texts to individuals need specific consent unless the soft opt-in applies, and PECR also applies to the cookies, scripts, tags and tracking pixels used for behavioural and browse-abandonment automation.

How To Measure

Pitfalls

• The biggest mistake is treating recovery flows as the fix for abandonment itself. Baymard’s current abandonment reasons still centre on cost shock, slow delivery, trust concerns, forced account creation, long checkout and site errors, so recovery messages can win back some buyers but cannot remove those frictions from the live checkout.A common myth is that browse-abandonment always means “send them the exact product they viewed”. That is only true in some stacks. In Omnisend, generic Browse Abandonment does not store product details or a page-specific return URL, while Product Abandonment does
• in Klaviyo, browse flows are based on Viewed Product for identifiable browsers and can be personalised around that event.Another frequent error is overlap: browse, product, cart and checkout flows all firing around the same journey. Omnisend explicitly warns that these flows can run simultaneously unless you use exit conditions and Skip Contacts, and Klaviyo’s browse flow guidance similarly adds filters to exclude purchase, checkout and add-to-cart cases.It is also a mistake to assume that because a platform can message non-subscribed contacts, a UK store is automatically compliant. The platform may be describing technical capability or its own message classification, but ICO guidance is what matters for a UK merchant sending marketing emails or texts to individuals.Finally, do not assume classic checkout customisations carry over to Blocks. WooCommerce says the old checkout_fields route is not how the new Checkout Block is extended, and plugins can differ materially in what they capture on block checkout. AutomateWoo, for example, currently documents a data-capture difference between classic and block checkout.

Examples

FAQs

Sources & Further Reading

• URL:
• URL:
• URL:
• URL:
• URL:
• URL: – and `https://help.klaviyo.com/hc/en-us/articles/360037957832
• URL:
• URL:
• URL:
• URL:
• URL:
• URL: – and `https://support.omnisend.com/en/articles/1636174-connect-your-woocommerce-wordpress-store-to-omnisend

About This Page

• Written By: Eliot Webb – Founder & WooCommerce CRO Consultant
• Last Reviewed: 22 Jun 2026
• Last Updated: 22 Jun 2026