iMile Delivery Tracking

iMile tracking at a glance

• Enter: One supported iMile tracking or shipment-order number.
• A recognised number confirms: A public iMile logistics record may be available.
• It does not confirm: Physical pickup, iMile possession, customs release, driver possession, or delivery.
• Stronger possession evidence: Picked up, collected, accepted, or received at an iMile or named operator facility.
• Courier assigned means: A delivery task was allocated. It does not necessarily mean the driver loaded the parcel or attempted delivery.
• Out for delivery means: A local route is planned or active. It is not a same-day guarantee.
• OTP, COD, and POD are separate: A code, payment instruction, or proof record does not automatically establish final delivery or correct contents.
• Keep: The iMile number and every verified origin, partner, piece, or return number.
• Before physical acceptance: Contact the merchant or shipper first.
• After iMile or a partner records receipt: Contact the operator controlling that stage.
• For a refund or replacement: Contact the merchant or marketplace separately.
• No universal rule: iMile does not publish one global identifier format, delivery time, attempt count, holding period, OTP rule, COD rule, POD type, address-change right, claim deadline, compensation table, or return rule for every country and product.

Track one supported iMile number

Use the tracking form with the identifier supplied as the iMile tracking number, shipment number, shipment-order number, or waybill for the logistics route.

Do not automatically enter:

• a marketplace purchase number;
• a merchant order number;
• a seller invoice number;
• an iMile account number;
• a warehouse order;
• a fulfilment reference;
• a customs declaration;
• a COD reference;
• an OTP;
• a claim case;
• a return authorisation;
• a pickup code.

The official iMile tracker uses “order number” wording, while official support and app material also use “tracking number” and “shipment.” That wording does not prove that every merchant or marketplace order is accepted. The current runtime must identify which iMile identifier families are supported.

What a supported result can contain

Depending on the product, country, and provider data, the public route can contain:

• electronic order creation;
• shipment information received;
• tracking number or waybill created;
• pickup requested;
• package collected;
• accepted at an origin facility;
• sorting;
• domestic transport;
• export processing;
• international line-haul;
• destination arrival;
• customs;
• destination injection;
• iMile or partner facility receipt;
• courier assignment;
• out for delivery;
• failed delivery or Non-Delivery Report;
• reschedule;
• OTP or COD dependency;
• Delivered;
• return.

The result may omit expected stages. A missing event does not prove whether the physical stage happened.

What the form cannot determine

The form cannot independently establish:

• whether the merchant packed the order;
• whether a generic purchase number maps to iMile;
• physical possession when only electronic data appears;
• the exact product from an unsupported number pattern;
• whether iMile or a partner controls every route leg;
• whether the assigned courier physically loaded the parcel;
• whether a COD or customs request is authentic;
• who supplied or used an OTP;
• whether a Proof of Delivery record is accessible to the recipient;
• the named person who received the package;
• contents, condition, value, liability, compensation, refund, or claim outcome.

What is iMile?

iMile is a technology-enabled ecommerce logistics and express-delivery operator established in Dubai in 2017. Current official company material states that it operates in 30 countries and employs more than 20,000 people.

Those are current corporate scale claims, not proof that every service is available in all 30 countries.

iMile and iMile Delivery

iMile is the short brand. iMile Delivery is the principal public service name and consumer-app identity. Country-specific legal entities can use names such as iMile Delivery Services LLC or a local affiliate.

The safest public model is:

iMile / iMile Delivery
= one global logistics brand

country affiliate
= local legal or operating entity

product and contract
= route-specific service and rights

One global brand does not create one global phone number, attempt rule, claim deadline, or delivery contract.

Domestic carrier

In a domestic route, iMile can control:

• pickup;
• origin sorting;
• transport;
• destination facility;
• courier assignment;
• delivery;
• COD;
• OTP;
• POD;
• return.

International operator

Official international services can include:

• origin pickup;
• warehouse receiving or consolidation;
• export customs;
• international transport;
• import clearance;
• destination last mile.

The exact operator can change by route.

Destination last-mile carrier

In some marketplace routes, iMile first appears after:

• an origin carrier;
• an international consolidator;
• line-haul transport;
• destination customs.

In that case, iMile may control only the destination delivery stage. An earlier carrier number can remain valid for the origin leg.

Partner-supported delivery

iMile also operates a Channel Service Partner program for pickup and delivery capacity.

This supports a mixed network model:

iMile tracking and service identity
+
iMile employee or contracted partner operations,
depending on the route

A private vehicle, unfamiliar uniform, or partner business name does not by itself prove fraud or authenticity. Verify the shipment, package, OTP or COD context, and official route.

iMile is not the merchant or marketplace

The merchant or marketplace can:

• create the purchase;
• submit shipment data;
• choose iMile;
• display “shipped”;
• control refund, replacement, and purchase disputes.

Those commercial actions are not physical carrier scans.

Which number should you enter?

The safest rule is:

Enter the identifier explicitly supplied as the iMile tracking, shipment, shipment-order, or waybill number.

No current official public evidence reviewed for this page establishes one universal iMile:

• prefix;
• suffix;
• numeric length;
• alphanumeric length;
• regular expression;
• country code;
• product code;
• check digit.

Unsupported universal format claims

Some third-party pages state that every iMile number:

• has 13 digits;
• begins with 4 or 6;
• follows one fixed numeric pattern.

The current official evidence does not support those global rules.

