About DPD Local
DPD Local is the carrier identity supplied for this tracking page. Use the official DPD Local website and the shipment number shown by the sender or retailer to establish whether DPD Local has received the parcel, is processing it, or is awaiting a handoff.
| Field | Verified page or value |
| Official website | https://www.dpdlocal.co.uk/ |
| Carrier identity | DPD Local |
| Tracking relationship | 17TRACK displays available events from DPD Local and other detected transport participants; 17TRACK does not transport the parcel. |
Carrier Entity Relationships
| Entity | Relationship |
| DPD Local | View all details for DPD Local| Entity type | DPD Local is the carrier name that should be selected when the shipment is identified as DPD Local. |
|---|
| Why it matters to tracking | Carrier selection helps route the number to the appropriate event source. |
|---|
| Official evidence | DPD Local official website. |
|---|
|
| 17TRACK | View all details for the 17TRACK relationship| Entity type | Independent multi-carrier tracking platform. |
|---|
| Why it matters to tracking | 17TRACK can consolidate available events, but it cannot alter delivery instructions, approve refunds, or decide claims. |
|---|
| Official evidence | 17TRACK carrier directory. |
|---|
|
Quick Answer
Enter the shipment tracking number, rather than the retailer’s order number, on the official DPD Local website or in 17TRACK. If no result appears, check for spaces, copied punctuation, a recently created label, and whether the seller supplied a partner or last-mile number. 17TRACK is independent and cannot redirect, refund, investigate, or compensate a shipment.
How to Track DPD Local Packages
The official route is the carrier website; 17TRACK is useful when a parcel changes carrier or when several shipments need one tracking view.
| Route | Steps |
| Official DPD Local tracking | View all details for official tracking| Where to start | Open the official DPD Local website and follow its current tracking route. |
|---|
| Number to enter | Use the shipment or parcel number supplied on the dispatch email, label, receipt, or delivery notice. |
|---|
| If it fails | Ask the sender to confirm the number and the carrier. A retailer order ID is not necessarily a tracking number. |
|---|
|
| 17TRACK | View all details for 17TRACK tracking| Where to start | Use the 17TRACK tracking page. |
|---|
| Carrier selection | Select DPD Local when automatic identification does not choose it. |
|---|
| If it fails | Try the official carrier route and request confirmation from the merchant before treating the parcel as lost. |
|---|
|
Tracking Statuses and Meanings
A tracking event describes the latest recorded scan, not necessarily the parcel’s exact physical location at every moment.
Status Quick Lookup
| Status | What it means |
| Label created or pre-advice | View all details for label creation| Lifecycle stage | Pre-shipment. |
|---|
| Current responsible party | The sender or fulfilment operation may still hold the parcel. |
|---|
| What happens next | A physical acceptance or processing scan should appear after handoff. |
|---|
| What you should do | Contact the seller if the dispatch promise has passed; do not treat label creation as carrier acceptance. |
|---|
|
| Accepted or collected | View all details for acceptance| Lifecycle stage | Carrier intake. |
|---|
| Current responsible party | The recorded collecting or processing carrier. |
|---|
| What happens next | Sorting and transport scans may follow. |
|---|
| What you should do | Keep the tracking record and check the delivery address supplied to the sender. |
|---|
|
| In transit or at depot | View all details for in-transit events| Lifecycle stage | Sorting, line-haul, or destination processing. |
|---|
| Current responsible party | The carrier or logistics partner associated with the latest scan. |
|---|
| What happens next | Further routing or delivery preparation. |
|---|
| What you should do | Allow for normal scan gaps and escalate through the sender if the parcel remains unchanged beyond the applicable service process. |
|---|
|
| Out for delivery | View all details for out-for-delivery status| Lifecycle stage | Final delivery attempt. |
|---|
| Current responsible party | The delivery operation assigned to the route. |
|---|
| What happens next | Delivery, an attempt event, or movement to an arranged collection point. |
|---|
| What you should do | Make access available and monitor delivery instructions from the official carrier source. |
|---|
|
| Delivered, exception, or returned | View all details for completed and exception statuses| Lifecycle stage | Final delivery, failed attempt, or reverse movement. |
|---|
| Current responsible party | The delivery operator, collection point, or sender depending on the event. |
|---|
| What happens next | Proof of delivery, another attempt, collection, or return processing. |
|---|
| What you should do | Check delivery evidence and contact the seller promptly if the parcel is missing, damaged, or being returned. |
|---|
|
Services and Delivery Times
Delivery timing depends on the service purchased, collection time, destination, address quality, operational disruption, and any partner handoff. A displayed estimate is not automatically a guaranteed delivery commitment.
Service Comparison
| Service category | Best for |
| Domestic parcel delivery | View all details for domestic parcel delivery| Coverage | Use the service and destination shown in the sender’s booking. |
|---|
| Tracking level | Available events depend on the shipment record and scans. |
|---|
| Conditions | Size, weight, collection cutoff, address, and access conditions are service-specific. |
|---|
| Limitation | Do not infer the exact product or delivery promise from the tracking number alone. |
|---|
|
| Business or retailer shipment | View all details for business shipments| Coverage | The merchant’s contract determines available services, options, and claims handling. |
|---|
| Tracking level | Business users should rely on their booking or integration records for shipment identity. |
|---|
| Limitation | The recipient may not have access to the sender’s account-level service information. |
|---|
|
Delivery Time
| Timing question | Practical answer |
| Published standard | Use the service-specific promise shown at booking or in the sender’s confirmation. |
| Counting point | Check whether the promise starts at collection, acceptance, or the next working day. |
| Destination Country Delivery Times | DPD Local tracking should be assessed against the booked route; a universal country-by-country schedule should not be inferred without the shipment’s service and origin. |
Common Tracking Problems and Solutions
| Problem/status shown | Check first |
| Invalid number | View all details for an invalid number| Likely cause | Typographical error, order ID, incomplete number, or wrong carrier. |
|---|
| Immediate action | Copy the number again without accidental punctuation and ask the sender to confirm its type. |
|---|
| Escalation | Escalate to the merchant because the sender controls the booking record. |
|---|
| Who to contact | Seller first; carrier support when the official record identifies the shipment. |
|---|
|
| No update or label created | View all details for no tracking update| Likely cause | Electronic pre-advice exists but the parcel has not received a physical scan, or scans are delayed. |
|---|
| Immediate action | Confirm the dispatch date and collection handoff with the seller. |
|---|
| Escalation | Use the sender’s service commitment and the carrier’s official process rather than an invented universal waiting period. |
|---|
| Who to contact | Sender or merchant for a shipment investigation. |
|---|
|
| Delivered but not received | View all details for delivered but not received| Check first | Delivery location, household members, neighbours, reception, safe place, and the official proof-of-delivery details. |
|---|
| Immediate action | Contact the seller promptly and ask for a delivery investigation. |
|---|
| Escalation | Ask the sender to use the contractual carrier process if the parcel cannot be located. |
|---|
| Who to contact | Merchant or sender, with the tracking number and address ready. |
|---|
|
| Exception, failed delivery, or return | View all details for delivery exceptions| Likely cause | Address, access, recipient availability, damage, operational disruption, or a return instruction. |
|---|
| Immediate action | Read the latest event and follow the official instruction; do not assume a redelivery is automatic. |
|---|
| Who to contact | Sender for changes, claims, or contract-level requests; carrier for an active delivery instruction where offered. |
|---|
|
International Shipping, Customs and Carrier Handoffs
For an international shipment, the latest event identifies the reporting system, not necessarily the company that created the original number. Arrival at an exchange facility is not the same as customs release.
International Flow
| Stage | Typical event |
| Origin preparation | View all details for origin preparation| Responsible entity | Merchant, origin carrier, or logistics partner. |
|---|
| What is happening | Label, electronic data, packaging, and collection are being prepared. |
|---|
| Number change | A partner or destination identifier may be associated with the original number. |
|---|
| Customer action | Confirm the declared address and customs information with the seller. |
|---|
|
| Export, line-haul, and import | View all details for customs and line-haul| Responsible entity | Origin authorities, transport operators, destination customs, and appointed carriers. |
|---|
| What is happening | Security, transport, customs presentation, duty assessment, and release may occur in separate steps. |
|---|
| Visibility gap | Scans can be absent while a shipment moves between facilities or systems. |
|---|
| Customer action | Provide requested documents and pay assessed charges only through verified official channels. |
|---|
|
| Partner handoff and last mile | View all details for partner handoff| Responsible entity | The operator shown by the latest physical acceptance or delivery scan. |
|---|
| What is happening | Electronic pre-advice, physical handoff, first receiving scan, and final delivery are distinct events. |
|---|
| Number change | The original identifier may continue, or a linked last-mile number may appear. |
|---|
| Customer action | Use the destination operator’s official tracking route only when the handoff event supplies a confirmed identifier. |
|---|
|
Delivery Management and Post-shipment Options
Delivery changes are controlled by the carrier’s service rules and the sender’s account. A recipient should use only options shown in the official shipment record and should not assume that a request is accepted until a confirmation appears.
| Option | Who should request it |
| Delivery instruction or redirection | View all details for delivery instructions| Eligibility | Depends on the shipment, address, service, security controls, and current delivery stage. |
|---|
| Deadline | Request before the parcel reaches the point at which the official system closes changes. |
|---|
| Fee and guarantee | Check the official transaction screen; a request is not a guaranteed outcome until accepted. |
|---|
| Action link | Official DPD Local website. |
|---|
|
| Collection or redelivery | View all details for collection and redelivery| Eligibility | Depends on the failed-attempt notice and the location or service offered for that parcel. |
|---|
| Customer action | Follow the notice, bring any required identification, and contact the seller if the notice is unclear. |
|---|
| Limitation | 17TRACK cannot book collection, redelivery, or a change of address. |
|---|
|
Lost, Damaged, Claims, Insurance and Refunds
A tracking inquiry, carrier investigation, insurance claim, postage refund, and marketplace refund are separate processes. The sender usually controls the contractual shipment record, so the recipient should notify the seller quickly and retain packaging, photographs, invoices, and delivery evidence.
| Process | Use when |
| Shipment investigation | View all details for a shipment investigation| Who files | The sender or merchant should normally initiate the carrier enquiry. |
|---|
| Evidence | Tracking number, booking details, dispatch date, address, contents description, and correspondence. |
|---|
| Possible outcome | Location update, delivery investigation, return, claim route, or request for further evidence. |
|---|
| Official link | DPD Local official website. |
|---|
|
| Damage or loss claim | View all details for a damage or loss claim| Who files | Eligibility depends on the shipment contract and service terms; ask the sender to use the applicable claim route. |
|---|
| Filing time | Deadlines vary by service and claim type and must be checked in the current terms. |
|---|
| Required evidence | Packaging, contents, value proof, photographs, tracking information, and damage description may be requested. |
|---|
| Possible outcome | Investigation, settlement, denial, or a request for more evidence. |
|---|
|
Shipping Restrictions and Special Handling
Do not rely on a tracking page as proof that an item is permitted for carriage. Check the current DPD Local rules before sending batteries, liquids, aerosols, dangerous goods, perishables, high-value goods, or restricted products.
| Category | Customer action |
| Dangerous goods, batteries, and liquids | View all details for regulated goods| Restriction | Acceptance depends on the item, packaging, route, declaration, and service. |
|---|
| Transport impact | Incorrectly declared goods may be refused, delayed, returned, or removed from transport. |
|---|
| Official rules | Review the current rules on the official DPD Local website before booking. |
|---|
|
| Perishable, fragile, or high-value goods | View all details for special handling| Packaging | Use packaging appropriate to the item and retain it if damage occurs. |
|---|
| Tracking impact | Special handling does not guarantee a particular scan frequency or delivery date. |
|---|
| Customer action | Confirm coverage and compensation conditions with the sender before dispatch. |
|---|
|
Customer Service
| Channel | Best use |
| Official website | View all details for official customer service| Verified contact/link | https://www.dpdlocal.co.uk/ |
|---|
| Best for | Current tracking, service guidance, delivery information, and the carrier’s published contact routes. |
|---|
| Information to prepare | Tracking number, sender and recipient details, dispatch date, latest event, and delivery address. |
|---|
| Limitation | The sender may need to open an investigation or claim. |
|---|
|
| Merchant or sender support | View all details for merchant support| Best for | Wrong address, missing parcel, damage, refund, booking details, and contractual claims. |
|---|
| Information to prepare | Order reference, tracking number, proof of value, photographs, and correspondence. |
|---|
| Escalation order | Check the official event, contact the seller, then use a carrier channel when the shipment record supports it. |
|---|
|
Ecommerce and Business Tracking
Merchants should keep the order ID, carrier tracking number, and any linked partner identifier as separate fields. A multi-carrier platform can normalize events and monitor exceptions, while carrier support or the seller remains responsible for operational investigation and claims.
Developer/API Comparison
| Option | Provider |
| Official carrier integration | View all details for the official carrier integration| Carrier coverage | Use the integration and credentials supplied under the relevant DPD Local business arrangement. |
|---|
| Primary use | Operational shipment creation, tracking, and account workflows where enabled. |
|---|
| Authentication | Confirm credentials and current technical requirements with the official business channel. |
|---|
| Current documentation | Use current documentation supplied by the carrier or contracted platform. |
|---|
| Migration note | Do not implement an old endpoint copied from an unverified integration article. |
|---|
|
| 17TRACK API | View all details for the 17TRACK API| Carrier coverage | Multi-carrier coverage subject to 17TRACK’s supported carrier catalogue. |
|---|
| Primary use | Unified tracking, batch registration, normalized events, and exception monitoring. |
|---|
| Authentication | 17token header authentication is shown in the current API reference. |
|---|
| Tracking/batch/webhook capability | Consult the current documentation for the account’s enabled functions and event delivery options. |
|---|
| Current documentation | 17TRACK API documentation. |
|---|
| Migration note | Use the documented API version and request format rather than an older example. |
|---|
|
FAQ
Basic FAQs
1. How do I track my DPD Local package?Enter the shipment tracking number on the official DPD Local website or 17TRACK, then compare the latest event with the seller’s dispatch information.
2. Where can I find my DPD Local tracking number?Look in the dispatch email, parcel label, receipt, delivery notice, or retailer order page, and ask the seller to identify which reference is the carrier number.
3. What does a DPD Local tracking number look like?The number should be copied from the shipment record because order references and partner identifiers can use different formats; a prefix alone does not prove the service.
4. When will the first DPD Local scan appear?The first scan appears when the relevant system records a shipment event, so label creation may precede physical acceptance.
5. Why is my DPD Local tracking not updating?A scan may be pending, delayed between facilities, or held in a partner system; confirm dispatch with the seller before escalating.
6. How long does DPD Local delivery take?Use the service-specific estimate supplied at booking because timing depends on route, cutoff, address, working days, and operational conditions.
7. What should I do after a DPD Local delivery failure?Read the official attempt notice, follow any collection or redelivery instruction, and contact the seller if the available option is unclear.
8. What should I do if DPD Local says delivered but I have not received the parcel?Check the delivery location, household members, neighbours, reception, safe place, and proof of delivery, then ask the seller to open an investigation.
9. What should I do if my DPD Local parcel is lost or damaged?Notify the seller promptly, preserve the packaging and contents, take photographs, and request the applicable carrier investigation or claim process.
10. How do I contact DPD Local?Start with the official DPD Local website and the contact route shown for the shipment or service; keep the tracking number and address ready.
Expert FAQs
11. Can a DPD Local label be visible before DPD Local receives the parcel?Yes, electronic pre-advice or label creation can appear before a physical acceptance scan, so the label event should not be treated as proof of collection.
12. Can a marketplace buyer receive a partner tracking number instead of a DPD Local number?Yes, a seller may expose a partner or last-mile identifier; ask the seller to map it to the shipment identifier used by DPD Local.
13. Does DPD Local tracking prove who currently has the parcel?It identifies the latest reporting event, but responsibility should be interpreted from the latest physical acceptance or delivery scan rather than an electronic pre-advice event.
14. Does arrival at a customs or exchange facility mean that a DPD Local parcel has cleared customs?No, arrival and customs release are separate events; follow any verified request for documents or charges from the destination authority or carrier.
15. Can businesses track DPD Local shipments through an API?Businesses should confirm the current integration available under their DPD Local account or use the documented 17TRACK API for multi-carrier tracking.
16. What is the difference between a DPD Local tracking inquiry and a claim?An inquiry seeks shipment information, while a claim requests compensation under applicable service terms and normally requires evidence from the sender.
17. Can 17TRACK change a DPD Local delivery address?No, 17TRACK only presents available tracking information; address changes and delivery instructions must be handled through the carrier or sender.
Tracking API
// 1. Current public official DPD Local tracking API:
// Current public official tracking API not confirmed.
// 2. 17TRACK API
// Documentation: https://api.17track.net/en/doc
POST https://api.17track.net/track/v2.4/register
17token: YourKey
Content-Type: application/json
[
{
"number": "TRACKING_NUMBER",
"carrier": "CARRIER_CODE"
}
]
Sources & References
17TRACK is an independent tracking platform and is not affiliated with DPD Local.