What should trigger your recovery flow?

For a first version, I recommend starting with people who began checkout. Checkout means the steps where a shopper supplies contact, delivery, and payment details. Write down the precise starting event before choosing a template.

Klaviyo distinguishes Added to Cart from Started Checkout. The first targets an abandoned shopping cart; the second targets an unfinished checkout. Its documentation uses abandoned cart as an umbrella term for both. Klaviyo trigger definitions.

A trigger is simply the recorded action that starts your automation. A flow is the sequence of waiting, checking, and messaging that follows. Give your flow a name that identifies its trigger, such as “Started checkout reminder”.

Shopify's legacy documentation defines an abandoned checkout as remaining incomplete for more than ten minutes after the shopper supplies their email. That is a classification rule, not a recommendation to email after ten minutes. Shopify's legacy definition.

Write an eligibility rule

Use this working rule: “Send only when the shopper has an eligible contact address, has not purchased, and meets the flow's sending conditions.” Ask whoever manages the store to demonstrate each condition with a test record.

Sketch the shopper's next steps using a customer journey map. Include returning to checkout, asking for help, purchasing, and opting out. Assign a clear outcome to each route.

How do you build the first automation?

Start by checking your existing store and email tools. Choose one system to send recovery messages. Before buying another subscription, ask for a demonstration using your own product and checkout.

A practical Mailchimp setup path

Mailchimp documents the following setup. Confirm that your store connection supports abandoned cart emails before following it. Mailchimp setup instructions.

1. Open Automations and choose Build from scratch.
2. Name the flow and select its audience.
3. Choose Shopping Activity, then Abandons cart.
4. Select the connected store and relevant products.
5. Set the abandoned cart wait time and entry filters.
6. Add Send email and choose an abandoned cart template.

Before activation, inspect the product content and return button with your own test checkout. Add a purchase check before any later message. Keep a written note of who owns the flow and who handles customer replies.

Klaviyo advises disabling the store's default abandoned cart messages when using its flow to avoid duplicate reminders. Plan that handover as part of your launch checklist. Klaviyo duplication guidance.

If changing providers is necessary, use a platform migration checklist. Test the replacement before retiring the existing setup, and confirm which system owns each active message.

When should the first reminder arrive?

Choose a delay of a few hours as an initial experiment, rather than treating any timing as universally best. Record when the checkout event reaches your email tool and when a completed order becomes visible there.

Klaviyo warns that some integrations do not sync checkout events immediately. Its guidance is to check the connection's sync frequency before setting a short delay. Klaviyo timing guidance.

Hypothetical stationery shop example

Imagine a small stationery shop testing one reminder three hours after checkout begins. If the shopper purchases during that wait, the flow should stop. Three hours is an illustrative test setting, not a reported performance benchmark.

Consider a second email the following day only if it has a useful purpose, such as offering help with delivery questions. Check purchase status again immediately before sending. Review local sending hours when customers live in different time zones.

• Use one clearly defined event to start the clock.
• Record the chosen delay in the flow name or notes.
• Set a rule for repeated entries by the same customer.
• Change timing separately from copy when evaluating a test.

What should the email say, and does it need a discount?

Make the first message a useful reminder with one obvious next step. I would test it without a discount first. Show the selected product, offer a return button, and give the customer a way to ask for help.

Example copy to adapt

Replace the placeholders with the platform's customer and product fields. Preview the version with no first name. Send replies to a monitored inbox, and check the button on a phone.

Do not promise reserved stock unless you actually reserve it. Avoid invented deadlines or claims that a product is nearly sold out. Verify every delivery promise and product detail against the current store information.

Make any incentive a separate decision

If you test a coupon, define eligible products, usage conditions, and the maximum discount you can afford. Test the code in a real checkout before adding it to the message. Compare money left after costs, not just order totals.

For a hypothetical shop with thin margins, I would try answering delivery questions before offering a blanket discount. For another store, a limited incentive may be worth testing. Write the reason for the offer before building it.

Use email segmentation, meaning dividing contacts into useful groups, to plan different treatment where necessary. Keep the initial groups simple enough for your team to explain and check.

Should you add SMS cart recovery?

Add SMS only after the email flow passes its tests and you have a clear reason to try another channel. The sources here do not establish that SMS will outperform email for your store. Evaluate it using orders, cost, and opt-outs.

Mailchimp requires an approved SMS Marketing program for its SMS functionality. It also distinguishes the initial abandoned cart message from additional sending steps, which only subscribed contacts receive. Mailchimp eligibility conditions.

Before enabling texts, check supported countries, your provider's permission requirements, and the opt-out process. Do not treat possession of a phone number as sufficient authorization. Use this SMS launch guide to organize the preparation.

For an initial experiment, I would replace a planned follow-up with SMS for eligible contacts rather than send both together. Keep the text focused on returning to checkout. Include the store name and the required opt-out method.

How do you test the flow and judge results?

Test the situations where a message should stop as carefully as the successful delivery. Use your own contact details and keep a record of expected versus actual behavior.

• Abandon an eligible checkout and confirm the correct product appears.
• Purchase during the delay and confirm the reminder stops.
• Withdraw sending eligibility and check subsequent messages are blocked.
• Repeat the starting event and inspect duplicate handling.
• Open the return button on a phone and verify the checkout.
• Check what happens when the selected product becomes unavailable.

Shopify's legacy documentation lists completed purchases, missing email addresses, unavailable products, and other conditions that prevent sending. Check the recorded reason before assuming the automation is broken. Shopify sending exceptions.

Use a small weekly report

Record eligible checkouts, messages sent, return clicks, completed orders, opt-outs, and complaints. Add incentive and messaging costs. Use the same reporting period and definitions each week.

Shopify notes that a checkout can be marked recovered when someone completes the order independently after the email. Therefore, do not describe every recovered order as an additional sale caused by the message. Shopify recovery status explanation.

Where your tooling and traffic allow, consider a randomly selected comparison group that receives no reminder. Compare completed orders over the same period. Treat results from only a handful of checkouts as preliminary.

Keep this flow separate from a lost customer win-back campaign. For this project, focus the rule on the unfinished purchase and document when the person exits.

This week, connect the store, confirm the event, write one email, and complete the stop-condition tests. Schedule a review with the person responsible. Add another message only when you can explain what useful job it will do.