Do not identify or reject a shipment from an unsupported format claim.

Identifier classes that must remain separate

One purchase can have several numbers

A cross-border purchase can contain:

• marketplace order number;
• origin-carrier number;
• international consolidator number;
• iMile tracking number;
• partner number;
• return number;
• claim case.

A new iMile or partner number does not make an earlier number fake. The numbers can describe different route legs or processes.

One order can contain several pieces

Order splitting, fulfilment, cargo, and multi-piece delivery can create several package numbers.

Do not treat one Delivered piece as proof that every piece arrived.

Why does the number not work?

A no-result response can mean:

• the number was copied incorrectly;
• a merchant order was entered instead of a carrier identifier;
• the iMile electronic order is not active publicly;
• an origin-carrier number has not been mapped to iMile;
• a partner number belongs on another tracker;
• the current product is unsupported;
• the record is outside retention;
• the provider is unavailable;
• the number is invalid.

No result alone does not prove fraud, cancellation, non-shipment, or loss.

From order to delivery: the evidence ladder

What evidence changes the conclusion?

• Electronic order data becomes possession evidence after pickup or acceptance.
• Pickup request becomes completed collection only after a physical event.
• Origin facility receipt becomes destination possession only after the later operator records receipt.
• Courier assignment becomes a delivery attempt only after a route outcome.
• Out for delivery becomes completion only after Delivered, failed attempt, pickup, or return.
• OTP becomes delivery evidence only when used in the legitimate handoff.
• COD becomes payment evidence only after authorized collection is recorded.
• Destination arrival becomes customs completion only after release.
• Customs release becomes iMile possession only after iMile or a partner accepts the package.
• Delivered becomes stronger when the entitled party can inspect route-specific POD.
• Return becomes a commercial remedy only after receipt, inspection, and seller decision.
• Claim becomes compensation only after liability and settlement.

Electronic order, pickup request, and physical acceptance

Order created

A merchant-integrated system can create an iMile logistics order before the package is collected.

iMile order created
→ shipment data exists
≠ iMile physically has the package

Tracking number or shipment order created

A number can be created for:

• route planning;
• label generation;
• pickup booking;
• merchant integration;
• public tracking activation.

Number creation does not prove possession.

Label or pre-advice

A label can contain route, address, item, customs, or account data. It is a shipping document, not a pickup receipt.

Pickup requested

Official iMile domestic, international, and reverse-logistics products include pickup.

pickup requested
≠ courier arrived
≠ parcel presented
≠ parcel accepted

Stronger possession evidence

Look for exact wording such as:

• picked up;
• collected;
• accepted;
• received at iMile facility;
• processed at origin facility;
• another physical-item event tied to iMile or the named operator.

Origin-carrier possession is not iMile possession

A marketplace shipment can use an upstream carrier or consolidator before iMile.

An upstream scan proves possession by that operator. It does not prove that iMile has received the parcel.

Can the first visible scan be delayed?

Yes. A scan can be delayed, batched, corrected, or omitted.

That possibility does not justify certainty:

no visible iMile acceptance
≠ iMile definitely does not have it
≠ iMile definitely has it

When the merchant’s dispatch period has passed and the record still contains only electronic data, contact the merchant or shipper first.

Domestic, international, and destination-last-mile roles

Domestic route

A domestic route can follow:

merchant
→ iMile pickup
→ origin facility
→ domestic network
→ courier or partner
→ recipient

International iMile-managed route

An international product can follow:

origin pickup or warehouse
→ export customs
→ international line-haul
→ import clearance
→ iMile or partner last mile

Destination-only iMile route

A marketplace cross-border route can follow:

merchant
→ origin carrier or consolidator
→ line-haul
→ destination customs
→ iMile injection
→ iMile or partner last mile

The iMile record can begin late in the purchase journey without being incomplete for iMile’s contracted leg.

iMile can use a delivery partner

A partner can perform pickup or delivery inside the iMile network.

Where the public record exposes a source operator, preserve it. Do not assume that every event was created by an iMile employee.

No universal last-mile model

Do not infer from the destination country that:

• iMile always uses its own employee;
• iMile always uses a contractor;
• a particular postal operator is involved;
• one local partner handles every shipment;
• the same pickup and proof options apply.

Use Find the Last-Mile Carrier when another operator appears or the handoff is unclear.

iMile products are not interchangeable

Official iMile product material includes several distinct service families.

Domestic Express Delivery

Domestic express can include:

• pickup;
• sorting;
• line-haul;
• destination processing;
• courier delivery;
• tracking;
• value-added services.

The delivery standard and options depend on country and contract.

Domestic Dropship Delivery

Dropship products can connect sellers, platforms, and recipients without the merchant storing the parcel in a traditional retail channel.

That commercial model does not change the evidence boundary between order creation and physical acceptance.

Domestic Cargo Delivery

Cargo can use different:

• dimensions;
• weight;
• handling;
• facility;
• vehicle;
• proof;
• claim terms.

A cargo reference must not automatically be treated as a normal small-parcel identifier.

International Dropship Delivery

Official product material can include:

• pickup;
• cross-border transport;
• import clearance;
• destination delivery;
• public tracking.

A claim of self-owned last mile applies only to the scoped corridors described by the product. It is not a global fleet promise.

International Consolidation Ship

Consolidation can include:

• warehouse receiving;
• packing;
• merging orders;
• export customs;
• line-haul;
• import clearance;
• last-mile delivery.

