Configuration & FAQ (English)

The products have no weight set, so Odoo will not build a package. Either set weights on the products, or rely on the carrier's Default weight (kg) field, which is sent when the parcel weight is 0. Note that an inaccurate declared weight can lead DHL to re-weigh the parcel and adjust the invoice.

The parcel type is fixed by the shipping method. Each method represents one DHL parcel type (Mailbox parcel / Parcel up to 10 kg / ... / Pallet up to 1000 kg), so the type is decided when you (or the customer) pick the method. Create one shipping method per type you want to offer. A regular parcel maxes at 31 kg; above that, use a Pallet method.

For shipments that mix parcel types in one delivery (like the DHL portal supports), create a method with Parcel type = Mixed (MIX). On deliveries using that method a DHL Parcels tab appears where you add one row per parcel, picking the type per row. The type list adapts to whether the recipient is a private person or a business.

The DHL Parcel API does not return live rates, so the price is set on the carrier itself. Choose Pricing mode = Flat and fill in DHL flat price, or Pricing mode = Weight-based rules and define the tiers on the Pricing tab (use weight as the variable). The generic "Fixed Price" field of the base carrier is not used by this provider.

A shipping method is filtered by company: its Company is inherited from its delivery product, so you can't change it on the carrier directly. If the delivery product has a company set, the carrier only appears for that company's deliveries. Fix: open the delivery product and clear its Company (blank = all companies), or set it to the company you ship from. Destination country also matters: the method only offers itself for the countries listed on the carrier.

The module filters DHL carriers in webshop checkout by the recipient's private-vs-business status, on top of Odoo's standard filters (published, website, country, price-availability). The filter mirrors the backend Add Shipping wizard so the same set of carriers is offered everywhere.

Concretely, a carrier built around a consumer-only parcel type (Envelope 50 to 500 g, Mailbox parcel) is hidden from business customers, and a carrier built around a business-only parcel type (Pallet up to 1000 kg) is hidden from private customers. The three "Parcel up to X kg" types (10/20/31) have no recipient restriction and show for both.

If your customers report "no DHL option appears", check whether you have at least one published DHL carrier that fits the recipient kind they are. The safest setup for a webshop serving both audiences is one carrier with a "Parcel up to X kg" type (no recipient restriction); add Envelope / Mailbox / Pallet variants on top of that if you want a richer offering, knowing they auto-hide for the audience they do not fit.

Check that Integration Level is set to Get Rate and Create Shipment. With "Get Rate" only, no label is created on validation.

Nothing, for this provider. DHL Parcel uses a single API address for both test and production. Whether you are in test or live depends only on which API key you enter.

Set the Delivery Method field on the customer (Contacts → customer → Sales and Purchase tab). New orders for that customer then default to it. There is no single global default for all orders without customization. For webshop orders the customer chooses the method at checkout.

Odoo creates a separate delivery per warehouse, and each becomes its own DHL shipment with its own correct sender address. A single label can carry only one sender, so different warehouses always mean different shipments.

On a DHL delivery there is an Number of parcels field. Set it to the number of identical parcels you want to ship; the module sends one DHL shipment with that many pieces, all of the carrier's parcel type. DHL returns one tracker per piece and one combined multi-page label PDF. No need to use Put in Pack when all pieces are the same type.

Enable the Packages feature: Inventory → Configuration → Settings → Operations → Packages, then save. The button appears on the delivery afterwards.

Odoo packs by quantity. In Detailed Operations, set the quantity only on the lines for the first box (set the others to 0), click Put in Pack, then set the remaining lines and Put in Pack again. Each Put in Pack bundles whatever currently has a quantity and is not yet packed.

That is fine; package type is not used by this module. The DHL parcel type is fixed by the shipping method.

Use native Put in Pack: split the quantities so the items for box 1 are "Done" first, click Put in Pack, then set the remaining quantities and Put in Pack again. Each package becomes one piece in the DHL shipment, all of the carrier's parcel type. Each piece gets its own tracking code, and all labels come back in one multi-page PDF attached to the delivery. When you don't care which items go in which box, use the Number of parcels field instead (simpler - one click).

All 31 European destinations covered by DHL eCommerce Benelux. See "Which destinations does the module support, and how is the DHL product picked?" below for the full list and product resolution logic.

