Skip to content
mailprompt
Start free trial
GuideUpdated

Abandoned checkout emails: a practical flow guide

An abandoned checkout flow starts when a customer begins checkout but does not complete it. A useful flow sends a short, specific reminder, makes the saved cart easy to reopen, stops when the customer orders and avoids discounting by default. Review the audience and exit rules before approval, because a recovery email sent to the wrong person is worse than no email.

Key facts

  • Shopify records a checkout that was started but not completed as an abandoned checkout, which the store can review. Source
  • Shopify's help center documents automated abandoned checkout email as a store feature with its own settings. Source
  • Klaviyo describes an abandoned cart flow as a message or sequence of messages triggered by a cart or checkout event. Source
  • Mailchimp's help center documents an abandoned cart email as an automated message tied to a cart event. Source

Build an abandoned checkout email flow

  1. Confirm the trigger. Decide which event starts the flow. Shopify records an abandoned checkout when a customer begins checkout and does not complete it. Confirm that the event exists in your store and that the flow audience is the group you mean to contact.
  2. Set the audience and consent rule. Include only profiles you have a lawful basis to email. The flow should respect unsubscribe state, suppression and the account's marketing consent rules. If the store cannot prove consent for a profile, the flow should not send to it.
  3. Choose the first delay. Start with a short delay that gives the customer time to finish the purchase without making the message feel late. The right delay depends on the store's sales cycle, so treat the first value as a hypothesis and change one variable at a time.
  4. Write a specific first email. Show the product or products that were left behind, the cart total and a clear link back to the saved cart. Avoid a generic reminder that could describe any store. The subject line and the first sentence should name the thing the customer was considering.
  5. Add an exit condition. Stop the flow when the customer places an order, unsubscribes or enters a segment that should not receive recovery mail. An exit condition is not optional: a second reminder after a completed purchase is a visible mistake.
  6. Review, approve and test. Send a test to a mailbox you control, check the rendered email and the recovery link, then approve the draft through the normal review step. After approval, watch the first sends before you increase volume.

What this guide covers

This guide is part of the email flows hub. It covers the abandoned checkout flow from trigger to approval. It does not promise a recovery rate, because the result depends on the store, the offer and the list. It does describe the decisions that make a flow useful instead of annoying.

Start with the event, not the template

An abandoned checkout flow begins with an event. Shopify records a checkout that was started but not completed as an abandoned checkout. The store can review those checkouts and, with the right settings, send a follow-up.

The event is not the same as “a customer looked at a product”. A product view is a weaker signal, and a flow built on it will contact people who were browsing rather than buying. A checkout event is stronger because the customer took a deliberate step toward payment.

Before you write a subject line, confirm three things: the event exists in your store, the flow audience is the group you mean to contact and the profile has a lawful basis to receive marketing. If any of those is unclear, the flow is not ready for copywriting.

An abandoned checkout is a behavioural signal, not a consent record. A customer can enter an email address at checkout and still not have agreed to marketing. The flow has to respect the consent state the store records, the unsubscribe list and the account's suppression rules.

This is where a generic automation tool can get a store into trouble. It is easy to build a flow that looks at the checkout event and ignores the consent field. It is harder to explain to a customer why they received a marketing email after they declined marketing at checkout.

Mailprompt's send gate checks consent and suppression before a marketing message leaves the account. The flow draft should still name the audience it assumes, so the approver can see whether the assumption matches the store's policy. A flow that is technically blocked at send time is better than one that sends, but it is better still to fix the audience before approval.

Timing is a hypothesis

The first delay is one of the most overthought settings in email marketing. A short delay can catch a customer who was interrupted; a longer delay can catch a customer who was comparing options. Both can be right for different stores.

The practical approach is to start with one delay, change it only after you have enough sends to compare, and avoid changing the copy at the same time. If you change the delay and the subject line together, you cannot tell which one moved the result.

