DPD Dashboard
The DPD Dashboard is your working view for the shipping day. At a glance it answers whether anything needs doing today: how many labels were created, whether DPD has been told to collect, what failed, and how the shipments on the road are getting on.
Opening the page
- Search for "DPD Dashboard" in the BC search bar (Alt+Q).
- Or: open the Shipment Provider List and click "Dashboard" on the DPD entry.
Layout
The figures sit in an overview with five KPI tiles and three cards below them. Every number is clickable and opens exactly the list it counted.
The five KPIs
| Tile | Shows | The line beneath answers |
|---|---|---|
| Labels today | Labels created today, with a trend line over the last seven days | How many this month, and how many of those are return labels |
| Waiting for close-out | Labels not yet closed out | Whether they are all from today, or since when the oldest has been waiting |
| Pickups not sent | Pickup requests entered but never transmitted to DPD | How many are due today and how many are overdue |
| Failed labels | Labels in error state | How many of those arrived in the last 24 hours |
| On the road | Shipments DPD has not delivered yet | How many were delivered today and how many have a problem — or that tracking is switched off |
Why the line beneath the number matters
An open pickup request for next Tuesday is not work — one from yesterday is, because no van came for it. The line beneath the number tells you which case you are looking at without opening the list.
Card "Where the shipments are"
A bar shows how the shipments in the DPD network are spread: Handed over, In transit, Out for delivery, At a ParcelShop, On the way back and Delivery problem. The order follows the shipment lifecycle and stays constant so the bar can be read at a glance. Every section is clickable.
The On the road tile counts only the first four sections — a parcel coming back or stuck with a problem is no longer on its way to the recipient. Both stay visible, because those are the shipments the customer calls about next.
If there are shipments with a delivery problem, a note appears below the bar — those shipments will not move on by themselves.
The ParcelShop is a stage of its own
A parcel DPD dropped at a ParcelShop is neither travelling nor delivered: it is waiting for the recipient to collect it, and if nobody does it comes back. That is why it has its own section here instead of being counted under "In transit".
Only with tracking enabled
This card only appears when tracking is enabled in the DPD setup. Without it every shipment would sit in "Unknown" and the bar would say nothing.
Card "Pickups"
DPD requires no end-of-day manifest towards the network — but DPD does have to be told to collect the parcels. This card shows the full path of a pickup request:
| Line | Description |
|---|---|
| Due today or earlier | Open requests whose date has arrived |
| Overdue | Open requests whose date has passed (red as soon as it is above zero) |
| Sent to DPD | Transmitted, not yet confirmed |
| Confirmed | Confirmed by DPD |
| Retry due | Failed, will be retried automatically |
| Out of attempts | Failed and abandoned — only cancelling and booking again helps |
| Waiting to be collected | Parcels and weight across the unfinished requests of the last seven days and the future |
| Today's window | Only shown when a pickup is booked for today |
| Next retry | Only shown when a retry is pending |
Overdue pickups
An overdue request means the date has passed and DPD was never informed. No van is coming for those parcels. Use the Send Open Pickups action before the date is reached.
Card "Connection and jobs"
| Line | Description |
|---|---|
| API status | Connected, Configured, Switched off, Error or Not configured |
| Mode | Live, Sandbox or Mock API |
| Depot | The DPD depot the shipments are booked against |
| Tracking job | State of the background job: Active, Running, On Hold, Error or Not configured |
| Tracking interval | How often the job polls tracking data |
| Last tracking sync | When data last came back from DPD |
| Delivery success rate | Share of delivered shipments among all tracked ones |
Watch the mode
In Sandbox and Mock API mode the labels produced look real and are worthless. That is why the mode is on the daily view and not only in the setup.
Watch the tracking job
A background job can quietly go "On Hold" — after a permission problem, for instance. Shipment statuses then stop updating without any error message appearing.
Further areas
| Area | When visible |
|---|---|
| Sandbox notice | When sandbox or mock mode is active — the labels produced are test labels |
| Getting started | While the setup is incomplete, pointing at where to configure |
| Close-out details | Always; last close-out and the print date for the internal manifest |
Actions
Processing
| Action | Description |
|---|---|
| Send Open Pickups | Sends every open pickup request to DPD and retries the failed ones whose retry time has come |
| Close Out (Manifest) | Marks all waiting labels as manifested, locally |
| Print Internal Manifest | Printable handover list for the selected date |
| Refresh Tracking | Runs tracking immediately, outside the interval |
After each of these actions the figures in the overview refresh automatically.
Navigation
| Action | Description |
|---|---|
| Labels | Opens the full list of DPD shipment labels |
| Pickup Requests | Opens the list of pickup requests |
No setup on the dashboard
The dashboard is the daily view. Configuration happens on the Shipping Agent Card and in the Assisted Setup — see Initial setup.
Close-out from the dashboard
Unlike DHL, DPD needs no API close-out — created labels are registered with the depot. The internal close-out serves your own traceability and the printable handover list:
- Check the Waiting for close-out tile — the line beneath tells you whether anything has been left behind.
- Click Close Out (Manifest) and confirm.
- Set the Print Date and click Print Internal Manifest.
Frequently asked questions
Why can't I see the delivery stage card?
It only appears when "Tracking Enabled" is set in the DPD setup.
What does "Pickups not sent" mean?
Pickup requests in status "Open": they were entered but never transmitted to DPD. That does not happen by itself — send them with the Send Open Pickups action, or individually from the pickup request list.
Why do the failed labels say "new in the last 24 hours"?
A failed label is never retried automatically, so the total can only grow. Only the last-24-hours figure shows whether something is broken right now or whether these are old cases.
How often does the dashboard refresh?
The figures reload every time the page is opened or returned to, after every action, and after every click on a number.