About DPD(IT)
DPD(IT) is the Lithuanian operation of the Geopost parcel-delivery network. It serves private and business customers with courier delivery, parcel-locker delivery, shipment tracking, returns, proof of delivery and ecommerce shipping tools. The official Lithuanian website presents DPD(IT) as a parcel-delivery operator in Lithuania, while the international network connects local operations and Geopost partner brands.
Carrier Overview
| Field | Verified information |
| Official operating identity | DPD(IT), the Lithuanian parcel-delivery operation presented locally as DPD Lietuva |
| Official website | https://www.dpd.com/lt/lt/ |
| Carrier type | Parcel courier, parcel-locker operator and domestic or cross-border delivery-network participant |
| Primary region | Lithuania, with connections to the wider European and international Geopost network |
| Tracking page | The “Kur mano siunta?” shipment-tracking tool on the official Lithuanian website |
| Parent organization | Geopost |
Carrier Entity Relationships
| Entity | Relationship |
| DPD(IT) | DPD(IT) is the canonical carrier entity for Lithuanian courier and parcel-locker tracking. |
View all details for DPD(IT)
| Entity type | Local parcel-delivery operation |
| Why it matters to tracking | Use this carrier when the shipment was booked with or is being delivered by the Lithuanian operation. |
| Official evidence | The Lithuanian website provides shipment tracking, parcel-locker search, delivery services and support. |
|
| Geopost | Geopost is the parent parcel-delivery network of DPD(IT). |
View all details for Geopost
| Entity type | Parent delivery network |
| Why it matters to tracking | Cross-border movements can involve another local operation or a Geopost partner brand. |
| Official evidence | The global official site identifies DPD(IT) as part of Geopost and lists its country operations and partner brands. |
|
| myDPD | myDPD is a shipment-management product offered for private and business users. |
View all details for myDPD
| Entity type | Tracking and shipment-management product |
| Why it matters to tracking | Eligible users can manage shipments through the carrier’s own environment. |
| Official evidence | The official Lithuanian navigation identifies separate myDPD options for business and private users. |
|
| Geopost country partners | Country operations and partner brands may carry a cross-border parcel before or after DPD(IT). |
View all details for network partners
| Entity type | International and last-mile delivery partners |
| Why it matters to tracking | A partner name or a second parcel identifier may appear after an international handoff. |
| Official evidence | The global network lists local operations and partners including Chronopost, SEUR, BRT, Speedy, PostNord and others. |
|
| 17TRACK | 17TRACK independently aggregates available tracking events for DPD(IT) and other carriers. |
View all details for 17TRACK
| Entity type | Independent multi-carrier tracking platform |
| Why it matters to tracking | It can centralize events from more than one carrier but cannot transport, redirect, refund or settle a claim. |
| Official evidence | 17TRACK provides consumer tracking and a multi-carrier API. |
|
Quick Answer
Enter the parcel number shown on the shipping label, dispatch message or sender’s shipment record in the official DPD(IT) “Kur mano siunta?” tool, or submit the same number to 17TRACK. If no result appears, remove accidental spaces, confirm that the number is a carrier tracking number rather than an order number, and allow time for the first physical acceptance scan. 17TRACK is an independent tracking platform; it does not carry parcels or control address changes, delivery attempts, refunds or claims.
Pro Tip: A label-created record proves that shipment data exists. It does not by itself prove that DPD(IT) has received the physical parcel.
How to Track DPD(IT) Packages
Use the official tool for carrier-controlled delivery information and 17TRACK when you need one view across multiple carriers or a cross-border handoff.
- Copy the complete parcel number from the shipping label, receipt, dispatch email, marketplace order page or sender.
- Open the official DPD(IT) website and select “Kur mano siunta?” to check the carrier record.
- Alternatively, enter the same number on 17TRACK and select DPD(IT) if automatic carrier detection needs confirmation.
- Read the latest event together with its location and timestamp. Determine whether DPD(IT), a sender, customs or a partner carrier currently controls the next action.
- For delivery changes, proof of delivery or a claim, continue through the official DPD(IT) support channel rather than 17TRACK.
Which Identifier Should You Use?
| Identifier | Correct use |
| Parcel tracking number | Use for official DPD(IT) tracking and 17TRACK. |
| Merchant order number | Use with the store; it may not be searchable in a carrier tracker. |
| Merchant reference | Use when communicating with the merchant unless the merchant confirms that it is also carrier-searchable. |
| Partner or last-mile number | Use with the named partner after a cross-border handoff; retain the original number as well. |
| Delivery notice information | Use for the instructions shown on the notice; it is not automatically interchangeable with the parcel number. |
Tracking Statuses and Meanings
Read each status as evidence of a specific logistics event, not as proof that every later step has already occurred.
Status Quick Lookup
| Status | What it means |
| Shipment data received | A label or electronic shipment record exists. |
View all details for shipment data received| Lifecycle stage | Pre-shipment |
|---|
| Current responsible party | The sender remains responsible until physical handoff is recorded. |
|---|
| What happens next | Pickup, locker deposit or acceptance scan. |
|---|
| What you should do | Ask the sender whether the parcel has physically left its premises if the status persists. |
|---|
|
| Parcel accepted | DPD(IT) or an identified origin partner has scanned the physical parcel. |
View all details for parcel accepted| Lifecycle stage | Accepted |
|---|
| Current responsible party | The carrier named in the event. |
|---|
| What happens next | Origin sorting and line-haul movement. |
|---|
| What you should do | Monitor the next processing scan. |
|---|
|
| In transit or at sorting terminal | The parcel is moving through a terminal or between network locations. |
View all details for in-transit processing| Lifecycle stage | In transit |
|---|
| Current responsible party | The operating carrier or line-haul partner. |
|---|
| What happens next | Another terminal scan, destination arrival or handoff. |
|---|
| What you should do | Wait while the parcel remains within the route estimate; investigate only after a material delay. |
|---|
|
| Customs or partner processing | A cross-border parcel is undergoing border formalities or network transfer. |
View all details for customs or handoff| Lifecycle stage | Customs/Handover |
|---|
| Current responsible party | Customs, a broker or the carrier named in the latest event. |
|---|
| What happens next | Release, request for information, tax collection or physical partner receipt. |
|---|
| What you should do | Respond only through a verified carrier or customs channel if documents or payment are requested. |
|---|
|
| Out for delivery | The parcel is assigned to the delivery route. |
View all details for out for delivery| Lifecycle stage | Out for delivery |
|---|
| Current responsible party | The local delivery operation. |
|---|
| What happens next | Door delivery, parcel-locker deposit or a delivery exception. |
|---|
| What you should do | Follow verified delivery notifications and ensure the recipient details are usable. |
|---|
|
| Delivered | A delivery scan records completion at the stated location or recipient. |
View all details for delivered| Lifecycle stage | Delivered |
|---|
| Current responsible party | The recipient controls the parcel after valid delivery; DPD(IT) controls any carrier investigation. |
|---|
| What happens next | The shipment closes unless delivery is disputed. |
|---|
| What you should do | Check the stated location, household members, reception, neighbors and proof of delivery before reporting non-receipt. |
|---|
|
| Ready for pickup | The parcel is available at the stated locker or pickup location. |
View all details for pickup| Lifecycle stage | Pickup |
|---|
| Current responsible party | The pickup location holds the parcel; the recipient must collect it. |
|---|
| What happens next | Collection or return after the applicable holding period. |
|---|
| What you should do | Use the official collection instructions and retrieve the parcel before the deadline in the notification. |
|---|
|
| Delivery exception | Delivery could not proceed because of an address, access, recipient, weather, damage or operational issue. |
View all details for a delivery exception| Lifecycle stage | Exception |
|---|
| Current responsible party | DPD(IT), the recipient or sender depending on the stated reason. |
|---|
| What happens next | Another attempt, pickup arrangement, clarification or return. |
|---|
| What you should do | Follow the event-specific instruction and contact official support when an action is required but unavailable online. |
|---|
|
| Returning to sender | The delivery process has ended and the parcel is moving back through the network. |
View all details for return to sender| Lifecycle stage | Return |
|---|
| Current responsible party | The carrier during transport; the sender controls the commercial resolution. |
|---|
| What happens next | Return sorting and delivery to the sender. |
|---|
| What you should do | The recipient should contact the seller; the sender should monitor the return and decide on refund or reshipment. |
|---|
|
Services and Delivery Times
DPD(IT) offers services for private customers, businesses, ecommerce shipments, courier delivery, parcel lockers, returns and temperature-oriented delivery through DPD fresh. Use the service-specific booking quote or official delivery-times tool for a route estimate; an estimated date is not automatically a guaranteed commitment.
Service Comparison
| Service | Best for |
| Courier parcel delivery | Address delivery for private and business shipments. |
View all details for courier parcel delivery| Service type | Parcel courier |
|---|
| Coverage | Lithuania and supported network destinations selected during booking. |
|---|
| Tracking level | Shipment-event tracking and delivery outcome where scans are available. |
|---|
| Key size/weight condition | The booked parcel must satisfy the current service and packaging rules. |
|---|
| Included protection/extra service | Depends on the booked contract or consumer service terms. |
|---|
| Main limitation | Route, parcel characteristics and destination determine eligibility. |
|---|
|
| Parcel-locker delivery | Out-of-home sending or collection through an eligible locker. |
View all details for parcel-locker delivery| Service type | Parcel locker |
|---|
| Coverage | Available DPD(IT) locker locations. |
|---|
| Tracking level | Deposit, network movement and pickup-related events where available. |
|---|
| Key size/weight condition | The parcel must fit an available compartment and meet current locker rules. |
|---|
| Included protection/extra service | Recipient collection notification and access instructions. |
|---|
| Main limitation | Locker capacity and parcel dimensions can affect routing. |
|---|
|
| Business shipping | Contract customers managing multiple shipments. |
View all details for business shipping| Service type | Business parcel solution |
|---|
| Coverage | Routes and services agreed for the customer account. |
|---|
| Tracking level | Shipment management through the carrier’s business tools. |
|---|
| Key size/weight condition | Account and product conditions apply. |
|---|
| Included protection/extra service | Account-specific administration and delivery options. |
|---|
| Main limitation | Features and prices depend on the commercial agreement. |
|---|
|
| Returns | Merchant-authorized return movements. |
View all details for returns| Service type | Reverse logistics |
|---|
| Coverage | Routes enabled by the merchant or booking method. |
|---|
| Tracking level | Return parcel events after registration and acceptance. |
|---|
| Key size/weight condition | The return must comply with the provided label and packaging instructions. |
|---|
| Included protection/extra service | Depends on the merchant’s return arrangement. |
|---|
| Main limitation | A carrier return does not itself authorize a merchant refund. |
|---|
|
| DPD fresh | Eligible temperature-sensitive food or specialized deliveries. |
View all details for DPD fresh| Service type | Specialized fresh-delivery solution |
|---|
| Coverage | Eligible Lithuanian routes and customer arrangements. |
|---|
| Tracking level | Shipment tracking according to the booked solution. |
|---|
| Key size/weight condition | Special product, packaging and handling conditions apply. |
|---|
| Included protection/extra service | Service-specific handling. |
|---|
| Main limitation | It should not be assumed to cover every parcel, commodity or route. |
|---|
|
Delivery Time
| Service | Published delivery standard |
| Lithuanian parcel delivery | Use the current DPD(IT) delivery-times tool or booking result for the specific route. |
View timing conditions for Lithuanian parcel delivery| Business or calendar days | The service-specific result controls; weekends and holidays can alter operating days. |
|---|
| Guarantee status | Treat a displayed estimate as non-guaranteed unless the booked terms expressly state otherwise. |
|---|
| Starts counting from | Physical acceptance under the applicable service terms, not merely label creation. |
|---|
| Main delay factors | Cutoff time, address quality, locker capacity, weather, peak volume, holidays and operational disruption. |
|---|
| Official source date/validity | Use the live official route result applicable when the shipment is booked. |
|---|
|
| Cross-border parcel delivery | Use the current origin-to-destination estimate supplied during booking or by the official delivery-times tool. |
View timing conditions for cross-border delivery| Business or calendar days | The route-specific result and local operating calendars apply. |
|---|
| Guarantee status | An estimated window does not establish a money-back guarantee. |
|---|
| Starts counting from | Carrier acceptance according to the selected service. |
|---|
| Main delay factors | International line-haul, partner handoff, customs where applicable, remote areas, holidays and incomplete data. |
|---|
| Official source date/validity | Use the live estimate for the booked shipment because route conditions can change. |
|---|
|
Destination Country Delivery Times
| Destination Country / Region | Estimated Delivery Time Range |
| Lithuania and supported international destinations | Use the live route-specific estimate displayed by DPD(IT) when booking or checking delivery times. |
View destination timing methodology
| Primary Service Type | Domestic courier, parcel locker or supported cross-border parcel service selected during booking. |
| Average Delivery Days | Use the shipment-specific carrier estimate rather than an unverified cross-carrier average. |
| Last-Mile Partner / Handoff Carrier | DPD(IT) in Lithuania; another Geopost operation or identified local partner may handle an international destination. |
| Customs & Clearance Tips | EU internal movements and third-country imports follow different formalities. A destination-arrival scan does not mean customs release, and recipients should respond only to verified requests. |
|
Route averages have deliberately not been invented. Delivery dates depend on the booked service, acceptance time, origin, destination, operating calendar, customs requirements and partner handoff. The shipment-specific official estimate is more reliable than a generic country average.
Common Tracking Problems and Solutions
Start with the latest physical scan, identify who currently controls the parcel, and escalate through the sender or DPD(IT) according to the problem.
Problem & Solution
| Problem/status shown | Immediate action |
| Invalid number or no result | Copy the complete carrier number again and remove accidental punctuation or spaces. |
View all details for an invalid number| Likely cause | Order reference used, transcription error, new record not synchronized or wrong carrier selected. |
|---|
| Check first | Compare the number with the label or sender’s dispatch message. |
|---|
| When to escalate | After the sender confirms dispatch but neither the official tracker nor 17TRACK recognizes the parcel. |
|---|
| Who to contact | The sender first; DPD(IT) if a carrier-issued number remains unrecognized. |
|---|
|
| Shipment data received only | Ask the sender whether the physical parcel has been handed over. |
View all details for pre-shipment only| Likely cause | Label created before pickup or locker deposit. |
|---|
| Check first | Sender’s actual handoff date. |
|---|
| When to escalate | When the sender confirms handoff but no physical scan appears within the expected pickup-processing cycle. |
|---|
| Who to contact | The sender, who can verify collection records. |
|---|
|
| Long gap or stuck in transit | Compare the elapsed time with the shipment-specific estimate and check service alerts or partner tracking. |
View all details for a tracking gap| Likely cause | Line-haul movement, missed scan, terminal backlog, international handoff or disruption. |
|---|
| Check first | Latest physical location, route estimate and any second carrier number. |
|---|
| When to escalate | When the parcel is beyond the applicable estimate or the carrier instructs the customer to open an inquiry. |
|---|
| Who to contact | DPD(IT) for a local movement; the sender for a formal contractual investigation. |
|---|
|
| Partner handoff pending | Wait for the receiving carrier’s first physical scan and retain both identifiers. |
View all details for a partner handoff| Likely cause | Electronic data arrived before the physical parcel. |
|---|
| Check first | Whether the event says data received or physically accepted. |
|---|
| When to escalate | After the route estimate is exceeded without a receiving scan. |
|---|
| Who to contact | The carrier that last recorded physical custody or the sender. |
|---|
|
| Address issue or failed delivery | Follow the official notification or myDPD option available for that parcel. |
View all details for a failed delivery| Likely cause | Incomplete address, access problem, unavailable recipient or route constraint. |
|---|
| Check first | The exception reason and any delivery-management link. |
|---|
| When to escalate | Immediately if the address is materially wrong or no permitted corrective option appears. |
|---|
| Who to contact | DPD(IT) for delivery options; the sender when contractual address correction is required. |
|---|
|
| Ready for pickup | Collect the parcel using the verified instructions before the deadline stated in the notification. |
View all details for pickup| Likely cause | The selected or redirected service ends at a locker or pickup point. |
|---|
| Check first | Location, access information and collection deadline. |
|---|
| When to escalate | If access information fails or the parcel is absent from the stated location. |
|---|
| Who to contact | DPD(IT). |
|---|
|
| Customs hold | Check for a verified request for invoice, identification, commodity details or tax payment. |
View all details for a customs hold| Likely cause | Import review, missing declaration data, tax assessment or restricted goods check. |
|---|
| Check first | The requesting organization and official payment or document channel. |
|---|
| When to escalate | When required information has been supplied but the authorized party requests follow-up. |
|---|
| Who to contact | The named broker, customs authority, DPD(IT) or sender according to the event. |
|---|
|
| Delivered but not received | Check the stated delivery location, household, reception, neighbors and proof of delivery before reporting non-receipt. |
View all details for delivered but not received| Likely cause | Safe-location delivery, another recipient, reception acceptance, locker delivery, address mismatch or scan dispute. |
|---|
| Check first | Proof of delivery, notification, parcel location and everyone who may have accepted it. |
|---|
| When to escalate | Promptly after local checks fail. |
|---|
| Who to contact | DPD(IT) for delivery evidence and the sender for a contractual claim or replacement. |
|---|
|
| Lost or damaged parcel | Preserve the parcel, contents, packaging, label, photographs and value evidence; notify the sender and DPD(IT). |
View all details for loss or damage| Likely cause | Transport damage, missing contents, delivery dispute or unresolved movement. |
|---|
| Check first | Claim eligibility under the booked service and who contracted with the carrier. |
|---|
| When to escalate | As soon as the problem is discovered, using the current official claim instructions. |
|---|
| Who to contact | The sender usually manages the carrier contract; recipients should also report visible damage and preserve evidence. |
|---|
|
| Returning to sender | Contact the seller about refund or reshipment and monitor the return movement. |
View all details for return to sender| Likely cause | Failed delivery, uncollected parcel, address problem, refusal or shipment-rule issue. |
|---|
| Check first | The return reason shown in tracking. |
|---|
| When to escalate | If the return stalls beyond the applicable route estimate. |
|---|
| Who to contact | The sender for the commercial outcome; DPD(IT) for transport information. |
|---|
|
International Shipping, Customs and Carrier Handoffs
A cross-border shipment can move through DPD(IT), another Geopost operation, line-haul providers, customs authorities and a destination delivery partner. Electronic pre-advice, physical handoff and the receiving carrier’s first scan are separate events.
International Flow
| Stage | What is happening |
| Shipment registration | The sender creates the shipment record and label. |
View all details for shipment registration| Physical custodian/responsible entity | The sender until physical acceptance. |
|---|
| Typical tracking event | Shipment data received. |
|---|
| Can the tracking number change? | A partner number may later be added, but the original should be retained. |
|---|
| Normal visibility gap | Between label creation and the first carrier scan. |
|---|
| What the customer should do | Confirm physical handoff with the sender if the status does not progress. |
|---|
|
| Origin acceptance and sorting | The origin operation scans and sorts the physical parcel. |
View all details for origin processing| Physical custodian/responsible entity | DPD(IT) for outbound Lithuanian shipments or the identified origin carrier for inbound shipments. |
|---|
| Typical tracking event | Accepted, collected or processed at terminal. |
|---|
| Can the tracking number change? | Usually the original remains, but an internal or partner identifier may be linked. |
|---|
| Normal visibility gap | Between terminal dispatch and the next hub scan. |
|---|
| What the customer should do | Monitor the route estimate. |
|---|
|
| Export and line-haul | The parcel leaves the origin network and travels toward the destination operation. |
View all details for export and line-haul| Physical custodian/responsible entity | The operating network or contracted line-haul provider. |
|---|
| Typical tracking event | Departed terminal or in transit. |
|---|
| Can the tracking number change? | A destination identifier may be prepared during this stage. |
|---|
| Normal visibility gap | Movement between hubs may produce no public scan. |
|---|
| What the customer should do | Do not interpret the absence of an intermediate scan as proof of loss. |
|---|
|
| Customs processing where applicable | Authorities or an authorized broker review declaration data, goods and import obligations. |
View all details for customs processing| Physical custodian/responsible entity | The carrier may hold the parcel while customs controls release. |
|---|
| Typical tracking event | Customs processing, information required, held or released. |
|---|
| Can the tracking number change? | Customs references may be added without replacing the parcel number. |
|---|
| Normal visibility gap | Review time is not a carrier transit guarantee. |
|---|
| What the customer should do | Provide accurate documents or payment through verified channels when requested. |
|---|
|
| Partner handoff | Electronic data is sent, the physical parcel is transferred, and the receiving operation records acceptance. |
View all details for partner handoff| Physical custodian/responsible entity | The dispatching carrier remains the last verified custodian until the receiving carrier records physical receipt. |
|---|
| Typical tracking event | Data received, handed to partner or received by destination operation. |
|---|
| Can the tracking number change? | Yes, a partner number can be linked while the original remains useful. |
|---|
| Normal visibility gap | Between electronic pre-advice and the first receiving scan. |
|---|
| What the customer should do | Track both identifiers and avoid assuming that pre-advice equals physical custody. |
|---|
|
| Destination delivery | The destination operation sorts the parcel and performs door, locker or pickup delivery. |
View all details for destination delivery| Physical custodian/responsible entity | DPD(IT) for eligible Lithuanian last-mile parcels or the identified destination partner abroad. |
|---|
| Typical tracking event | At destination terminal, out for delivery, ready for pickup or delivered. |
|---|
| Can the tracking number change? | The partner identifier may become the most detailed local reference. |
|---|
| Normal visibility gap | Between destination arrival and route assignment. |
|---|
| What the customer should do | Use the destination carrier’s official delivery-management options when named. |
|---|
|
Delivery Management and Post-shipment Options
DPD(IT) provides myDPD, parcel-locker tools, pickup-location search and proof-of-delivery access. Options depend on the shipment, sender restrictions and its current stage.
Delivery Management
| Option | Who can request |
| myDPD shipment management | Eligible private or business users. |
View all details for myDPD| Eligibility | The shipment and user account must support the displayed option. |
|---|
| Deadline/available stage | Before the delivery stage closes and while the option remains visible. |
|---|
| Fee | Any applicable charge should be shown in the official workflow. |
|---|
| Guaranteed? | No; operational and sender restrictions can apply. |
|---|
| Official action link | Open the DPD(IT) website and select myDPD. |
|---|
|
| Parcel-locker pickup | The named recipient using the official collection instructions. |
View all details for parcel-locker pickup| Eligibility | The parcel must be routed to and available in a locker. |
|---|
| Deadline/available stage | During the collection period stated in the notification. |
|---|
| Fee | Determined by the booked delivery service. |
|---|
| Guaranteed? | Availability depends on successful deposit and valid access information. |
|---|
| Official action link | Use the official locker finder and shipment tools. |
|---|
|
| Proof of delivery | Authorized shipment parties using the official POD function. |
View all details for proof of delivery| Eligibility | A completed shipment with available delivery evidence. |
|---|
| Deadline/available stage | After a delivery event is recorded. |
|---|
| Fee | Depends on service and account conditions. |
|---|
| Guaranteed? | The available record depends on the delivery method and shipment permissions. |
|---|
| Official action link | Select the official shipment delivery confirmation function. |
|---|
|
Lost, Damaged, Claims, Insurance and Refunds
A tracking inquiry, carrier claim and merchant refund are separate processes. The party that booked and paid for carriage commonly controls the carrier contract, while the recipient should promptly document loss, damage or missing contents.
Claims and Refunds
| Process | Use when |
| Tracking inquiry | The parcel is delayed, has conflicting events or needs delivery clarification. |
View all details for a tracking inquiry| Who files | Sender or recipient may ask for tracking clarification, subject to shipment permissions. |
|---|
| Earliest/latest filing time | Use the current official support instructions and the applicable service terms. |
|---|
| Required evidence | Parcel number, sender and recipient details, dispatch date and latest event. |
|---|
| Possible outcome | Status explanation, operational inquiry or instruction to submit a formal claim. |
|---|
| Official link | DPD(IT) support |
|---|
|
| Loss, damage or missing-contents claim | The parcel is lost, damaged or arrives with contents missing. |
View all details for a carrier claim| Who files | The contracting sender or another party permitted by the applicable terms. |
|---|
| Earliest/latest filing time | Report promptly and follow the current service-specific deadline shown in the official rules or claim workflow. |
|---|
| Required evidence | Tracking record, value proof, item description, photographs, label, outer and inner packaging, and damage evidence. |
|---|
| Possible outcome | Investigation, request for evidence, compensation under applicable terms or denial. |
|---|
| Official link | Select “Registruoti pretenziją” on the official website |
|---|
|
| Merchant refund or replacement | The buyer seeks a commercial remedy for goods not received or received damaged. |
View all details for merchant resolution| Who files | The buyer contacts the seller or marketplace. |
|---|
| Earliest/latest filing time | The merchant or marketplace policy controls. |
|---|
| Required evidence | Order record, tracking, photographs and communication history. |
|---|
| Possible outcome | Refund, replacement, denial or request to await a carrier investigation. |
|---|
| Official link | Use the seller or marketplace order-support channel. |
|---|
|
17TRACK can display tracking information but cannot approve compensation, postage refunds, merchant refunds or insurance settlements.
Shipping Restrictions and Special Handling
Check the current DPD(IT) shipping rules before tendering goods. Restrictions depend on the commodity, packaging, route, transport mode and destination law.
Shipping Restrictions
| Category | Prohibited or restricted |
| Dangerous or regulated goods | Acceptability depends on the exact substance, classification, route and service authorization. |
View handling details for dangerous goods| Typical examples | Flammable, explosive, corrosive, toxic or pressurized materials. |
|---|
| Key condition/packaging | Legal classification, documentation, approved packaging and carrier authorization may be required. |
|---|
| Transport limitation | Some goods cannot use ordinary parcel channels or certain cross-border routes. |
|---|
| Possible tracking/delivery impact | Refusal, hold, inspection, route change or return. |
|---|
| Official rules | DPD(IT) shipping and delivery rules |
|---|
|
| Batteries and liquids | Restrictions vary by battery chemistry, installation state, liquid type and route. |
View handling details for batteries and liquids| Typical examples | Lithium batteries, aerosols, chemicals and leak-prone liquids. |
|---|
| Key condition/packaging | Prevent short circuits, movement, leakage and damage; use required labels and documentation. |
|---|
| Transport limitation | Air, road and international rules can differ. |
|---|
| Possible tracking/delivery impact | Security review, rejection or return. |
|---|
| Official rules | DPD(IT) packaging and shipment rules |
|---|
|
| Perishable or temperature-sensitive goods | Use only an eligible specialized solution, such as DPD fresh, when its conditions cover the commodity and route. |
View handling details for perishables| Typical examples | Fresh food and temperature-sensitive products. |
|---|
| Key condition/packaging | Service-specific packaging, preparation and handoff conditions apply. |
|---|
| Transport limitation | Ordinary parcel service should not be assumed suitable. |
|---|
| Possible tracking/delivery impact | Time-sensitive routing, refusal or spoilage risk after delay. |
|---|
| Official rules | DPD(IT) service information |
|---|
|
| Poorly packed or non-standard parcels | Acceptance and handling depend on current packaging and standard/non-standard shipment rules. |
View handling details for non-standard parcels| Typical examples | Irregular shapes, unstable packaging, exposed parts or insufficient cushioning. |
|---|
| Key condition/packaging | Use rigid outer packaging, secure closure, internal cushioning and a readable label. |
|---|
| Transport limitation | Manual handling, surcharge, refusal or specialized arrangement may apply. |
|---|
| Possible tracking/delivery impact | Processing delay, damage, return or claim limitation. |
|---|
| Official rules | DPD(IT) packaging guidance |
|---|
|
Customer Service
Use the official tracking tool first, then the relevant support, claim, proof-of-delivery or locker function. Prepare the parcel number and latest scan before contacting DPD(IT).
Customer Service
| Channel | Verified contact/link |
| Official tracking | Open DPD(IT) and select “Kur mano siunta?” |
View all details for official tracking| Best for | Latest carrier events and delivery status. |
|---|
| Region/language | Lithuania; Lithuanian and English site options are presented. |
|---|
| Hours and time zone | Online self-service. |
|---|
| Information to prepare | Complete parcel number. |
|---|
| Important limitation | Tracking cannot authorize a claim or merchant refund. |
|---|
|
| Official contact page | Open the DPD(IT) website and select “Kontaktai” |
View all details for official contact| Best for | Delivery exceptions, tracking clarification and service questions. |
|---|
| Region/language | Lithuanian operation. |
|---|
| Hours and time zone | Follow the current hours displayed on the official contact page. |
|---|
| Information to prepare | Parcel number, sender, recipient, dispatch date, address, latest event and requested outcome. |
|---|
| Important limitation | Some changes or claims may require the contracting sender. |
|---|
|
| Claim registration | Open the official website and select “Registruoti pretenziją” |
View all details for claim registration| Best for | Eligible loss, damage or missing-contents cases. |
|---|
| Region/language | Lithuanian operation and applicable service terms. |
|---|
| Hours and time zone | Online submission availability is shown by the official workflow. |
|---|
| Information to prepare | Parcel number, value proof, item description, photographs, packaging and account details. |
|---|
| Important limitation | Claim rights and filing authority depend on the transport contract. |
|---|
|
| Locker finder | Open the official website and select the parcel-locker finder |
View all details for the locker finder| Best for | Finding a DPD(IT) parcel locker and checking location information. |
|---|
| Region/language | Lithuania. |
|---|
| Hours and time zone | Location access and servicing information depends on the selected locker. |
|---|
| Information to prepare | City, address or preferred area. |
|---|
| Important limitation | Finding a locker does not guarantee compartment capacity for a specific parcel. |
|---|
|
Efficient escalation order: check tracking, review the latest notification, use myDPD if an eligible action is displayed, contact DPD(IT), and involve the sender when the carrier contract, claim or commercial refund requires sender action.
Ecommerce and Business Tracking
DPD(IT) offers business shipment management and ecommerce modules, while 17TRACK provides independent multi-carrier tracking and API access. Merchants should keep order IDs separate from carrier parcel numbers and preserve partner identifiers during handoffs.
Developer/API Comparison
| Option | Provider |
| Consumer tracking and myDPD | DPD(IT) |
View all details for DPD(IT) consumer and business tools| Carrier coverage | DPD(IT) shipments and supported network movements. |
|---|
| Primary use | Individual tracking, shipment administration and eligible delivery management. |
|---|
| Authentication | Public tracking uses a parcel number; account functions use the relevant customer access. |
|---|
| Tracking/batch/webhook capability | Capabilities depend on the customer product and account arrangement. |
|---|
| Current developer documentation | Use official business support for approved technical integration information. |
|---|
| Migration/deprecation note | Do not build against undocumented endpoints or copied legacy examples. |
|---|
|
| Ecommerce platform modules | DPD(IT) |
View all details for ecommerce modules| Carrier coverage | DPD(IT) shipping functions supported by the selected ecommerce module. |
|---|
| Primary use | Shipment creation and store-platform workflow integration. |
|---|
| Authentication | Module and customer-account configuration. |
|---|
| Tracking/batch/webhook capability | Depends on the official module and account configuration. |
|---|
| Current developer documentation | Official DPD(IT) ecommerce modules |
|---|
| Migration/deprecation note | Confirm platform compatibility before upgrading a store or module. |
|---|
|
| Multi-carrier Tracking API | 17TRACK |
View all details for the 17TRACK API| Carrier coverage | Multiple carriers through one integration. |
|---|
| Primary use | Registration, normalized tracking visibility and multi-carrier operational workflows. |
|---|
| Authentication | 17token request header. |
|---|
| Tracking/batch/webhook capability | Use the capabilities and limits documented for the selected 17TRACK API product. |
|---|
| Current developer documentation | 17TRACK API documentation |
|---|
| Migration/deprecation note | Use the current documented version and review release or migration notices before deployment. |
|---|
|
DPD(IT) FAQ
1. How do I track my DPD(IT) package?Enter the carrier parcel number in the official DPD(IT) “Kur mano siunta?” tool or submit it to 17TRACK. Use the official channel for delivery changes, proof of delivery and claims.
2. Where can I find my DPD(IT) tracking number?Look on the shipping label, sender’s shipment record, dispatch email, marketplace order page or verified delivery notification. If you only have an order number, ask the seller for the carrier parcel number.
3. What does a DPD(IT) tracking number look like?Use the complete value generated for the shipment rather than identifying it from a prefix alone. Different account, service, country and partner systems may use different identifier structures.
4. When will the first DPD(IT) tracking event appear?The first physical movement event normally appears after pickup, locker deposit or carrier acceptance. A label-created status can appear earlier and does not prove that DPD(IT) has the parcel.
5. Why is my DPD(IT) tracking not updating?A parcel can travel between terminals without a public scan, wait for partner receipt or encounter an operational delay. Compare the elapsed time with the shipment-specific estimate and contact the sender or DPD(IT) if the route estimate is exceeded.
6. How long does DPD(IT) delivery take?Use the live route estimate shown by DPD(IT) for the booked service and destination. Label creation, weekends, holidays, remote delivery, customs and partner handoffs can change the final date.
7. What should I do after a failed DPD(IT) delivery?Read the exception reason and follow the official notification or eligible myDPD option. Contact DPD(IT) promptly if the address is wrong or no usable redelivery or pickup instruction appears.
8. What should I do if DPD(IT) says delivered but I have no parcel?Check the stated location, household members, reception, neighbors, locker notification and proof of delivery first. If the parcel remains missing, contact DPD(IT) for delivery evidence and notify the sender so the contractual investigation can begin.
9. How do I report a lost or damaged DPD(IT) parcel?Preserve the item, label, outer and inner packaging, photographs and value proof, then use the official claim route. The sender may need to file because the sender commonly holds the transport contract.
10. How do I contact DPD(IT)?Open the official DPD(IT) website and select “Kontaktai” for current contact channels. Prepare the parcel number, dispatch date, addresses, service, latest event and requested resolution.
11. Can a DPD(IT) international parcel keep its original tracking number?Yes, the original identifier may continue across the network, but a destination partner can also add a local number. Keep both because each support system may index a different identifier.
12. Does a partner-data event mean DPD(IT) physically has the parcel?No, electronic pre-advice can arrive before physical handoff. Custody is better established by the receiving carrier’s acceptance or processing scan.
13. Does destination arrival mean a DPD(IT) parcel has cleared customs?No, destination arrival and customs release are different events. Wait for an explicit release or onward-processing event and respond only to verified document or tax requests.
14. Can I obtain proof of delivery from DPD(IT)?DPD(IT) provides a shipment delivery confirmation function for eligible completed shipments. Availability and the information shown depend on the delivery method, service and user authorization.
15. Is the estimated DPD(IT) delivery date guaranteed?An estimate is not automatically a guarantee. A guaranteed commitment must be expressly included in the booked service terms, while ordinary estimates can change because of route and operational conditions.
16. Can businesses track DPD(IT) shipments through an API?Businesses can use approved DPD(IT) account tools or integrate multi-carrier tracking through the documented 17TRACK API. Obtain official technical documentation before using a carrier endpoint and do not rely on undocumented or legacy examples.
17. How should an ecommerce merchant handle DPD(IT) tracking IDs?Store the merchant order ID, original carrier parcel number and any partner number as separate linked fields. This prevents an order reference from being submitted as a tracking number and preserves visibility after a cross-border handoff.
Tracking API
# 1. DPD(IT) official tracking API
# Current public official tracking API not confirmed from the cited public material.
# Obtain current endpoint, method, authentication and account approval
# directly from DPD(IT) before implementation. Do not use undocumented endpoints.
# 2. 17TRACK multi-carrier API
# Documentation: https://api.17track.net/en/doc
# Replace TRACKING_NUMBER, CARRIER_CODE and YourKey with verified values.
# The DPD(IT) carrier code is intentionally left as a placeholder.
curl --request POST \
--url https://api.17track.net/track/v2.4/register \
--header '17token: YourKey' \
--header 'Content-Type: application/json' \
--data '[
{
"number": "TRACKING_NUMBER",
"carrier": "CARRIER_CODE"
}
]'
Sources & References
17TRACK is an independent tracking platform and is not affiliated with DPD(IT).