eLogii offers different types of codes and IDs that serve various purposes. They are the following:

These codes are automatically generated by eLogii, and serve as unique identifiers for each entity (Tasks, Teams, Users, Drivers, Vehicles, Customers, Customer locations. Depots, Routes, and Items.). UID stands for Unique Identifier and is a series of numbers and letters that refer to specific data in the dashboard. For example, Task UID, allows differentiating between Tasks as each of them upon creation or import gets a unique number automatically that cannot be changed. If you import Drivers, (or any other entity) delete them, and import the same file, even though these Drivers are the same people as the deleted ones, they will have different UIDs. The same logic applies to all entities.

The UID can be found/added in Tasks ⇒ Task Profile ⇒ Details ⇒ UID.

These are user-generated codes assigned to Tasks and Items on import or during Task/Item creation. Barcodes can be added retroactively after Task creation by populating the Barcode / product code field, or they can be added to the CSV file if the Tasks are being imported, under the column productCode. Barcodes can be added for Tasks and Items and can be used alongside Labels.

The barcode can be found/added in Tasks ⇒ Task Profile ⇒ Details ⇒ Product Code / Barcode.

References are generated by users and are usually used to reference entities between eLogii and other external systems. They do not need to be unique values.

External IDs, similarly to references, are generated by users, and are usually used to reference entities between eLogii and other external systems, however, these need to be unique values.

The reference and external ID can be found/added in Tasks ⇒ Task Profile ⇒ Details ⇒ Reference / External ID. Drivers, Vehicles, Users, and Teams can also have external IDs and references.

Identity tracking codes are automatically generated by eLogii for both pickup and delivery. They are used to access the Tracking page, as an additional layer of security and authentication to prevent data theft and to protect the recipient's personal information. These codes can be found in the tracking link URL.

This code is usually sent via email or SMS notifications and is auto-populated once you click on the link from the message,
​

In case someone unauthorized is trying to get information about the recipient's location, number, and identity based on their tracking code, since they wouldn't be accessing it from the tracking link, they would be required to enter the appropriate code.

The identity tracking code can be found/added in Tasks ⇒ Task Profile ⇒ Details ⇒ Tracking codes.

Data update - UIDs, References, and External IDs are often used for updating data via CSV. eLogii matches the existing data based on any of these 3 fields, and that's how it knows which entities it needs to update. For example, if you would like to update some of the Drivers' schedules, you would need to tell eLogii which specific Drivers you want to update schedules for. This can easily be done by specifying either the Driver UID, Reference, or External ID. In case you don't use references or external IDs, you can export the UIDs of the Drivers whose schedules you'd like to update and use them in the import file.

Merging data - In case you need to merge multiple Tasks into multiple Items under one Task, you can do that by grouping them on import based on the same reference.

API Communication between any external system and eLogii - UIDs, References, and External IDs can also be used to cross-reference data between eLogii and any external system you use for planning.