Skip to content

Features

Three people use this. They need different things.

Dispatch needs to see the whole day at once. A rider needs one stop and a camera. A customer needs a link that works. Below is what each of them actually gets.

For dispatch

The dashboard

Where the day is run from. Orders land on their own and leave assigned.

  • Orders arrive by webhook

    Shopify calls the moment an order is paid for. Nothing polls, and nobody presses import.

  • One queue for the unassigned

    Everything waiting for a rider collects in a single place, so the backlog is a list rather than a feeling.

  • Assign and reassign

    Give a stop to a rider, or move it. The change reaches their phone without them refreshing anything.

  • Where the riders are

    Positions on a map while riders are on shift, with anything stale marked stale rather than drawn as current.

  • Counts that respect the clock

    Today’s numbers use the store’s timezone, so a 1am order counts as tonight and not as yesterday.

For riders

The phone

The half of the job that happens where the signal does not reach.

  • The stops for this shift

    A rider sees their own assigned work and nothing else.

  • Proof at the door

    A photo and a GPS stamp recorded at the doorstep, stored against the delivery.

  • Delivered, or why not

    A failed attempt is a first-class outcome with a reason attached, not a stop that silently stays open.

  • Written before the network

    The delivery is saved to the phone first and sent when there is something to send it over. A basement does not lose it.

  • Submitting twice is safe

    A request that times out but actually arrived is recognised as the same delivery. It is never counted, or fulfilled, twice.

For customers

The tracking link

One page, no account, nothing to install.

  • A code, not a login

    The customer opens a link and sees their order. There is no password to forget.

  • What happened, and when

    Received, assigned, out for delivery, delivered — with the times, as they occurred.

  • The proof photo

    Served through a signed URL that expires, so the image is not left sitting on a public address forever.

Underneath

Most of the work went into what happens when something fails.

A delivery app is easy while the network holds and nobody taps twice. These are the parts that deal with the rest of it.

Fulfilled exactly once

Shopify is told a parcel arrived one time, even when the same delivery is submitted three times from a patchy connection.

Riders and staff are separated

Roles live in metadata only the service role can write, and an unrecognised role is denied rather than assumed to be staff.

Webhooks are verified

Every payload Shopify sends is checked against its HMAC signature before it is allowed to change anything.

Sync survives a real catalogue

First sync was built and corrected against a store with thirteen thousand orders, not against a test fixture with five.

Easier to watch an order come through than to read about it.

Connect a store and the next paid order appears on its own.