Help › Booking couriers

Booked but not dispatched: the alert

A booking is not a hand-over. Orders that stay booked without being logged as dispatched raise an alert on the bell, with a list and an optional reminder email.

Booking an order with a courier does not mean the parcel has left your hands, and a parcel the courier marks as returned has not necessarily reached you. That is why you log dispatches and returns yourself (Logging dispatches and returns). The alert catches the gap: orders that were booked but never logged as dispatched.

What you see

  • The bell shows a line Booked, not dispatched with the number of overdue orders and a View button.
  • View opens the list. The first column is Tracking → order: the parcel's tracking number (it opens the courier's tracking page) and the order it belongs to, the way Log orders shows a number it knows. Then the courier it was booked with, the customer, the city, what the courier says, when it was booked and by whom, and how long it has waited. Overdue shows only the ones past the time limit; All waiting shows every booked order that has not been dispatched yet.
  • Under the list you see the courier split of the ticked parcels, for example 12 PostEx · 3 TCS. Each one is logged with the courier it was booked with.
  • Tick the parcels and press Log dispatched. Their tracking numbers go into Log orders (Dispatch box), not their order numbers: Log orders knows each number's order and courier, so nothing falls back to your default courier. A parcel with no tracking number yet goes in by its order number. Everything is checked there like any other number before it is saved.
  • If the Courier switch on Log orders is set to one courier and some ticked parcels were booked with another, the list says so before you leave: Log orders is set to TCS. 12 of the ticked parcels were booked with PostEx. The box Log each with its own courier is ticked: it sets Log orders to Auto. Untick it to keep your choice; Log orders then asks about those parcels when you save.
  • The Log orders page shows the same list as a strip: N booked orders are waiting for dispatch, with the courier split, Add to list (their tracking numbers go into the box) and Choose….

Who sees it

The owners, and people who may log dispatches. Someone who only works with one courier sees only that courier's orders. A person who can see the list but may not log dispatches sees the orders and is told who can log them.

What is never counted

  • Bookings you cancelled.
  • Orders the courier has already updated (a courier status such as delivered or returned means the parcel was clearly with them).
  • Bookings older than the look-back period you set.

Setting it up (admins)

Open Settings › Notifications, card Booked orders that are not dispatched:

  1. Tick Watch for booked orders that are not dispatched.
  2. Alert when an order has been booked for more than: the longest time you allow between booking and dispatch (for example 24 hours). After that the order is overdue and the alert becomes active. Pick a ready value or type your own number of hours.
  3. Only look at bookings from the last: 7 to 120 days. Older ones never raise an alert.
  4. Show an alert in the app puts it on the bell for the owners and the people who may log dispatches. Switch it off if you only want email.
  5. Send a reminder email: choose to the owners and/or to people who may log dispatches (each of them gets only their own couriers) and how often to remind again (at most every 6 hours up to once a week). Send reminder tests it.
TipThe bell works without any email set-up. The reminder email goes out from the same background job as the daily summary, so email must be set up under Settings › Notifications and the background job must run (see Email and the daily summary).