Rundocs › POS

Scheduled deliveries

Last updated 2026-10-29

Schedule deliveries for the transactions that need to go out on a truck, group them into stops by address, and put a driver and a departure date on each run. Your driver then works the run from the Rundoo mobile staff app, navigating stop to stop and capturing proof of delivery (a photo and a signature) as they go.

In the POS mode, open the Deliveries tab in the left sidebar. It opens on the Calendar view; a List view sits next to it. A delivery is a truck run for a departure date: it holds one or more stops (one stop per address), and each stop carries the transactions going to that address.

Calendar vs List

The two tabs at the top of the page are two ways to look at the same deliveries.

Deliveries Calendar view with a week grid of delivery cards, the To schedule queue, and the New delivery button
  • Calendar lays deliveries out by day. Use Today, the arrows, and the Week / Month toggle to move through dates. Each card shows the delivery's ID, how many stops it has, and the assigned driver. The To schedule panel on the right lists transactions that are staged for delivery but not yet on a run.
  • List is a table of every delivery: Departure date, Delivery ID, Status, Location, number of Stops, Items, Total, and the Transaction IDs on it. Use Sort, Show/hide, and Filter to narrow it down.

Scheduling a delivery

Before a sale can go on a run it has to be staged for delivery. On the cart, click Schedule delivery to open the Delivery details box, set the Requested date (the date the customer needs it on site) and a Time, confirm the job-site address, then Stage for delivery. The Time defaults to All day; open it to pick a narrower window when the customer needs the drop at a particular time. The sale then waits in the To schedule queue.

There are two ways to build a run.

From the To schedule queue. On the Calendar view, the To schedule panel holds transactions that are staged for delivery and waiting for a run. Tick the ones going out together (or Select all), then click Schedule delivery.

From scratch. Click + New delivery and fill in the run.

New delivery modal with departure date, carrier, driver, notes, and a Stops section for attaching transactions
  • Departure date — the day the truck goes out.
  • Carrier — the delivery company or service, if you use one. Add a carrier to create one.
  • Driver — pick who's driving from Select a driver.
  • Notes and Internal notes — both optional. Notes travel with the delivery; internal notes are for your team.
  • Stops — a stop is one address the driver delivers to, so attach the transactions going to that address. Search transactions to find them (the search is filtered to the current Location and to transactions Staged for delivery). Add a stop per address on the run.

Schedule delivery stays greyed out until the run has at least one stop with a transaction on it.

💡

A transaction has to be staged for delivery to show up here. Both the To schedule queue and the New delivery transaction search only surface transactions that are staged for delivery, so if a sale isn't appearing, check that it was marked for delivery on the cart rather than pickup or carry-out.

Setting the stop order

A run with more than one stop goes out in the order the stops are listed, and you control that order two ways. Open the delivery and click Route stops: Rundoo puts the stops in a sensible driving order so your driver isn't doubling back across town. A Stops reordered banner appears; click Save to keep it. Prefer to set the order yourself? Drag the stops into the order you want by the handle on the left of each one, then Save. Either way the driver sees the stops in that saved order on their phone.

How the driver gets the run (the mobile delivery app)

You put a driver on the delivery with the Driver field, and the run then shows on the Calendar and List views (and on the delivery's card) under that driver's name. Your driver picks it up from there on their phone, in the Rundoo mobile staff app.

The driver signs in to the Rundoo POS mobile app on their phone and sees the deliveries assigned to them. From the app they can work the whole run without a paper sheet:

  • See which deliveries to make and tap through to navigate from one stop to the next.
  • Capture proof of delivery at each stop, a photo and a signature.
  • Record a failed attempt when nobody's there to receive it.

As the driver works the run, its status moves along the stages in the Legend on the Deliveries page: Scheduled (planned, awaiting departure) to In Progress (en route to its stops) to Completed when the run is finished (or Cancelled if it's called off). The store and the customer get a notification whenever a delivery's status changes, so you don't have to chase the driver for an update.

💡

Drivers log in with their own Rundoo staff account. A driver has to be a Rundoo staff user to sign in to the mobile app, so add anyone who drives as staff first. The delivery features live in the same Rundoo POS mobile app your team already uses at the counter.

Reminders for deliveries that need to go out

Rundoo doesn't ship a built-in "deliveries due today" alert, but you can build one with a Dooey routine so the people who run your deliveries get a scheduled reminder without opening the app.

💡

Suggestion: use a Dooey routine for delivery reminders. Set up a Routine of type Report on a staff account that has reporting permissions, and have it text or email whoever manages deliveries a daily rundown: what's scheduled to go out that day, plus anything sold for delivery that hasn't been put on a run yet and is coming due. Dooey runs it on the schedule you set and delivers it by text or email (you tell Dooey which). A single person who dispatches for the whole shop is exactly who this reminder is for.

Here's what that reminder looks like when Dooey sends it, the same rundown as a text and as an email. Each line names the delivery, its status, the driver, the sale it covers, and how many stops it has.

Example text reminder listing the day's scheduled deliveries, each with its delivery ID, status, driver, linked sale, and stop count
Example Rundoo email reminder of the day's scheduled deliveries with the same delivery rundown and a support contact footer

Multi-location deliveries

If one logistics team dispatches for several stores, the view you want is List, not Calendar.

Deliveries List view table of scheduled deliveries with departure date, delivery ID, status, location, and totals
  • The Calendar is scoped to one location at a time, set by the Location picker. A central dispatcher would have to switch locations one by one to see every store's runs on the calendar.
  • The List view has its own Location filter and defaults to the location you're signed in to. Open the filter and pick the locations you dispatch for to see deliveries across stores in one table. This is the way to run all of a chain's deliveries from one desk today.
💡

One shared calendar across all locations isn't available yet. The all-in-one view for a central logistics team is the List view with the location filter widened. If a single cross-location calendar would help you, it's worth a note to Rundoo Support so the request is on record.

  • Sales — how a transaction is rung up and marked for delivery before it lands in the To schedule queue.
  • Drafts, quotes & will-calls — the other ways a sale waits before it's completed or handed off.
  • Locations — how the locations the Deliveries filters use are set up.