The abandoned checkout timer restarts every time the shopper comes back

How Beacon Messenger times a WhatsApp abandoned checkout reminder: the delay counts from the last edit, what cancels it, and how to test it with one checkout.

Set the abandoned checkout delay to 60 minutes and the natural reading is that a reminder goes out an hour after the shopper opens checkout. It does not. It goes out an hour after the last thing the shopper did in that checkout, which can be much later, and that difference explains most of the questions we get about this automation: why a reminder arrived at 2am, why a shopper who kept coming back never got one, why the delivery log shows a message rescheduled four times. The broad case for recovering checkouts over WhatsApp is in Abandoned checkout recovery via WhatsApp; this post is only about the clock.

What Shopify tells the app, and when

Shopify does not send an abandoned checkout event. It sends checkout events: one when a checkout is created, which happens the moment a shopper reaches the checkout page with an email or phone, and one every time something about that checkout changes afterwards, such as a new address line, a changed quantity or a different shipping method. There is no event that means the shopper has given up, because Shopify cannot know that. An abandoned checkout is a checkout that has gone quiet, and quiet is something the app has to measure for itself.

Beacon Messenger measures it with a timer. On the create event, it puts a reminder in the queue with a send time of now plus your delay. On every update event, it finds that same queued reminder and moves its send time to now plus your delay again. The reminder only becomes due once the shopper has stopped touching the checkout for a full delay period. Think of it as a timer that resets whenever the shopper is in the room.

Why a reset, and not the first timestamp

The alternative, counting from the first time the shopper reached checkout, sends reminders to people who are still buying. A shopper who opens checkout at 9:00, gets interrupted, comes back at 9:50 to fix the address and is about to pay would receive a reminder at 10:00 while entering a card number. That is the message that gets screenshotted and posted as an example of pushy marketing. With the reset, the same shopper receives nothing at 10:00; if they walk away for good at 9:52, the reminder goes out at 10:52, which is the moment it should.

The cost is predictability. Because the timer follows the shopper, the send time is not something you can read off the clock, and a shopper who revisits their checkout once an evening for three days will not get a reminder until the fourth. That is almost always the behaviour you want, since a shopper who keeps returning has not abandoned anything, but it is worth knowing when someone asks why a particular customer never got a message.

What cancels the reminder outright

  • The shopper pays. Shopify sends a completed checkout and an order carrying the checkout's token, and either one deletes the queued reminder. The order confirmation automation takes over from there.
  • Shopify deletes the checkout. Checkouts that Shopify removes on its side send a delete event, and the reminder goes with them.
  • The checkout has no phone number the app can use. Shopify's checkout carries the number the shopper typed, the shipping phone and the billing phone, and the app uses the first it finds. With none of them, nothing is queued and the log records the skip; the reasons a number can be missing are in why some orders have no phone.
  • Consent is required and absent. The reminder is a marketing message, and by default the automation only sends when the shopper ticked the marketing box at checkout or the customer record is subscribed. Without it the checkout is skipped, not delayed.

A reminder that has already been sent is not sent again. If the shopper edits the checkout after receiving the message, the update event finds a sent reminder rather than a queued one and leaves it alone. One checkout, one reminder, however long it lingers.

The numbers behind the setting

Abandoned checkout delay in Beacon Messenger
SettingValueWhy
Default delay60 minutesLong enough for a shopper who is still comparing to finish; short enough to catch them in the same session.
Minimum delay10 minutesBelow this the app would be messaging people mid-checkout. The editor enforces it, and the sender applies it even if the stored value is lower.
Maximum delay7 daysAfter a week the checkout is cold and Shopify's own retention of the checkout may have run out.
Timer resets onEvery checkout updateA shopper who returns to edit is not abandoning.
Queue resolutionAbout 30 secondsDue reminders are picked up by the next queue run, so sends land within half a minute of the scheduled time.

Choosing a delay, with the reset in mind

