Data imports and volume

This article provides an in-depth look into how Xeneta handles the volume information that we import into our database with your rate data.

How Xeneta stores volume data

Volume data points (or objects) are sorted in the our database by their validity date, their initial import date, and then filtered by company.

Additionally, we also save other relevant values such as the company ID, destination, origin, equipment type, and supplier ID. This means that each volume object is only tied to a single company within the database.

How Xeneta handles similar volume objects

When two volume objects contain similar values and are not duplicates, their volume amounts are combined and stored as a single value in our database.

For example, if two volume objects are imported with the same date, origin, destination, equipment type, and supplier ID, but have volume values of 10 and 15, we will store them as a single entry with the combined value of 25, as well as any remaining values from the newer volume object.

When there are multiple imports with similar parameters, we will choose the volume object with the newer creation date.

For example, if Import A has the volume of 50 and the volume contained in Import B equals 100 (with all other parameters being similar), the volume from Import B will be the we choose for allocation.

How volume allocation works

Allocation is the process of matching an imported rate to the origin, destination, equipment type, and supplier within the validity period of the imported volume object.

Volumes and rates are not linked initially. If there are multiple rates available, only the most recently added rate will be selected for allocation.

📘

Volume objects are stored separately and are mapped and assigned to their matching rates during the allocation process. This means that rates can be updated without affecting the currently active volume objects. When a rate has been linked to a volume object, it's considered allocated.