Last Mile Logistics automated.
Our API is developed to support real-world logistics scenarios at last mile. We cover advanced business requirements for same and next day delivery, with great customization flexibility under the hood.
Routing technology for tomorrow's logistics challenges.
What's in the box?
We support many common routing constraints out of the box. Most of them are optional, so you can start routing your vehicles without added complexity, and increase it on the go when needed.
Flexible routing constraints.
All API features and route optimization constraints are fully available for free and paid tiers. Get in touch if you need custom functionality or routing constraints, specific for your logistics operations.
Transport logistics use cases
FEATURES AVAILABILITY

During next day delivery, orders are accepted until cut-off time, typically in the evening.

At cut-off time, vehicle routes are planned ensuring satisfaction of routing constraints (time windows, load limits, orders priority, etc).

At last, orders are consolidated at warehouse for loading to vehicles and actualy delivery.

GA

During same day delivery, orders are accepted until cut-off time. Typically there are several cut-off time points during the day, and several "waves" of delivery.

At cut-off time, vehicle routes are planned ensuring satisfaction of routing constraints (time windows, load limits, orders priority, etc).

At last, orders are consolidated at warehouse for loading to vehicles and actualy delivery.

GA
Routes for a fixed set of sites, recalculated on daily (or hourly) basis to ensure accurate time of arrival with respect to traffic.
GA

Routes are planned for several days of operations. Customers typically accept deliveries over several days, with specified time window for each site and day.

This type of operations typically used to plan deliveries over 2-3 days horizont, with number of deliveries too high to be performed by fixed amount of vehicles over 1 day.

Q4 2018

Route planning, that involves pickup tasks at visited sites, when goods can be loaded to vehicle at any site, not only at depot.

It is possible to specify additional delivery constraint, that forces vehicle to visit specified site during the route to unload picked up goods.

Q1 2019
Optimization targets
FEATURES AVAILABILITY
The total transit time of all vehicles is minimized. Travelled distance will be ignored.
GA
The total transit distance of all vehicles is minimized. Travelled time will be ignored.
GA
The total transit distance and travel time of all vehicles is minimized simultaneously. This is default production mode.
GA

Cost-aware minimization strategy: every component of routing problem has associated value in currency.

Examples of costs include: cost per kilometer of used vehicle, fixed cost of driver's shift, cost of untimely arrival to a site, and other.

This is recommended production mode for logistics operations, balancing resources using cost components.

GA
Routing and traffic support
FEATURES AVAILABILITY
Origin-destination matrix, built from OSM data for entire world. This is default routing mode on free tier without traffic support. Automatic weekly updates from OSM snapshot to ensure up to date road graph.
GA

Historic traffic patterns are crucial for accurate estimation of vehicle transits and Time of Arrival.

Our route optimization system utilizes traffic data from HERE, a world-leading provider of Location Services. This is default routing mode on paid tiers.

Q3 2018

Full support of HERE truck routing profiles and road tolls

Q3 2018

Allows to bring your own origin-destination matrix with traffic.

This functionality is useful in case when organization already consumes origin-destination matrix data from third party provider under separate license. Available only on paid tiers.

GA
Allows automatic detection of risks on route, related to transit estimation errors. No traffic prediction is 100% perfect, and it is important to understand which sites en route are under most risk.
Q3 2018
API features
FEATURES AVAILABILITY
Our service is build on REST principles, and fully documented with OpenAPI 3.0 specification for easy integration.
GA
For secure machine-to-machine communication over HTTPS we utilize API key authentication scheme.
GA
More complex and secure authentication mechanism for machine-to-machine communication.
Q4 2018
Requests and optimization results stored and accessible forever by authenticated users for retrospection and analysis.
Q1 2019
Our service runs on Google Cloud, fully secure and compliant environment. See https://cloud.google.com/security/compliance for more information.
GA
Site properties and constraints
FEATURES AVAILABILITY
Time interval when site can be visited. When defined, route will be optimized such that time of arrival will happen during specified time interval.
GA

Time windows that are treated flexibly, ie allow untimely arrival to a site. An arrival that does not happen on time is subject to penalties during optimization (and subject to automatic minimization).

This mode allows planning of tight schedules, when there are too many sites to visit for defined number of vehicles.

GA

Time windows that are treated strictly, ie do not allow untimely arrival.

If site can not be visited within specified time window, instead of untimely arrival, such sites will be excluded from result routes, and moved to "unserved sites" in response.

GA
Multiple time intervals when arrival on site can happen. For example, this allows definitions of sites, closed for some time during the day.
Q4 2018
Time windows, specified in relative format, ie using only time of the day ("10:00 - 18:00"). This is easier to use and default format.
GA