Several commercial orders can therefore be grouped into one logistics route, or one commercial order can create several pieces.

International Cargo Delivery

International cargo can include:

• pickup;
• palletizing;
• B2B customs;
• international transport;
• last-mile delivery.

Cargo identifiers and timelines should not be generalized to ordinary ecommerce parcels.

Reverse Pick-up

Reverse Pick-up can include:

• collection from the customer;
• transport to a return centre;
• return to the seller.

Pickup does not prove the seller received the returned item.

Return Management

Return Management can include:

• warehouse inbound;
• unpacking;
• shelving;
• inspection;
• outbound processing.

Those are merchant and warehouse stages, not automatic buyer-refund stages.

Fulfilment and storage

Fulfilment can include:

• inbound inventory;
• storage;
• order sorting;
• packing;
• outbound delivery;
• returned-goods handling.

A fulfilment order is not automatically a public iMile tracking number.

Cool Box Delivery

Cool Box Delivery is a scoped temperature-controlled service.

The existence of that product does not create a universal promise of:

• one temperature range;
• public sensor data;
• continuous temperature evidence;
• one liability standard.

The “1+5+X” value-added layer

Current iMile material describes an “X” value-added layer that can include:

• Proof of Delivery;
• Cash on Delivery;
• OTP;
• customized delivery-attempt timing;
• Non-Delivery Reports.

The existence of a capability does not mean it applies to every shipment.

How to read iMile route events

Public tracking is a sequence of recorded updates, not a live map.

Read the exact event and source operator

A normalized parent status can hide:

• order creation;
• pickup request;
• acceptance;
• facility receipt;
• domestic transport;
• international line-haul;
• customs;
• destination injection;
• driver assignment;
• failed attempt;
• return.

The exact wording and operator control the interpretation.

Events can be delayed, duplicated, or corrected

Possible causes include:

• merchant API delay;
• facility batch upload;
• partner synchronization;
• time-zone conversion;
• late driver upload;
• correction;
• translation;
• provider normalization;
• duplicate data feeds.

A later display timestamp does not always mean a later physical event.

“Real-time tracking” does not mean continuous GPS

iMile marketing uses real-time tracking language for current route visibility.

Public tracking still does not establish:

• live driver location;
• live vehicle location;
• live aircraft location;
• continuous package location;
• every internal movement.

Flight or line-haul event

A flight, airline, departure, or line-haul event can confirm that an international transport stage was recorded.

It does not identify:

• the exact aircraft;
• live aircraft position;
• customs release;
• destination-facility receipt;
• guaranteed delivery date.

Destination facility

A destination facility can be:

• customs-adjacent hub;
• regional sort centre;
• local depot;
• partner facility;
• broad normalized location.

It is not automatically out for delivery.

Exception

A generic exception can concern:

• address;
• customs;
• prohibited item;
• capacity;
• data;
• recipient availability;
• payment;
• damage;
• partner transfer;
• return.

Read the exact reason before deciding who can act.

Courier assigned and Out for Delivery

What does “courier assigned” mean?

Official driver-app material shows a task workflow in which a courier can receive a delivery task, begin delivery, record success, or upload a non-delivery reason.

Use this interpretation:

courier assigned
→ delivery task allocated
≠ parcel physically loaded
≠ courier reached the address
≠ delivery attempt completed

Why can assignment remain for a long time?

Possible reasons include:

• future route assignment;
• parcel not yet loaded;
• route capacity;
• courier reassignment;
• incomplete address or contact data;
• facility backlog;
• delayed driver update;
• provider synchronization;
• failed attempt not yet reflected.

The assignment state alone does not prove loss or misconduct.

What does Out for Delivery mean?

out for delivery
→ local route planned or active
≠ delivery guaranteed that day

Possible next events include:

• Delivered;
• failed attempt;
• address exception;
• recipient unavailable;
• OTP problem;
• COD problem;
• route delay;
• return to facility;
• reschedule.

Repeated Out for Delivery events

Repeated route events can reflect:

• a new attempt;
• reassignment;
• capacity;
• route interruption;
• address clarification;
• late upload;
• duplicate provider events.

They do not automatically prove fraud.

Out for Delivery but not delivered

Check:

1. the exact latest event;
2. whether a failed-attempt reason appears;
3. whether an OTP, COD, address, or contact dependency exists;
4. whether a new attempt or reschedule appears;
5. the official iMile country support route;
6. the merchant or marketplace deadline.

Use Out for Delivery but Not Delivered for the broader action model.

Failed delivery attempts and Non-Delivery Reports

Failed attempt

A failed-attempt event is a carrier-recorded unsuccessful delivery outcome.

It does not automatically prove:

• the courier reached the exact door;
• the recipient refused;
• the address was wrong;
• a call was made;
• the stated reason is independently verified;
• another attempt is guaranteed.

Regional three-attempt example

A current Saudi iMile FAQ states that delivery may be attempted up to three times when the recipient is unavailable.

This is a regional example. It is not a global iMile rule.

Customized attempt timing

Current iMile value-added material indicates that merchants can configure delivery-attempt timing in scoped services.

This means attempt behavior can be:

• country-specific;
• product-specific;
• merchant-configured.

It does not mean every recipient can choose any time.

Non-Delivery Report

An NDR can record a failed-delivery reason and support merchant-side action.

Possible reasons can include:

