DHL Freight

Purpose

This page describes the DHL Freight-specific setup in Shipping Labels. It focuses on product constraints, package types, API access, stackability, and the package dimensions and weights that must stay within the limits of the selected DHL Freight product.

Prerequisites

• The shared Shipping Labels setup is complete.
• DHL Freight account number, API key, and the correct test or productive endpoint are available.
• DHL Freight product settings and package types are known from the carrier onboarding.
• Item attributes or fallback package data are available for the relevant shipment scenario.

Recommended sequence

1. Maintain or import the DHL Freight product settings.
2. Maintain the DHL Freight package types.
3. Assign account number, API key, and URL.
4. Choose the product, package type, stackability, and fallback dimensions and weight.
5. Validate the request against the selected product constraints before productive use.

Setup components

Start with the product settings, not with the final setup line

DHL Freight is strongly driven by carrier product constraints. The product settings define the allowed ranges for package dimensions, package weight, total shipment weight, volume, pieces, and loading meters.

This means the final setup line is only correct if it stays within the selected product limits.

Typical product settings include the product code and description as well as minimum and maximum values for length, width, height, weight, pieces, shipment weight, volume, and loading meters. Especially during the first setup, Business Central often opens these product settings before the actual setup line because there is no reliable product selection without that base data.

Maintain package types and carrier access together

After the product settings are ready, maintain the package types and complete the technical access with account number, API key, and the correct environment URL. The product, package type, and endpoint should always be validated as one combination.

Choose the package type only from the maintained DHL Freight package-type list. In pallet-based B2B scenarios, PAL is often relevant, but the decisive value is always the carrier-approved type for the selected product.

Keep dimensions, weight, and stackability aligned to the chosen product

The DHL Freight setup includes fallback package dimensions and weight as well as the stackable flag. These values influence whether the request matches the chosen freight product.

If the maintained fallback values exceed the allowed minimum or maximum values of the chosen product, the request can fail even though the general setup looks complete.

Check the fallback fields individually against the selected product. Default length, width, height, and weight must stay within the minimum and maximum values. The same applies indirectly to the number of pieces, shipment weight, volume, and loading meters whenever the scenario uses those limits.

Use carrier-defined product data without reinterpretation

The product settings and package types should be taken over from the carrier as they are. This is especially important when different products differ only by freight-specific thresholds or logistics rules that are not obvious from the name alone.