Issue label and QR securely
Shipper address, receiverId, weight and destination are validated. Provider PDFs land in protected storage rather than an expiring third-party URL.
DHL Paket Returns · direct integration
Automate DHL returns without hiding the exceptions.
Returno issues DHL Paket return labels and QR documents through the merchant contract, consumes scan events and keeps failure, retry and manual fallback visible. Activation waits until DHL accepts the exact app, user and Returns-profile combination.
Direct DHL Paket Returns is implemented; production needs your DHL business contract and a successful Returns API preflight.
Carrier execution
Automation that stays honest through 401s, timeouts and missing addresses.
Bring scans back into the journey
DHL tracking advances the return status and can trigger configured shopper messages. Warehouse receipt remains an explicit operations confirmation.
Turn failures into work
Credential, profile, validation and transport errors stay distinct. Retry, manual label and escalation are observable states.
DHL preflight
Four proofs before the first automated label.
A valid OAuth token is not enough: DHL must accept the same app and user on the Parcel DE Returns API.
- 01
Check the Returns product in DHL Developer Portal
The app needs Parcel DE Returns in the correct sandbox or production environment.
Proof: Returns API assigned to app - 02
Connect the business profile
DHL user, password and receiverId are encrypted and kept separate from the platform key.
Proof: credentials securely readable - 03
Run locations/profile preflight
Returno calls the DHL Returns API with the same authentication path used for labels and classifies rejections.
Proof: DHL accepts Returns access - 04
Accept a real test label and QR
Address, documents, tracking number, shopper download and manual fallback are checked end to end.
Proof: real label in the portal
Clear ownership
Returno operates the integration. The DHL contract remains yours.
Returno takes care of
- Platform API configuration and encrypted credential storage
- Preflight, request validation and idempotent label issuance
- Protected label and QR PDF storage
- Tracking, failure classification, retry and manual fallback
Your team provides
- An active DHL business contract for Paket Returns
- An authorized user and returns receiver ID
- The correct return destination in the DHL profile
- A test order and acceptance of the real label
Returno does not resell a DHL contract and cannot bypass missing DHL product access. A merchant-owned Sendcloud connection or manual label upload remains available as an alternative.
DHL returns automation questions
Does the merchant need their own DHL credentials?
Yes. DHL Paket Returns needs the merchant business-portal user, password and receiverId. Returno manages the platform API key.
Why can OAuth work while the Returns API still rejects access?
DHL additionally validates the app, API product and business-user profile mapping. Returno therefore tests the actual Returns API permission, not only the token endpoint.
What happens when DHL does not return a label?
Returno never fabricates a placeholder. The failure stays visible and policy can retry, escalate or request a manual label upload.
Test DHL against your real contract.
Validate profile, receiverId, documents and shopper download on one controlled case before automatic labels are enabled.