Pricing

Routes are optimised using typical traffic for the time of day.

Set a different end address, such as a driver going straight home after their last job, and the route is optimised for it.

Set the time each driver must finish by. If there are more jobs than the shifts allow, the extras are left unserved rather than making drivers late.

Add lunch or legally required breaks for each driver. Fixed breaks happen at a set time; floating breaks fit around the work, such as "a 30-minute break between 1pm and 3pm".

The optimiser works well by default. If you need a result faster, or can wait longer for a better one, set a time limit, an improvement threshold per second or an improvement interval.

Re-optimise the rest of the route for one or all drivers, even after they have started delivering.

Put chosen jobs at the start or end of a route without artificial time windows. Several start or end jobs form a block that's optimised within itself. Set it per job, or as a default for a client.

Set capacity limits on several dimensions at once, such as number of pallets and weight.

For vehicles with reconfigurable layouts, such as 4 pallets and 1 bike, or 1 pallet and 8 bikes.

For couriers and other operations where items (or people) are picked up and delivered on the same run.

When there aren't enough drivers for every job, priority jobs are served first.

Control which drivers and vehicles can do which jobs: refrigerated deliveries, qualified technicians, large parcels that need a tail lift, a driver the customer asked for, or only small or electric vehicles in city centres.

Express complex business rules about which drivers and vehicles can do which jobs.

Choose what the optimiser minimises: driving time, driving distance, or total cost based on your cost per km, hour, stop and run.

If you have fixed delivery zones or territories, the optimiser keeps each route within them.

Read the Optimisation API documentation.

Drivers can keep delivering without a signal. Proofs and updates are sent automatically when the device reconnects.

Drivers and dispatchers message each other about a run, in the Driver App and in Tarot Routing.

Dispatchers can push last-minute changes to drivers for on-demand work.

Drivers aren't tracked when they aren't working.

Drivers collect planned or ad hoc returns and record proof of each item at pickup and back at the depot.

Scan items into a box, crate or other container when loading, so the driver scans one barcode to deliver them all.

Drivers scan a QR code shown on a screen at the depot to load their runsheet into the Driver App.

Send a runsheet straight to a driver who is logged in to the Driver App.

Often used by subcontracted drivers who don't want to install the app.

For drivers without a smartphone or tablet.

For importing runs planned in Tarot Routing into another system.

Scan parcels and containers before runs are dispatched, so drivers get on the road faster.

Every barcode scan is recorded, to help trace when a parcel goes missing or is loaded into the wrong vehicle.

Drivers can only choose reasons consistent with what has already happened. For example, a parcel marked missing at loading can't then be marked delivered.

As each package is scanned, the scanner shows its place in the delivery sequence, so the driver knows where to put it.

For example: delivered damaged, delivered with reservations, not delivered because the customer was closed.

For example: signature required except for customers with night lockers, or a photo required if an item is damaged.

Jobs are coloured so successful and failed deliveries stand out.

Write rules in plain English (or your own language) and AI checks whether the planned routes follow them.

Dispatchers, admins, managers and finance can download PoD PDFs one at a time or in bulk, and end customers can download their own.

Group jobs by category, or record why a job was carried over, so everyone in a multi-dispatcher team can see it.

Automatically merge several jobs for the same customer into one visit.

Re-optimise a route while relaxing some rules, such as letting a driver take one more job and finish 15 minutes late, or giving a job to a driver from another territory.

When a driver leaves late, ETAs update and you can see which time windows or jobs they'll no longer make.

ETAs update whenever the driver does something, such as leaving the depot or finishing a job.

No login needed. Recipients open a tracking link, or enter a tracking token, to follow their delivery. You can customise how the page displays for your organisation.

Send email or SMS* to customers, your billing team or anyone else when something happens: the driver leaves the warehouse, a delivery succeeds or fails, the driver is two stops away, and many more.

Recipients reply by SMS* or chat from their tracking link, and dispatchers answer in Tarot Routing.

Recipients confirm they can accept a delivery, or choose another day when deliveries are already scheduled in their area.

For example: dispatchers plan, dispatch and track; managers can delete jobs and override a delivery status; admins add users and reset passwords.

For managing several sites or business units in one company.

Connect your own systems to Tarot Routing through the documented REST API.

See the Tarot Routing status page.

Trained QA staff test every feature by hand at least once before each release.

Detailed security policy available on request.

Automatic SMS* or email when a delivery is scheduled, out for delivery, next, or delivered.

Automatic SMS* or email to managers when a delivery is late or fails, or on any other event you choose.

Send SMS* from your own number through your own Twilio account.

Any Tarot Routing event can call your own software. For example: update your ERP when a delivery is completed, or notify your CRM when one is late.

Embed Tarot Routing in your own software.

A Tarot Analytics account manager joins the channel your team already uses: Teams, WhatsApp, Slack, Jira, email or phone.

Audit results, a data processing agreement and more.

With any platform that supports integrations, imports or exports, over REST, HTTP(S), FTP, SFTP, AS2, SOAP or a custom protocol, in XML, JSON, CSV, Excel or a custom format.