Abandoned-cart automation for Shopify: the key flows

What is abandoned-cart automation on Shopify?

Shopify abandoned-cart automation follows up with eligible shoppers who add products but leave before starting checkout. Abandoned-checkout recovery covers shoppers who start checkout and leave before ordering. Choose the matching recovery template, confirm its audience and timing, then test the result before switching it on.

Choose the right Shopify recovery flow

Shopify separates three stages in its marketing automation templates:

Use the stage that matches the event you want to recover. Keep a list of the recovery flows already active in Shopify and any connected messaging app so the same shopper follows one agreed sequence.

Start with the native automation

In Shopify admin, go to Apps > Messaging > Automations. Choose Create automation, select the relevant recovery template and channel, then edit and test the message. Save it while you review the audience, workflow and existing sends; activate it after those checks.

Shopify's automation requirements specify Basic or higher, Shopify Flow for full functionality, and the relevant Marketing and Flow app permissions. Check the store's plan, installed apps and permissions before planning the build.

Start with the native template when it handles your required outcome. A connected workflow automation becomes useful when your helpdesk, CRM, review queue or another app needs to act on the same event.

The abandoned-cart recovery sequence

Give the eligible shopper a useful route back to the items they were considering. The trigger, waiting period, message and purchase check need to describe the same recovery stage.

When to fire

There is no single Shopify delay that applies to every recovery flow. Shopify's abandoned-checkout guidance says migrated settings carry over. A second abandoned-checkout automation defaults to a ten-hour wait and an audience subscribed to email marketing. The workflow can be edited in Shopify Flow.

Inspect the actual wait step, recipients and stopping conditions in your store. Choose an initial schedule, record the reason for it, then compare results over complete periods before changing it. A 30-minute, 24-hour or three-message sequence is a test proposal, not a universal default.

Shopify's Wait action guidance explains how waiting runs use refreshed store data when they resume. Put the purchase and eligibility checks after the wait, close to the send. Review active waiting runs before editing a live workflow.

Email plus SMS

Email can carry product detail and a return link. SMS can be a separate, approved touch for eligible recipients. Shopify documents both channel choices for recovery templates; confirm the channel is available and configured in your store. Keep the channel-specific audience rules and message costs in the plan. Coordinate Shopify and third-party sends before activating a second channel.

Make it conditional on cart value

If cart value changes the help or incentive you can offer, test separate branches. For example, compare the margin and support needed for a £15 basket with a £400 basket:

• Low-value carts: a simple reminder, no discount. Protect your margin.
• Mid-value carts: reminder plus reassurance (reviews, delivery times, an easy returns line).
• High-value carts: a personal touch. Offer help, answer likely objections, and consider routing to a person or an AI chat agent that can respond to questions there and then.

Treat those branches as workflow design choices to configure and test. If a shopper progresses from cart to checkout, check which recovery flow now owns the follow-up.

Test the send and the stopping rules

Use controlled shopper details and an inbox your team owns. This is a proposed acceptance checklist, not a claim that each rule is already configured:

• The intended browse, cart or checkout event starts the correct flow.
• The recipient meets the chosen channel's eligibility rules.
• The message contains the intended products and a working return route.
• A completed purchase during the waiting period stops the planned reminder.
• A shopper moving to a later stage follows the agreed handover rule.
• Repeated events and another active messaging app produce the agreed number of sends.
• Unavailable products and failed delivery follow the named review route.

Keep the run IDs and expected results. If the outcome differs, use the activity details to trace the trigger, conditions and send before changing the schedule.

Other flows to consider

The following are additional workflows to scope around your store. Give each its own trigger, eligible audience and message checks.

Welcome flow

A subscriber welcome flow starts when someone signs up for marketing. Introduce the brand, set expectations on delivery and returns, and point to relevant products. Keep a purchase-triggered message in the post-purchase flow so the two events have distinct roles.

Browse-abandonment flow

A browse-recovery flow starts from product viewing before the shopper adds anything to the cart. Repeated views are a possible condition to design, rather than a requirement of Shopify's template. Test a short message that helps the eligible recipient return to the product.

Post-purchase review and UGC flow

For a review workflow, agree a delay after confirmed delivery that gives the customer time to use the product. Invite a review or a photo, and record which material is approved for your intended use. Check how delayed, returned and cancelled orders leave the sequence.

90-day win-back flow

Fires when a customer hasn't ordered in the window you define. Treat 90 days as a test setting to compare with your store's reorder cycle. Remind eligible recipients what they bought, show what's new, and measure orders and margin against the cost of sending.

Connecting your store, helpdesk and CRM

For the operational process after an order is returned, inspect our worked returns automation example. Its downloadable fictional cases show return approval, warehouse receipt, refund authorisation and reconciliation, including an exception held for review.

Flows are only as good as the data behind them. The parts that need to talk to each other:

• Your Shopify store: the source of orders, carts, browsing and customer records.
• Your email and SMS platform: where the messages are built and sent.
• Your helpdesk: so every reply to a recovery email reaches your support team.
• Your CRM or customer list: one clean view of each customer, coordinating the timing and content across flows.

The hard part is rarely any single tool. It's mapping the triggers, the branching and the timing to your store without customers falling through gaps. That's the sort of build we handle as workflow automation, and it's a core part of what we do for e-commerce businesses.

Once the flows are live, track recovered revenue, open and click rates, and repeat-order rate. A scheduled reporting workflow gathers the approved fields and delivers the recurring performance summary. When you need governed analysis or a decision dashboard, Turing BI owns that layer.

Read the recovery measure alongside the run details. Shopify's checkout recovery guidance says a checkout can be counted as recovered after an email even when the shopper completes it independently. Reported recovery alone does not establish incremental sales caused by the message. Review send costs, discounts and margin before expanding the sequence.

Where to start

Start with the recovery stage you can identify and test, then add other flows as the source data and audience rules allow. To see the current state of all five flows at a glance, work through the e-commerce flows audit kit.

Tell us what you want to automate and we'll design the flows around your Shopify setup and existing tools, then return a free plan with a fixed quote to review. For a quick read on your strongest opportunities, take the Automation Scorecard.