Journeys
17 Aug – 13 Sep · vs last year: 17 Aug 2025 – 13 Sep 2025
Four flows that run off something a customer did rather than off a date somebody chose. The conditions are checked at the moment of sending, not at the moment of entry, which is what stops an automation writing to somebody who unsubscribed on Tuesday or ordered again this morning.
Over 28 days these flows sent 3,305 messages that nobody scheduled, and produced ₺6,710 above what the people held back from them produced on their own.
Basket left behind
The highest-ordering automation in the shop and the one most likely to be overused. It is capped at one message and cannot be raised without a person editing this journey.
Web store only
Basket idle 4 hours
Web store only. A marketplace does not tell a seller about an abandoned basket, and never will.
No order since
Checked at the moment of sending, not at entry.
Under the frequency cap
Two messages in seven days, across every send and every flow that is not a notice.
You left the grinder in the basket
No second reminder
The tool can send three. The shop decided on one.
Web store customers only: no marketplace reports an abandoned basket to a seller. The conditions are permission and the frequency cap, checked at the moment of sending.
Second and third reminders removed on 3 Mar. Orders fell 4 per cent, unsubscribes fell by a third.
Ordered within seven days
The hold-out placed 3 orders over these days, under 5. This flow reports what it sent and what came back, and no result, until the window is long enough to carry one.
After an order
The only automatic message the shop sends to first-time and returning buyers alike. It sells nothing: it says when the coffee was roasted and how to keep it.
Web store · order hub
Order paid
Any channel the order hub normalises, which is all of them.
Wait 2 hours
Long enough that it does not arrive under the receipt.
We may write to them
A marketplace order has no address we are allowed to use; those people leave here.
They have not had two this week
It sells nothing, but it is measured against the hold-out like everything else that is not a notice — so it meets the cap like everything else too.
On its way
People whose last order falls inside the period. The conditions take out everybody whose order came through a marketplace, because the address on it is a relay, and anybody already at the cap.
Wait shortened from four hours to two on 14 Jul, after the receipt and this arrived together.
Ordered within seven days
Subscription ships in two days
Notice, not marketing. The cancellations that cost the most are the ones where somebody got a bag they did not want and could have stopped.
Subscription record
Two days before the roast
Runs against the subscription record, not the calendar.
Subscription still active
Your bag ships on Thursday
Every running subscription, once a month. It is a service note, so it goes to subscribers who never gave marketing permission as well — and it carries nothing to buy.
Unchanged since March.
Ordered within seven days
A notice, so nobody is held back from it. Withholding it from a tenth of the subscribers would not measure anything — it would leave them without the one message that tells them a bag is coming.
A bag's worth ago
Written and switched off. It says almost exactly what the subscription note says, to an audience that overlaps it, and nobody could explain what a person should do with both.
Order history
32 days after an order
Roughly when 250 g runs out in a two-person house.
Not a subscriber
The reason this is off: subscribers would get this and the subscription note.
No order since
About a bag's worth ago
Built on 26 Aug, never switched on.
Not running
Nobody has entered it, so there is nothing to count.
Sample data. Every figure here is counted off the list for the period on the page: who could enter, who still met the conditions, and what the people who were sent nothing did anyway.