How To Build An Abandoned Cart Automation

An abandoned cart automation sends a timely reminder after someone adds products to a basket or begins checkout, provides an email address, then leaves without completing the order. It sounds simple: wait, send a message, recover a sale. The dependable version is more disciplined.

It needs a clear definition of abandonment, reliable hand-offs between your shop and email platform, a lawful and customer-friendly contact rule, and a final purchase check immediately before every send. It also needs to know when not to send. A reminder arriving after an order confirmation, or continuing after an unsubscribe, is more than an awkward customer experience: it creates complaints and can damage future inbox placement.

This guide focuses on email. SMS and push notifications can sit alongside the same journey, but they need their own consent, channel limits and suppression logic.

Start by defining the event you mean by “abandoned cart”

“Abandoned cart” is often used for several different behaviours. They should not automatically receive the same treatment.

This distinction matters operationally and legally. Shopify, for example, describes an abandoned checkout as a checkout where contact information has been added but the purchase has not been completed; its current abandonment model also separates browsing, cart and checkout journeys. Shopify’s abandoned checkout documentation is a useful illustration of why a platform event is not simply “someone left the site”.

Write down the trigger in a sentence that engineering, CRM and customer service all understand. For example: “Enter a customer when they have supplied an email address, have at least one purchasable item in a cart, have not placed an order since that cart was updated, are eligible for email marketing, and have had no recovery email for the same cart in the past 24 hours.” The exact rules will vary, but ambiguity will otherwise surface as duplicate sends.

Decide who may receive the email before designing the creative

A cart reminder can feel operational, but it may still be direct marketing. Do not label it “transactional” merely because it refers to a basket. If the message promotes products, includes an offer, or encourages a sale, treat the classification carefully.

For UK senders, the relevant rules include PECR and UK data protection law. The ICO says marketing email to individuals generally needs consent, unless the products-and-services “soft opt-in” applies. That exception is limited: you must have obtained the details directly during a sale or negotiation for a sale, market your own similar products or services, give a clear opt-out when collecting the details, and include an opt-out in each subsequent message. The ICO specifically notes that adding an item to an online basket can form part of a negotiation for a sale, whereas mere browsing does not. See the ICO’s guidance on complying with electronic mail marketing rules for the full conditions.

For a practical build, put eligibility upstream of the workflow:

• Do not enrol people who have unsubscribed, objected to marketing, hard-bounced or complained.
• Do not use bought, scraped or partner-supplied addresses for cart recovery.
• Store the permission state and the source of the email address alongside the cart event.
• Exclude employees, test accounts, fraud holds and orders awaiting manual review where appropriate.
• Apply the law and consent requirements for the recipient’s location, not only the country where your business is based.

If the interpretation is uncertain, ask privacy counsel to review the collection wording, the eligibility logic and the email itself. The technical workflow should enforce the decision consistently; it should not leave a difficult legal judgement to a campaign manager at send time.

Build the automation around state changes, not a simple delay

The most common weak design is: cart created → wait two hours → send email. A robust automation uses a series of checks because the customer’s state can change during the wait.

Capture a reliable enrolment record

When the qualifying event occurs, create one recovery record containing a stable cart or checkout ID, customer or visitor ID where available, email address, timestamp, currency, item IDs and quantities, cart value, consent status, market or storefront, and a version of the checkout-resume URL. Avoid using the email address as the only identifier: one person may create several carts, and shared email addresses do exist.

Use an idempotency key, meaning a unique reference that lets your systems recognise the same event if it is delivered twice. Webhooks and integrations can retry. Without this protection, a duplicated “checkout abandoned” event can create two journeys.

Wait, then qualify again

After the chosen delay, query the source of truth for the latest status. The person should only proceed if the cart still qualifies. At minimum, check:

• no order has been placed by that customer or for that checkout since enrolment;
• the email address remains eligible and has not unsubscribed during the wait;
• the cart still contains sellable items;
• the recovery link is valid and points to the correct market, currency and session where possible; and
• the contact has not exceeded your wider contact-pressure limit.

Repeat this purchase and suppression check immediately before every subsequent message, not just before the first. Commerce systems can update asynchronously; a customer may buy on another device, through an app or after contacting support. A cancellation rule should remove the person as soon as a qualifying order is detected, rather than waiting for the next workflow step.

Use a sensible recovery window

There is no universal best delay. The right timing depends on the buying cycle, delivery proposition and value of the product. A refill purchase may need a short reminder; high-consideration furniture may not. Begin with one message after the customer has had a reasonable chance to resolve an interruption, then add a second only if it offers a distinct reason to return.

A modest starting design might send an initial reminder after a few hours and, if there is still no purchase, one follow-up the next day or two. That is a starting hypothesis, not a law. Test timing by product category and market, while holding volume and eligibility stable enough to interpret the result.

Set a clear expiry. Once the basket is stale, products have changed or the person has received enough contact from you, end the journey rather than turning a cart into a long promotional sequence.

Make the email useful before making it persuasive

The first message rarely needs complicated copy. It should answer the customer’s likely question: “Can I get back to the items I was considering?”

