Simpler Pricing.

Traffic Patterns Traffic patterns are taken into account when optimising routes

Separate Driver Start/End Location Sometimes Drivers go straight home after their last Job. You can set a specific route end address to optimise for this.

Driver Shifts 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.

Driver Breaks 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"

Custom Optimiser Stopping Criteria 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

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

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

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

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

Priority Jobs 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 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 specfic 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

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

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

Fully Documented Optimisation API Take a look at the Optimisation API Documentation

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

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

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

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

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

Dispatch to App via QR Code 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

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

Browser-Based Mobile Runsheet Often used by subcontracted drivers who don't want to install the App

Printable PDF Runsheet Drivers without Smartphones/Tablets can use a printed PDF runsheet

Excel/CSV Runsheet Useful if you need to import Runs planned in Tarot Routing into another system

Customisable Delivery Failure Reasons & Workflow 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'

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

Customise Delivery Failure/Success Reasons For example:

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

Customise Delivery Requirements For Example:

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

See Depots and Jobs on the Map Jobs coloured to instantly recognise Delivery Failure/Success

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

End Customer can self-service download PoD PDFs

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

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

Advanced Re-Optimisation Ignoring Some Constraints 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

Delay Driver Departure 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

Real-Time ETA Updates ETAs update whenever the Driver performs an action (leaving the depot, finishing an earlier Job, etc)

Tracking Portal Accessible by Delivery Recipient No Login Required.

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

Interactive Delivery Management (IDM) 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)

Multiple User Types 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

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

Import & Export Everything as JSON (via REST API) Take a look at the REST API Documentation

Uptime Monitor Take a look at the Tarot Routing Uptime Monitor

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

Security Best Practices Enforced & Monitored Detailed Security Policy available upon request

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

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

Events Trigger Webhooks 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

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

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

UK GDPR & EU GDPR Documentation Audit results, Data Protection Agreement, etc available

Custom Integration to/from your ERP, WMS, TMS, DMS, Accounting System, etc 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