• recipient unavailable;
• address issue;
• refusal;
• COD issue;
• OTP issue;
• another delivery exception.

The complete private NDR can contain more detail than the public status. 11Tracking cannot access a merchant portal or private report.

Reason code is not an independent blame decision

A reason such as “recipient unavailable,” “wrong address,” or “refused” is a carrier-system record.

It is not independent proof of who caused the failure.

What to do after a failed attempt

1. Read the exact reason.
2. Verify the address and phone stored with the merchant.
3. Check whether OTP or COD was required.
4. Check for an announced next attempt, support action, or return.
5. Contact iMile through the official country route.
6. Contact the merchant if order data needs correction.
7. Preserve marketplace deadlines.

Use Delivery Attempted for the generic evidence model.

Scheduling, address changes, and delivery management

Consumer app capabilities

Current iMile Delivery app listings describe features such as:

• shipment tracking;
• notifications;
• preferred-date delivery or pickup scheduling;
• address management.

These establish platform capability.

They do not establish universal shipment eligibility.

app offers feature
≠ feature available in every country
≠ this merchant allows it
≠ this parcel is eligible
≠ request accepted
≠ route changed
≠ selected date guaranteed

Can the delivery date be changed?

Possibly, depending on:

• country;
• product;
• merchant contract;
• route stage;
• app eligibility;
• courier operation.

A submitted request is not proof of an accepted schedule.

Can the address be changed?

A current Saudi FAQ provides a scoped example where an address change can be possible after pickup.

That must not be generalized to every country.

Authority can belong to:

• merchant;
• shipper;
• iMile account holder;
• recipient;
• marketplace;
• broker or customs party in a data-correction context.

Request state model

request submitted
→ identity and eligibility checked
→ accepted or rejected
→ route updated
→ courier receives instruction
→ final outcome

Address exception

An address problem can originate from:

• buyer entry;
• merchant transmission;
• marketplace formatting;
• missing postcode;
• phone problem;
• geocoding;
• iMile processing;
• driver interpretation;
• customs data.

Do not assign blame from the status alone.

11Tracking cannot change the route

11Tracking and USTracking cannot:

• submit an address change;
• reschedule delivery;
• contact the driver;
• hold the package;
• reroute it;
• verify that a request was accepted.

Use Change, Reroute, or Hold a Package for the general decision model.

OTP delivery verification

What is iMile OTP?

iMile offers a scoped OTP service for secure delivery verification. The reviewed official service states that the code can be sent through:

• SMS;
• WhatsApp.

The current reviewed service page lists coverage in major cities in the UAE and Saudi Arabia.

That is scoped coverage, not a universal rule.

OTP is not required for every iMile shipment

Availability depends on:

• country;
• merchant contract;
• product;
• delivery workflow;
• item or risk settings.

OTP state model

OTP generated
→ OTP sent
→ recipient verifies legitimate delivery context
→ code supplied during authorized handoff
→ carrier records verification

What OTP can support

Correct use can support evidence that:

• someone with access to the code authorized the handoff;
• the carrier completed a verification step.

What OTP does not universally prove

OTP does not automatically prove:

• the named buyer personally received the parcel;
• the delivery address was correct;
• the package contained the correct item;
• the item was undamaged;
• the recipient inspected the contents;
• the merchant owes no remedy.

Safe OTP handling

Never:

• enter OTP in a public tracking form;
• publish it;
• send it through an unverified link;
• give it to an unsolicited caller;
• share it before confirming the legitimate shipment and handoff context.

An OTP can be requested through WhatsApp in the legitimate iMile service described by the official page. WhatsApp alone therefore does not prove authenticity. Verify the shipment and context independently.

OTP is not the same as POD

OTP can be one evidence component. It is not identical to:

• photo;
• signature;
• recipient name;
• timestamp;
• complete Proof of Delivery.

Cash on Delivery

What is iMile COD?

iMile offers Cash on Delivery in scoped markets and merchant contracts.

COD means:

merchant-arranged amount
→ collected from recipient at delivery
→ recorded by iMile
→ remitted to merchant under the contract

COD is not customs duty

Keep these separate:

• COD purchase payment;
• customs duty;
• import VAT or tax;
• brokerage;
• carrier handling;
• storage;
• delivery charge.

A shipment can have one, several, or none of those obligations.

COD coverage is scoped

The reviewed official page lists major cities in:

• United Arab Emirates;
• Saudi Arabia;
• Oman;
• Kuwait;
• Qatar;
• Bahrain;
• Jordan;
• Malaysia.

That is current service-page coverage, not a permanent global list.

COD state model

COD instruction exists
→ amount presented
→ recipient verifies merchant order and authorized collection
→ payment collected
→ payment recorded
→ merchant remittance

What a COD amount does not prove

COD amount visible
≠ payment request authentic

payment requested
≠ recipient owes it

payment collected
≠ correct contents or condition

payment recorded
≠ merchant remittance completed

Unordered COD package

Do not pay merely because:

• the parcel has your name;
• the address is correct;
• the courier knows the amount;
• the iMile number is real;
• an OTP was sent.

Verify the merchant order independently.

11Tracking cannot verify or collect COD

11Tracking cannot:

• authenticate the collector;
• verify the amount;
• collect the payment;
• reconcile merchant funds;
• decide whether the amount is a merchant charge or customs charge without official order context.

Proof of Delivery

Does iMile provide POD?

Yes, iMile publicly promotes Proof of Delivery as a value-added service.