Because the clock counts from the last edit, you can use a shorter delay than you might for a system that counts from the first visit. Thirty to sixty minutes after the shopper stops typing is a different proposition from thirty minutes after they arrived: it is a message to someone who has demonstrably left. Stores that sell quickly decided things, consumables, gifts, replacements, tend to do well in that range. Considered purchases, furniture, anything over a few hundred dollars, suit a longer gap of several hours, both because the shopper may genuinely be thinking and because a same-hour nudge on a large purchase reads as pressure.

Then think about the hour of day. A delay of 60 minutes applied to a checkout last edited at 1am sends at 2am. WhatsApp will deliver it, the phone may well buzz, and the shopper will not thank you. Nothing in the app holds the message until morning, so if a meaningful share of your checkouts happen late, either push the delay to eight or ten hours, which lands late-night checkouts in the morning and daytime checkouts in the evening, or accept the 2am sends as a cost of the shorter window. Both are defensible; sending at 2am by accident is not.

Finally, consider Shopify's own abandoned checkout email, if you have it on. Shopify's abandoned checkout recovery runs on its own schedule from the time the checkout was abandoned, and it is not aware of the WhatsApp message. Two reminders in the same hour on two channels is overkill; set the WhatsApp delay so that it lands clearly before or clearly after the email, and let the one that performs better keep the earlier slot.

Reading the delivery log

Each queued reminder appears in the delivery log as a single row whose scheduled time moves. If you watch a live checkout, you will see the time jump forward each time the shopper changes something; that is the reset at work, not a bug. A row that disappears was cancelled by a payment or deletion. A row marked skipped carries the reason, usually no phone or no consent. A row that sent shows the time it actually went, which should be within a minute of its final scheduled time. If you see a reminder scheduled days out when your delay is an hour, check that the automation's delay was saved in minutes and not mistaken for hours.

Testing the clock with one checkout

  1. Temporarily set the delay to 10 minutes, the minimum, and save.
  2. On your phone, with your own number, add something to the cart and go to checkout. Enter your number and tick the marketing box if consent is required. Do not pay.
  3. Open the delivery log on another screen and note the scheduled time, roughly ten minutes out.
  4. Wait five minutes, then go back to the checkout and change the quantity. Refresh the log: the scheduled time should have moved to ten minutes from now.
  5. Leave it. Within about ten and a half minutes the reminder arrives on your phone. Open the checkout link in it and confirm it lands on the checkout with the cart intact.
  6. Repeat once more, but pay before the timer ends. The row should vanish from the log and the order confirmation should arrive instead.
  7. Put the delay back to its real value.

That is three WhatsApp conversations and twenty-five minutes, and afterwards you know exactly what your shoppers experience. Pricing is per conversation, so a test costs what a real reminder costs, which is covered in how WhatsApp conversations are billed. Beacon Messenger keeps the timer simple on purpose: one number, counted from the last thing the shopper did, cancelled the moment they pay.

Frequently asked questions

When does the abandoned checkout delay start counting?

From the last change the shopper made to the checkout, not from when they first opened it. Every Shopify checkout update event moves the scheduled send to now plus your delay, so a reminder only goes out once the checkout has been untouched for the whole delay period.

What is the shortest abandoned checkout delay I can set?

Ten minutes. The automation editor rejects anything lower, and the sender enforces the same floor. The maximum is seven days, and the default is sixty minutes.

Will a shopper get a WhatsApp reminder if they already paid?

No. A completed checkout or an order carrying the checkout's token deletes the queued reminder. The only way a paid shopper sees a reminder is if the message was already sent before they paid, in which case the order confirmation follows it.

Can a shopper receive two abandoned checkout reminders for the same cart?

Not from the same checkout. Once the reminder has been sent, later updates to that checkout are ignored. A shopper who starts a brand new checkout days later, with a new checkout token, can receive a new reminder for it.

Why did an abandoned checkout reminder go out at night?

Because the shopper's last edit plus your delay fell at night. The app sends at the scheduled time regardless of hour. If late-night checkouts are common for you, use a delay of eight to ten hours so those sends land in the morning.

More guides