Initial Setup
This guide takes you from installation to your first test label. With credentials at hand the setup takes about 10 minutes — with the built-in test account, just two.
Prerequisites
| Prerequisite | Details |
|---|---|
| merchantCENTRAL hub | The "AD merchantCENTRAL" app must be installed and configured — otherwise the DPD AT wizard redirects you to the hub setup first |
| HttpClient permission | In Extension Management, "Allow HttpClient Requests" must be enabled for the connector |
| DPD AT credentials | Username, mandant, and MD5 password from the IT-Kundenberatung — or start with the test account |
What is the MD5 password?
DPD AT does not authenticate requests with your plaintext password but with its MD5 hash (32 characters, e.g. e51524d2…). This is exactly the value you receive together with your credentials from the IT-Kundenberatung. The connector stores only this hash — encrypted in the merchantCENTRAL Credential Store, never in table fields.
The Setup Wizard
Open search (++alt+q++) → Assisted Setup → merchantCENTRAL: Set up DPD Austria. Alternatively: DPD Austria Dashboard → action Setup Wizard.
Step 1 — Welcome
Overview of the prerequisites. Have your credentials ready and click Next.
Step 2 — Authentication
| Field | Input |
|---|---|
| Use Test Account | Testing only — fills in all credentials automatically (see below) |
| Username | Your 9-digit DPD AT username |
| Mandant | Your client number (usually 1) |
| MD5 Password | Click the field and enter the 32-character MD5 value — the display switches to Configured |
| API Base URL | Preset to the WEB.Service endpoint — change only when instructed |
Step 3 — Connection Test
Click Test Connection. The connector calls the WEB.Service getStatus function and shows the status list of all DPD AT services:
Connection successful! DPD AT service status:
WEB.Service: Im Betrieb
Return.Paketomat: Im Betrieb
…
If the test fails, check username, mandant, and MD5 password — see Troubleshooting.
Step 4 — Shipper Address (Optional)
Usually leave empty
By default DPD AT prints the sender address stored in your DPD account on the label. Fill these fields only if the label should deliberately show a different address. The action Fill from Company Information populates the fields from company information.
Step 5 — Default Settings
| Field | Recommendation |
|---|---|
| Default Parcel Type | DPD (B2B) for business, B2C for consumer shipments |
| Default Product | Auto (by weight) — selects Small Parcel up to 3 kg, Normal Parcel above |
| Default Output Format | PDF for laser printers, ZPL for Zebra thermal printers |
| Default Weight (g) | Used when the shipment carries no weight |
All further settings (return options, collective print, self-booking list) are available later on the setup page.
Step 6 — Finish
Click Finish. The settings are saved and the provider status in the hub refreshes automatically.
Activating the Provider & License
- Open Shipment Providers (hub) — DPD Austria appears there as DPDAT
- Open the card and switch Enabled on
- Without a license, activation starts the demo period — the license status is shown in the card's license FactBox, together with Register Demo and Refresh License
Option: Test Account
For testing without your own credentials, enable Use Test Account in step 2:
- Username, mandant, and MD5 password of the public DPD AT integration test account are filled in automatically
- The dashboard permanently shows the "TEST ACCOUNT MODE" banner
Rules for the test account
The test account creates labels on DPD AT's real test system. Therefore use fictional recipient data only (e.g. "Testfirma Mustermann, Teststrasse 1, 1090 Wien") — this is a DPD Austria requirement. Also keep the switch Manifest Performs Day Closing off and cancel test labels where possible. For production, switch the test account off and enter your own credentials.