Absolute time window definitions are useful for routes, spanning across different time zones.

In this case, we recommend to translate all time windows to absolute date and time format, to avoid time zone calculation errors.

Q4 2018
Allows weight and volume definition for load to be delivered at site. Supports optional weight and volume, with transparent conversion between values using common dimensional weight factor.
GA
Allows definition for non-metric size of load to be delivered at site. Examples include pallets, barrels, crates, standartized shipping containers, and other types of load, where exact units are not defined. To use non-metric size, define corresponding capacity limits for vehicles. Non-metric size is an additional constraint to dimensional weight (checked independently if both are defined) to allow mixed types of load.
Q4 2018
Allows prioritising visits to specific sites by defining their normalized priority, or currency value (revenue) of the shipment.
GA
Allows to specify if certain sites needs to be visited only by certain vehicles. Uses expression-based syntax to defined complex rules of vehicles and sites matching.
Q3 2018
Allows to specify time, predicted to be spent at the site after arrival and before departure, ie handling goods or performing services.
GA
When multiple sites are co-located at same geographical coordinate, specify service time to reflect two site duration time components - shared time for a geo location (ie parking), and time for handling each delivery to a separate customer (physical unloading from a vehicle).
Q4 2018
Strict ordering of site visits. Allows to specify if certain site requires goods pickup, with subsequent delivery by same vehicle to another specified site.
Q4 2018
Depot properties and constraints
FEATURES AVAILABILITY
Time interval when depot operates. Vehicles start loading and departing from depot when depot time window begins, and return to depot before time window ends.
GA

Time window that is treated flexibly, ie allow untimely arrival or departure of vehicle to depot. An arrival that does not happen on time is subject to penalties during optimization (and subject to automatic minimization).

This mode allows planning of tight schedules, when there are too many sites to visit for defined number of vehicles, and some vehicles can arrive to depot after hours.

GA

Time windows that are treated strictly, ie do not allow late arrival after depot is closed, or early departures before depot opening time.

If vehicle can not return to depot within specified time window, instead of untimely arrival, some sites will be excluded from result routes, and moved to "unserved sites" in response.

GA
One depot where all vehicles can start from, and optionally finish at.
GA
Multiple depots, where some vehicles can start from and optionally finish at. Can be defined with possibility of some vehicles to finish at specified depot, or any depot closest to last visited site.
Q4 2018

Allows definition of depot performance. Expressed in units of weight, which can be loaded to docked vehicles simultaneously.

Represents ability of a depot to serve (or load) multiple vehicles, docked to the depot at the same time.

Q4 2018
Vehicle properties and constraints
FEATURES AVAILABILITY
Allows to define volume and weight limits of load, carried by vehicle. Supports optional weight and volume, with transparent conversion between values using common dimensional weight factor.
GA
Allows definition for non-metric capacity of a vehicle. Examples include pallets, barrels, crates, standartized shipping containers, and other types of load, where exact units are not defined. To use non-metric size, define corresponding size for load to be delivered to site. Non-metric size is an additional constraint to dimensional weight (checked independently if both are defined) to allow mixed types of load.
Q4 2018
Allows to specify if certain vehicles should visit only certain sites. Uses expression-based syntax to defined complex rules of vehicles and sites matching.
Q3 2018
Allows to specify if certain vehicles should not carry certain types of load together during single route. For example, milk and raw meat products should not be delivered by same vehicle. Uses expression-based syntax to defined complex rules of load incompatibility.
Q3 2018
Controls returning of vehicle to a depot. When set, vehicle will finish route at last site without returning to depot.
GA
Controls returning of vehicle to a depot during driving shift. Vehicles can return to depot to pick up additional load and additionaly drive one or more routes.
GA

Allows to specify strict or relaxed order of sites to be visited by vehicle.

Pre-assignment is used during planning of same day delivery, when some shipments are already prepared at warehouse for loading to particular vehicle, and routes should be re-planned taking into account sites newly added for routing.

It is also possible to use strict pre-assignment with optionally specified time of arrival to each site to calculate route statistics for already completed routes, to analyze the difference in planned vs actual routes.

Q4 2018

Allows specification of driver's shifts. A shift is an interval within depot time window, when vehicle should operate.

A vehicle can have multiple non-overlapping shifts, with optional penalty for finishing the shift later than specified time. Constraint also supports duration between shifts, needed to finish the shift after arrival to depot.

Q4 2018
What's next?
Learn how to make your first request by following quickstart guide for developers. Did not find information you wanted? Reach us out with a question about anything.