A current Saudi FAQ states that a delivered-parcel photo and digital signature can be available in the iMile portal. The current privacy policy also states that tracking and POD records can be provided to the entity that initiated the shipment, such as the merchant or logistics partner.

POD existence and access are separate

POD exists
≠ recipient can automatically download it
≠ POD is public
≠ 11Tracking can retrieve it

The merchant or account holder may have broader access than the recipient.

Possible POD components

Depending on the service, POD can include:

• delivery photo;
• digital signature;
• OTP;
• timestamp;
• delivery status;
• recipient or handoff notation;
• driver-uploaded information.

No universal combination was confirmed.

What POD can confirm

POD confirms that the carrier system stored a delivery-evidence record.

The record can support evidence that:

• a package was placed at a location;
• a signature was captured;
• an OTP was used;
• delivery was marked complete.

What POD does not universally confirm

• named buyer personally received it;
• correct address;
• signer authority;
• contents;
• condition;
• parcel remained at the location;
• no theft occurred;
• carrier liability;
• merchant refund outcome.

Photo boundaries

A photo can show:

• parcel;
• door;
• gate;
• mailbox;
• building feature;
• another location.

It may not show enough to prove the address.

A correct-location photo also does not prove that the parcel remained there.

Signature boundaries

A digital signature can belong to:

• recipient;
• household member;
• agent;
• building staff;
• another accepted person.

The identity and authority of the signer depend on the service and record.

Disputed POD workflow

1. Preserve the exact Delivered event.
2. Identify the available POD type.
3. Compare the photo or location with the real address.
4. Identify the signature or OTP context when available.
5. Contact iMile through the official country support route.
6. Contact the merchant or marketplace.
7. Preserve purchase-protection deadlines.
8. Keep carrier investigation separate from refund or replacement.

Use Proof of Delivery, Photo, and Signature for the broader evidence model.

Customs and international tracking

iMile can coordinate transport and customs processes, but it is not the government customs authority.

Customs actor model

Customs events are separate stages

Possible events include:

• data submitted;
• package presented;
• documents requested;
• assessment;
• inspection;
• payment requested;
• payment accepted;
• release;
• rejection;
• return.

Payment does not prove customs release

charge calculated
→ request independently verified
→ payment submitted
→ payment accepted
→ customs decision
→ release
→ iMile or partner processing resumes

Customs Cleared does not prove iMile possession

After release, the parcel may still need:

• broker handoff;
• line-haul movement;
• destination injection;
• iMile facility receipt;
• partner acceptance;
• local-number activation.

COD and customs are separate

A COD amount is merchant-arranged payment. Customs duty, tax, brokerage, and carrier handling are separate obligations.

No universal DDP rule

No official evidence reviewed supports one universal DDP rule for all iMile shipments.

Who pays can depend on:

• route;
• merchant;
• marketplace;
• product;
• entry method;
• shipping terms.

United States low-value imports: July 2026 context

Duty-free de minimis is not a safe default

Current U.S. official material states that duty-free de minimis treatment remains suspended for covered low-value shipments, subject to stated legal exceptions.

Do not assume an iMile-linked ecommerce package is duty-free because:

• its value is below an old threshold;
• the marketplace collected tax;
• it entered through mail;
• an earlier order had no charge.

Postal and non-postal routes can differ

An iMile route can involve:

• commercial carrier entry;
• postal partner entry;
• consolidator entry;
• another qualified party.

The carrier label alone does not identify the U.S. entry method.

Mail informal-entry process

U.S. Customs and Border Protection states that a new mail informal-entry process took effect on July 24, 2026.

This is very high-volatility guidance. Verify the current CBP rules when a shipment or payment decision depends on them.

No universal U.S. charge

The amount can depend on:

• classification;
• origin;
• value;
• entry type;
• trade measures;
• exemptions;
• broker or carrier handling;
• merchant arrangement.

11Tracking cannot calculate, collect, dispute, or pay it.

European Union low-value imports: July 2026 context

Temporary €3 customs duty

European Commission guidance reviewed for this page states that from July 1, 2026, a temporary €3 customs duty per item applies to scoped low-value distance-sale consignments up to €150 imported from outside the European Union.

The current temporary measure is scheduled through July 1, 2028.

Not simply once per parcel

The Commission describes calculation by item based on tariff classification.

Several goods can therefore create:

• one €3 amount when they share a classification;
• several €3 amounts when classifications differ.

VAT, IOSS, duty, and handling are separate

• VAT is not customs duty.
• IOSS does not automatically remove the temporary duty.
• Carrier or broker handling is separate.
• Storage and delivery charges can be separate.
• A proposed Union handling fee is not the temporary €3 duty.

Who is responsible?

Current Commission guidance places primary responsibility on the declarant, seller or importer, IOSS holder, special-arrangements user, or representative in the stated flow, with residual consumer cases.

Do not assume every recipient pays iMile directly.

Product identifiers are not movement evidence

Product identifiers can be customs-data fields.

Submitting them does not prove:

• customs presentation;
• assessment;
• release;
• iMile possession.

Because these rules are highly volatile, use current European Commission and destination customs guidance for shipment-specific action.

Why iMile tracking may not update

A tracking gap does not have one diagnosis.

Possible branches include:

