Foxtrot Overview

Foxtrot optimizes the sequence of a route in real time. A route is considered to be a set of stops (waypoints), which usually take time (service time), have a set of tasks to complete (deliveries), and optionally have time windows.

Foxtrot not only optimizes a route throughout its operation, but it also learns about your customers’ time windows, locations and service times from the drivers’ behavior. While these parameters are optional, providing them will help Foxtrot yield better optimization results.

Distribution Centers

For most API calls, a Distribution Center (see DC) ID must be specified. A list of all the DCs for an organization can be obtained by calling GET DCs.

Drivers

Create, read, update, and delete individual drivers (see Driver) or all drivers for a single distribution center can be obtained using the Drivers API.

Driver authentication is done at the SDK level using the login_token. See the SDK documentation for more details.

The Route Lifecycle

A Route typically is imported before the driver starts their day. A route is composed of its unique Route ID, an estimated start date, waypoints, and more. Details can be found in the create route API.

Note

If an incorrect route is accidentally imported or it needs to be modified, that route must first be DELETED and then import it again.

Typically, using a Foxtrot’s mobile SDK integrated application, drivers will obtain their corresponding active route based on their credentials and driver ID. To create a route, please refer to: Create Route. To activate or deactivate an individual route after importing, use the route’s ID.

After a driver completes all waypoints in a route and finishes it, Foxtrot’s mobile SDK will look for the next (based on planned route start time) active unfinished route assigned to them.