Skip to main content
DPD (RU)

DPD (RU) Tracking

Please enter the DPD (RU) tracking number to check the latest shipping status.

To extract possible tracking number complying with all tracking number rules.Clear text from input field.Track the entered order number.

About DPD (RU)

DPD (RU) is the carrier identity used for tracking shipments associated with DPD operations in Russia. Use the official DPD (RU) website for the carrier’s current shipment options, tracking results, delivery instructions and support routes. Service availability, route coverage and customer options depend on the shipment contract, origin, destination and current operating conditions.

Carrier Overview

FieldVerified reference
Canonical display nameDPD (RU)
Official websitehttps://www.dpd.ru/
Primary tracking actionEnter the shipment identifier supplied by the sender or shown on the carrier label.

Carrier Entity Relationships

EntityRelationship summary
DPD (RU)DPD (RU) is the carrier identity to select when a shipment is assigned to this tracking network.
Shipment identifierThe shipment identifier connects a label or booking record with available carrier events; an order number is a different commercial reference.
Official tracking pageThe official DPD (RU) website is the primary source for carrier-controlled tracking and delivery actions.
17TRACK17TRACK aggregates available tracking events as an independent platform and does not physically transport shipments or decide claims.

Quick Answer

To track a DPD (RU) shipment, enter the shipment number from the sender, label, receipt or dispatch notification on the official DPD (RU) website or use 17TRACK. If no result appears, check that you entered a tracking number rather than an order number, remove accidental spaces, and ask the sender whether the parcel has been physically handed over.

Pro Tip: A label or electronic booking can exist before the first physical acceptance scan. 17TRACK cannot change an address, release customs cargo, approve a refund or open a carrier claim.

How to Track DPD (RU) Packages

The official route is best for carrier-specific delivery options. 17TRACK is useful when the shipment has passed through more than one logistics network or when you want a consolidated event history.

Tracking Paths

PathAction
Official DPD (RU) trackingOpen the official website, locate the tracking function, enter the shipment identifier and review the latest carrier event.
17TRACK trackingOpen 17TRACK, paste the shipment identifier, select or confirm DPD (RU) when prompted, and compare the event history with the seller’s information.
No tracking numberAsk the sender or marketplace seller for the shipment identifier and dispatch confirmation; an order number alone may not be searchable.

A buyer normally finds the tracking number in the shipping email, marketplace order page, carrier notification or seller message. A reference number, invoice number, order number, delivery notice number and tracking number can be different identifiers. Do not infer the carrier solely from a prefix; use the official lookup or 17TRACK’s carrier recognition.

Tracking Number Formats and Examples

DPD (RU) shipment identifiers should be copied exactly as supplied by the sender. Public materials do not establish one universal format that can safely identify every DPD (RU) service, so a prefix or length should not be treated as proof of a product, origin or destination. Examples below are deliberately masked.

Tracking Number Format

Identifier familyNormalized pattern
DPD (RU) shipment identifierUse the exact carrier-issued or booking-issued value shown by the sender; a masked example may look like ############.
View all details for DPD (RU) shipment identifiers
Issued byThe identifier is supplied within the shipment booking or carrier label workflow; the sender should confirm its issuing context.
Typical useDomestic or cross-border parcel identification, depending on the contracted service and route.
Who sees itConsumers may see it in a dispatch message, label or receipt; business users may receive it from a shipping system.
Tracking scopeVisibility depends on scans received from the responsible carrier and any connected logistics partner.
CaveatDo not substitute an order number, invoice number or customer reference unless the official lookup explicitly accepts that field.
Partner or handoff identifierA separate partner value may appear in cross-border or multi-carrier records; use the number linked to the current tracking page.
View all details for partner or handoff identifiers
Issued byA transport or last-mile partner may issue its own identifier.
User scenarioA marketplace buyer may see the origin number first and a destination number later.
VisibilityOne identifier may show events only for the segment handled by its issuing network.
ActionAsk the seller to provide all linked identifiers when the handoff is visible but the new number is absent.
Order or reference numberA merchant value such as ORDER-#### is not automatically a DPD (RU) tracking number.
View all details for order or reference numbers
Issued byThe retailer, marketplace or shipping software issues the commercial reference.
Where seenOrder confirmations, invoices and seller dashboards.
Tracking limitationIt may locate an order in a merchant system but may produce no carrier scan.
Next stepRequest the carrier shipment identifier from the seller.

