In Portal you can see an Estimated Time of Arrival (ETA) in the Shipment Viewer whenever the information is available.
Examples showing different ETA information:
ETA information is available from a number of different sources and we will check each source for information in the following prioritized order:
- ETA from return data
- ETA from webservices
- ETA from carrier performance (XML)
- ETA from reference fields in On-premises
- ETA from delivery reference fields in On-premises
- ETA based on AI
1. ETA from return data
First source of ETA information is the return data received from carriers. If we receive information about delivery time together with status events from a carrier, this will be displayed in Portal.
Not all carriers support return data with ETA information and some carriers require that return data is ordered and activated for the individual customer.
2. ETA from webservices
If no ETA information is available in return data, we will check the fields Reference Carrier ETA Start (kind id 329) and Reference kind 330 (Carrier ETA End) . These fields are not visible to the end user but will be populated by information received from carrier webservices like shipment booking, routing codes and price calculation. Only information in ISO format is supported.
3. ETA from carrier performance (XML)
Many customers have an SLA (Service Level Agreement) with their carriers about transit times for given products, e.g. delivery within X days or within a delivery window. If you have an SLA with your carriers, you can get reports from Portal showing you how many shipments are delivered according to the SLA. As a part of the carrier performance setup, Portal can show ETA based on your agreement with the carrier.
Read more about carrier performance and how to order it here.
4. ETA from reference fields in On-premises
The reference fields Carrier ETA Earliest Arrival Time (reference kind ID 292) and Carrier ETA latest Arrival Time (reference kind ID 293) available in On-premises import can be populated with data from a carrier ETA setup, Shipping Rules or by the customer's import files. Portal will look for data in these fields if no data were available from priority 1-3.
5. ETA from delivery reference fields in On-premises
Priority 5 is the delivery reference fields Delivery date start (reference kind id 10) and Delivery date end (reference kind id 11).These fields can be populated using import or manually in the production view.
6. ETA based on AI
Using AI, machine learning, and data from similar shipments, the ETA (Estimated Time of Arrival) feature in DeliveryHub predicts a realistic estimated arrival of the parcel. This ETA will be used when no other ETA is available and only on supported products. (see availability). If the product and destination supports AI based ETA, it will automatically be available. No activation or setup needed.
AI based ETA is currently available on the following products:
|Bring||Bedriftspakke||From Norway to Norway|
|Bpost||Bpack 24h Pro||From Belgium to Belgium|
|DHL||DHL Paket||From Germany to Germany|
|DHL Ecommerce||Parcel Plus Expedited Max||From the US to the US|
|Hermes||Home Delivery||From UK to UK|
|Post NL||Normal Package||From the Netherlands to the Netherlands|
|UPS||UPS Standard||From Belgium to Germany|
|UPS||UPS Ground||From the US to the US|