You can download a sample file when you create a route plan. However, there is no specific format the file needs to be in.
To make sure stops are imported correct, check the following:
The first column should not be empty
The first row should only contain column names
Avoid special formatting and formulas
Avoid multiple sheets in the same file
The Supported file types are .csv / .xls / .xlsx
📝 : Google Sheets are not supported as of now. But you can still download the Google Sheet and upload it as a CSV or an Excel
Use Excel or a CSV file
When using excel, make sure you do not have data using formulas
The first column and first row should not be empty
The first row should always contain the names/titles of the columns.
Let's learn more about what the columns are:
It is the essential piece of information you need to import the file and optimize the stops.
As shown above image, the addresses can be in several ways. You can have the address broken down into Address, City, Region (State), Zip Code, and Country or simply write the full address in one cell. As long as the address is correct, the import should go smoothly.
📝 Are some addresses incomplete or incorrect? Try to find the full address or import "as-is" Upper import will try to find the correct address or suggest you check the specific addresses out.
Building Name/Apartment/Unit number
The unit number in the above example is only there for your reference. The Upper address validator may or may not pin the exact unit number depending on the availability of the data. Upper will try to pin the exact building addresses instead.
Service Time: This estimates the time the driver will spend at each stop, from parking to delivering or picking up and returning to the vehicle. These estimates are crucial for the correct ETAs at each stop. You can have either an average Service time for all stops or individually give different service times. Example: Building deliveries will take more time vs curbside deliveries.
From: This will determine how Upper optimizes the stop concerning when you want to be at an address at the earliest.
To: This will determine how Upper optimizes the stop concerning when you want to be at an address at the latest.
The notes field lets you add a string of information about that particular stop. It could contain information like buzzer codes, delivery instructions, etc.
This will help the driver save time moving back and forth to his physical notes.
You can add customer information like Name, Business/Company Name, Phone Number, and Email.
Name, Business/Company name could be any information you want particular to your business processes. You can use them as additional info fields instead.
The Phone and Email field, however, will be helpful for the customer notification feature that Upper offers.
Full Name and Business Name: This is the Name of the customer and their business (Both fields are optional)
Phone: Phone number of the customer. Preferably a mobile phone number if you want to use the Customer Notification by text message. The recommended format for the customer phone number is +14374887337
📝 +1 is necessary to determine the correct country code, and there should not be any spaces or special characters between numbers.
Formats not accepted:
+1 437 488 7337
437 488 7337
Or any variation of the above.
Email: Ensure the email is correct if you want to send the customer notifications via Email.
Stop Type and Parcel Count
You can let the Upper route planner know what type of stops each address is and how many parcels the driver needs to pick up or deliver at each address.
The Stop Type can be Delivery or PickUp. By default, Upper plan the routes with Pickups in Between Deliveries. But you can always select the optimization either Pickup before or after deliveries.
Custom Fields: You can also have up to 5 custom text fields available for you to toggle on from settings and use across the Upper system. Import, add stops, driver app, export, etc.