Tracking Statuses and Meanings

A tracking status describes the latest recorded event, not necessarily the parcel’s exact position at the moment you check. Responsibility can change during a partner handoff, customs process or last-mile delivery attempt.

Status Quick Lookup

Status familyMeaning
Pre-shipment or label createdShipment data may exist before physical acceptance; the sender should confirm handover.
View all details for pre-shipment status
Lifecycle stageBooking or electronic pre-advice.
Responsible partyUsually the sender or booking channel until a carrier acceptance event appears.
What happens nextA physical acceptance or processing scan should be added after handover.
Customer actionCheck the number and ask the sender when the parcel was handed over.
Accepted or in transitThe shipment has a recorded carrier movement or processing event.
View all details for accepted or in-transit status
Lifecycle stageSorting, line-haul or movement between facilities.
Responsible partyThe carrier or logistics partner shown by the latest event.
What happens nextFurther facility, destination or delivery scans may appear.
Customer actionCompare the latest scan location with the expected route and avoid treating a scan gap as proof of loss.
Customs or handoverThe shipment is undergoing border, documentation or partner-transfer processing.
View all details for customs or handover status
Lifecycle stageImport or export processing, exchange or transfer to a destination network.
Responsible partyThe customs authority, carrier or partner named in the event.
What happens nextRelease, additional information request, partner acceptance or onward movement.
Customer actionProvide requested documents or tax information through the official channel; arrival at a customs facility does not equal release.
Out for delivery or deliveredThe parcel is assigned to a delivery route or has a recorded delivery event.
View all details for delivery statuses
Lifecycle stageFinal-mile delivery, pickup or completed delivery.
Responsible partyThe delivery unit or pickup location associated with the event.
What happens nextDelivery, collection, another attempt or return processing.
Customer actionCheck the address, delivery instructions, household members, reception desk and proof-of-delivery information.
Exception or returnA delivery, address, payment, customs or handling issue requires resolution.
View all details for exception or return status
Lifecycle stageDelivery interruption, failed attempt or movement back to the sender.
Responsible partyThe party identified in the event, with the sender often controlling shipment-level corrections.
What happens nextCorrection, reattempt, pickup, hold, investigation or return.
Customer actionContact the seller or official carrier promptly and preserve all shipment evidence.

Services and Delivery Times

Delivery timing must be read from the shipment’s service agreement and route-specific quote. A tracking page may show an estimate, while a service standard or guarantee has separate contractual conditions.

Service Comparison

Service categoryBest use
Domestic parcel deliveryShipments moving within the carrier’s applicable domestic network.
Cross-border shipmentA parcel requiring international transport, border processing or a destination partner.
Business shipmentCommercial consignments arranged under a sender’s account or contract.

Delivery Time

Timing itemHow to interpret it
Estimated delivery dateA planning estimate generated from route, service and available shipment data.
Published service standardA service-specific standard whose scope, exclusions and counting rules must be checked in the applicable carrier terms.
Delivery guaranteeA contractual commitment only where the selected service explicitly provides one; an estimate is not automatically a guarantee.

Destination Country Delivery Times

Destination groupPlanning guidance
Domestic Russian destinationsUse the route-specific estimate shown in the shipment booking or official tracking record.
International destinationsConfirm the contracted service, border route, customs requirements and destination delivery arrangement before relying on an estimate.
Remote or restricted destinationsAllow for additional routing, access, weather, customs or partner-processing time where applicable.

A precise country-by-country average is not inserted without a current DPD (RU) service source because route times can change with origin, destination, contract, customs, weekends, holidays, weather, address quality and handoff arrangements.

Common Tracking Problems and Solutions

Problem & Solution

Problem or statusFirst action
Invalid numberCopy the identifier again, remove accidental spaces, and ask the sender to confirm the carrier number rather than the order number.
No events or label createdAsk when the parcel was physically handed over; electronic pre-advice does not prove acceptance.
No update for an extended periodReview the last scan, consider weekends and handoffs, then ask the sender to contact the shipping account owner.
Customs or handover delayCheck whether documents, duties or recipient information are required through the official channel.
Delivery exception or failed attemptVerify the address and contact the official delivery channel or sender about reattempt or pickup options.
Delivered but not receivedCheck the entrance, safe place, reception desk, household members and neighbours, then request proof-of-delivery details and contact the seller.
Lost or damaged parcelPreserve packaging, photographs, invoices and correspondence; the sender or account holder should ask the carrier about an investigation or claim.
Returned to senderAsk the sender why the return was triggered and whether a corrected address, customs document or new shipment is required.

