The moment it's ready.
The moment they want them back.
No app to check obsessively, no hovering at the counter refreshing a page — it arrives the same way a text would.
See how it worksThursday 24 September
8:39
Sent the instant the order is placed, without the shop doing anything.
An order doesn't stay quiet. The moment it's confirmed, being made, and ready, the customer's phone already knows.
For the shop, the same system becomes a way to bring a regular back: a new roast, a seat at an event, a reason to stop by again.
One notification system. Two different reasons to use it.
01 / Automatic, for every order
Every order, kept up to date.
Confirmed, being prepared, ready for pickup, refunded — a customer hears about each one without asking.
It's on the moment they grant the one-time permission most sites ask for. Nothing further to configure, no setting to remember to turn on.
02 / A real push, not a badge
Said once, arrives instantly.
This is a real push notification, not an in-app badge nobody notices — it reaches a customer's lock screen the way any notification does.
No separate app to download from a store. It works from the same storefront a customer already has open or installed.
Thursday 24 September
8:39
03 / For the shop
For the shop: bring the right people back.
A shop can send an announcement to everyone, or narrow it — customers with a loyalty standing, a specific tier, people who haven't been in for a while, or people who just have.
It's a choice made on purpose each time, not a blast to the entire customer list by default.
Announce something real, not a typed-in link.
An announcement can point straight at a real Community post instead of a hand-typed address.
The correct link is built automatically, and a post that isn't published yet can't be announced at all — better an announcement waits than one that opens to nothing.
Thought through, underneath
Now, or on schedule.
Never a second-tier channel.
The timing and the pipeline.
Now, or exactly when it should land.
An announcement can go out the moment it's written, or scheduled for a better time — the morning a new roast actually arrives, not whenever someone happened to sit down and write it.
One pipeline, so nothing is treated as less important.
A customer's "order ready" and a shop's announcement about Saturday's tasting travel through the exact same delivery system.
There's no second-tier channel quietly handling one kind of message with less care than the other.
Security
How it's protected.
01Permission is asked, never assumed.
A customer's device only receives anything after they've said yes to notifications — the same permission prompt any site would ask, refusable at any time.
02An announcement can only ever reach its own shop's customers.
A campaign is scoped to the business that sent it from the moment it's created — it cannot be aimed at another shop's audience.
03An announcement can't be pointed at something it doesn't own.
When it names a real Community post, that post is checked against the shop sending it — so an announcement can never link out to another business's page by mistake.
Yours to shape.
Said once.
Arrives the moment it matters.
What counts as worth a notification, and to whom, is entirely up to the shop sending it.
If there's a way you'd want this to work that isn't here yet, tell us.