Abandoned Checkout Shopify: Set Up Native Recovery Emails

Abandoned checkout Shopify recovery is the one automated email Shopify ships natively, and most $3M–$30M merchants either never configure it past the default delay or leave it running for months after a dedicated flow tool takes over the same event — sending two unrelated recovery emails to the same shopper with no suppression between them. This piece covers the setting itself: where it lives, what it can and cannot do, how to read the report it feeds, and the exact point at which to switch it off.

What counts as an abandoned checkout, and why the report is titled that instead of “abandoned cart”?

An abandoned checkout is a Shopify record created the moment a shopper begins checkout — typically by entering an email address, or by landing on the checkout page through an express-pay button such as Shop Pay — and then leaves without completing an order. Shopify does not track the cart itself as an object with a status field; there is no “abandoned” flag on a cart. The record that exists, and the one the native email and every third-party flow tool act on, is the checkout. That is why the admin report under Orders is labelled “Abandoned checkouts,” not “abandoned carts” — the label is the more accurate description of what Shopify is actually storing.

A shopper who adds products and closes the tab without ever starting checkout leaves no record behind. Nothing in Shopify’s admin, and nothing in a connected ESP, can act on that session, because no identity was ever captured. Every recovery tool marketed as an “abandoned cart” solution — Shopify’s native email included — is mechanically an abandoned checkout tool. That distinction decides which sessions are even eligible for recovery before any setting is configured.

Where does the abandoned checkout Shopify setting actually live?

The control sits under Settings → Checkout → Abandoned checkout emails, a single toggle with one adjustable field: the delay before the email sends. There is no separate menu for “abandoned cart recovery” anywhere else in the admin — searches for that phrase inside Shopify settings return this same screen, because a checkout, not a cart, is the record Shopify actually stores and names its own interface around.

Two more controls sit in the template editor reached from the same settings page: the sender name shown in the recipient’s inbox, and the logo and accent colour applied to the email template. That is the entire configuration surface. There is no subject-line field, no body-copy editor beyond the logo and colour, and no way to add a second email to the sequence from inside Shopify’s native settings.

How do you set up the native abandoned checkout email, step by step?

Setting up the native email is five steps, in order, and skipping the order is where most of the avoidable mistakes happen — configuring a delay before confirming the event fires, or going live without a real test send.

Check the Abandoned checkouts report first

Review Orders → Abandoned checkouts to confirm the event is firing on your storefront before configuring anything downstream of it. If the report is empty over a window where you know checkouts were started, the problem sits upstream of the email setting — usually a theme or pixel issue — and no amount of delay tuning fixes that.

Turn on the toggle under Settings → Checkout → Abandoned checkout emails

Enable Abandoned checkout emails and set the send delay, the only send-timing control Shopify gives you. Pick a window of a few hours rather than the shortest available option, since sending immediately can land in a shopper’s inbox while they are still active in another tab, which reads as premature rather than helpful.

Set the sender name, logo and accent colour in the template editor

Match the sender name, logo and accent colour to your brand — the only visual customisation the native template allows. There is no subject-line field and no body-copy editor beyond these three settings.

Send yourself a real test abandonment

Start checkout, enter an email, leave without paying, and confirm the email arrives at the delay you set and renders correctly on mobile, where most abandoned checkouts are created.

Turn the native email off the same day a dedicated flow goes live

Disable the toggle under Settings → Checkout → Abandoned checkout emails at the same time a Klaviyo or Postscript flow starts covering the same event, not after — the reasoning for this step gets its own section below, because it’s the one most teams skip.

What does Shopify’s native recovery email not do?

The native email sends exactly once per abandoned checkout. It is not a sequence, and Shopify’s settings give no way to add a second or third touch — that requires a separate app or ESP flow layered on top. It has no SMS channel; if a shopper enters a phone number at checkout instead of an email, Shopify’s own documentation states the email cannot be sent at all, and there is no fallback text message from the native tool to catch that session.