International Shipping, Customs and Carrier Handoffs

For a cross-border shipment, the latest scan may belong to an origin carrier, customs authority, transport partner or destination delivery network. Arrival at an exchange or customs facility does not by itself mean that customs clearance is complete.

International Flow

StageWhat it means
Origin acceptanceThe origin shipping network records receipt or preparation of the parcel.
Export processingThe shipment is sorted and prepared for departure, subject to route and documentation rules.
Line-haul movementThe shipment moves between transport facilities; scan gaps can occur between departures and arrivals.
Partner handoffElectronic pre-advice, physical transfer and first receiving scan are separate events; a partner scan does not necessarily prove final-carrier acceptance.
Import customsAuthorities or their appointed agents assess documents, duties, restrictions and release requirements.
Destination deliveryA destination network performs final-mile movement, pickup, delivery or return according to the applicable arrangement.

Delivery Management and Post-shipment Options

Delivery changes are controlled by the carrier, sender account or destination partner. The recipient should use the official DPD (RU) route shown for the shipment rather than relying on a third-party tracker to change delivery instructions.

OptionWho should request it
Address correctionUsually the sender or contracted account holder, with recipient cooperation where the carrier permits it.
Redelivery or pickupThe recipient may follow the delivery notice or official tracking instructions, subject to shipment eligibility.
Proof of deliveryThe recipient or sender should request it through the official carrier or account channel when a delivery dispute exists.

Lost, Damaged, Claims, Insurance and Refunds

A tracking inquiry, carrier investigation, insurance claim, postage refund and seller refund are different processes. Keep the shipment number, dispatch record, packaging, contents photographs, invoice and proof of value. The sender or account holder commonly controls carrier claims, while a marketplace refund follows the marketplace’s own rules.

Claims and Refunds

ProcessUse when
Tracking inquiryThe latest event needs clarification or the shipment appears delayed.
Carrier investigationThe shipment appears lost, misrouted or delivered incorrectly; ask the sender or account holder to initiate the official process.
Damage claimContents or packaging arrived damaged; retain the parcel and document the condition before disposal.
Seller or marketplace refundThe purchase dispute concerns the merchant transaction rather than a carrier payment obligation.

Shipping Restrictions and Special Handling

Prohibited and restricted goods depend on the route, service, packaging, transport mode and applicable law. Confirm the current DPD (RU) rules before shipping batteries, liquids, aerosols, dangerous goods, valuables, perishables or regulated documents.

Shipping Restrictions

CategoryPractical precaution
Dangerous goods and batteriesConfirm acceptance, classification and packaging before tender; rejection or delay may follow from incorrect declaration.
Liquids, aerosols and perishablesCheck route-specific restrictions, leakage protection and temperature requirements.
Valuable or regulated goodsCheck declared-value, insurance, documentation and signature conditions.
Customs-controlled goodsUse accurate descriptions, value and origin information; incomplete data can delay clearance or cause return.

Customer Service

Use the official DPD (RU) website for the current tracking entry, contact route and regional service information. Prepare the shipment number, sender and recipient details, dispatch date, latest scan, address, service type, contents description and any photographs before contacting support.

ChannelBest use
Official websiteCurrent tracking, service information and official contact routes.
Sender or marketplaceMissing shipment data, address corrections, seller refunds and account-controlled claims.
17TRACKIndependent multi-carrier event aggregation; it cannot authorize delivery changes or claims.

Ecommerce and Business Tracking

Businesses should distinguish the consumer tracking page, any carrier account integration and a multi-carrier tracking API. A merchant can use standardized events and exception monitoring to answer delivery questions, but the carrier or contracted account owner remains responsible for operational corrections and claims.

Developer/API Comparison

