To get started in Detrack, a crucial step is to get your jobs imported into Detrack based on your desired job fields terminology
In Detrack, you can customize how your job data appears by mapping Detrack fields to your own internal terms. This ensures your job data in Detrack looks familiar and works seamlessly for your team, be it whether you’re importing job details or exporting delivery completion data
Let us run you through the 2 steps in importing your jobs successfully
Importing your jobs into Detrack (Excel/CSV)
Customizing your job fields with Field Mapping
Detrack’s field mapping feature makes it easy to align Detrack with your workflow and terminologies
Field mapping enables you to rename Detrack field names to match your internal terms. For example, if Detrack uses Address but your organization calls it Delivery Address, you can map the two fields so everything feels consistent and easy to understand.
Let us guide you on how this works:
1. Rename Detrack fields to match your internal terms
1.1 Name Your Fields
You can rename each field in Detrack to match your internal terms by going to Settings > Jobs > Fields. The Customized Header column is where you add your internal naming conventions
For Example:
You can rename Detrack’s default header of Date in Detrack to Delivery Date
You can rename Detrack’s default header of Address in Detrack to Delivery Address
2. Understanding the types of Detrack Fields
Detrack has over 100 fields that can utilize to cater to your workflow. Fields can be renamed and displayed across various touchpoints in Detrack. (Learn more about Detrack fields)
When using Detrack, you will primarily work with 2 types of fields, namely import fields and export fields
2.1 Import Fields
Import fields are job details you upload into Detrack that is provided to your drivers during a delivery/collection, such as:
Address
Date
Recipient name
Delivery Instructions
These details are typically uploaded into Detrack via an excel/csv file, created manually through a job form or via API integration with any upstream system you may have
2.2 Export Fields
Export fields are job details collected by your driver during job completion on the driver app, such as (eg. time of completion, driver notes, failed reasons, driver inputs such as weight, temperature and actual quantity)
Time of POD submission
Job failure reasons
Driver inputs such as weight, temperature or actual quantity
3. Decide where you want to display your customized fields
You can decide how you want to display your mapped fields to your drivers, internal users and your end customers.
These fields can be displayed across various touchpoints such as the
Jobs Table (Learn more)
Driver App
Proof of delivery PDF (Learn more)
Run Sheet (Learn more)
Tracking Widget (Learn more)
Job Export File (Learn more)
2) Importing your jobs into Detrack
When importing jobs, these are the key fields that need to be specified clearly in the job file
Field | Description |
Detrack Job Type | Either Delivery or Collection |
Date | Date to perform the job |
D.O. No. | Unique identifier for the job |
Address | Location to perform the job |
The default date format is YYYY-MM-DD. To select other formats, navigate to Settings > Job Options > Import Date Format.
To import jobs across multiple dates:
Click on Jobs > Import Jobs.
Select your file for import.
Click Import.
The results will appear in the Import Results section.
USE OF COLLECTION HEADERS
By default, the headers settings will take reference from your Delivery settings for importing.
If you wish for the systems to separately take the Delivery and Collection headers for importing your file, navigate to Settings > Collection > Switch on Use collection headers for cross date import > Save.
Thereafter, when the Detrack Job Type (either Delivery or Collection”) is being specified, it will take reference from the Delivery or Collection headers respectively.