• merchant order exists but no iMile shipment was created;
• iMile electronic order exists but no pickup occurred;
• pickup was requested but not completed;
• first acceptance scan is delayed;
• origin carrier still controls the parcel;
• line-haul tracking is sparse;
• customs action is pending;
• destination injection is pending;
• iMile facility scan is delayed;
• courier assignment has not become an active route;
• failed attempt is waiting for NDR action;
• partner synchronization is delayed;
• identifier is wrong;
• product is unsupported;
• record is old;
• number is invalid.

Evidence-first check

1. Confirm the identifier type.
2. Read the exact latest event and source operator.
3. Identify whether physical iMile acceptance exists.
4. Check whether another carrier controls the earlier leg.
5. Check customs or import dependencies.
6. Check destination facility receipt.
7. Separate courier assignment from actual route or attempt.
8. Check for OTP, COD, address, or recipient-contact dependencies.
9. Preserve merchant and marketplace deadlines.
10. Contact the actor controlling the current stage.

No universal waiting interval

Do not use one global 24-hour, 48-hour, 72-hour, three-day, or seven-day rule.

The next action depends on:

• exact event;
• current operator;
• country;
• product;
• expected delivery;
• explicit dependency;
• merchant or marketplace deadline.

Use Tracking Not Updating for the broader escalation model.

iMile says Delivered, but the package is missing

What Delivered confirms

Delivered
→ iMile or the publishing operator recorded completion
≠ named buyer personally received it
≠ correct address independently verified
≠ contents or condition proved

Delivery evidence can vary

Completion can be recorded through:

• photo;
• signature;
• OTP;
• driver status;
• household or agent handoff;
• reception;
• safe place;
• another contracted method.

Delivered but missing workflow

1. Preserve the exact event, time, location, and source operator.
2. Identify every package number and piece.
3. Ask the entitled party for available POD.
4. Check household members, reception, mailroom, safe place, gate, mailbox, and the location shown in the photo.
5. Contact iMile through the official country support route.
6. Contact the merchant or marketplace.
7. Preserve purchase-protection deadlines.
8. Ask the logistics contract holder to open the carrier inquiry.
9. Keep carrier compensation separate from merchant refund or replacement.

Conflicting marketplace and iMile records

Possible causes include:

• synchronization delay;
• correction;
• wrong address;
• multi-piece partial delivery;
• proof dispute;
• merchant normalization;
• provider error;
• late event upload.

Do not diagnose theft or fraud from one record

A disputed delivery can involve:

• authorized alternate recipient;
• wrong address;
• misplaced parcel;
• insufficient photo;
• incorrect signature;
• data error;
• theft;
• driver misconduct;
• another cause.

Public tracking alone cannot determine which.

Use Delivered but Not Received for the complete recovery sequence.

Returns and reverse logistics

Reverse Pick-up

Official Reverse Pick-up can include:

• collection from the customer;
• return-centre operations;
• transport back to the seller.

Return Management

Official Return Management can include:

• warehouse inbound;
• unpacking;
• shelving;
• quality inspection;
• outbound action.

Return state model

return requested
→ merchant or marketplace authorization
→ pickup requested
→ return carrier acceptance
→ reverse transport
→ return centre or seller receipt
→ unpacking or inspection
→ refund or replacement decision
→ payment

What return tracking does not prove

return requested
≠ pickup completed

pickup completed
≠ return centre received

return centre received
≠ inspection passed

inspection completed
≠ refund approved

refund approved
≠ refund paid

Undeliverable return

A failed delivery can lead to:

• redelivery;
• hold;
• address correction;
• return to facility;
• return to shipper.

No universal branch or interval was confirmed.

Return can use a new number

Keep:

• original iMile number;
• partner number;
• return number;
• merchant order;
• return authorization;
• timestamps.

A new return number does not invalidate the outbound number.

Claims, liability, and merchant remedies

No current official evidence reviewed supports one global iMile claim rule for every country and product.

Who usually controls a formal claim?

The logistics contract can belong to:

• merchant;
• shipper;
• marketplace;
• fulfilment customer;
• account holder.

The recipient can often:

• report non-delivery;
• provide evidence;
• dispute POD;
• contact local support;
• use merchant or marketplace remedy.

Direct recipient eligibility must be verified from current country and product terms.

Merchant remedy and carrier claim are separate

merchant refund or replacement
≠ iMile carrier compensation
≠ marketplace decision
≠ payment-card dispute
≠ customs refund

No universal deadline or payout

No universal public rule was confirmed for:

• claim deadline;
• eligible claimant;
• liability limit;
• compensation amount;
• insurance promise;
• damage-notice period;
• legal effect of POD.

Claim state model

problem reported
→ correct contract and product identified
→ eligible claimant identified
→ evidence submitted
→ investigation
→ liability decision
→ compensation calculation
→ settlement

claim opened
≠ carrier fault
≠ compensation approved
≠ merchant refund

POD does not automatically decide liability

A POD record can be important evidence.

It does not universally:

• defeat a missing-package claim;
• prove correct address;
• prove named-recipient receipt;
• prove contents;
• determine refund rights.

Evidence to preserve

Keep privately:

• merchant order;
• iMile number;
• origin and partner numbers;
• route history;
• POD;
• OTP or COD context;
• packaging and labels;
• damage photos;
• missing-content list;
• value evidence;
• customs records;
• support correspondence;
• deadlines.

Use Package Claim Guide and Package Damaged or Contents Missing for the broader evidence models.

Who should you contact?

Privacy and scam safety

Treat tracking numbers as shipment data

A tracking number can expose:

