EN DPD Georouting

At the beginning of the year, DPD announced that there would be a comprehensive change in the so-called "georouting" at the turn of the year 2022/2023.

With the beginning of 2023 there will be no possibillity to create DPD Labels anymore with the "old" routing.

DPD has put together a page with information on this.

https://www.dpd.com/de/de/support/it-anbindung-und-dpd-schnittstellen/georouting-transformation-gr-gl/

What does this change mean for the user of HVS32?

If you are currently using HVS32 for creating your DPD labels as your service provider, the previously known process of route updates will change. You can continue to use the HVS32 "offline" solution with the new Georouting process, as we will be certified by DPD.

There will also be the option of connecting the DPD web service in the HVS32 with a corresponding plugin which would make the routing import process no longe be needed.

On this page we would like to describe to you in detail what will change or could change becasue of this adjustment of DPD.

Changes in process and options

So far, DPD route updates have taken place every 4 months on the relevant date. With the change in routing, it will be necessary to check the routes once a day, so it would be possible that daily route updates would also have to be provided by DPD and downloaded by the sender. Another change will be that there will no longer be separate route files per depot, but one global route file for all depots. The new georouting format will then contain about twice as many route entries in a route file (compared to a depot-related old file format). Thus, the import process of the routes will be correspondingly longer or shorter if you have more than 3 depots in use.

A regular update interval every 2 months is currently planned by DPD, but DPD reserves the right to provide unscheduled updates at any time between an update interval, whenever it should be necessary.

HVS32 generally prints the labels according to the loaded route status, there could be delays in delivery if outdated routes are used or additional charges by DPD, but DPD has not given any more details on such cases at the moment.

The process of RELABELS will be omitted.

You can register for our newsletter under the following link, where we will also regularly provide new information: Newsletter Registration

Depending on the configuration of your HVS32 installation, the following options are available to meet the requirements:

Option A: manual trigger/initiation in the HVS32 for the route update

There will be the possibility to check manually via any HVS32 station whether there are current routes. If the check is positive, the route import begins. During this time, the station is occupied by this process and DPD shipping can take place during this time. However, we recommend starting the import from the HVS32 server.

Option B: an HVS32 station checks whether there are current routes at each restart

Each time the station is restarted, DPD checks whether there are new routes and imports them if necessary. During this time, the station is occupied by this process and DPD shipping can take place during this time. However, we recommend starting the import from the HVS32 server.

Option C: Using an automatic polling loop

The "Automatic Polling" extension module (automatic printing of shipping labels) can be used to check for new DPD route updates at specific times. The automatic polling cannot carry out any other actions such as import, label printing or daily closing at the same time.

Option D: Monitoring Light (additional background service)

An additional HVS32-Monitoring instance/service checks for new route updates and imports routes at defined times.

You may incur additional licenses and configuration work.

Option E: Connection to DPD web service

Conversion of the HVS32 "offline" DPD route determination & label printing to the connection via DPD web service. This would eliminate the route update process as in option A-D, since when using the DPD web service, the label and all necessary information are retrieved from the DPD web service and then processed via HVS32 according to their process. You may incur additional license and configuration work. In addition, please note the general web service requirements/variables (Internet speed, latency, availability, overloads,...).

The following limitations have been released by DPD regarding the webserivice:

• max 60 deliveries/requests per minute
• max 10.000 deliveries / requets per day

individual lableslayoust are not possible anymore

If you want to switch to the webservice you can open a call on the dpd side under [[1]] with you customernumber.

The webservice solution will be available on our side at the beginning of october. Please contact us under support@heidler-strichcode.de if you are interested in a switch to the DPD webservice.

Changes on the DPD Labels

The DPD label will change as seen in the screenshot on the right side.

If you are currently using individually customized labels then this layouts will be disabled with the HVS32 update. A automatic adaption of the layouts is not possible.

Because of the new georouting update there will be no individual logos and other parts anymore on the standard label size. If you are using extend labels, for example length over 200 mm, the individual parts on this labels can be continued to use.

Please contact our Support to transport those parts on the new labels. In addition you have to contact your local DPD Depot to clearify those individual labels.

HVS32 Update and Commanager

As soon as our certification with DPD has been completed, we will publish the HVS32 program version which is needed for the update.

A HVS32 Update is then required for activation/conversion. You will then receive the current version as usual from our support at support@heidler-strichcode.de.

In addition, the Heidler Commanager (at least version 1.2.0.114) is required, if you use the HVS32 "offline" version, which acts as a central service for data transmission to the carrier. With these DPD route changes, the Commanager is then also used to download and check the routes.

If you have not yet switched your EDI transfers to the ComManager, this should take place before the DPD switchover. Also if you still use the outdated ftp protocol, you also need to switch the your EDI communication to SFTP. Please contact cit@dpd.de, so DPD can start the process for the ftp / sftp change.

If you want to use option E and change you setup to the webservice, you onle need a hvs32 update.

Required Data

Access data or similar are not required for the DPD route download. You must ensure that the ComManager then requires approval according to your firewall constellation in order to download the DPD route files via the https download links published by DPD.

General link:

https://esolutions.dpd.com/partnerloesungen/rdbdistributionservice.aspx

Version dependent link:

https://esolutions.dpd.com/partnerloesungen/rdbdistributionservice.aspx?version=22070402

If you still using the old FTP protocol for transmitting the SFTP EDI, you need to contact DPD cit@dpd.de for your new SFTP account.

If you want to make a change to the DPD Webservice, you need to contact DPD cit@dpd.de for your webservice account.

Possible workflow of the adjustment

1. HVS32 Update (Version / Release still pending)
2. ComManager Update to Version 1.2.0.114 or higher
3. change of the EDI upload from FTP to SFTP (if needed)
4. configuration of the whole new routing process via the heidler support
5. licensing and configuration of the needed components (Option C, D, E)
6. message / info to DPD from you that the change has been made
7. GoLive with the new georouting setup

Our Support supports you with all the above mentioned points

Final conversion / certification / acceptance

Because of the general certification of HVS32 by DPD, there will be no need for a label approval after the change.

It is sufficent after the change to wirte an email to cit@dpd.de with you customernumber.

Deadline: End of 2022

The change has to bee done by the end of 2022. With the start of 2023 tehre will be no possibillity anymore to use the old setup / routing anymore.