The email is also silently withheld in several situations that are not visible from the Orders admin without opening each abandoned checkout individually: depleted inventory on an item in the cart, a fraud risk flag, an unsupported shipping address, or a payment-processing error during the checkout attempt. None of these produce a warning in the settings screen — the checkout simply does not receive an email, and the report still lists it as abandoned. A merchant reading only the report’s total count, without checking how many of those checkouts actually triggered a send, will overestimate how much recovery coverage the native tool is providing.

Shopify’s native recovery is also off by default for B2B checkouts. A wholesale buyer who abandons a B2B cart gets no automatic follow-up unless a merchant enables that separately or routes those checkout events into an ESP as their own flow.

What’s the step most teams get wrong?

The step that causes the most avoidable damage is not the delay setting — it’s what happens after a dedicated flow goes live. A merchant connects Klaviyo, builds a multi-step abandoned checkout flow with real send logic, and treats the project as finished. The native Shopify email, still switched on under Settings → Checkout, keeps firing on the exact same event Klaviyo is now also listening for.

The result is two unrelated recovery emails, from two different senders, referencing the same abandoned order, landing in the same inbox within the same window — often on the same day, since Shopify’s own delay and a flow’s first-message delay are frequently set to a similar number of hours. There is no shared suppression between Shopify’s native settings and a connected app; each system sends according to its own configuration, with no awareness of the other. A shopper who gets one recovery email reads it as a nudge. A shopper who gets two, from two different-looking senders, about the same order, reads it as a system that doesn’t know what it already sent — which is close to what actually happened.

The fix is a single step, taken at the moment the new flow activates, not weeks later: turn the native toggle off under Settings → Checkout → Abandoned checkout emails on the same day the Klaviyo or Postscript flow goes live on that trigger. There is no setting that lets the two coexist cleanly — one has to own the abandoned checkout event.

How do you read the Abandoned checkouts report correctly?

The report under Orders → Abandoned checkouts lists every checkout Shopify has recorded as started and not completed, with the shopper’s captured contact detail, cart contents and the time the checkout began. Two things are easy to misread in it.

First, the report’s total count is not the same as the number of recovery emails sent — the gap between those two numbers is the set of conditions that silently withhold a send: depleted inventory, a fraud flag, an unsupported shipping address, or a payment error, plus any checkout that started after the native email was switched off. Second, the report reflects abandoned checkouts, not abandoned carts — a shopper who added products but never reached the checkout step at all never appears here, because no record exists for that session. Comparing the report’s total against your storefront’s total add-to-cart events, where you have that data, gives a more honest read on how much of the funnel the report — and any recovery flow built on it — can actually reach.

When should recovery move from the native email to a dedicated flow tool?

Shopify’s native email answers one job: a single, branded nudge with no build cost, useful from day one on any store. It stops being enough once a merchant needs more than one message, a channel beyond email, segmentation by cart contents or customer history, or measurable incrementality against a holdout. None of that is available inside Shopify’s settings — Klaviyo, Postscript or a comparable ESP has to take over the abandoned-checkout event to provide it, guides on abandoned cart recovery and what changed with checkout extensibility cover the mechanics of that event and the checkout surface in more depth.

The handoff itself is a two-part action, not one: connect the ESP’s abandoned checkout trigger, confirm a real test abandonment reaches the new flow, and only then disable the native toggle — in that order, so there is never a gap where neither system is covering the event, and never a window where both are covering it at once.

Klaviyo’s own benchmark data, drawn from more than 183,000 brands, attributes 41% of email revenue to automated flows overall (vendor-reported) — one reason the native single email is usually a starting point rather than a finished programme once a store is doing meaningful volume.

Getting the handoff sequenced correctly — connecting the event, verifying the send, and switching off the native email on the same day rather than leaving both live — is exactly the kind of build we do inside lifecycle flows. If you want to see what a properly sequenced flow is worth against your own numbers before changing anything, the flow revenue calculator is a faster starting point than guessing at it.