OptionProvider
Official carrier integrationDPD (RU)
View all details for the official carrier integration
Carrier coverageDPD (RU) shipment data subject to the account and service arrangement.
Primary useOperational shipment creation, status retrieval or account workflows where the carrier provides access.
AuthenticationUse the credentials and access method supplied through the carrier’s current business documentation.
Current documentationConfirm the current developer or business integration route directly with DPD (RU).
Migration noteDo not rely on an old endpoint or third-party code sample without checking current carrier documentation.
17TRACK API17TRACK
View all details for the 17TRACK API
Carrier coverageMulti-carrier tracking subject to supported carrier recognition and available events.
Primary useCentralized tracking, normalized events and multi-carrier shipment workflows.
AuthenticationUse a 17TRACK API token in the 17token header.
Current documentation17TRACK API documentation.
Migration noteCheck the current API documentation before production deployment and confirm the carrier code used by your account.

FAQ

Basic FAQs

1. How do I track my DPD (RU) package?

Enter the shipment number on the official DPD (RU) website or use 17TRACK to view available shipment events.

2. Where can I find my DPD (RU) tracking number?

Look in the seller’s dispatch message, marketplace order page, carrier notification, label or shipping receipt.

3. What does a DPD (RU) tracking number look like?

The format depends on the shipment workflow, so use the complete identifier supplied by the sender rather than guessing from a prefix.

4. Why is my DPD (RU) tracking number not updating?

The parcel may be between scans, awaiting handover, undergoing processing or affected by a data delay; ask the sender to confirm physical acceptance.

5. How long does DPD (RU) delivery take?

Delivery time depends on origin, destination, selected service, address, operating conditions and any customs or partner processing.

6. What should I do after a failed DPD (RU) delivery?

Check the delivery event and official instructions, verify the address and contact the carrier or sender about reattempt or pickup options.

7. What should I do if DPD (RU) says delivered but I cannot find the parcel?

Check the entrance, safe place, reception desk, household members and neighbours, then request delivery details and contact the seller.

8. How do I report a lost or damaged DPD (RU) shipment?

Preserve packaging and evidence, then ask the sender or contracted account holder to begin the carrier investigation or claim process.

9. How do I track an international DPD (RU) package?

Use the shipment identifier on the official site or 17TRACK and remember that a partner or destination carrier may provide later events.

10. How do I contact DPD (RU)?

Start with the current contact route on the official DPD (RU) website and prepare the shipment number, address and latest event.

Expert FAQs

11. Is a DPD (RU) label the same as physical acceptance?

No. A label or electronic booking can precede the first physical acceptance scan, so the sender should confirm handover.

12. Can a DPD (RU) shipment have more than one tracking identifier?

Yes, a cross-border or partner workflow can expose linked identifiers; ask the sender to provide the number used by the current delivery network.

13. Does arrival at customs mean a DPD (RU) shipment is cleared?

No. Arrival, inspection, document review, duty assessment and release are separate stages.

14. Who can request a DPD (RU) address correction?

The sender or contracted account holder generally controls shipment corrections, while recipient participation depends on the service and delivery stage.

15. Can businesses track DPD (RU) shipments through an API?

Businesses should confirm current DPD (RU) integration access directly with the carrier or use the documented 17TRACK API for supported multi-carrier tracking.

16. What is the difference between DPD (RU) tracking and 17TRACK tracking?

The official DPD (RU) route is carrier-specific, while 17TRACK is an independent aggregator that organizes available events from supported networks.

17. Can 17TRACK change a DPD (RU) delivery address?

No. Address changes, redelivery requests and claims must follow the official carrier or sender-account process.

18. Is a DPD (RU) estimated delivery date guaranteed?

Not automatically. An estimate is a planning indication; a guarantee exists only when the selected service terms expressly provide one.

Tracking API

API
// 1. Carrier official tracking API
// Current public official DPD (RU) tracking API endpoint and authentication
// are not established from the available evidence. Confirm them directly
// with DPD (RU) before implementing an official integration.

// 2. 17TRACK API
POST https://api.17track.net/track/v2.4/register
Headers:
  17token: YourKey
  Content-Type: application/json

Body:
[
  {
    "number": "TRACKING_NUMBER",
    "carrier": "CARRIER_CODE"
  }
]

// Confirm the current DPD (RU) carrier code in the 17TRACK documentation
// or account materials before sending production requests.

Sources & References

17TRACK is an independent tracking platform and is not affiliated with DPD (RU).

A professional and stable global package tracking platform.

17TRACK