Address Format and Routing Codes

Correct address data is the invisible foundation of every successful DHL shipment. Sorting facilities, delivery depots and Packstation routing do not work with "approximate" addresses, but with machine-readable structures and precise routing codes. Errors in name, street, postal code or additional fields lead to delays, forwarding, returns to the warehouse and avoidable support effort. For fulfillment teams, the address format is therefore not a side issue, but a central quality lever – regardless of whether you frank in your own warehouse or ship via a 3PL system.

This guide explains how DHL processes addresses technically, which format applies to home addresses, Packstations and branches, and how you can secure routing codes in shop, WMS and carrier interface.

What routing codes mean at DHL

Routing codes refer to the automatic assignment of an address to a delivery district. DHL uses the postal code, street name, house number and – for Packstations – the Packstation number as well as the recipient's Postnummer (customer number). The system compares the transmitted data with reference databases. If postal code and city do not match or mandatory fields are missing, the shipment cannot be routed reliably.

Routing codes are applied in several stages:

• 001. Entry in shop or ERP – Customer or employee captures the delivery address.
• 002. Validation before label printing – Address check via DHL interface, CSV import or manual plausibility check.
• 003. Sorting at DHL hub – OCR scan of the label, comparison with routing code data, assignment to delivery depot.
• 004. Last mile – Delivery driver receives sorted shipments by route and district.

Process flow: DHL routing codes

Standard address format for DHL domestic parcel

For home addresses in Germany, DHL expects a clear, single-line structure per field. Special characters, abbreviations and unnecessary additions make automatic recognition more difficult.

Mandatory fields and recommended order

Writing rules for better recognition rates

• Street names spelled out instead of abbreviated (e.g. "Musterstraße" instead of "Musterstr.")
• House number always specified, even for single houses without visible number on the street
• No duplicate city entries (e.g. "10115 Berlin Berlin")
• Do not mix phone number and email in address lines – use separate fields
• Business addresses: contact person on separate line below company name

Packstation, branch and alternative address formats

Alternative delivery addresses follow their own format rules. They are not interchangeable with standard home addresses. Anyone who treats Packstation and branch like a normal street address creates systematic delivery errors.

Detailed notes on Packstation and branch routing can be found in Packstation and Branch Delivery. Address errors from the customer perspective and their handling in order management are described in Address Errors and Investigation.

Routing codes in shop, WMS and DHL interface

Professional fulfillment validates addresses before physical shipping. DHL offers various options for this via the business customer portal, CSV bulk import and API integration.

Validation levels at a glance

• 001. Plausibility check in frontend
  Mandatory fields, length limits, numeric postal code, Postnummer format for Packstation.
• 002. Address check via DHL API
  Comparison with reference data, correction suggestions, routability status before label generation.
• 003. Release at packing station
  Spot checks for manual address changes, block on warnings from step 2.
• 004. Monitoring after shipping
  Evaluate tracking events such as "shipment delayed" or return to sender as KPI for address quality.

Technical details on integration: API and Shop Integration DHL. For larger volumes with CSV upload: Bulk Shipping and CSV Import.

Workflow: address validation before label printing

Typical errors and their consequences

Most routing code problems repeat themselves. Those who know the patterns can tighten rules in shop and packing process in a targeted manner.

The five most common address errors

• 001. Postal code does not match city – Customer selects neighboring city or typo in postal code.
• 002. House number missing or included in street name – Sorting cannot assign street uniquely.
• 003. Packstation without Postnummer – Routing to Packstation fails.
• 004. Special characters and emojis in name fields – Label printer or OCR produce faulty scans.
• 005. Multi-line company names without separation – Character limit per label line exceeded, section cut off.

Further DHL error categories and their connection to addresses: Common DHL Shipping Errors. If shipments do not arrive despite correct address, it is worth looking at Delivery Attempts and Forwarding.

Address error share by error category

Trend: slightly declining in shops with API validation.

Best practices for e-commerce and fulfillment

Checkout and customer data

• Address fields with character limits per DHL specification (typically 35 characters per line)
• Integrate Packstation search instead of free text entry
• With postal code auto-completion: city field readonly or with warning on deviation
• Clearly separate billing and delivery address; generate shipping label only from delivery address

Warehouse and packing station

• No manual "correction" of addresses without renewed API check
• Spot checks for first shipment to new customers or B2B addresses
• Training: Difference between Packstation, branch, home address using sample labels
• Destroy faulty labels, generate new label – do not cover up

Reporting and continuous improvement

Metrics that make address quality visible:

• Share of shipments with status "address incomplete" or return to sender
• Share of manual address corrections before shipping
• Complaints with cause "wrong address" vs. "DHL delivery error"
• Comparison of address error rate before and after introduction of DHL address check

Comparison: before vs. after address validation

Checklist: address format before shipping

Go through these points before every label print – manually for low volume or automated in WMS:

• Postal code is five digits and consistent with city (API status "routable")
• Street and house number are in separate, correct fields
• Recipient name is complete and within character limits
• For Packstation: number and Postnummer present
• No emojis, HTML or special characters in address lines
• Address line 2 (floor, c/o) on separate line, not in street
• Country field set (DE for domestic)
• After customer change: old label cancelled, new label generated

International shipping: note deviations

For shipments abroad, different address standards apply than in Germany. Country-specific field orders, provinces, states and postal code formats must be correctly mapped in the interface. Applying German postal code logic to international addresses leads to systematic routing code errors.

Principles for international:

• 001. Always set ISO country code (not just "EU" or continent).
• 002. Validate postal code format per country (e.g. four digits in Austria, alphanumeric in UK).
• 003. State/province mandatory only where the destination carrier requires it.
• 004. Prefer Latin script; for non-Latin addresses, use additional field "address in local script" if the product provides it.

Conclusion: address quality as fulfillment KPI

Address format and routing codes determine whether a DHL shipment arrives on the first delivery attempt or spends days in reprocessing. The investment in checkout validation, API integration and packing station processes pays off through fewer forwarding cases, lower return costs and more satisfied customers. Those who only discover address errors reactively via tracking events pay twice: once for the failed shipment, once for support and reshipping.

Therefore, establish routing codes as a fixed quality step before label printing – not as a correction after the first delivery failure.

Related topics

• Common DHL Shipping Errors
• Packstation and Branch Delivery
• Address Errors and Investigation
• API and Shop Integration DHL
• Delivery Attempts and Forwarding

Last updated: July 7, 2026