Omniva tracking at a glance
- Enter: One supported Omniva shipment tracking code.
- Do not enter: A six-digit parcel-machine door code.
- Number format: Current public evidence does not establish one universal Omniva length, prefix, suffix, or regular expression.
Shipment data registered: An electronic shipment record exists. Physical handover is not proved.- Sender deposited in a parcel machine: Physical deposit exists. Omniva courier collection is not yet proved.
Shipment departed from parcel machine: The deposited item entered Omniva’s transport network.- Courier pickup, post-office handover, or terminal registration: Strong physical-possession evidence.
- Postal-facility or exchange event: Processing or movement exists. It is not exact live GPS.
Shipment movement has been temporarily stopped: Movement is paused. The generic event does not identify why.Shipment movement restored: The temporary stop ended.- Courier delivery started: Last-mile activity exists. Same-day completion is not guaranteed.
- Redirection requested: A recipient instruction exists. An executed route change is not yet proved.
- Requested parcel machine: Not guaranteed when the machine is full or unavailable.
Shipment stored in parcel machine: The parcel is physically in the pickup locker.- Arrival notification sent: Omniva sent the message. Receipt, opening, and collection remain separate.
- Door code: A private six-digit release credential. One code can cover several parcels in the same locker.
- Storage: Current Estonian branches include four days at a parcel machine and seven days for selected courier overflow at a post office or delivery centre.
- Extension: Current Estonian machine storage can be extended in four-day increments, up to twelve additional days; a separate post-office branch can allow one extension up to one month.
- Picapac: A related personal or community parcel-machine service, not the transport carrier.
- COD: Payment, locker opening, and collection are separate.
- Delivered: Carrier completion is recorded. Named-recipient receipt, contents, and condition are not automatically proved.
- Return: Registration, locker deposit, Omniva pickup, merchant receipt, inspection, and refund are separate.
- International: Origin post, Omniva, transit operator, delivery partner, customs, and destination post can control different stages.
- Customs: Notification, declaration, payment, authority release, and delivery are separate.
- July 2026 duty: Current Omniva guidance describes €3 per product category in the stated low-value import scope, not €3 per parcel.
- Claim: A delivery-status request or damage report begins a review. Loss, liability, compensation, and merchant refund remain separate.
Track one supported Omniva shipment code
Use the shipment tracking code shown on:
- shipping label;
- address card;
- mailing receipt;
- merchant shipping notice;
- SMS;
- e-mail;
- Omniva app;
- return instruction;
- sender communication.
Does Omniva use one number format?
No universal public format is confirmed.
Official Omniva materials refer to:
- tracking number;
- tracking code;
- shipment number.
The supported format can depend on:
- Baltic parcel product;
- courier service;
- registered letter;
- international postal product;
- return;
- origin postal operator;
- delivery partner.
Do not publish or enforce one universal Omniva regular expression unless the current runtime provider and official documentation support it.
Is the code on the address card the tracking code?
It can be.
Omniva allows an address card to be printed after the user provides the shipment code in a supported posting workflow. That confirms the code’s role but does not define every possible format.
Can I enter a merchant order?
Not automatically.
A merchant order proves a purchase. It does not prove:
- Omniva is the carrier;
- a transport label exists;
- the seller handed over the parcel;
- one order equals one shipment.
Can I track by phone or e-mail?
Not through the public tracking-code form.
Phone and e-mail can be used privately for:
- notifications;
- account matching;
- preferred-location routing;
- Picapac routing;
- customs communication;
- cash-on-delivery communication.
That does not create public lookup by those fields.
Can I enter a customs, COD, or claim reference?
No.
Keep separate:
- shipment tracking code;
- six-digit door code;
- COD payment reference;
- customs declaration;
- customs payment;
- damage report;
- delivery-status request;
- merchant return or refund case.
Omniva, AS Eesti Post, Baltic entities, and Picapac
Omniva
Omniva is the public Baltic postal and logistics brand.
AS Eesti Post
Current official materials identify AS Eesti Post as:
- Omniva Group’s parent company;
- the Estonian legal operator;
- the company using the Omniva trademark;
- Estonia’s current universal postal-service provider.
Omniva SIA
Omniva SIA is the Latvian operating subsidiary.
Omniva LT UAB
Omniva LT UAB is the Lithuanian operating subsidiary.
One brand does not mean one contract
The public page should use one Omniva canonical while preserving country-specific differences involving:
- legal entity;
- service contract;
- parcel-machine network;
- storage period;
- support route;
- customs;
- claim actor;
- compensation.
Picapac OÜ
Picapac OÜ is a related Omniva Group company offering personal, shared, or community parcel-machine services.
parcel routed to Picapac
≠ Picapac is the transport carrier
Delivery partners and foreign posts
An Omniva tracking history can include:
- origin postal operator;
- international exchange office;
- transit operator;
- delivery partner;
- destination post.
These are not automatic Omniva aliases.
Tracking code versus six-digit door code
Shipment tracking code
Use the shipment code to view public route events.
Parcel-machine door code
The door code:
- contains six digits;
- arrives by SMS or e-mail;
- opens the parcel-machine compartment;
- can authorize operational release;
- is not a tracking code.
shipment tracking code
→ public tracking lookup
six-digit door code
→ parcel-machine release
One door code can cover several parcels
Official guidance says several notifications can contain the same door code when multiple shipments are stored in one locker.
one door code
→ one shared locker credential
≠ one parcel only
Why this matters
Opening the locker does not automatically prove:
- every shipment was removed;
- the named recipient used the code;
- the correct parcel was inside;
- the contents were correct.
Door-code privacy
Never publish the code in:
- URL;
- metadata;
- JSON-LD;
- analytics;
- screenshot;
- product review;
- support forum;
- AI prompt.
From registration to final outcome
| Stage | What it can confirm | What it does not confirm |
|---|---|---|
| Merchant order | Purchase exists | Omniva shipment exists |
| Shipment data registered | Electronic shipment record exists | Physical handover |
| Sender deposited parcel in machine | Physical customer deposit exists | Omniva courier collected it |
| Shipment departed from parcel machine | Parcel entered Omniva’s network | Sorting completed |
| Courier picked up shipment | Physical Omniva collection exists | Contents or condition |
| Sender handed shipment to post office | Postal acceptance exists | Delivery target guaranteed |
| Shipment registered in Omniva terminal | Physical terminal arrival exists | Prior electronic record existed |
| Arrival at postal facility | Network processing exists | Exact live location |
| Courier delivery started | Last-mile activity exists | Same-day completion |
| Redirection requested | Recipient instruction exists | Route changed |
| Shipment redirected | Operational change is recorded | Final destination reached |
| Shipment stored in parcel machine | Pickup readiness exists | Notification received or parcel collected |
| Arrival notification sent | Message was issued | Message read |
| Door code received | Release credential exists | Locker opened |
| Door code used | Locker access can be recorded | Named recipient or all parcels collected |
| Shipment delivered | Carrier completion is recorded | Correct contents, condition, or continued possession |
| Return registered | Reverse shipment data exists | Parcel deposited |
| Return deposited | Customer handover exists | Omniva pickup |
| Customs payment submitted | Payment action exists | Customs release |
| Released from customs | Release exists | Final delivery |
| Delivery-status request opened | Investigation exists | Loss or liability accepted |
What changes the conclusion?
- Electronic registration becomes physical custody after machine departure, courier pickup, post-office handover, terminal registration, or another verified physical event.
- A requested redirection becomes a real route change after
Shipment redirectedor a new destination event. - Machine arrival becomes recipient possession only after a release or collection event.
- A delivered event becomes stronger named-person evidence only when the product’s identity or signature proof supports it.
- Return deposit becomes carrier possession after Omniva collection or a reverse network event.
- Payment becomes customs release only after the authority or carrier publishes a release event.
- A claim becomes compensation only after liability and payment are accepted.
Shipment data registered
What does it mean?
The official event means that shipment data was registered electronically.
Shipment data registered
→ electronic record exists
≠ Omniva physically has the parcel
Why can the seller say “shipped”?
A seller can mark an order shipped after:
- label creation;
- data transfer;
- packing;
- collection booking.
The first physical event can still be missing.
What should the recipient do?
- verify the shipment code;
- wait for a physical acceptance event;
- ask the sender when the parcel was handed over;
- preserve the merchant’s promised dispatch date.
Use Label Created for the generic pre-advice model.
Sender parcel-machine deposit and Omniva custody
Sender dropped off the shipment in a parcel machine
This confirms physical deposit by the sender.
It does not confirm that Omniva’s courier has emptied the machine.
Shipment departed from parcel machine
This is stronger evidence that Omniva collected the deposited shipment into the transport network.
Courier has picked up the shipment
Physical collection is recorded.
Sender handed the shipment to a post office
Physical postal acceptance is recorded.
Shipment registered in our terminal
The parcel reached an Omniva terminal without the expected preregistration.
This is a physical network event despite missing earlier electronic data.
Possession ladder
shipment data registered
→ sender machine deposit
→ machine departure or courier pickup
→ terminal or postal-facility processing
Acceptance does not inspect the purchase
A physical event does not prove:
- the seller packed the correct goods;
- the quantity is correct;
- the declared value is correct;
- packaging is adequate;
- hidden damage is absent.
Omniva status meanings
Shipment cancelled
The shipment record was cancelled.
It does not prove:
- merchant refund;
- order cancellation;
- replacement parcel;
- completed return.
Arrival to postal facility
The shipment reached a postal facility for processing.
arrival to postal facility
→ network processing exists
≠ exact current shelf
≠ continuous GPS
Courier delivery started
The parcel was handed to a courier for delivery.
courier delivery started
→ last-mile delivery activity exists
≠ exact courier location
≠ guaranteed delivery that day
Courier contacted receiver
The carrier records a contact attempt or contact event.
It does not prove:
- the recipient answered;
- a time was accepted;
- the courier reached the address.
Shipment stored in parcel machine
The parcel is in the pickup machine.
This is stronger than a general facility-arrival event.
Arrived at final post office
The item reached the post office for pickup.
Arrival notification sent
Omniva sent the pickup message.
notification sent
≠ message delivered to the correct device
≠ message read
≠ parcel collected
Reminder notification sent
A storage reminder was issued.
The reminder does not change the deadline unless the current item record confirms an extension.
Shipment redirected
An operational route change was recorded.
This is stronger than a request confirmation.
Failed delivery attempt
The delivery process did not complete.
It does not independently prove:
- the address was correct;
- the bell was used;
- the phone was called;
- the recipient was absent;
- the recipient caused the failure.
Shipment delivered
The carrier records completion.
The delivery object and proof determine what can be concluded.
Shipment return initiated
A reverse route started.
The sender has not necessarily received the item.
Return cancelled
The reverse process was cancelled.
It does not prove that delivery will now succeed.
Returned by customer
The customer entered a return workflow.
The exact custody stage depends on the event source.
Document returned to sender
This can be a document-specific event, not a merchant parcel refund.
Shipment movement temporarily stopped
Official event
Omniva’s 2026 event list contains:
Shipment movement has been temporarily stopped;Shipment movement restored.
What a temporary stop proves
The ordinary movement process was paused.
What it does not prove
The generic event does not identify:
- customs;
- sanctions;
- weather;
- weekend;
- address problem;
- prohibited contents;
- damage;
- loss;
- seizure;
- permanent return.
Movement restored
A later restored event confirms that the temporary stop ended.
Best action
Check:
- surrounding raw events;
- event country;
- publishing operator;
- customs events;
- sender communication;
- current official support route.
Do not diagnose the cause from the generic phrase alone.
Parcel-machine exception events
Shipment missing in parcel machine
The official event can mean that the courier did not find the expected shipment in the machine.
It is not automatically the same as:
- recipient opened an empty locker;
- parcel was delivered;
- parcel was stolen;
- carrier lost it after collection.
Empty locker
Use Omniva’s official support route immediately.
Someone else’s parcel is inside
Current support guidance describes a carrier-assisted recovery workflow. The user should contact support rather than treating the parcel as their own or processing an ordinary merchant return.
Wrong delivery location
Preserve the final notification and contact Omniva.
Same code, several parcels
Confirm that every parcel in the shared locker was removed before closing the door.
locker opened
≠ every parcel collected Tracking not updating
Common explanations
- shipment data exists but the sender has not handed over the parcel;
- parcel was deposited but the machine has not been emptied;
- first terminal scan is delayed;
- provider or event publication is delayed;
- route moved between Baltic facilities without a public event;
- international operator has not shared data;
- Economy product has limited destination tracking;
- customs information is in a separate workflow;
- tracking code is wrong or unsupported;
- temporary movement stop is active.
No update is not one diagnosis
no new event
≠ lost
≠ still at the last visible place
≠ moving normally
≠ customs released
First checks
- Compare the tracking code with the label or sender message.
- Confirm the carrier and destination country.
- Find the first physical handover event.
- Check whether the item is international Economy.
- Ask the sender when and where it was handed over.
- Check for a delivery-partner identifier.
Use Tracking Not Updating for the broader evidence model.
Delivery timeframes
When does the delivery clock begin?
Current guidance measures the service target from physical handover to Omniva.
Shipment data registered
≠ delivery clock necessarily started
Domestic target
Current official guidance describes:
- one to two working days to a parcel machine;
- one to two working days to a post office in Estonia.
Baltic target
Current guidance describes:
- two to three working days across the Baltics.
Courier target
The current public courier branch describes next-working-day delivery in the Baltics, but no later than three days after handover, excluding Sundays and public holidays.
Why can it take longer?
- collection cut-off;
- weather;
- traffic;
- public holiday;
- full parcel machine;
- technical failure;
- remote route;
- international handoff;
- customs;
- another operational exception.
Target is not an appointment
one-to-two or two-to-three working days
→ current service target
≠ guaranteed arrival time Redirect an Omniva parcel
Free redirection before sorting
Current Estonian guidance says an eligible recipient can redirect for free before the parcel reaches the sorting centre.
The action can be available through:
- a link in the e-mail;
- private self-service.
Possible destinations
Depending on the item:
- another parcel machine;
- post office;
- home or courier address.
Courier redirection can cost extra
Changing from a parcel-machine or postal route to courier delivery can involve a fee.
Timing matters
The free branch can close after:
- sorting-centre arrival;
- advanced processing;
- pickup readiness;
- delivery;
- return.
Request versus executed route
redirection request submitted
→ instruction exists
≠ route changed
Shipment redirected
→ operational route change recorded
11Tracking limitation
11Tracking cannot submit, cancel, pay for, or verify a private redirection request.
Preferred delivery location
Private account instruction
The user can save preferred delivery locations in a private Omniva account.
Current Estonian options include:
- parcel machine;
- post office.
Preference is not a guarantee
preferred location saved
→ account instruction exists
≠ every shipment eligible
≠ sender accepted it
≠ requested location available
Picapac routing
In the reviewed Estonian workflow, a linked Picapac machine can override other preferred locations and receive eligible parcels automatically.
Phone-number matching
Picapac routing can depend on the phone number associated with the account or order.
Phone matching is private delivery logic, not public tracking by phone.
Automatic redirection and full parcel machines
Requested machine is full
Omniva can move the parcel to another nearby machine.
Technical problem
A faulty machine can cause the same diversion.
Courier cannot reach the recipient
Selected courier parcels can be moved to:
- nearby parcel machine;
- post office;
- delivery centre.
Size matters
Larger parcels can be routed to a staffed location instead of a machine.
Final notification controls
original machine selected
≠ original machine guaranteed
Use the final SMS, e-mail, app, or tracking event for the actual pickup location.
Picapac
What is Picapac?
Picapac is a related personal, shared, or community parcel-machine service.
It can support receipt of selected:
- parcels;
- letters;
- newspapers;
- grocery deliveries.
Picapac is not the carrier
Omniva or another verified operator transports the shipment.
Automatic routing
A private Picapac preference can route eligible items to the machine through account and phone matching.
Full Picapac machine
A capacity issue can move the parcel to:
- another machine;
- post office;
- another supported point.
Tracking boundary
Picapac destination event
→ delivery location or route clue
≠ Picapac carrier identity Courier delivery
Advance notice
The recipient can receive an SMS with a planned delivery date.
Courier contact
The courier can contact the recipient before arrival.
Delivery place
Current guidance distinguishes:
- apartment door;
- private-house front door;
- gate of a fenced property;
- building entrance or gate for XXL delivery.
Weight branches
Current public guidance includes:
- ordinary courier parcels up to 30 kg;
- XXL parcels up to 100 kg in the relevant entrance or gate branch.
Can another person receive?
Yes, when no restrictive service applies.
Restrictive services
Examples include:
- adult verification;
- document return;
- delivery to a specific person.
Contact does not create a guarantee
A planned day or time does not provide:
- exact courier GPS;
- exact stop order;
- guaranteed minute;
- direct courier contact through 11Tracking.
Parcel-machine readiness and notifications
When is the parcel ready?
The strongest readiness event is:
Shipment stored in parcel machine
Notification
Omniva then sends an arrival notification by SMS or e-mail.
Separate evidence stages
stored in parcel machine
→ item is physically in the pickup locker
arrival notification sent
→ message was issued
door code received
→ release credential exists
locker opened
→ access event exists
parcel collected
→ item left with the code holder
Notification delivery can fail
Possible causes include:
- wrong phone;
- wrong e-mail;
- message filtering;
- provider delay;
- account mismatch;
- missing sender data.
Do not publish contact data
Phone and e-mail are private shipment-routing data.
Door code, delegation, and identity
Pickup sequence
The recipient normally:
- visits the machine shown in the final notice;
- selects parcel receipt;
- enters the six-digit door code;
- completes identity verification if the sender required it;
- pays COD if required;
- removes all parcels;
- closes the door.
Can another person collect?
The recipient can share the door code with another person.
A valid code gives operational access unless another identity restriction applies.
Does the code prove named-recipient collection?
No.
door code used
→ locker access exists
≠ named recipient used it
When is identity required?
A sender can select a product requiring:
- age verification;
- identity verification;
- delivery to a specific person.
Shared locker risk
One locker can contain several parcels for the same recipient or code.
The code holder should remove and verify all expected items.
Cash on delivery and Receiver Pays
Separate products
Omniva distinguishes:
- Cash on delivery;
- Receiver Pays.
Payment before release
A parcel-machine workflow can require payment before the door opens.
Mobile-app payment
In June 2026, Omniva announced COD payment in the mobile app for selected parcel machines without a payment terminal, including community machines.
Payment evidence ladder
COD requested
→ financial condition exists
payment confirmed
→ release condition can be satisfied
≠ locker opened
≠ parcel collected
≠ goods accepted as correct
COD is not customs
Keep separate:
- merchant or sender COD;
- Receiver Pays;
- VAT;
- customs duty;
- Omniva customs-declaration fee;
- delivery charge.
Storage periods
Parcel machine in Estonia
Current official guidance uses:
- four days.
Selected courier overflow to parcel machine
Current branch uses:
- four days.
Selected courier overflow to post office
Current branch uses:
- seven days.
XXL delivery-centre storage
Current branch uses:
- seven days.
No universal Baltic deadline
Do not automatically apply the Estonian table to:
- Latvia;
- Lithuania;
- Picapac;
- international items;
- business contracts;
- every courier product.
Actual notice controls
Use the current SMS, e-mail, app, or arrival notice for the exact deadline.
Extend storage
Parcel-machine extension
Current Estonian guidance allows:
- up to four additional days per extension;
- repeated extensions;
- a maximum of twelve additional days in total.
Post-office extension
Current Estonian guidance allows one extension:
- up to one month.
Fee
A storage fee can apply.
Request is not confirmation
extension requested or paid
→ management action exists
≠ new deadline confirmed
Use the updated official deadline.
What happens after expiry?
The parcel returns to the sender.
Current Estonian guidance says the sender pays the return charge in the stated branch.
Delivery attempts and non-delivery
No universal attempt count
Attempt handling differs among:
- parcel-machine delivery;
- courier delivery;
- post-office delivery;
- registered letters;
- restrictive services;
- international partners;
- country contracts.
Courier non-delivery
The parcel can move to:
- another planned day;
- nearby parcel machine;
- post office;
- delivery centre;
- return.
Failed delivery does not prove recipient fault
failed delivery
→ non-completion recorded
≠ recipient absence proved
≠ bell use proved
≠ phone contact proved
Courier delivery cancelled
This is different from:
- shipment record cancelled;
- failed attempt;
- return initiated;
- final return.
Who opens the delivery-status request?
For an undelivered parcel, current Estonian guidance routes:
- sender → delivery-status request;
- recipient → sender.
Registered letters
Which letters are trackable?
Only registered letters are trackable in the reviewed ordinary-letter guidance.
Delivery proof
A signature is required.
Authorized person
Another authorized person can receive unless the sender selected delivery in person.
Delivery in person
This changes:
- identity verification;
- delegation;
- proof.
Failed delivery
The letter can move to post-office pickup.
Post-office redirection
Current guidance allows one free redirect to another post office when the recipient cannot collect from the original office.
Signature limits
signature exists
≠ named addressee necessarily signed
The product’s personal-delivery setting controls.
Proof of delivery
Parcel-machine proof
Possible route evidence includes:
- stored in machine;
- notification;
- door-code use;
- locker opening;
- delivered event.
The public runtime must verify which fields are actually available.
Courier proof
Possible fields include:
- delivered event;
- signature;
- identity check;
- age verification;
- specific-person confirmation.
Sensitive identity fields must not be exposed publicly.
Post-office proof
Pickup can involve:
- arrival notice;
- identity document;
- authorized person;
- signature.
Registered-letter proof
Signature is the reviewed proof object.
International proof
An international Economy product can offer Proof of Delivery even when destination-country route tracking is unavailable.
The proof can require customer service or destination-post confirmation.
Proof limits
proof exists
≠ anonymous public download
≠ named buyer necessarily received
≠ correct contents or condition verified Delivered but not received
What Delivered proves
Shipment delivered
→ carrier records completion
≠ named recipient personally received
≠ correct contents or condition proved
Classify the delivery object
Check whether completion occurred at:
- parcel machine;
- shared locker;
- Picapac;
- post office;
- courier address;
- another person;
- foreign operator;
- redirected point.
Check shared-locker collection
The same code can release several shipments.
Confirm whether every expected parcel was removed.
Empty locker
Contact Omniva support immediately.
Someone else’s parcel
Follow Omniva’s support-assisted recovery procedure.
Wrong location
Preserve the final notice and contact Omniva.
Preserve evidence
Keep:
- tracking code;
- raw events;
- timestamps;
- operator and country;
- final pickup location;
- notification;
- door-code message without publishing the code;
- partner identifier;
- merchant communication;
- proof availability;
- support case number.
Responsible actor
The sender normally opens the formal delivery-status request and generally controls the carrier compensation relationship.
Use Delivered but Not Received for the broader escalation model.
Returns
Baltic merchant return
Omniva provides a return portal for participating merchants in Estonia, Latvia, and Lithuania.
Merchant controls the remedy
The merchant decides whether the commercial result is:
- refund;
- exchange;
- repair;
- replacement;
- another outcome.
Return registration
return registered
→ reverse shipment data exists
≠ parcel deposited
Parcel-machine deposit
The customer places the return in a locker.
This proves customer deposit, not necessarily Omniva network collection.
Omniva pickup
A machine-departure, courier-pickup, terminal, or reverse-transit event is stronger evidence of carrier possession.
Return ladder
return registration
→ customer deposit
→ Omniva collection
→ reverse transit
→ merchant receipt
→ inspection
→ refund or exchange decision
→ payment or replacement
Merchant processing time
Current public guidance says merchants typically process returns and refunds or exchanges within fourteen to thirty days after receipt.
This is a general statement, not a guarantee for one seller.
International return
Returning goods to a foreign seller can require:
- customer-paid return transport;
- customs-declaration cancellation;
- separate VAT or customs refund request.
International operator chain
Outbound events
Omniva’s 2026 event list includes stages such as:
- posting or collection;
- arrival at outward office of exchange;
- departure from outward office;
- transit-country arrival;
- inward exchange;
- destination delivery office;
- physical delivery;
- unsuccessful delivery;
- final delivery.
Import and border events
The same list includes:
- held at inward office of exchange;
- presented to import border agency;
- returned from border agency;
- sorting centre;
- delivery depot;
- out for physical delivery;
- collection point;
- import termination.
Operator attribution
The event country and publishing operator determine current custody.
Origin database dependency
Inbound tracking depends on the sending country entering events into the international database.
Before the parcel reaches Estonia, the origin-post tracker can provide the better record.
Same code, changing custody
same international code continues
≠ Omniva still has physical possession Delivery-partner barcode
The official event list includes:
Delivery partner barcode assigned to shipment
What it confirms
A related identifier was assigned for a delivery partner.
What it does not confirm
It does not automatically prove:
- physical partner acceptance;
- original code is invalid;
- every later event belongs to Omniva;
- the partner is the final carrier.
Best practice
Preserve:
- original identifier;
- partner identifier;
- relationship;
- operator;
- country;
- event timestamp.
Use Find the Last-Mile Carrier when the final operator is unclear.
International Economy tracking limits
Incomplete destination tracking
Some destination countries do not publish ordinary route tracking for selected international Economy products.
Proof can still exist
Proof of Delivery available
≠ full public route history available
Destination operator controls the last mile
The foreign operator controls:
- local attempt;
- pickup location;
- storage;
- proof;
- complaint intake.
International estimates
Customs, aviation security, sanctions, destination operations, and data exchange can change the timeline.
Customs responsibility
Omniva’s role
Omniva can:
- notify the recipient;
- request declaration;
- offer a paid declaration service;
- collect service charges;
- pass information;
- resume delivery after release.
Estonian Tax and Customs Board
The authority controls:
- legal declaration acceptance;
- VAT and duty;
- inspection;
- release.
Self-declaration
The recipient can submit the declaration through Estonia’s e-tax/e-customs environment.
Omniva declaration service
Omniva can prepare the declaration for the recipient for a fee in the supported workflow.
Thirty-day requirement
Current Estonian guidance says an item from outside the EU tax territory must be declared within thirty days.
11Tracking limitation
11Tracking cannot:
- authenticate the recipient;
- upload documents;
- classify goods;
- calculate duty;
- pay;
- release the parcel;
- appeal an authority decision.
Customs status ladder
| Stage | What it can confirm | What it does not confirm |
|---|---|---|
| Shipment taken to customs | Customs handling started | Declaration accepted |
| Customs arrival notification | Recipient action was requested | Message read |
| Declaration reminder | Required action remains open | Rejection |
| Declaration submitted | Data was provided | Authority accepted it |
| Additional payment notification | More payment is requested | Payment completed |
| Payment reminder | Amount remains outstanding | Release denied |
| Payment confirmed | Requested amount was recorded | Customs release |
| Released from customs | Legal or operational release exists | Final delivery |
| Onward Omniva processing | Carrier route resumed | Delivered |
Payment is not release
declaration submitted
→ information provided
≠ accepted
payment confirmed
→ requested amount paid
≠ released from customs
released from customs
→ delivery can resume
≠ parcel delivered
Use Customs Processing and Package Stuck in Customs for broader guidance.
July 2026 €3 import duty
Current official rule
Omniva states that the rule applies from July 1, 2026.
In the stated low-value scope, the amount is:
€3 per product category
Scope
Current guidance describes:
- goods worth up to €150;
- direct purchase from a third country;
- applicable low-value import branch.
Category, not parcel
Official examples distinguish:
- several units in one product category → one €3 amount;
- three product categories → €9.
€3 per product category
≠ €3 per parcel
≠ €3 per unit in the same category
EU warehouse or intermediary
If goods were already customs-cleared through an EU warehouse or intermediary, the additional import duty does not apply in the described branch.
Gifts
The current Omniva article says the new duty does not apply to gifts sent from one private individual to another.
Other VAT and gift conditions remain separate.
Separate amounts
Keep separate:
- €3 import duty;
- VAT;
- other customs duty;
- Omniva declaration-service fee;
- transport charge;
- COD;
- merchant payment.
This 2026 rule is highly volatile and must be revalidated before action or publication.
Damage, loss, and delivery-status requests
Undelivered parcel
Current Estonian guidance routes:
- sender → parcel delivery-status form;
- recipient → sender.
Damaged parcel
The damage or loss report should be submitted promptly.
Six-month maximum
Current guidance uses a maximum of six months after handover to Omniva in the reviewed branch.
Who usually receives carrier compensation?
The sender generally controls the carrier refund relationship.
International damage
The recipient should immediately contact the postal organization that delivered the item, then inform the sender so the sender can report the damage to Omniva.
Registered-letter search
Current guidance includes:
- six-month submission branch;
- destination-time-based branch for international letters;
- ten-working-day domestic processing target;
- up to two months for international processing.
Investigation is not a conclusion
delivery-status request or damage report opened
→ formal review exists
≠ item lost
≠ Omniva liable
≠ compensation approved
≠ merchant refund Compensation boundaries
Product-specific rules
Compensation can depend on:
- parcel product;
- registered letter;
- international postal convention;
- shipment insurance;
- declared value;
- packaging;
- prohibited contents;
- sender contract;
- claim timing.
Shipment insurance
Current Omniva materials offer insurance to a declared value in supported products.
That does not guarantee automatic payment.
Packaging matters
Official packaging instructions can affect liability.
Sender-centered relationship
The sender generally owns the carrier compensation relationship.
Separate remedies
Omniva compensation
≠ merchant refund
≠ marketplace dispute
≠ payment-card dispute
≠ personal insurance Who should you contact?
| What the record shows | Best first actor | Why |
|---|---|---|
| Merchant order; no Omniva code | Merchant or sender | Carrier item is unconfirmed |
| Shipment data registered only | Sender | Physical handover is unconfirmed |
| Sender deposited parcel; no machine departure | Sender and Omniva | Carrier collection is unconfirmed |
| Courier pickup, post-office handover, or terminal registration | Sender and Omniva | Physical carrier possession is recorded |
| Movement temporarily stopped | Omniva and sender | Generic event does not identify the cause |
| International item before Estonia | Sender and origin post | Origin database controls visibility |
| Delivery-partner barcode assigned | Current operator and sender | Partner relationship must be verified |
| Courier delivery started but not completed | Check the next event; contact sender or Omniva | Route event is not a guarantee |
| Redirection requested | Omniva e-service or support | Carrier must execute the change |
| Parcel moved to another machine | Follow the final notification | Capacity or technical diversion can apply |
| Stored in machine; no door code | Omniva support and sender | Notification or contact data can be wrong |
| Door code does not work | Omniva support | Code is a private release credential |
| Locker empty or wrong parcel | Omniva support immediately | Operational incident requires carrier action |
| Delivered but missing | Sender, merchant, and Omniva | Proof, carrier claim, and refund differ |
| Return deposited; no reverse scan | Omniva and merchant | Network pickup is unconfirmed |
| Return delivered; no refund | Merchant | Commercial remedy is merchant-controlled |
| Customs notification | Official Omniva or Estonian authority route | Public tracker cannot declare |
| Customs payment made; no release | Omniva customs and authority workflow | Payment is not release |
| Damaged parcel | Preserve packaging; contact sender and Omniva promptly | Sender generally controls compensation |
| Suspicious message | Independently opened official Omniva domain | The message does not authenticate itself |
Privacy and scam safety
Public tracking input
The public form should request only:
- one supported shipment tracking code.
Never enter these into a public tracker
- six-digit door code;
- sender or recipient name;
- phone;
- e-mail;
- full address;
- postcode;
- e-service login;
- Picapac routing details;
- identity document;
- signature;
- age-verification information;
- COD payment credential;
- customs document;
- invoice;
- goods description;
- claim evidence;
- banking data.
Treat the tracking code as private shipment data
It can reveal:
- route;
- machine or post office;
- timing;
- customs status;
- delivery partner;
- return state;
- proof availability.
Do not publish it in:
- URL;
- metadata;
- JSON-LD;
- analytics;
- screenshots;
- public reviews;
- support forums;
- unnecessary AI prompts.
Official Omniva domains
Current Omniva guidance recognizes:
omniva.ee;omniva.lv;omniva.lt;omniva.eu.
The current Estonian self-service is:
minu.omniva.ee.
What Omniva says it does not request by phone or SMS
Current fraud guidance says Omniva does not request:
- card details;
- bank username;
- PIN1;
- PIN2;
- banking information;
- payment confirmation;
- identity-document copy;
- transmission of personal data.
Legitimate actions can still exist
Omniva can legitimately ask a user to:
- update delivery information;
- pay customs duty;
- declare a parcel.
The link and final destination must be an official Omniva country domain.
Real shipment information does not authenticate the message
real tracking code
≠ authentic message
correct route
≠ legitimate payment page
Omniva in the URL
≠ Omniva-controlled domain
correct door-code context
≠ safe request to share the code
Safe verification sequence
- Do not use the unsolicited link.
- Open the correct Omniva country site independently.
- Enter only the tracking code.
- Open
minu.omniva.eeindependently for supported Estonian actions. - Never share the door code, bank PIN, card details, or ID copy through an unsolicited message.
- Contact the bank if financial information was exposed.
- Preserve the suspicious message privately.
Use Fake Delivery Message for broader safety guidance.
Frequently asked questions
How do I track an Omniva parcel?
Enter one supported Omniva shipment tracking code from the label, receipt, message, app, or sender.
Does Omniva use one number format?
No universal public format is confirmed.
Is Omniva the same as AS Eesti Post?
Omniva is the public brand. AS Eesti Post is the Estonian legal operator and parent company.
Does Omniva operate in Latvia and Lithuania?
Yes, through separate group entities in the reviewed current structure.
Is Picapac a carrier?
No. It is a related parcel-machine service.
What is the six-digit code?
It is the parcel-machine door code.
Is the door code the tracking code?
No.
Can one door code cover several parcels?
Yes, when several shipments are placed in the same locker.
Can I track by phone or e-mail?
Not through the public tracking-code form.
Can I use a merchant order?
Not automatically.
What does Shipment data registered mean?
Electronic shipment data exists. Physical Omniva possession is not proved.
Does depositing a parcel in a machine prove Omniva collected it?
No.
Which event proves Omniva pickup from the machine?
Shipment departed from parcel machine is stronger evidence.
What does courier picked up mean?
Physical Omniva collection is recorded.
What does registered in Omniva terminal mean?
The item physically reached a terminal without preregistration.
What does arrival to postal facility mean?
The parcel reached a processing facility.
Does Omniva show exact GPS?
Current evidence does not support a universal exact-GPS promise.
What does movement temporarily stopped mean?
The ordinary movement process was paused. The generic event does not identify the cause.
Does it mean customs or loss?
Not automatically.
What does movement restored mean?
The temporary stop ended.
What does courier delivery started mean?
The last-mile delivery process started.
Is delivery guaranteed that day?
No.
Can I redirect a parcel?
Eligible items can be redirected before the current cut-off.
Is redirection free?
The reviewed Estonian pre-sorting branch is free. A courier-channel change can involve a fee.
Does a redirect request prove the route changed?
No.
Why was the parcel moved to another machine?
The requested machine can be full or unavailable.
What is a preferred delivery location?
A private account instruction for eligible shipments.
Can Picapac override my preference?
In the reviewed Estonian workflow, a linked Picapac machine can take priority.
When is the parcel ready?
After it is stored in the parcel machine.
Why did no door code arrive?
The phone or e-mail can be wrong, delayed, filtered, or missing.
Can someone else collect?
A person with the code can collect unless an identity restriction applies.
When is ID required?
When the sender selected an age, identity, or specific-person service.
Can I pay COD in the app?
Current June 2026 guidance supports this for selected machines without payment terminals.
Does COD payment mean collection?
No.
How long is a parcel stored?
The current Estonian ordinary machine branch uses four days. Other products and countries can differ.
Why do some items use seven days?
Selected courier overflow at a post office or delivery centre uses a separate branch.
Can storage be extended?
Eligible Estonian machine storage can be extended in four-day increments, up to twelve additional days.
Can a post-office item be extended for one month?
The reviewed Estonian branch allows one such extension.
What happens after expiry?
The parcel returns to the sender.
What if the locker is empty?
Contact Omniva support immediately.
What if someone else’s parcel is inside?
Use Omniva’s support-assisted recovery process.
What if the door code does not work?
Contact Omniva support and do not publish the code.
Does Delivered prove the named recipient collected?
No.
How is a registered letter delivered?
It uses signature proof, with product-specific identity and delegation rules.
Who opens an undelivered-parcel search?
Current guidance routes the formal request through the sender.
Who normally receives carrier compensation?
The sender generally controls the carrier refund relationship.
How do I return a parcel?
Use the merchant’s Omniva return instruction or supported Baltic return portal.
Does return registration prove Omniva collected it?
No.
Does return delivery prove a refund?
No.
Why did international tracking stop?
The product or destination operator can provide limited route data.
What is a delivery-partner barcode?
A related identifier assigned for a partner delivery stage.
Does Proof of Delivery mean full tracking?
No.
Does customs payment mean release?
No.
What is the July 2026 €3 duty?
Current Omniva guidance describes €3 per product category in the stated low-value direct-import scope.
Is it €3 per parcel?
No.
Which Omniva domains are official?
Current guidance recognizes omniva.ee, omniva.lv, omniva.lt, and omniva.eu.
Can 11Tracking redirect or extend storage?
No.
Can USTracking retrieve the door code or pay customs?
No.
Use USTracking as a tracking companion
After identifying the correct shipment code and current operator, USTracking may help you:
- save a supported tracking code;
- organize public events;
- preserve verified original, return, international, and delivery-partner identifiers;
- compare registration, possession, sorting, last-mile, pickup, return, and customs stages;
- monitor public updates;
- receive notifications.
USTracking cannot:
- track by merchant order, name, address, phone, e-mail, postcode, door code, COD reference, customs reference, or claim number;
- decide one universal Omniva format;
- infer Omniva carrier identity from Picapac or another delivery location alone;
- redirect a parcel;
- set a preferred location;
- extend storage;
- retrieve or resend a door code;
- open a parcel machine;
- pay COD;
- verify who used a code;
- retrieve a signature or identity record;
- access private Omniva self-service;
- submit a customs declaration;
- pay customs charges;
- clear customs;
- file or manage a claim;
- recover a shipment;
- decide liability;
- decide compensation;
- decide merchant refund;
- guarantee delivery, pickup, customs release, or claim outcome.
Track more easily
Keep all your deliveries in one place
Add packages from different carriers to USTracking, return to active shipments faster and get plain-language help with unfamiliar tracking events.
Official Omniva resources
Tracking and receiving
- Omniva Estonia
- Track & Trace
- Track and receive parcels
- How to track your parcel
- Official 2026 event list
- Receive items
- Receive a parcel at a parcel machine
- Delivery notifications
Redirection, storage, and parcel machines
- Redirect a parcel or letter
- Preferred delivery location
- Set or change a preferred location
- Picapac preferred location
- Parcel storage periods
- Extend parcel storage
- Another person collecting
- Identity verification
- Door-code problem
- Empty locker or missing shipment
- Someone else’s parcel in the locker
Payments, proof, claims, and returns
- Cash on delivery and Receiver Pays
- COD payment in the Omniva app
- Registered-letter receipt
- Undelivered parcel
- Damaged parcel
- Return a Baltic merchant parcel
- Omniva return portal
International, customs, and safety
- International parcel sending
- Customs when receiving
- Customs declaration help
- How to fill in a customs declaration
- Gift received from outside the EU
- July 2026 low-value import duty
- Fraud and official domains
Identity and privacy
Scope, evidence, and limitations
This page is an English-language guide to Omniva parcel, registered-letter, courier, parcel-machine, return, international, and customs tracking. It explains carrier identity, tracking-code limits, electronic registration, physical custody, official events, movement interruption, delivery estimates, redirection, preferred locations, parcel-machine overflow, Picapac, door codes, delegation, identity verification, cash on delivery, storage, extensions, proof, disputed delivery, returns, international handoffs, delivery-partner identifiers, Estonian customs, July 2026 duty changes, claims, privacy, scams, and responsible-party routing.
It is based primarily on current official Omniva and Omniva Group sources reviewed on July 27, 2026, including the public tracker, 2026 event dictionary, receiving and parcel-machine instructions, redirection and storage guidance, registered-letter information, return workflows, international-service pages, customs guidance, claim routes, privacy materials, and fraud guidance.
Important limitations:
- The runtime provider code, aliases, country mappings, identifier families, event fields, delivery-partner relationships, redirection fields, storage fields, Picapac fields, COD fields, proof fields, customs fields, claim fields, and sensitive-field suppression must be verified during implementation.
- Omniva is the public brand.
- AS Eesti Post, Omniva SIA, and Omniva LT UAB are separate legal entities in the reviewed structure.
- Picapac is a related parcel-machine service, not an automatic carrier alias.
- Current public evidence does not support one universal Omniva tracking-number format.
- Merchant orders, phone numbers, e-mail addresses, addresses, postcodes, six-digit door codes, COD references, customs references, and claim references are not ordinary public tracking-code inputs.
Shipment data registeredis electronic pre-advice.- Sender machine deposit is distinct from Omniva collection.
- Machine departure, courier pickup, post-office handover, or terminal registration is stronger possession evidence.
- Statuses do not provide exact continuous GPS.
Shipment movement has been temporarily stoppeddoes not identify one universal cause.- A redirection request or saved preferred location does not prove the route changed.
- The originally selected parcel machine is not guaranteed.
- Stored in a parcel machine, notification, door-code receipt, locker opening, and collection are separate.
- One door code can cover several parcels.
- Door-code use does not universally prove named-recipient collection.
- COD payment does not prove locker opening or collection.
- Storage and extension periods differ by country, product, size, and delivery object.
- The current four-day, seven-day, twelve-additional-day, and one-month branches are not one universal Baltic rule.
- Delivery targets begin after physical handover and are not guaranteed appointments.
- Proof objects differ by parcel-machine, courier, post-office, registered-letter, and international workflow.
- Delivered does not verify contents, condition, or continued possession.
- Return registration, deposit, Omniva pickup, merchant receipt, inspection, and refund are separate.
- International tracking can be incomplete after handoff.
- Proof of Delivery can exist without complete route tracking.
- Customs notification, declaration, payment, release, and delivery are separate.
- The July 2026 €3 duty must not be simplified to €3 per parcel.
- Claims, compensation, and merchant remedies are separate.
- Public events can be delayed, incomplete, corrected, normalized, or out of order.
- 11Tracking does not diagnose a specific shipment and cannot act on it.
Last reviewed: July 27, 2026 Review due: October 25, 2026 Research decision: Ready to draft with explicit Omniva, AS Eesti Post, Baltic entity, tracking-code, pre-advice, parcel-machine custody, redirection, storage, door-code, Picapac, COD, proof, return, international, customs, claim, privacy, and runtime limitations
Omniva, AS Eesti Post, Omniva SIA, Omniva LT UAB, and Picapac are trademarks of their respective owners. 11Tracking is an independent tracking helper and is not affiliated with or endorsed by Omniva, AS Eesti Post, Omniva SIA, Omniva LT UAB, Picapac, or Finbite.
Tracking events and delivery estimates come from connected tracking services and carriers. Updates may be delayed, incomplete or revised. 11Tracking does not transport packages and cannot change a delivery.
After you track a parcel, its number is added to the page address so the result can be refreshed or shared. Anyone with that link can use the number, so share it only with people you trust.
