Abandoned Checkout Reminders: Which Carts Should Your Shop Follow Up?

A checkout reminder should refer to a real unfinished purchase journey, not treat every product view as an order waiting to be collected. Before enabling automated follow-up, agree which carts qualify, whether you know who owns them and when the message should no longer be sent.

This is a commissioning guide for checkout follow-up, not a promise of recovered sales or legal permission to email. A wishlist is an explicit saved selection; an abandoned checkout is inferred from an incomplete journey. Keep those populations separate.

Decide what counts as unfinished

In a fictional homewares shop, one visitor adds a mug and leaves without entering contact details. Another enters an email address but stops before payment. A third completes the purchase on a different device. These are not three interchangeable reminder opportunities.

Odoo 19's order-handling documentation describes an abandoned cart as products added without completing checkout, including leaving the site before completion. Its reminders require contact details entered during checkout or a logged-in customer adding items. Without those details, the quotation remains without follow-up. That documents one product's identification boundary, not a way to identify every anonymous visitor.

For your brief, specify which checkout state enters the candidate list. Keep incomplete checkout distinct from an unresolved payment that needs investigation. A message inviting another purchase can be inappropriate while staff are still establishing whether payment succeeded.

Set a deliberate activation boundary

Odoo documents a configurable delay and an editable reminder template. It also explicitly says reminders apply only to carts created after the feature is enabled; existing abandoned carts are unaffected.

Ask what activation means in your chosen system. Do not assume switching on a feature should contact every historical shopper. Agree an effective start, test cohort and a way to stop pending reminders. Select timing from your actual fulfilment and support process, not an invented universal best-performing interval.

These are proposed operating controls. The source does not establish your shop's lawful basis, delivery success or cancellation semantics. Have privacy and marketing requirements checked for the intended audience before sending anything.

Recheck the situation before the message leaves

Require a demonstration of a purchase completed after the cart becomes eligible but before the reminder is dispatched. Decide how that purchase is associated with the pending reminder. Do not rely solely on an old browser screen or a previously exported candidate list.

Also define what happens when staff cancel a cart, the shopper changes contact details, or the same customer has several unfinished carts. Prefer one understandable invitation over conflicting messages about overlapping selections. These are acceptance requirements to implement and test, not verified Odoo behaviour.

A reminder must not imply that goods are reserved or that an old discount remains valid unless those promises genuinely apply. If a return link opens the checkout, show the current offer and explain changed or unavailable items before asking for commitment. Keep access through the link within your agreed privacy model.

Test outcomes, not just a successful email preview

Use harmless test identities and cover an anonymous cart, an identified cart, an older pre-activation cart, a completed purchase awaiting reminder dispatch and a cancelled candidate. Include an unavailable item and a changed total on return.

Put the expected recipient, send-or-suppress result and destination in the acceptance criteria. A sent message is not a completed order. If you later measure purchases after reminders, define the attribution window and do not present association as proof that the message caused the sale.

Bring these examples to a shop-development discussion. The useful feature is controlled, relevant follow-up with an honest continuation path, not simply an automated email switch.