Ship with DPD directly from Odoo — no more portal double-entry

If your business runs on DPD as its core carrier, you already know the pain of the disconnect: orders live in Odoo, but every parcel has to be re-keyed into MyDPD or the DPD shipping portal to get a label. Addresses get mistyped, Predict notifications go out inconsistently, tracking numbers never make it back to the sales order, and your warehouse team wastes hours copy-pasting between two systems.

The DPD Shipping Connector for Odoo closes that gap. It is a build-to-order module that ECOSIRE designs, develops, installs and supports specifically for your Odoo database — not a generic download. We extend Odoo's native delivery.carrier framework with a dedicated DPD provider so that generating a label, buying a rate, triggering a Predict notification and syncing tracking all happen inside the delivery order you already work in.

Because this is a bespoke build, the connector is fitted to your DPD account, your service codes (Classic, Next Day, Two Day, DPD Local, international Air/Road), and your Odoo edition (Community or Enterprise, versions 17.0, 18.0 and 19.0). We wire it into your real warehouse flow — from Inventory stock.picking validation through to the customer's tracking email.

What "build-to-order" means here

This is not an instant apps.odoo.com download. After purchase, ECOSIRE runs a short discovery, builds the module against your Odoo version and DPD credentials, tests it end-to-end in a staging database, and deploys it to your production server. Typical lead time is 2–4 weeks depending on the number of DPD services and the depth of automation you need. You receive the full module source — a proper Odoo addon with __manifest__.py, Python models, ir.model.access.csv security, XML/OWL views and QWeb label/manifest reports — so you are never locked in.

How it works under the hood

• We add a DPD delivery provider to delivery.carrier (a new delivery_type selection), so DPD appears as a shippable method on quotations, sales orders and delivery transfers exactly like Odoo's built-in carriers.
• A dedicated dpd.account model stores your credentials, depot and Geo-session token, refreshed automatically via a scheduled ir.cron job so authenticated calls never fail mid-shipment.
• Rate quoting calls the DPD pricing API when a carrier is selected, returning a live shipping cost that flows onto the sale order line — no guessed shipping charges.
• On picking validation, a send_shipping() implementation calls the DPD label API, stores the returned parcel number(s) and label PDF as attachments, and writes the tracking reference back onto the stock.picking and its sale order.
• Predict / notification payloads are populated from the partner's phone and email so your customers get DPD's one-hour delivery window SMS/email.
• A tracking sync ir.cron polls DPD for scan events and updates delivery status, with a customer-facing tracking link surfaced on the portal.
• Errors from the DPD API are caught and shown as clear Odoo UserError messages (bad postcode, missing phone for Predict, service unavailable) instead of silent failures.

Everything respects Odoo multi-company and multi-warehouse. Access is controlled with ir.model.access.csv plus record rules so only shipping and warehouse users can generate or cancel labels. The connector exposes its actions over Odoo's XML-RPC/JSON-RPC layer too, so an external WMS or marketplace bridge can trigger DPD labels programmatically.

Built for UK and EU DPD shippers

We know DPD's UK and European nuances — depot codes, PredictID, mandatory phone numbers for Predict, customs data for GB↔EU parcels post-Brexit, and the difference between DPD (parcels) and DPD Local networks. The build accounts for the services and countries you actually ship to, and we hand it over documented and supported.