• route;
• destination area;
• timing;
• delivery outcome;
• proof availability;
• related identifiers.

Do not publish a real number in:

• a public post;
• a review;
• a support screenshot;
• a page URL;
• metadata;
• an AI prompt that does not need it.

Never enter these in a public tracker

• merchant login;
• iMile portal credentials;
• phone number;
• full address;
• passport or national ID;
• tax number;
• invoice;
• customs document;
• payment card;
• OTP;
• COD payment;
• signature;
• delivery photo;
• claim evidence;
• pickup code.

POD contains sensitive delivery evidence

POD can expose:

• front door;
• building;
• mailbox;
• signature;
• recipient or agent;
• delivery time;
• location details.

Do not post it publicly unless sensitive data is removed and disclosure is necessary.

Real tracking data does not authenticate a message

A fraudulent message can contain:

• real iMile number;
• correct status;
• destination city;
• real OTP;
• known COD amount;
• iMile logo.

real tracking number
≠ authentic sender

correct status
≠ official link

real OTP
≠ legitimate caller

known COD amount
≠ authorized collection

Common suspicious narratives

• address-correction fee;
• customs-release fee;
• redelivery payment;
• storage fee;
• unordered COD package;
• OTP request;
• identity-document request;
• payment to a personal account;
• proof-download link.

Safe verification sequence

1. Do not use the message link.
2. Open iMile, the merchant, marketplace, broker, or customs site independently.
3. Enter only the supported tracking number in the official or trusted tracker.
4. Identify the current shipment and operator.
5. Verify COD, customs, or payment obligations in the independent order record.
6. Do not share OTP, card data, credentials, or identity documents through an unverified channel.
7. Preserve the message privately.
8. Use Fake Delivery Message for the full process.

Frequently asked questions

How do I track an iMile package?

Enter one supported iMile tracking or shipment-order number. Do not enter a generic marketplace order, OTP, COD reference, customs reference, or claim case unless the official service explicitly identifies it as the tracking number.

Why does the iMile tracker say “order number”?

That is the official public wording. Other iMile sources use tracking number and shipment terminology. The wording does not prove that every merchant purchase number is accepted.

Can I track a marketplace order number?

Not automatically. Use the iMile tracking, shipment-order, or waybill identifier supplied in the shipping details.

Does every iMile number have the same format?

No universal public format was confirmed. Do not rely on one length, prefix, suffix, or regular expression.

Are all iMile tracking numbers 13 digits?

That claim was not confirmed by current official evidence.

Does Order Created mean iMile has the parcel?

No. It means logistics data exists. Look for pickup, collection, acceptance, or facility receipt.

Does Pickup Requested mean the parcel was collected?

No. It confirms a request, not completed collection.

Which event proves iMile received it?

Picked up, collected, accepted, or received at an iMile facility is stronger possession evidence. Read the exact operator.

Why did iMile tracking start only after customs?

iMile may control only the destination last-mile stage. Another carrier or consolidator may have handled the origin and line-haul stages.

Does Customs Cleared mean iMile has it?

No. Release and carrier possession are separate. Look for iMile or partner facility acceptance.

What does Courier Assigned mean?

It means a delivery task was allocated. It does not necessarily mean the courier physically loaded the package or attempted delivery.

Does Courier Assigned mean delivery today?

No. Assignment can occur before the active route and can remain through delays or reassignment.

Does Out for Delivery guarantee delivery today?

No. It means a local route is planned or active. A failed attempt, delay, exception, reschedule, or return can follow.

Why is Out for Delivery repeated?

Possible causes include reassignment, repeated attempt, capacity, address clarification, delayed upload, or duplicate data.

What does Failed Delivery Attempt mean?

It means a non-delivery outcome was recorded. Read the exact reason. It does not independently prove recipient fault.

How many delivery attempts will iMile make?

No global attempt count was confirmed. A Saudi FAQ gives a regional example of up to three attempts, but other countries and merchant contracts can differ.

What is an NDR?

A Non-Delivery Report records a failed-delivery reason and can support merchant-side action. The full private report may not be public.

Can I reschedule iMile delivery?

The iMile app offers preferred-date scheduling in its current feature set, but eligibility depends on country, merchant, product, and shipment stage.

Can I change the address?

Possibly in some countries and products. A current Saudi FAQ gives a scoped example. A submitted request is not proof that the route changed.

Why did iMile send me an OTP?

OTP can be used as a delivery-verification credential in scoped products.

Is OTP required for every iMile parcel?

No. Availability depends on country, merchant, product, and delivery workflow.

Can an iMile OTP arrive through WhatsApp?

The reviewed official OTP service states that SMS and WhatsApp can be used in its scoped coverage.

Should I give the OTP over the phone or in a message?

Only after independently verifying the shipment and legitimate handoff context. Never publish it or send it through an unverified link.

Does OTP prove I received the correct item?

No. It can support evidence of an authorized handoff step. It does not prove contents or condition.

What is iMile COD?

Cash on Delivery is merchant-arranged payment collected at delivery and remitted to the merchant under the contract.

Is COD the same as customs duty?

No. COD, customs duty, tax, brokerage, handling, and delivery charges are separate.

How do I verify a COD amount?

Check the merchant order independently and verify the collection through official iMile or merchant channels. Do not pay only because the number and address are real.

Does iMile provide Proof of Delivery?

Yes, in scoped services. POD can include a photo, digital signature, OTP, timestamp, or other record.

