Maintaining an up-to-date Integration

Maintaining an up-to-date integration is your responsibility

  1. GeoData

    The data requirements are related to version. Currently the DPD Belux accepted data format is GeoDATA V3.3.2 , a file based EDI which contains around 600 mandatory, optional or conditional value containers divided over 23 subtypes, arranged in 5 ranks. EDI always needs to mirror exactly the printed label and used routing codes.

    Data versions are unlikely to ever change frequently but can happen and there will always be limited backwards compatibility provided by our datahub and Business Intelligence. However, only the most recent version use will ensure you are able to use all DPD offered features.

    In case of a new data format coming into standard use, you will be notified and you can assess whether it is mandatory or optional for your integration to adopt the new version.

    At all times self-integrated customers are fully liable and responsible for providing correct data format and contents to the agreed upon drop-off location. Currently an SFTP setup is standard and FTP is no longer allowed.

  2. GeoLabel

    The label format is issued by GeoPost and DPDgroup as part of the international standards.

    Label versions are unlikely to change frequently and there will always be limited backwards compatibility.

    In case of a new label format coming into standard use, you will be notified and you can assess whether it is mandatory or optional for your integration to adopt the new version.

     

  3. GeoRouting

    The routing requirements are related to version and change frequently, in time they may even change version daily.

    You can automatically check-download-update the DB from the SFTP location and make sure you are calculating the routing using the latest version. Your designated SFTP download location will be given by the CIT department and will remain fixed.

    • If you are a single-BU integrated customer, you will be provided with the ‘CustomerRDB’, a deducted routing database from the full network GeoRDB, only suited for one BU.
    • If you are a multi-BU customer or an integration partner, you will needmultiple ‘CustomerRDB’s’ from multiple locations (other BU’s)

    All versions are numbered upon release and can be recognised by the following syntax: ”YYMMDDVV” (Y=year, M=month, D=day, V=version). The closest to day version available on the SFTP is the only viable DB. The desired frequency of checking for updates from your end is  24 hours.

    Routing is the most essential part of self-integration with DPD to keep aligned. Failure in this area will result in delayed or returned parcel and surcharges due to re-labeling.

Was this post helpful?(Required)