A second message is a separate decision. It should have a reason to exist: a reminder about a low-stock item, a answer to a common objection or a final note before the cart expires. A second message that repeats the first with a different adjective adds volume without adding information.

Write the first email around the cart

The first email has one job: help the customer finish the purchase they started. It should show the product, the cart total and a link back to the saved cart. It should not read like a newsletter with a cart link buried in the footer.

The subject line should name the thing the customer was considering. “Still thinking about the linen shirt?” is more useful than “Don't forget your cart”. The first sentence should continue that thought, not restart the sales pitch. If the store has a reason the customer paused, such as a shipping threshold or a size question, address it.

A recovery link is part of the copy. It should return the customer to a cart that still has the items, not to an empty cart or a generic home page. Test the link with a real cart before you approve the flow. A broken recovery link turns a helpful reminder into a support ticket.

Discounts are a last resort

A discount can rescue a checkout, and it can also teach customers to abandon on purpose. The first version of a flow should usually run without one. Measure the recovery rate and the margin, then decide whether a discount adds enough orders to pay for the margin it gives away.

If you do use a discount, make it specific to the flow and give it an expiry. A code that works forever and on every product is a permanent price cut disguised as a recovery tactic. The approval view should show the coupon rule, not just the code in the copy.

Exits and frequency

The exit condition is the part of the flow that protects the customer experience. A customer who completes the order should leave the flow immediately. A customer who unsubscribes should leave every marketing flow. A customer who enters a service or wholesale segment may need a different message or no message at all.

Frequency matters too. A recovery flow that sends three messages in a day is not more persistent than one that sends a single good message; it is more likely to be marked as spam. The account's frequency cap and quiet hours are there to stop that, but the flow design should not rely on the cap to fix a bad cadence.

Measure the flow, not the myth

The useful measures are sends, clicks, recovered orders and the revenue attributed to the flow. Opens are a weak signal for the reasons described on the revenue per email page. A flow that looks good on opens and weak on clicks is not necessarily working.

Compare the flow with a control period or a holdout when you can. A seasonal change in store traffic can look like a flow improvement if you only look at the weeks after launch. The comparison does not have to be statistically perfect to be useful; it has to be honest about what changed.

Approve before you scale

The last step is the approval. Review the trigger, the audience, the wait, the rendered email, the recovery link and the exit condition. Send a test to a mailbox you control. Then approve the draft and watch the first sends before you increase volume.

The AI flows by chat page explains how a draft is produced, and the approvals page explains the gate. If the flow depends on a store integration that is not available in your account, do not approve a mock-up. Fix the integration first.

Frequently asked questions

How many abandoned checkout emails should a flow send?

Start with one useful reminder and add a second only when the first has earned it. More messages increase the chance of a recovery and the chance of an unsubscribe; the right number depends on the store's sales cycle and the value of the cart. A flow with two well-written messages is easier to review and measure than a long sequence nobody has read end to end.

Should the first email include a discount?

Not by default. A discount trains customers to abandon checkout on purpose and gives away margin on orders that might have completed anyway. Start without one, measure the recovery rate and the margin, and add a discount only when the data shows that the flow needs it. If you do add one, make the code specific to the flow and give it an expiry.

What is the difference between an abandoned cart and an abandoned checkout?

The labels vary by platform. Shopify's help center uses abandoned checkout for a checkout that was started but not completed. Some tools call the same event an abandoned cart and use a separate event for a product added to the cart. The important thing is to know which event your store emits and what the customer had done when it fired.

Can I email someone who did not subscribe to marketing?

Consent rules vary by jurisdiction and by the relationship the store has with the customer. A checkout email address is not automatically permission to send marketing. Check the applicable rules, use the consent state the store records and let the send gate block profiles that should not receive marketing. When in doubt, ask before you send.

When should the flow stop?

The flow should stop as soon as the customer orders, unsubscribes or enters a segment that should be excluded. A recovery flow that keeps sending after a purchase is one of the most visible automation mistakes a store can make. Test the exit condition with a real order before you approve the flow for live traffic.

Sources