Currently the DPD Belux standard accepted data format is GeoDATA V3.3.2
- MPSEXPDATA 1.13.X for general use
- MPSEXPDATA 1.13.20 for UK Shipments
- CRDATA01 1.9 and above for collection requests
- PICKUPDIFF 1.X for pickup assignments
- MPSEXPDATA 1.X => GeoDATA 3.3.2 SHPNOT
- CRDATA01 => GeoDATA 3.3.2 COLREQ and COLANS
- PICKUPDIFF => Integrated into GeoDATA 3.3.2 SHPNOT
Currently the DPD Belux standard 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
As a legacy format MPSEXPDATA is also still accepted by DPD Belux. Our internal datahub ingests the records and translates them into GeoDATA V3.3.2 for further DPD internal and network use.
Allowed legacy formats are:
We do encourage adopting the GeoDATA format and specifications because it allows for specific services being used and more valuable detail entry options overall. We do not allow any more onboardings in the legacy format as of 2021.
Succession to the legacy formats :
If you would like to check the difference and mapping, please refer to following MPSEXPDATA-GEODATA translation tables:
graag een “+” uitschuif per segment (sender, parcel, inter, msg, …) en zodat de file hier niet te donwloaden is
The full GeoDATA specifications can be found here, they contain the needed segments to allow for collection requests and pickup orders.
By default DPD does not accept any other EDI formats, nor does it facilitate translation. It is however possible to contract a 3rd party integrator who will translate your own EDI format into the DPD format and maintain compliance by SLA. This is a common practice which we recommend.