The problem we help solve
A clearer handoff. Less uncertainty.
A seller may assume the same DPD account, interface and service codes apply across every European shipping origin.
How BrownBag helps
BrownBag helps structure DPD workflows around your actual shipping account and operating market. We review the available portal, approved connector or carrier interface, then connect shipment references and dispatch responsibilities to your order process. The implementation includes the manual handoffs that still need an operator.
From requirement to operation
Your DPD workflow
Confirm the service and account
Identify the DPD country business, contracted services and actual cross-border lanes.
Connect the dispatch record
Map the local account shipment fields and pickup or delivery options through its approved interface.
Test the operational handoff
Test label output, tracking events and delivery exceptions before combining the account with other country operations.
What we can deliver
- DPD account and service capability map
- Order, shipment and dispatch-document mapping
- Tested handoff and exception-handling instructions
We agree the systems, responsibilities, acceptance checks and support arrangements before implementation begins.
Ready for dispatch
Shipping labels, packing slips & dispatch
Connect courier shipment booking to the AWB or consignment number, then prepare the documents the packing team needs. Carrier-provided shipping labels and custom printable packing documents have different roles.
Use the label specification supplied by the relevant DPD country business. Pickup-point, return and cross-border documents may differ and need explicit validation.
- Individual and bulk shipping label generation or retrieval through the carrier’s supported API, connector or portal
- Thermal and A4 printing where the carrier’s label formats and your printer setup support them
- Reprints of an existing shipment label without creating a duplicate booking
- Custom packing slips and dispatch manifests; carrier acceptance and manifest formats confirmed separately
- Tracking, COD reconciliation and returns linked to the same shipment reference
Carrier labels retain the courier’s required barcodes and layout. We verify format, batch and reprint support for each account before automating. A custom packing slip is not a substitute for a carrier-issued label. This website describes implementation services; it does not book live shipments or generate carrier labels.
Scope your label workflow →Define the right scope
DPD controls service availability, account permissions, rates and shipment acceptance. Market listings are starting points for a lane review, not a promise that every origin, destination or API action is supported. We confirm approved access before implementing booking, labels or returns. Customs decisions and delivery outcomes remain with the responsible authorities and carrier.
Provider requirements and interfaces can change. We recheck the applicable documentation and account access when scoping your project.
Official DPD reference →Your questions, answered
Can we start with DPD before a direct API is approved?
Yes. We can design an assisted DPD dispatch process that preserves the order reference, official shipment identifier and handover evidence. Direct automation is added only after the relevant account interface and permitted functions are confirmed.
What should we include in the first brief?
Share your current store and systems, provider account status, target markets and the workflow you want to improve. Include typical volumes and the person responsible for operations. Do not send passwords, API keys or customer records.
Can you handle bulk labels, thermal printing and reprints?
Use the label specification supplied by the relevant DPD country business. Pickup-point, return and cross-border documents may differ and need explicit validation. We verify thermal/A4 compatibility and distinguish carrier labels from custom packing slips. Reprinting uses the existing shipment reference rather than creating another booking.