What happens when it goes down.
Every platform has incidents. What matters is whether you hear about them from us or from a courier standing in a doorway.
What counts as an incident
Anything that stops a retailer dispatching, a courier accepting or completing a job, or a payment settling. Slow is an incident too, if it is slow enough to miss a delivery window.
How you find out
This page is updated first, then affected retailers and couriers are contacted directly. We do not wait until an incident is resolved to say it is happening.
What happens afterwards
Anything that interrupted service is written up here: what broke, how long it lasted, and what changed so it does not recur. Incidents stay on the record rather than being quietly deleted.
Nothing to report yet.
An empty incident list this early means the service is young, not that it is flawless. When something breaks it will be written up here and left here.
What changed recently.
Courier and territory pages
5 August 2026Couriers and prospective territory operators now have their own pages and their own applications, rather than the booking form built for restaurants.
Dual-mode work described properly
5 August 2026A courier attached to a restaurant can take network jobs between shifts. The platform always worked this way; the site described two separate kinds of courier. It now describes one person with two modes, and states that shift work takes precedence.
Contact replaces booking
5 August 2026Every route to a human sits on one page: write to us, book a time, or send a territory enquiry to the founder. A calendar was previously the only way in.