Outline
Introduction
Importing orders can be a complex process. To ensure the accuracy and cleanliness of the data, validation layers are used to verify that every order is correctly matched to the correct destination. In countries where the addressing system is not postal-based, geocoding becomes even more important as it requires sophisticated algorithms to accurately match a fuzzy address to a specific location. The importance of these algorithms is magnified in these circumstances.
Import Types:
Integration via our open API, http://docs.fleetrunnr.com
Importing via excel or csv file
How to guide: Importing via excel or csv and Validating orders on FleetRunnr:
Start by clicking on the three dots on the top right corner followed by “Import orders”.
2. Upload file: choose which file you would like uploaded, either as CSV or XLXS format. (You can also download the sample file for reference).
3. Configuration: choose the appropriate order workflow either Standard, Return, or Internal followed by the relative source or destination location.
Standard: Use this workflow to deliver orders to customers.
Return: Use this workflow to pickup orders from customers.
Internal: Use this workflow to move orders between your locations. (No customer is required)
4. Field Mapping: map your existing import file with the fields required on the FleetRunnr portal. (If the column names on the import file match the names on the sample file, the mapping will be done automatically)
5. Summary: in this section, FleetRunnr will validate if there are any issues with the inputs such as wrong phone number format, wrong use of seperation character if multiple values are present, wrong input for required POD, etc.
If validation issues are present, you will be able to download the invalid orders, view the reason of failure and perform the necessary changes while also proceeding with the import of the successful orders.
6. Address Validation: after successfully importing the orders that have no format validation issues, you will be able to monitor and take action on orders that potentially have wrong or invalid addresses.
New: orders marked as “New” means that no address validation issues are found
Draft: orders marked as “DFT” means certain address validation issues are found
Adress Validation Issues:
. No geocoding results: The address is extremely “fuzzy” or incomplete the geocoder did not return any results
. Inaccurate geocoding results: The geocoded address falls outside the region inputted in the import file
. Multiple geocoding results: The geocoder returned multiple results
By applying filters, you can easily search for the Draft orders along with the type of address validation issue.
As a portal user, you have the ability to review and take action on draft orders. For example, if the original address and the geocoded address differ, you can choose to edit the address or validate the results. Example, you have an original address 2275 Quadra St, Victoria, BC V8T 4C4, Canada, Surrey, while the geocoded address is 2275 Quadra St Victoria, V8T 4C4 , British Colombia (The original address is in Surrey, while the geocoded address is in British Columbia). You can update the address or confirm that the geocoded address is correct.
Bonus: Keeping your customers and drivers in the loop about address validity.
Customer tracking URL: Customers are the backbone of any organization, and keeping them aware about every step in the delivery operation is crucial in maintaining a low customer churn rate.
FleetRunnr provides your customers with a tracking link that constantly updates based on real-time information such as driver idle times, traffic, breaks, and much more. Notifications are sent out to customers for updates regarding the entire delivery lifecycle (first, middle and last mile). Customers can view accurate and dynamic ETAs and have the ability to update both addresses and time windows.