The latest update to our API means you can now add proof of delivery requirements.

Enhance your API integration to include proof of delivery requirements for stops, which will automatically use your POD global account settings.

Set the POD API field as False, and the feature will be turned off, and drivers will not be prompted to collect POD in their driver app.

Set POD API field as True, and the feature will be turned on for that stop with your global account settings for POD applied. Drivers will be prompted on their driver app to collect the type of POD specified in your global account settings, eg, signature POD is mandatory

How to add proof of delivery requirements to your API integration

• For each stop you want to require POD for add the field > proofOfAttemptRequirements
• Set the enabled flag to true, false, or null
• If marked as true, your global account settings for POD will be applied to stops

Preparing client order data for import into Circuit for Teams can be a time-consuming yet necessary task, but that has just gotten easier.

Circuit’s Client Portal now allows your clients to import their orders directly into your Circuit for Teams account and instantly access real-time information about their deliveries.

Clients can import their orders at any time. Once an order is marked by the client as ready for delivery, it will automatically appear on your unassigned stops list as a delivery ready to be added to a route.

Clients can also track the status of their deliveries via the client portal, which allows them to resolve any customer disputes directly. All the information they need about a package’s progress and status is visible in real-time.

How clients can upload orders to the Client Portal

• Your client will log in to their client portal dashboard
• They will import a spreadsheet that contains the orders they want delivered
• Your client will select which imported orders they want to submit for delivery
• All submitted orders will then appear on your unassigned stops list, ready for delivery
• Your client will be able to track the live progress of every delivery via the client portal

Previously, all dashboard members could view and modify all account activity. Consequently, dashboard members from one depot could accidentally make changes that affected another depot.

The latest update to dashboard permissions means that Owners and Admins who have the highest level of permissions remain able to view and edit anything across their entire Circuit for Teams account.

Depot managers, Dispatchers, and Read-only roles can now only see and change activity for their assigned depots. This allows each depot to be managed independently and prevents unintentional changes.

How to assign depots to dashboard members:

• Go to Settings > Dashboard members
• Select a Dashboard member to edit
• Assign a Depot
• Assign a dashboard member role

Drivers sometimes tap start on their route so they can view the details of their journey several hours before actually beginning their route. This can have a knock-on impact on recipient ETAs, which are triggered when a driver taps start on a route.

When drivers tap start to look at their route but don't actually start their route for a while, recipients will receive incorrect ETAs based on the time the driver tapped start, not when they really began their route.

New notifications in the Driver app provide drivers with a clear warning before they start their route about the impact of that action on recipient ETAs. When a driver receives a new route notification, they are now guided to look at it in their routes list rather than tapping start.

Editing stops on a route, in the client portal, or on the unassigned stops list was possible but not always easy. The level of detail associated with a stop can vary, and visualizing all stop details in a clear and usable design becomes difficult as the number of stop settings expands.

The redesigned stop details card, with its new streamlined design and tooltips for each element, makes it easy for users to discover all the stop editing actions available.

Occasionally, Drivers mistakenly deliver the wrong package to an address. This can be a difficult and costly problem to resolve, as it impacts two recipients.

Dispatchers can now prevent this by importing stops with barcode IDs. When a driver arrives at a stop with an associated barcode ID, the driver can mark the stop as delivered and is now given the option to scan the package barcode to confirm the correct item was delivered.

This feature is enabled by default, but Dispatchers can disable it in their account settings so that it is not visible in the Driver app.

How Drivers can scan barcodes at the point of delivery

• Dispatchers import stops with barcode IDs into Circuit for Teams
• Drivers attempt a delivery and mark the stop as delivered
• If the stop has a barcode ID, the barcode scanning view will automatically open on the Driver app
• Drivers have the option to scan the package barcode to confirm the correct item for that address has been delivered or skip this step

When dealing with large tables of delivery data, it can be tricky and time-consuming to find a specific driver, delivery, or unassigned stop.

Now, tables can be sorted chronologically or alphabetically.

You can sort your data by clicking the sort icon in the top right corner of a table. Order information in a way that works best for your needs, and find the information you’re looking for faster.

How to sort tables

• Drivers, Unassigned stops, and Client portal tables can be sorted
• Go to the table > Click the sort icon in the top right corner
• Choose the field you want to sort your table data by eg Name
• Select the order you want that field sorted in eg A-Z or Z-A

Managing multiple drivers in a single delivery zone can become visually confusing if it’s hard to differentiate between individual driver routes.

Dispatchers can now choose from 18 colors when color-coding individual drivers. This makes selecting contrasting route colors for drivers in the same delivery zone easier.

Once a color has been assigned to a driver, this color will persist unless the driver is paused or assigned to a new depot.

How to color code individual drivers

• Go to Drivers > Select a driver to edit
• Click > Edit driver
• Go to Appearance > click the drop-down menu
• Select one of 18 available colors

Many courier companies use barcode scanning for various steps along the last-mile delivery journey. Our latest feature allows Dispatchers to upload unassigned stops via spreadsheet or the API and include package Barcode IDs.

Now, when a Driver creates a route, they have the option to scan the barcode label attached to a package, which will automatically move that stop from the unassigned stops list onto their route.

Barcode scanning was not previously supported, and this is the first step towards building more comprehensive barcode functionality.

How to import barcode data and scan barcode labels

• Add Barcode ID numbers to the Barcode ID column in the spreadsheet or via your API integration
• If you are using a spreadsheet, import the spreadsheet data to unassigned stops in the Dispatcher dashboard
• On the Driver app, the Driver taps the viewfinder icon to add a stop to a route
• Select > Barcode and line up the package barcode label in the viewfinder to scan it
• Once successfully scanned, that unassigned stop will automatically move from the unassigned stops list onto the Driver’s route

The complexity of delivery routes means that sometimes, certain stops need to take place before or after others for the route to be effective.

Now, Dispatchers can manually set an order for stops on a route and place them at a convenient point relative to other deliveries.

For example, it’s now possible to set a package collection stop to happen before that package’s eventual delivery stop later in the route.

How to manually order stops on a route

• Go to the route you want to edit
• Click the dotted square 'select area' icon on the map
• Select the hexagon sections which contain the stops you want to order
• On the toolbar at the bottom of the map click > Edit > Manual ordering
• Click > + Set stop order
• Place selected stops before/directly before/directly after/after other stops
• Next select the stop you want the new stop order to relate to
• Click > Finish then preview and save the changes