I just got started to implement the DPD shipping module, but couldn’t authenticate. I also got other links then the module has implemented. Even an extreme simple script using zeep didn’t work, so I’m in contact with DPD to see what I’m doing wrong.
I’m just curious if anyone is using this module successfully, what credentials are you using, did you have to create accounts etc.
The tests are using the sandbox from DPD eSolutions
On production I do not know how my customers had their credentials.
So I can conclude that the module is working correctly? The customers can authenticate and create shipment labels?
The site you mention seems a German one. Now I know why the tracking url has dpd.de instead of a .com or something more general.
I got the implementation details for the Dutch one DPD Shipper Webservices - DPD NL. But I have to wait until the I got a response from DPD about the authentication.
Indeed DPD does not have a global API. Each country has its own setup.
I got new credentials and are able to login into the DPD service. I replaced the links in the module for my links and it just works. So it seems the actual service is a global one, but each country has their own links.
So I was wondering if the links can be customized through the trytond.conf. There are 3 links:
I think the best would be to collect the possibles URLs and put them in carrier.credential.dpd as a configuration selection.