No. DHL's parcel-type catalog is the same regardless of recipient; the business-versus-consumer difference is handled by the product DHL selects automatically (a home-delivery product for consumers, a business product otherwise).

In the DHL portal - there is no programmatic alternative. DHL's public API has no cancel endpoint, only a read-only GET /intervention-options that reports whether a cancel would be allowed. The module's cancel action posts a note on the delivery (with the tracking reference still readable so you can look it up in the portal).

Note from DHL: a label that was created but the parcel never entered DHL's network (i.e. you cancelled before drop-off) is not billed. You only need to cancel in the portal if you want the shipment removed from your MDP shipment list for housekeeping.

Yes for production keys: shipments created via the API show up in the DHL portal under your account, exactly as if you had entered them manually. Sandbox shipments do not appear in the production portal (that is the whole point of sandbox: labels are generated and tracker codes returned, but the parcel never enters DHL's network and is not billed).

No, and it cannot: DHL Parcel's public API has no address-book / customer endpoints. The "save customer" tickbox in the DHL portal is a portal-internal feature that only matters when you enter shipments manually through the portal UI. In our flow, Odoo's res.partner records are the customer database: each delivery sends its receiver address straight from the partner to DHL, so there is no need for a second copy of the address living in DHL's portal. The tickbox can safely be ignored when using this module.

There are two steps: first DHL has to enable API access on the account, then you create the actual keys in the portal.

1. DHL grants the API role on your account. API access is not part of a standard DHL eCommerce Benelux contract. Before any API Key can be created in the portal, your DHL contact (or DHL eCommerce support) has to assign the API role to your account. This is a manual action on DHL's side - you cannot trigger it yourself. Mail your DHL account manager with your customer number and explicitly ask them to enable API access on the account so you can create API keys via the portal.

Until that role is granted, the DHL portal shows only a "Connections" page and no API Keys section. That is the signal that step 1 is not yet done.

2. Create the keys in the portal. Once DHL confirms the role is active, log into the DHL portal and go to Settings → API Keys. Copy the User ID and API Key shown there. The Account ID is the short customer number visible on invoices and in your account details.

As of module version 17.0.0.8.8 the three credential fields (User ID, API Key, Account ID) are restricted to a dedicated group DHL Parcel Administrator. Odoo administrators are added automatically. Other users who need to set or read those fields must be added to the group manually: Settings → Users & Companies → Users → [the user] → Access Rights → tab Other → DHL Parcel Administrator. Members of that group retain their regular access to everything else; the group only unlocks the credential fields.

Non-members can still create, edit and use DHL Parcel carriers - they just don't see the credential fields on the form and cannot read them via XML-RPC/ORM. All internal reads by the module itself use sudo(), so day-to-day operations (validating deliveries, printing labels, Test Connection triggered by an admin who did the setup) work independently of the operator's group membership.

The module supports outbound from BE / NL / LU to 31 European destinations. The Countries dropdown on the carrier is filtered to that list (and further narrowed by parcel type: Envelope = NL only, Mailbox parcel = BE + NL, other parcels + Pallet = all 31).

For each shipment the module resolves the correct DHL product from the destination country and the recipient type (business / consumer):

• Benelux (BE / NL / LU): blank product code; DHL resolves DFY / Europlus / Parcel Connect automatically at their side.
• Non-Benelux EU: CON (Parcel Connect) for private recipients, EPL-INT (Europlus International) for business recipients.
• Non-EU (post-Brexit UK, Switzerland, Norway, ...): CON2C (Parcel Connect 2C) for private, EPL-INT for business. A bulk customs declaration is added to the request automatically.
• Pallets (Pallet up to 1000 kg): EPL-PAL (Europlus Pallet).

Use the Verify Contract button in the Contract check section of the DHL Parcel tab on the carrier. It queries DHL's /products endpoint for every enabled destination country + relevant recipient type, and reports whether the product this carrier would use is actually active on your DHL contract. Countries flagged NOT IN CONTRACT will fail at label creation; ask DHL to activate the missing product, or uncheck those countries on the carrier. It is a read-only call - nothing is shipped and nothing appears in the DHL portal.