Simpler Pricing.

Traffic patterns are taken into account when optimising routes

Sometimes Drivers go straight home after their last Job. You can set a specific route end address to optimise for this.

Set the time that drivers must finish their route by. If there are too many Jobs to visit during the drivers' shifts, they will be unserved.

Set lunch breaks or legally mandated breaks for each Driver.

Fixed Breaks can be set so that the Driver must take them at a certain time.

Floating Breaks can be set so that breaks don't interrupt work:
e.g. "Take a 30 minute break between 1pm and 3pm"

The optimiser just works by default. But if you need a result really fast, or you can afford to take longer to get a more optimal solution, you can set:

• Optimisation Time Limit
• Improvement Threshold per Second
• Improvement Interval

Re-Optimise the rest of the route for one or all drivers, even after they have started their deliveries

You can set capacity constraints on multiple dimensions at the same time.
e.g. "number of pallets" AND "weight"

Useful for vehicles that have re-configurable layouts.
e.g.
4 pallets and 1 bike
OR
1 pallet and 8 bikes

Useful for couriers, and other use-cases where items (or people!) are picked up and then delivered in the same run.

Sometimes you don't have enough Drivers to do all your Jobs today. Mark certain Jobs as priority to ensure they will be served, even if several others aren't.

Types restrict which Drivers are allowed to do which Jobs

This is often used for:

• Ensuring certain deliveries are performed by refrigerated vehicles

• Ensuring that the driver has the right qualifications to perform a service (e.g. she is a level 2 qualified electrician)

• Ensuring that large parcels are delivered by large enough vehicles, or vehicles with a tail lift
• Forcing a Job to be performed by a specific Driver (because the customer requested her, for example)
• Ensuring only certain vehicle types (e.g. small trucks, bicycles, electric vehicles) perform deliveries in city areas

Express complicated business rules about which Drivers and Vehicles can do which Jobs

Configure the Optimiser to minimise

• Driving Time: Fewest hours spent driving
• Driving Distance: Fewest KMs driven
• Total Cost: Set the cost per KM, per Hour, per Stop and per Run, and allow the optimiser to minimise this

If you have pre-determined delivery zones or territories, the optimiser can respect these and optimise within them.

Take a look at the Optimisation API Documentation

The Driver can make deliveries even if their device has no connectivity.

All Delivery Proofs and other information will be automatically sent when the device reconnects.

The Dispatcher can push real-time or last-minute updates to the driver to support on-demand situations

Drivers are not tracked when they are not performing their work.

Drivers can pick up planned or ad-hoc returns, and record proof of item at pickup and back at the depot

Scan multiple items into a box, crate, or other container at loading time. Then, the driver only scans a single barcode to deliver them all to the customer.

Drivers can scan a QR Code (designed to be displayed on a screen at the depot) which loads their Runsheet into the Driver App on their device

You can send a Runsheet/Manifest directly to a Driver if they are logged in to the App

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

Drivers without Smartphones/Tablets can use a printed PDF runsheet

Useful if you need to import Runs planned in Tarot Routing into another system

Drivers can only select reasons which are consistent with already performed actions.
E.g. they can't say a parcel is 'Delivered - OK' if it already has 'Not Loaded - Missing'

The Driver is advised on how to pack the vehicle based on the delivery sequence

For example:

• Delivered - Damaged
• Not Delivered - Damaged
• Delivered - With Reservations
• Not Delivered - Missing
• Not Delivered - Customer Closed

For Example:

• Signature Required, Except for customers with night-lockers
• Photo required if damaged

Jobs coloured to instantly recognise Delivery Failure/Success

Write rules in plain English (or your language!) and let AI check if the planned routes meet those rules.

Dispatchers, Admins, Managers and Finance Team can all download PoD PDFs individually or in bulk.

End Customer can self-service download PoD PDFs

Useful to easily identify categories of Jobs, or to communicate carry-over reasons in multi-dispatcher teams.

Automatically merge multiple Jobs to the same customer into a single visit

Sometimes you may want to re-optimise a Route while ignoring existing constraints.
For example:

• to force a Driver to deliver an extra Job even if they finish 15 minutes late
• to give a job to a Driver who usually has a different territory

Useful since

1. ETAs change when a driver departs late
2. the driver might not be able to make certain time windows
3. the driver might not have time to visit all the Jobs during their shift

ETAs update whenever the Driver performs an action (leaving the depot, finishing an earlier Job, etc)

No Login Required.

Delivery Recipients use a Tracking Link or Tracking Token to access the End-Customer Tracking Portal for a single delivery.

Events & Actions allow you to send custom messages by Email or SMS to your customers, your billing team, or whoever you like, based on any Event that can happen in Tarot.

• the Driver leaving the warehouse,
• a successful or failed delivery,
• when the driver is 2 stops away, or
• many other customisable events

The Delivery Recipient can:

• signal that they can/cannot accept a delivery as scheduled
• request another delivery date (if other deliveries in the same area are already scheduled for that date)

For Example:

• Dispatchers can plan routes, dispatch and track
• Managers can delete Jobs and manually override a delivery status
• Admins can add new users and reset their passwords

Useful for managing multiple sites in the same company, or multiple different business units.

Take a look at the REST API Documentation

Take a look at the Tarot Routing Uptime Monitor

All Tarot Routing Features are manually tested by trained QA staff at least once before each deploy

Detailed Security Policy available upon request

Automatically send SMS or Email notifications to customers when their delivery is scheduled, out for delivery, up next, or delivered

Automatically send SMS or Email notifications to managers when a delivery is late, failed, or upon any other custom event

Any Tarot event can trigger webhook calls to your own software.

For example:

• When a delivery is late, send a webhook to your CRM to notify the customer
• When a delivery is completed, send a webhook to your ERP to update the order status
• When routes are planned, send a webhook to your notification system to send SMS to customers

Embed Tarot Routing in your own software (iFrame or other)

A Tarot Analytics Account Manager can join your preferred channel (Teams, WhatsApp, Slack, JIRA, Email, Phone, etc) to provide support to your team

Audit results, Data Protection Agreement, etc available

Integrations can be made:

• with any software platform that allows integrations, imports, or exports
• using REST, HTTP, HTTPS, FTP, SFTP, AS2, SOAP, or any custom protocol
• in XML, JSON, CSV, Excel, or any custom format