DSV
Purpose
This page describes the DSV-specific setup in Shipping Labels. It covers residential delivery handling, pickup windows, fallback package data, notification options, and the multiple credential sets needed for shipping and tracking-related services.
Prerequisites
- The shared Shipping Labels setup is complete.
- DSV shipping credentials, tracking-related credentials, and the correct environment URLs are available.
- Sender and recipient contact data are maintained in the required format.
- The required notification scenario is known.
Recommended sequence
- Maintain shipping credentials and URL assignment.
- Maintain pickup window and residential-delivery behavior.
- Maintain notification settings and the related tracking credentials.
- Verify phone and email data in a realistic test request.
Setup components
Start with the DSV credential model
DSV setup can include several technical values, for example account number, x-pat, Subscription-Key, Service-Auth, and additional tracking-oriented values for notification scenarios. Keep these values grouped by service purpose so that shipping requests and notification flows are not mixed accidentally.
Maintain pickup and delivery behavior
The DSV setup contains operational properties such as pickup-from time, pickup-until time, residential handling, and fallback package dimensions and weight. These values shape the actual request and should be validated against the intended customer scenario.
Activate the residential flag only when the receiver is actually a private recipient; it changes the delivery scenario that is requested from DSV. The pickup-from and pickup-until fields should describe a realistic time window in which DSV can actually collect the shipment.
Configure notifications only with complete contact data
DSV notifications for departure, delivery, or exception events are valuable but depend on complete supporting data. The recipient email must be available for the notification use case, and the notification language should be chosen deliberately.
The phone-number format must match the expected pattern exactly.
If no recipient email is maintained on the customer card, the default sender email can act as fallback. However, the notification logic only becomes usable when the tracking service is also activated and the required fields such as Subscription-Key and Service-Auth are maintained. A practical reference format for phone numbers is +49 211 87451233.
Keep sender and recipient fallback behavior visible
If the customer-specific email is missing, the default sender email can be reused depending on the scenario. This is useful for onboarding, but it should not hide poor customer master data quality in productive use.
As with other carriers, maintained item attributes for dimensions and weight take priority over the DSV fallback values on the setup.
Process Important DSV notes DSV setup depends heavily on correct contact data and on the right combination of shipping and notification credentials.
- Use the exact phone-number format required by DSV.
- Keep shipping credentials and tracking or notification credentials clearly separated.
- Activate notifications only when recipient email and tracking activation are both available.
- Use fallback dimensions and weight only when item-level data is not maintained.
Links