We have created an example spreadsheet to help make importing stop data simple.
If you don't want to use Circuit's example spreadsheet, click here to watch our handy video on how to import any spreadsheet into Circuit for Teams. Accepted file formats include .csv .tsv .xls .xlsx .xlm .txt.
How to add data to Circuit's example spreadsheet
Step 1. Input address data
Unit/Flat/Unit Name - This is an optional field.
In this column, you can enter a unit number, flat number, or unit name.
Address Line 1 - This is a required field.
In this column, you must add the first line of the main address of the stop.
Circuit uses this column’s data to map a route. Circuit optimizes routes for drivers at street level, so make sure that Address Line 1 always contains street level data.
Address Line 2 - This is a recommended field.
In this column, add a second line to the stop address if you have one.
City - This is a recommended field.
In this column, add the city the stop address is in.
State - This is a recommended field.
In this column, add the state/county the stop address is in.
Zip - This is a required field.
In this column, you must add the zip code/postal code the stop address is in.
Country - This is a recommended field.
In this column, add the country the stop address is in
To avoid incorrectly mapped stops, we recommend accurately filling out as many address data columns as possible. However, if you do put all the address information for a stop into the column Address Line 1, Circuit is still able to map your stops.
Step 2. Input timing and delivery data
Earliest Arrival Time - This is an optional field.
In this column, you can add the earliest arrival time for a stop in 24hr clock format.
When creating a route, Circuit will make sure that the ETA for this stop is later than the earliest arrival time.
Latest Arrival Time - This is an optional field.
In this column, you can add the latest arrival time for a stop in 24hr clock format.
When creating a route, Circuit will make sure that the ETA for this stop is earlier than the latest arrival time.
Time at stop - This is an optional field.
In this column, you can add the estimated time in minutes that the driver will need to go from parking at the address to leaving again.
By default, Circuit will use the time at stop specified within your account if this column is left blank.
Notes - This is an optional field.
In this column, you can add helpful notes about a specific stop.
Notes are used for general information and can be seen and edited by admins, dispatchers, or drivers. On arrival at a stop, notes will be displayed to the driver, so adding notes can help them successfully complete a delivery.
Size - This is an optional field.
In this column, you can add size information about the delivery, such as small, large, rectangle, long, and envelope.
Recipient Name - This is an optional field.
In this column, you can add the name of the recipient.
If you have Customer Notifications enabled, you can add Recipient/Customer Name to your email/SMS notifications.
Type of stop - This is a recommended/required field.
In this column, you can mark the type of stop as either a pickup or a delivery.
By default, a stop will be marked as a delivery if it is left blank.
If you have Customer Notifications turned on, you must fill in this column because this enables Circuit to send the correct Customer Notifications to your recipients.
Step 3. Input stop priority order, POD, recipient, tracking visibility, package, seller, driver data and client ID
Order - This is an optional field
In this column, you can specify if you want stops to be placed first or last on a route.
Any stops without a specified position can be left blank or set as auto, and they will automatically be placed in the most logical position on the route
Proof of delivery - This is an optional field.
In this column, you can specify if proof of delivery is required or not required for this stop.
If you leave this column blank, your team's default settings will be applied.
Recipient Email Address - This is a recommended/required field.
In this column, you can add the recipient’s email address.
If you have Customer Notifications turned on, you must fill in this column because this enables Circuit to send the Customer Notifications to your recipients by email.
Recipient Phone Number - This is a recommended/required field
In this column, you can add the recipient’s phone number.
If you have Customer Notifications turned on, you must fill in this column because this enables Circuit to send the Customer Notifications to your recipients by SMS.
Tracking Visibility - This is an optional field
In this column you can add the level of tracking visibility you wish to provide in Customer Notifications. If you leave this column blank your account settings for tracking visibility will be used.
ID - This is an optional field.
In this column, you can add an ID number for your delivery to identify it when cross-referencing between Circuit and your own database.
If you have Customer Notifications turned on, you can add ID to your email/SMS notifications.
Package Count - This is a recommended field.
In this column, you can add the number of packages associated with a stop.
This is useful as it lets the driver know there is more than one package to be delivered to that stop.
Products - This is an optional field.
In this column, you can add information about the type of products being delivered. This could be useful for age-restricted items such as alcohol that require a signature.
If you have Customer Notifications turned on, you can add Products information to your email/SMS notifications.
Seller website - This is an optional field
In this column, you can add a link to the seller’s website.
Seller Name - This is an optional field
In this column, you can add the seller’s name.
If you have Customer Notifications turned on, you can add Seller Name information to your email/SMS notifications.
Driver (email or phone number) - This is an optional field
In this column, you can add the email address or phone number of the specific driver(s) you wish to carry out this stop. Phone numbers must be in the international format and not contain any spaces. If adding multiple drivers separate each one with a comma.
By default, Circuit will assign a driver to the stop when creating a route if this column is left blank.
Circuit Client ID - This is an optional field
In this column you can add the Client ID of a client if you have invited them to join your Client Portal. Click here to learn more about the Client Portal.
Barcode ID - This is an optional field
In this column you can add the Barcode ID of a package if it has a barcode associated with it.
Import your data without using Circuit's example spreadsheet.
If you don't want to use this example spreadsheet Circuit also lets you upload your own spreadsheet. Simply upload your data in its current format and map it to the correct columns during the import process.
Read next...
If you are using Circuit's example spreadsheet or uploading one of your own, watch our handy video on how to import spreadsheets into Circuit next.
Spreadsheet Glossary
Column Header/Title | Description | Data Type Examples |
Address Name/Flat/Building/Unit Number | The name of the stop, such as a building or business name. This is not street-level data |
|
Address Line 1 | The main address of the stop.
This must be street-level data. |
|
Address Line 2 | A secondary line of the address. |
|
City | The city the stop is in. |
|
State | The state/county the stop is in. |
|
Zip | The zip/postal code of the stop. |
|
Country | The country the stop is in. |
|
Earliest Arrival Time | The earliest time you wish for the driver to arrive at the stop. This must be in 24hr clock format. |
|
Latest Arrival Time | The latest time you wish for the driver to arrive at the stop. This must be in 24hr clock format. |
|
Time at stop (minutes) | How many minutes your driver will spend at the stop. |
|
Notes | Any information you need the driver to know about the stop. |
|
Size | Size information about the package/parcel. |
|
Proof of delivery | Specify if proof of delivery is required or not required for each stop. |
|
Recipient Name
| Name of the recipient associated with the stop. |
|
Recipient Email Address | Email address of the recipient associated with the stop. | |
Recipient Phone Number | Phone number of the recipient associated with the stop. |
|
Tracking Visibility | The level of tracking visibility you want to provide in Customer Notifications |
|
Type of stop | Marking the stop as a delivery or pickup/collection. |
|
Order | The order you want a stop to be placed in on a route eg first/auto/last |
|
ID | An external ID, order, or reference number is associated with the stop. |
|
Package Count | The number of packages or parcels associated with the stop. |
|
Products | The products that are being collected or delivered to the stop. |
|
Seller Website | A direct link to the seller's website. | |
Seller Name | You are stating the seller's name you are delivering/collecting on behalf of. |
|
Driver | The driver's email address or phone number you wish Circuit to allocate this stop to when creating the route. |
|
Client ID | The client ID generated for each client that is invited to the client portal. |
|
Barcode ID | The Barcode ID number associated with a package barcode |
|
Latitude | The Latitude coordinates of the corresponding stop. |
|
Longitude | The Longitude coordinates of the corresponding stop. |
|
How to add latitude and longitude coordinates
There may be rare cases where some addresses cannot be found, such as newly constructed homes. In those circumstances, you can use the latitude and longitude coordinates for the location instead of the address.
Download this example spreadsheet with latitude and longitude columns included.
Fill in your data, and for each stop, add the latitude and longitude coordinates OR the address field, but not both.
Got a question?
Contact your account manager, start a live chat, or email [email protected]