About 'stock_package_shipping_dpd'

Message Board
1

One of my customers would like to implement interconnection with DPD WebService. Perfect, a standard module exists for this: stock_package_shipping_dpd. After a few checks, it would seem (according to DPD France) that the implementation would be for DPD Germany, bad luck my customer is French and of course the WebService for French customers is not the same :frowning:

Maybe it should be indicated somewhere.

2

See Anyone using the DPD shipment module successfully?

3

I had to change 3 links in the code to make it work.

  • the loginservice (you can find this in configuration.py)
  • creating shipments (you can find this in configuration.py)
  • track-and-trace url (you can find this in stock.py)

For now I have made the changes in the module itself and after the changes everything works like expected.

4

Thank you for your feedback.

It seems to me that for France the changes will be more important.

5

As I already said, it will be good to update the module to include the configurations.

Where is the documentation?

6

Yes, I did see that :slight_smile:

WebService étiquetage DPD France - GeoLabel.pdf (1,0 Mo)

7

Indeed it is a complete different API. So it will probably simpler to create a new module.
Another option is to use Sendcloud.

8

My customer contacted DPD France directly, so I think a new module would be more appropriate. However, it’s still in version 6.0 (migration is envisaged but not at all planned). I’m waiting for his reply to see if he wants to finance this development.

9

If we were to create a new module, what name would be most appropriate: stock_package_shipping_dpd_fr?

10

I think it will be better to avoid country bound as we already see the current DPD implementation works for different countries. Here I think stock_package_shipping_cargonet seems more accurate.