Watch our handy video on how to import your spreadsheet and download an example spreadsheet below.
Click here to download our example spreadsheet as a starting point
How to import your spreadsheet a step-by-step guide
Select > Create route from spreadsheet
Next drag your spreadsheet into this window or click 'Upload data from file' to browse for the file on your PC.
Accepted file formats include .csv .tsv .xls .xlsx .xlm .txt.
You will be asked if the top row of your spreadsheet contains your column names
Read our guide on preparing your spreadsheet for import if you need help with this
Next, make sure each column is mapped correctly
Click > Confirm mapping for every column that is mapped correctly
If you have imported any data that's not required, click > Ignore this column
If a column has been mapped incorrectly, you can correct it by clicking the drop-down menu, selecting the correct option, then clicking > Confirm mapping
You only need to map your columns once, as Circuit will remember these settings.
You would only need to re-map your data if you change your spreadsheet format.
Once everything looks correct, click > Continue to finish importing
You'll now see all the stops next to the map. From here, you can add drivers and create their routes.
Read next...
Click here to find out how to prepare your spreadsheet for import using Circuit's example spreadsheet, or use the spreadsheet glossary below to check that your column headers and the data you have input are correct.
Click here to learn about how to create a route.
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 Time | The earliest time you wish for the driver to arrive at the stop. This must be in 24hr clock format. |
|
Latest Time | The latest time you wish for the driver to arrive at the stop. This must be in 24hr clock format. |
|
Time at Stop | 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 | Marking the stop as a delivery or pickup/collection. |
|
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. |
|
Circuit Client ID | The client ID generated for each client that is invited to the client portal. |
|
Latitude | The Latitude coordinates of the corresponding stop |
|
Longitude | The Longitude coordinates of the corresponding stop. |
|
Got a question?
Contact your account manager, start a live chat, or email [email protected]