Can every recipient download POD?

No universal recipient entitlement was confirmed. POD may be available primarily to the merchant or logistics partner that initiated the shipment.

Does a delivery photo prove correct delivery?

Not by itself. The photo may not establish the exact address, recipient, contents, or what happened after placement.

Does a signature prove the named buyer signed?

Not universally. The signer can be another accepted person. The service-specific record controls.

What should I do if iMile says Delivered but the parcel is missing?

Preserve the record, identify all pieces, request available POD through the entitled party, check the shown location, contact iMile, contact the merchant, and preserve marketplace deadlines.

Can iMile use partner drivers?

Yes, iMile operates a Channel Service Partner program. The exact operating model depends on the route.

Does a private car mean the delivery is fake?

No. It also does not prove legitimacy. Verify the shipment, package, OTP or COD context, and official carrier record.

Does customs payment mean the parcel was released?

No. Payment is one dependency. Wait for an explicit release or later carrier-processing event.

Is every iMile shipment DDP?

No universal DDP rule was confirmed.

Is the EU €3 duty charged once per parcel?

No. Current European Commission guidance describes it per item based on tariff classification in the scoped flow, not simply once for the physical parcel.

What is Reverse Pick-up?

It is a return service that can collect an item from the customer and transport it into the return process.

Does return pickup mean my refund is approved?

No. Pickup, return-centre receipt, inspection, refund approval, and payment are separate.

Who can file an iMile carrier claim?

The merchant, shipper, marketplace, fulfilment customer, or account holder commonly controls the logistics contract. Direct recipient eligibility depends on current country and product terms.

Is there one global iMile claim deadline?

No universal deadline was confirmed.

Can 11Tracking contact iMile or the driver?

No. 11Tracking can display supported public tracking data and guidance. It cannot contact carriers, merchants, marketplaces, brokers, customs authorities, or drivers.

Can USTracking use OTP, collect COD, retrieve POD, or file a claim?

No. It cannot use delivery credentials, handle payment, retrieve protected proof, submit customs information, file claims, recover the package, or guarantee delivery.

Can a real iMile number appear in a scam?

Yes. Real tracking, status, OTP, COD, or POD-related data does not authenticate the sender or payment link.

Use USTracking as a tracking companion

After identifying the correct number and current operator, USTracking may help you:

• save a supported iMile tracking or shipment-order number;
• organize public route events;
• preserve verified origin, iMile, partner, piece, and return numbers;
• monitor later public updates;
• compare public iMile and partner events;
• receive notifications.

USTracking cannot:

• access merchant, marketplace, iMile, warehouse, driver, broker, customs, or partner accounts;
• track by phone, address, identity, OTP, COD reference, customs reference, claim case, or pickup code;
• determine a universal number format;
• identify a universal driver or partner;
• locate a parcel, driver, vehicle, aircraft, or person;
• contact an operator;
• change the date or address;
• redirect, hold, or return the package;
• use an OTP;
• collect or pay COD;
• pay customs;
• retrieve protected POD;
• file a claim;
• recover the package;
• decide a refund;
• guarantee tracking completeness, delivery, compensation, customs release, refund, or arrival time.

Related guides

• Package Tracking Help Center
• How Package Tracking Works
• Label Created
• Carrier Received Package
• In Transit
• Handed to a Local Carrier
• Customs Processing
• Customs Cleared
• Tracking Not Updating
• Tracking Number Not Found
• Out for Delivery
• Out for Delivery but Not Delivered
• Delivery Attempted
• Available for Pickup
• Delivered
• Delivered but Not Received
• Return to Sender
• Package Stuck in Customs
• Customs Cleared but No Update
• Wrong Address or Address Information Required
• Find the Last-Mile Carrier
• Change, Reroute, or Hold a Package
• Proof of Delivery, Photo, and Signature
• Package Claim Guide
• Who to Contact About a Package
• Package Damaged or Contents Missing
• Fake Delivery Message
• How International Package Tracking Works

Scope, evidence, and limitations

This page is an English-language guide to public iMile tracking evidence, identifier classes, electronic order and possession stages, domestic and international route roles, courier assignment, delivery attempts, OTP, COD, Proof of Delivery, customs, returns, claims, and responsible-party routing.

It is based primarily on official iMile product, support, app, privacy, and partner-program material, plus current U.S. and European Union customs sources reviewed on July 25, 2026.

Important limitations:

• The current runtime provider, aliases, accepted identifier families, and “order number” behavior must be verified during implementation.
• No universal iMile number format was confirmed.
• No universal country coverage list applies to every product.
• No universal self-operated or partner-delivery model was confirmed.
• No universal delivery time, attempt count, holding period, app eligibility, address-change right, OTP rule, COD rule, POD type, recipient POD access, claim deadline, compensation amount, insurance promise, DDP rule, or return rule was confirmed.
• Regional FAQs, service pages, and legal terms apply only to their stated country, product, and contract.
• Public tracking can be delayed, incomplete, normalized, translated, corrected, duplicated, or out of order.
• U.S. and EU customs rules are highly volatile and can change before the next scheduled review.
• 11Tracking does not diagnose a specific shipment and cannot act on the package.

Last reviewed: July 25, 2026 Review due: October 23, 2026 Research decision: Ready to draft with explicit identifier, possession, product, country, OTP, COD, POD, attempt, partner, customs, return, claim, and runtime limitations