Include the items in the current basket, accurate price and currency, a prominent return-to-cart or resume-checkout button, and a recognisable sender name. If availability or price has changed, say so accurately rather than recreating a historic basket that can no longer be bought. Avoid an invented urgency claim such as “selling fast” unless it is supported by live, meaningful inventory data and remains true when the message is delivered.

Discounts deserve restraint. Sending an offer in every first reminder can train customers to abandon intentionally and may erode margin. Where an incentive is commercially justified, separate the test question from the workflow question: compare an offer against a no-offer control for eligible audiences, account for gross margin and repeat purchasing, and ensure the discount is not shown to people who already converted.

Do not overload a recovery email with unrelated recommendations, a newsletter module, social competitions and several offers. They blur the purpose of the message, make marketing classification clearer, and create more ways for a customer to leave without returning to checkout.

Control frequency across the whole programme

Cart reminders do not arrive in isolation. A customer might qualify for a welcome series, price-drop alert, weekly promotion and cart recovery in the same 24 hours. Each individual flow can look reasonable while the combined experience feels excessive.

Build a central contact-pressure rule that considers recent marketing messages across automations and campaigns. It should define which messages can override others and why. A genuinely operational service message may have priority; a second promotional cart reminder usually should not. Record the reason whenever an override is used so the rule can be audited and improved.

Frequency control is also a deliverability safeguard. Google advises senders to make subscription easy, confirm addresses and consider removing people who do not engage. Its sender guidance treats marketing and subscribed messages as messages that need a straightforward route to unsubscribe. Google’s email sender guidelines also require bulk senders to authenticate mail and support one-click unsubscribe for marketing and subscribed messages.

Get the sending foundations right

An abandoned-cart flow is usually high intent, but it is still marketing email when it invites a purchase. It should therefore be sent through an authenticated, well-governed marketing stream rather than being disguised as a receipt or password reset.

At a minimum, authenticate the sending domain with SPF and DKIM, publish DMARC, use an aligned visible From domain, and ensure the automation platform can generate the required headers. For senders at Gmail’s bulk threshold, Google specifies SPF, DKIM, DMARC, TLS, valid DNS and a spam rate below 0.3% in Postmaster Tools, alongside one-click unsubscribe for marketing messages. Yahoo similarly requires a List-Unsubscribe header for promotional or marketing mail subject to its sender requirements. Yahoo’s sender FAQ explains that a body-link alone does not meet its one-click unsubscribe expectation.

Use both: a clearly visible unsubscribe link in the email body and standards-based one-click unsubscribe headers where applicable. Suppress the address promptly and permanently from the relevant marketing list when the person opts out. Google recommends honouring one-click unsubscribe requests within 48 hours; its newer subscription guidance also calls for separate sending addresses for subscription and non-subscription mail. Google’s subscription message guidance is worth reviewing with your email service provider.

When a brand has already suffered elevated complaints, spam-folder placement or authentication failures, adding another automation can deepen the problem. In that situation, an independent deliverability review of authentication, suppression handling, sending patterns and mailbox-provider signals should come before scaling recovery volume. This is where a managed service such as Email Foundry can be relevant: the goal is to repair the sending foundation, not to work around provider protections.

Test the workflow as a customer and as a system

Before launch, create controlled test carts using addresses at more than one mailbox provider. Test each branch: consented and non-consented addresses, purchase before send, purchase after first email, unsubscribe during the delay, item out of stock, discount ineligible, payment failure, multiple carts and repeated event delivery.

Inspect the received message, not merely the workflow canvas. Check From and Reply-To addresses, authentication results, unsubscribe behaviour, product image and price rendering, link destination, mobile layout, tracking parameters and whether the link still works after a reasonable delay. Confirm that the purchase event stops the flow even when the order originated outside the email platform.

Keep an operational log: enrolment time, event ID, eligibility decision, suppression reason, message ID, delivery outcome, click, order linkage and cancellation time. This makes duplicate or post-purchase sends diagnosable rather than anecdotal.

Measure recovery without overstating it

Revenue attributed to a recovery email is not automatically revenue caused by it. Some people would have returned and bought anyway. Report the basics—eligible carts, sends, deliveries, clicks, orders, revenue, unsubscribes, complaints and conversion after each message—but interpret them alongside incrementality.

The most useful method is a properly designed holdout: randomly withhold the automation from a small, eligible group for a limited period, subject to commercial and privacy approval, then compare order rates over the same attribution window. This estimates the additional orders created by the flow rather than simply crediting it with every order that happened after an email.

Also segment results. A flow that performs well for returning customers with an active marketing relationship may perform poorly for newly captured checkout addresses. Watch complaints and unsubscribes by mailbox provider, message number, delay, market and source. A rise in negative signals is a reason to reduce frequency or rethink eligibility, even if short-term attributed revenue appears healthy.

A strong abandoned cart automation is therefore less about chasing a perfect subject line and more about reliable customer-state management. Contact only people you are entitled to contact, verify that the basket is still relevant at every send, stop immediately when circumstances change, and let customer response—not only attributed revenue—determine how far the sequence goes.