This video will give you a detailed description of how to Import Spreadsheets onto vinDISPATCH.
For bulk work you can import spreadsheets with the details of vehicles and where they need to be moved. To do this begin by selecting 'Create' - 'import spreadsheet'. You must then select an import handler from the list. If there is not a import handler listed please contact the CDN to have the import handler enabled. The CDN can create import routines to import your data or you can use our Standard Load importer.
CDN Standard Load Importer
The CDN Standard Load importer allows you to import a standard spreadsheet into the system to create Jobs / Loads. The import routine requires the first row of the csv to be the headers and for the columns to be in the specified order, if you dont want to put data in a column you dont need to but it still must be part of the csv. (,,)
Once you have received permission to download.
Go to Create - Import - CDN Standard - Download template - Open CSV
You will now have a copy of The CDN Standard Load importer spreadsheet.
Next we will go over what load data you will need to enter into each column. You will then be able to import this spreadsheet onto vinDISPATCH to create muliple loads, aswell as allocate them to the carrier and send to the relevant drivers app.
M - Manditory
O - Optional
Y - Yes
| Field Name | Mandatory | Rules / Notes |
| LoadId | M |
Unique identifier for each A to B stop. If you have a unique LoadId per row then a single vehicle load will be created. The LoadId must be unique and not reused. To specify a multi vehicle load you can repeat the LoadId in subsequent rows, all information in the subsequent rows with the LoadId must be the same except for the Vehicle information where VIN etc may be different. If you repeat a LoadId then the Pickup and Delivery locations must be the same (eg same stop for the pickup and the delivery) If either the pickup or delivery stop is different you must use a different LoadId. If you do not use LoadId's just use your own unique job number, or compose your own. |
| TripId | If you want to tie Loads to a Trip then you can specify a TripId to group Loads to a Trip | |
| ShipperScac | The Shipper SCAC code indicates the shipper of the load, if you specify this then the Shipper will get visibility of the load and the load will be created as if it had been created by the Shipper. The Shipper must grant permission for a Carrier to do this by adding the Carrier to a Network that allows members to create loads on their behalf (Setup > Carrier Networks> Allow members to create jobs | |
| AllocatedCarrierScac | SCAC code indicating the Carrer that the loads is to be allocated to. If specified the load will be created in the ALLOCATED status. If not specified job will be saved in the QUOTED status. | |
| AllocatedDriverCdnId | Sends the load to the Driver of the specified Driver remote ID. This can only be used when the 'AllocatedCarrierScac' is specified. . | |
| OrderNumber | A order number for the Job / load | |
| JobInitiator | Person or System creating the load | |
| ServiceRequired | Y | Service type (transported or driven) |
| DriverNotes | Notes to the driver | |
| CustomerQuickCode | O | Unique customer code, will use this record to store a master record, will create a new record if unknown, requires Organization, City and State to create a new record |
| CustomerContact | Customer contact name | |
| CustomerOrganizationName | Y | Name of Customers company |
| CustomerAddressLines | Address of customer | |
| CustomerCity | Y | City |
| CustomerRegionArea | Y | State |
| CustomerZipCode | ZipCode / PostCode | |
| CustomerEmail | Email address (comma separated for more than 1 email) | |
| CustomerPhone | ||
| CustomerMobilePhone | ||
| CustomerOtherPhone | ||
| CustomerNotes | Notes about customer | |
| PickupQuickCode | O | Unique location code, will use this record to store a master record, will create a new record if unknown, requires Organization, City and State to create a new record |
| PickupContact | Person for driver to ask for | |
| PickupOrganizationName | Y | Name of company |
| PickupAddressLines | Recommended for driver navigation | |
| PickupCity | Y | |
| PickupRegionArea | Y | |
| PickupZipCode | Recommended for driver navigation | |
| PickupEmail | Email address (comma separated for more than 1 email) | |
| PickupPhone | ||
| PickupMobilePhone | ||
| PickupOtherPhone | ||
| PickupNotes | Pickup location notes | |
| PickupRequestedDate | Y | Date vehicle is required to be picked up (USA - MM/DD/YYYY, UK DD/MM/YYYY) |
| PickupRequestedDateExact | Y | Pickup exactly on the PickupRequestedDate (TRUE) or available to pickup from the date (FALSE) |
| DeliveryQuickCode | O | Unique location code, will use this record to store a master record, will create a new record if unknown, requires Organization, City and State to create a new record |
| DeliveryContact | Person for driver to ask for | |
| DeliveryOrganizationName | Name of company | |
| DeliveryAddressLines | Recommended for driver navigation | |
| DeliveryCity | Y | |
| DeliveryRegionArea | Y | |
| DeliveryZipCode | Recommended for driver navigation | |
| DeliveryEmail | Email address (comma separated for more than 1 email) | |
| DeliveryPhone | ||
| DeliveryMobilePhone | ||
| DeliveryOtherPhone | ||
| DeliveryNotes | Delivery location notes | |
| DeliveryRequestedDate | Y | Date vehicle is required to be delivered (USA MM/DD/YYYY, UK DD/MM/YYYY ) |
| DeliveryRequestedDateExact | Y | Delivery exactly on the DeliveryRequestedDate(TRUE) or can be delivered by the date (FALSE) |
| VehicleRegOrYear | ||
| VehicleVin | Y | Must be at least 6 digits to be valid |
| VehicleMake | ||
| VehicleModel | ||
| VehicleVariant | ||
| VehicleLocation | Bay location or area | |
| VehicleMovementOrder | Vehicle movement order number | |
| VehicleNotes |