Palletline requests their depots to provide ETAs for the deliveries they’re executing.
​
It’s very useful for the Palletline members since syncing the expected ETA between the Palletline system and Qargo allows the end customer to view the ETA for their consignment on the Qargo customer portal.
​
This reduces the depots administrative workload, since they need to take less calls from their customers as they can just refer to the portal.
​
Palletline maintains a KPI on this for the depots, which can be viewed in Contrado:
​

When an ETA has been uploaded in Contrado, it appears in the Contrado UI like this:

ETA download
​

The ETA download will update the delivery stop start timestamp (start timestamp is updated with the retrieved ETA + the stop time is set to fixed).
​

The ETA updates are only applied if the depot is the requesting and not the delivery depot, and if the stop has not been started yet.

​

ETA upload
​
The ETA upload will send the ETAs to Contrado when the estimated start timestamp of a stop changes (i.e., when a route calculation happens, e.g. when the driver departs on delivery 1 on the trip the ETAs for delivery 2 onwards are recalculated and sent to Contrado).

The ETA updates are only exported when:

So ETAs are sent once the trip is in progress for each stop on the trip, each time the route calculation changes (i.e. when the driver departs on delivery 1 on the trip the ETAs for delivery 2 onwards are recalculated and sent to Contrado)
​
​However, while we sent them anyway they are only picked up by Contrado if there was a valid DPDV scan on the consignment before.
​
​
​