Ekart Tracking: Parcel Number, Pickup, Hubs, Out for Delivery, NDR, RTO, OTP, COD, and POD

Ekart tracking at a glance

• Enter: One supported Ekart ecommerce parcel tracking number.
• Do not assume: A Flipkart order number, merchant order, or LR Shipment ID is the parcel tracking number.
• A recognised number confirms: A public Ekart logistics record may be available.
• It does not confirm: Physical pickup, Ekart possession, current live location, last-mile assignment, delivery, or refund.
• Stronger possession evidence: Picked up, collected, accepted, or received at an Ekart facility.
• Mother Hub means: A major sortation or transit event. It does not automatically mean the parcel is near the recipient.
• Delivery hub means: A local or regional facility event. It does not automatically mean Out for Delivery or public self-collection.
• Out for Delivery means: A local route is planned or active. It is not an unconditional same-day guarantee.
• NDR reason means: An operational non-delivery reason was recorded. It is not independent proof of recipient fault.
• RTO means: Return to Origin. RTO marking is not the same as physical seller receipt or refund.
• Open Box Delivery: Applies only to eligible marketplace, product, seller, location, and route combinations.
• OTP, COD, and POD: Separate delivery, payment, and evidence objects.
• Before pickup: Contact the merchant or shipper.
• After Ekart acceptance: Contact Ekart through the applicable official or merchant-controlled route.
• For refund or replacement: Contact Flipkart or the actual merchant separately.
• No universal rule: Ekart does not publish one parcel-number format, ETA, attempt count, Open Box entitlement, OTP rule, COD rule, POD type, hub-collection right, RTO stop right, claim deadline, or compensation table for every shipment.

Track one supported Ekart ecommerce parcel number

Use the tracking form with the identifier explicitly supplied as the Ekart:

• tracking number;
• tracking ID;
• AWB;
• waybill;
• consignment number

for the ecommerce parcel route.

Do not automatically enter:

• a Flipkart order number;
• another merchant purchase number;
• an invoice number;
• an Elite account number;
• an Elite merchant order;
• an LR Shipment ID;
• a freight document;
• a pickup reference;
• a delivery OTP;
• a COD payment reference;
• a POD or dispute ticket;
• an RTO authorization;
• a return request;
• a claim case.

Ecommerce parcel tracking and LR freight tracking are separate

Ekart’s official tracking page distinguishes:

Ecommerce Parcel Tracking
→ enter a parcel tracking number

B2B / FTL / PTL / Bulk Shipment Tracking
→ use the separate official portal
→ enter an LR Shipment ID

An LR Shipment ID belongs to a freight or bulk-shipment workflow. The consumer parcel form should not silently send it to the ecommerce parcel provider.

What a supported result can contain

Depending on the merchant, product, and provider data, public Ekart tracking can show:

• shipment information received;
• manifest created;
• AWB or tracking ID generated;
• pickup booked;
• pickup attempted;
• picked up or accepted;
• origin facility receipt;
• sortation;
• Mother Hub processing;
• line-haul movement;
• destination facility;
• delivery hub;
• last-mile allocation;
• Out for Delivery;
• failed attempt;
• NDR;
• reschedule;
• customer rejection;
• OTP or COD dependency;
• Delivered;
• RTO marked;
• return movement;
• returned to seller;
• reverse pickup.

The public record may omit an expected stage. Missing data does not establish whether that physical event happened.

What the form cannot determine

The form cannot independently establish:

• whether a merchant packed the order;
• whether a generic Flipkart order maps to Ekart;
• whether an AWB was physically handed over;
• parcel contents, authenticity, completeness, or condition;
• the exact product or merchant contract from an unsupported number format;
• whether a Wishmaster physically loaded the parcel;
• whether the recorded NDR reason is independently correct;
• whether an Open Box request is eligible;
• who used an OTP;
• whether a COD amount is authorized;
• whether the recipient can access POD;
• whether RTO can be stopped;
• claim eligibility, liability, compensation, refund, or replacement.

What are Ekart, Instakart, Flipkart, Elite, and Wishmaster?

Ekart Logistics

Ekart is an India-focused logistics and supply-chain brand that began operations in 2009. Current official company material describes a large network of sortation facilities, fulfilment centres, last-mile hubs, trucks, and daily shipments.

Those figures are corporate scale claims. They do not mean every product or service is available for every PIN code or account.

Instakart Services Private Limited

Current Ekart and Elite terms identify Instakart Services Private Limited as the owner and operator of the reviewed platform and as the contractual service provider in the Elite relationship.

The correct public model is:

Ekart Logistics
= public logistics brand and service identity

Instakart Services Private Limited
= current platform owner and service provider
  in the reviewed Ekart and Elite terms

This does not create a second carrier page.

Flipkart

Flipkart is the marketplace and purchase environment for scoped orders.

Flipkart can control:

• the purchase;
• seller relationship;
• Open Box eligibility;
• return or replacement request;
• buyer support;
• refund decision.

Ekart can perform the physical logistics stage.

Flipkart order
≠ Ekart tracking number

Flipkart refund
≠ Ekart carrier compensation

Ekart carries parcels for other merchants

Ekart publicly markets logistics services to ecommerce businesses, D2C brands, retailers, SMEs, and other merchants.

Therefore:

Ekart parcel
≠ automatically a Flipkart purchase

For a third-party merchant shipment, use that merchant’s order and remedy process rather than assuming Flipkart controls it.

Elite

Elite is Ekart’s self-serve merchant shipping platform.

It can involve:

• merchant onboarding;
• KYC and account data;
• wallet funding;
• rate cards;
• AWB generation;
• manifesting;
• pickup;
• delivery;
• COD remittance;
• POD;
• NDR;
• RTO;
• disputes;
• claims.

An ordinary buyer or consignee is not automatically the Elite contractual Client.

Wishmaster

Flipkart and Ekart use Wishmaster for a delivery-partner role.

A Wishmaster can perform delivery and related operational steps. The title does not independently establish:

• employee status;
• contractor status;
• identity of a caller;
• authority to change the merchant order;
• authority to decide a refund;
• authorization to collect money through an unrelated personal account.

Delivery partners and field apps

Official field and partner apps support operational tasks such as:

• pickup;
• delivery;
• navigation;
• status updates;
• payment collection.

Those apps are not public live-driver tracking services.

Which number should you enter?

The safest rule is:

Enter the identifier explicitly provided as the Ekart ecommerce parcel tracking number, AWB, waybill, tracking ID, or consignment number.

No current official public source reviewed for this page establishes one universal Ekart:

• prefix;
• suffix;
• numeric length;
• alphanumeric length;
• regular expression;
• marketplace code;
• product code;
• PIN-code encoding;
• check digit.

Identifier classes that must remain separate

Manifest is not a parcel receipt

Elite merchant terms describe a manifest as shipment data supplied by the Client.

It can contain:

• consignee details;
• address;
• PIN code;
• invoice value;
• prepaid or COD designation;
• product description;
• other routing data.

manifest uploaded
→ Ekart has shipment data
≠ Ekart physically has the parcel

AWB generation can precede pickup

The current Elite account workflow allows merchants to generate AWBs before Ekart collects the goods.

AWB generated
→ carrier shipment identity exists
≠ parcel picked up

One commercial order can have several parcel numbers

A Flipkart or merchant order can be:

• split by seller;
• split by warehouse;
• packed into several parcels;
• partly exchanged;
• partly returned.

One Delivered parcel does not prove that every piece arrived.

Reverse pickup and replacement can create new numbers

A return or exchange can create:

• reverse AWB;
• replacement AWB;
• new forward shipment;
• separate merchant return reference.

Keep every mapped number.

Why does the number not work?

A no-result response can mean:

• the merchant order was entered instead of the tracking number;
• an LR Shipment ID was entered in the parcel tracker;
• the number was copied incorrectly;
• the manifest or AWB is not public yet;
• the pickup has not activated the route;
• another carrier is responsible;
• the current Ekart product is unsupported;
• the record is outside retention;
• the provider is unavailable;
• the identifier is invalid.

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

From merchant order to delivery: the evidence ladder

What evidence changes the conclusion?

• Manifest or AWB becomes possession evidence after physical pickup or acceptance.
• Pickup attempt becomes handover only after a successful collection event.
• Facility movement becomes destination readiness only after destination processing and last-mile allocation.
• Out for Delivery becomes a final result only after delivery, failed attempt, pickup, or return.
• An NDR becomes a next operational instruction only after the merchant or account holder acts on it.
• RTO marking becomes physical return after reverse-route events.
• Returned to seller becomes a refund only after the merchant or marketplace makes a separate decision.
• OTP becomes stronger handoff evidence only in the legitimate scoped workflow.
• COD becomes payment evidence only after authorized collection.
• POD becomes stronger delivery evidence when the entitled account holder can inspect the record.
• A claim becomes compensation only after investigation, liability, and settlement.

Manifest, AWB, pickup, and physical Ekart possession

Merchant order

A merchant or marketplace can create the commercial order before any carrier shipment exists.

order confirmed
≠ parcel packed
≠ Ekart AWB created
≠ Ekart pickup completed

Manifest uploaded

A manifest is administrative shipment data.

It can be uploaded before:

• goods are ready;
• pickup;
• physical handover;
• origin scan.

AWB or tracking ID created

An AWB or tracking ID can support:

• label generation;
• routing;
• pickup booking;
• account billing;
• public tracking activation.

It does not prove physical possession.

Pickup booked

Current Elite merchant guidance includes pickup booking and cutoff rules.

A booked pickup does not prove that a field agent arrived.

Pickup attempted

A pickup attempt can fail because:

• goods were not ready;
• merchant was unavailable;
• packaging was incomplete;
• address or access was wrong;
• capacity changed;
• another operational issue occurred.

pickup attempted
≠ parcel handed over

Conflicting official pickup-attempt counts

Current official Ekart material does not present one consistent number:

• the Elite FAQ describes one first-mile reattempt model;
• the current Elite Terms of Service describe another pickup-attempt limit.

These can reflect different products, versions, definitions, or contract precedence.

The safe conclusion is:

Pickup-attempt limits depend on the current merchant contract and product. Do not apply one published count universally.

Stronger possession evidence

Look for exact events such as:

• picked up;
• shipment collected;
• accepted;
• received at Ekart facility;
• processed at origin facility.

The operator matters where another merchant, aggregator, or partner appears.

“Said to contain” does not verify contents

The current Elite contract treats consignments on a said to contain basis.

This means Ekart does not necessarily verify the parcel contents against the merchant declaration during ordinary transport.

Ekart accepted parcel
≠ correct product verified
≠ contents complete
≠ product genuine
≠ item undamaged

Mother Hub, sortation, destination hub, and delivery hub

Public tracking can show several facility types.

Origin facility

An origin-facility event is stronger evidence that the parcel entered the physical Ekart network.

It does not show every internal movement.

Sortation facility

A sortation event can represent:

• receipt;
• scanning;
• routing;
• consolidation;
• dispatch preparation.

It is not live location.

Mother Hub

A Mother Hub is a major network or sortation node.

received at Mother Hub
→ major Ekart network event recorded
≠ destination city
≠ final delivery hub
≠ parcel is near the recipient
≠ public pickup available

Transit or line-haul hub

A transit hub can process the parcel between origin and destination regions.

The visible place name can be a routing point rather than the consignee’s city.

Destination facility

A destination-facility event means destination-side processing has begun.

It does not automatically mean a Wishmaster has the parcel.

Delivery hub

A delivery-hub event is stronger evidence that the parcel reached a local or regional last-mile facility.

received at delivery hub
≠ loaded on delivery vehicle
≠ Out for Delivery
≠ delivery today
≠ recipient may walk in and collect

Same-city misroute

Current scoped Elite NDR terms describe a same-city address and PIN-code mismatch that can cause movement between delivery hubs while a correction is requested.

A same-city misroute does not by itself prove the parcel is lost.

Other-state misroute

Current scoped terms distinguish another-state address/PIN mismatch and can require RTO plus a fresh forward order rather than a simple interstate correction.

This is an Elite Client workflow, not a universal recipient right.

Events can be delayed, duplicated, or out of order

Possible causes include:

• batch scan upload;
• late facility synchronization;
• route correction;
• duplicate hub feed;
• merchant-system synchronization;
• RTO insertion;
• provider normalization.

Public tracking is not GPS

Even where Ekart uses internal GPS and route systems, the public parcel timeline does not establish:

• live truck location;
• live Wishmaster location;
• facility shelf location;
• continuous chain of custody.

Ekart products and current availability

Ekart operates several materially different service lines.

B2C Smart Express

Current B2C material markets capabilities such as:

• surface and air express;
• same-day and next-day delivery;
• large and oversize parcels;
• documents;
• reverse pickup;
• exchange;
• Open Box Delivery;
• installation and demo;
• refurbishment and value recovery.

The existence of a corporate capability does not prove that it is active for every merchant account or route.

B2B Express, FTL, and PTL

B2B freight can use:

• FTL;
• PTL;
• LTL;
• air or surface;
• commercial freight identifiers;
• a separate LR tracking portal.

Do not apply parcel status rules to freight automatically.

Warehousing and fulfilment

Warehouse operations can include:

• inbound receipt;
• storage;
• inventory;
• quality check;
• picking;
• packing;
• dispatch;
• returns;
• refurbishment;
• liquidation.

A warehouse or fulfilment event is not automatically a consumer delivery event.

4PL

A 4PL product can coordinate several logistics providers and service lines.

It does not prove that Ekart physically performed every stage.

Current official availability conflicts

Current official Ekart sources do not align perfectly:

• B2C pages market air, same-day, next-day, Open Box, and large-parcel capabilities;
• the current Elite FAQ states that some of those products are not active in the reviewed self-serve service and describes a lower current weight scope.

The correct interpretation is:

Ekart corporate capability
≠ every Elite rate card
≠ every merchant account
≠ every route
≠ every currently activated product

Availability can depend on:

• merchant agreement;
• account;
• route;
• PIN code;
• weight;
• parcel dimensions;
• service line;
• current product activation.

No universal delivery estimate

Official product pages can advertise route-specific same-day, next-day, or other commitments.

Do not combine them into one global Ekart ETA.

Out for Delivery

What does Out for Delivery mean?

Out for Delivery
→ local delivery route is planned or active
≠ unconditional same-day delivery

What can happen next?

• Delivered;
• OTP dependency;
• COD dependency;
• customer unavailable;
• no response;
• incomplete address;
• customer rejection;
• Open Delivery demand;
• reschedule;
• route interruption;
• security issue;
• damage;
• RTO decision.

Wishmaster or delivery-task assignment

A delivery task can be allocated before:

• parcel loading;
• vehicle departure;
• arrival at the address;
• phone call;
• completed attempt.

delivery task assigned
≠ Wishmaster physically has parcel
≠ attempt completed

Why can Out for Delivery repeat?

Possible reasons include:

• another attempt;
• route reassignment;
• unresolved NDR;
• capacity;
• late hub dispatch;
• address correction;
• recipient-requested reschedule;
• duplicate provider events.

Repeated Out for Delivery does not automatically prove fraud, loss, or deliberate delay.

Delivery estimate is not a guarantee

Same-day and next-day capabilities exist in scoped products, but the route shown for one parcel depends on its account, PIN code, product, hub, and current operation.

What to do when Out for Delivery does not complete

1. Read the exact event and any attempt reason.
2. Check whether OTP or COD was required.
3. Verify the address and phone stored with the merchant.
4. Check for reschedule, NDR, customer rejection, damage, or RTO.
5. Preserve merchant and marketplace deadlines.
6. Contact the merchant or official Ekart support route controlling the shipment.

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

Failed delivery attempts and NDR

What is NDR?

NDR means Non-Delivery Report in the merchant or account workflow.

Current Elite terms describe reasons such as:

• COD not ready;
• no response;
• incomplete address;
• same-city misroute;
• non-serviceable PIN code;
• customer demands Open Delivery;
• customer rejection;
• other-state misroute;
• security instability;
• damage;
• door locked or customer unavailable;
• reschedule request.

NDR is a carrier-system record

NDR reason recorded
→ operational reason entered
≠ recipient fault independently proved

A no response event does not independently prove:

• the phone call connected;
• the courier reached the exact address;
• nobody was present;
• the recipient ignored the courier.

Scoped last-mile attempt rules

Current Elite terms describe a maximum-attempt model for qualifying undelivered consignments and different branches for:

• customer rejection;
• rescheduling;
• address problems;
• damage;
• security;
• non-serviceable PIN code.

These are registered Client contract rules.

Do not tell every recipient that Ekart will always make the same number of attempts.

Recipient request versus Client instruction

In the current Elite model, the registered merchant or Client can provide alternate instructions based on customer input.

recipient asks to reschedule
→ merchant or Client receives request
→ eligibility checked
→ instruction sent
→ route updated

A recipient request does not prove a new attempt was scheduled.

Incomplete address

Current scoped terms can hold an incomplete-address consignment for a limited period while Client instructions are requested.

That contract-specific hold must not be presented as a universal public promise.

Non-serviceable PIN code

Current scoped terms describe a self-collect branch for a non-serviceable PIN-code exception.

This does not create a general right to collect any Ekart parcel from any hub.

Customer demands Open Delivery

A recipient can want the parcel opened even when the shipment is not eligible for Open Box Delivery.

Current Elite terms contain a separate NDR branch for this situation.

recipient requests open delivery
≠ shipment is eligible

Damage event

A damage event can stop delivery and trigger another operational or RTO branch.

It does not automatically decide the buyer’s refund.

Return to Origin

What does RTO mean?

RTO means Return to Origin.

It can follow:

• exhausted attempts;
• customer rejection;
• incomplete address;
• non-serviceable PIN code;
• same-city or other-state misroute;
• damage;
• security issue;
• merchant instruction;
• another undeliverable outcome.

RTO state model

RTO recommended or requested
→ merchant or Client confirms where required
→ RTO marked
→ parcel dispatched from delivery hub
→ reverse line-haul
→ origin facility
→ seller, Client, or warehouse delivery attempt
→ returned or unclaimed outcome

RTO marked is not physical return completion

RTO marked
≠ parcel already left the hub
≠ seller received it
≠ buyer refund approved

RTO attempts to the merchant

Current Elite terms contain scoped return-attempt rules for delivery back to the Client or specified return location.

Those are merchant-contract rules, not a promise about recipient delivery attempts.

Can RTO be stopped?

No universal RTO-stop right was confirmed.

Possibility can depend on:

• route stage;
• merchant instruction;
• unresolved NDR;
• address correction;
• product;
• marketplace policy;
• operational feasibility.

A request to stop RTO does not prove that the parcel was physically intercepted.

Some returns require a fresh forward shipment

Current scoped terms indicate that certain address-related returns require a new manifest and a new forward shipment.

The old AWB may not resume delivery.

RTO and refund are separate

The merchant or marketplace controls the buyer’s refund or replacement.

Ekart’s RTO record is logistics evidence.

Use Return to Sender for the general state model.

Open Box Delivery

What is Open Box Delivery?

Flipkart’s current official material describes Open Box Delivery for eligible products in select locations. In the scoped process, a Wishmaster opens the package in the recipient’s presence so that the eligible item can be visually inspected before final acceptance.

Current examples include certain:

• mobile phones;
• laptops;
• large appliances.

Eligibility can change.

Open Box is not available for every Ekart parcel

It depends on:

• marketplace;
• merchant;
• seller;
• product;
• location;
• route;
• order eligibility;
• current program rules.

Official sources show different service scopes

Current official evidence supports all of the following:

• Flipkart operates eligible Open Box Delivery;
• Ekart B2C marketing lists Open Box as a carrier capability;
• the current Elite FAQ states that Open Box is not active in the reviewed Elite self-serve service snapshot.

The correct conclusion is:

Ekart can perform Open Box Delivery
≠ every Ekart merchant can buy it
≠ every Elite parcel is eligible
≠ every recipient can demand it

Eligible Open Box flow

A scoped eligible process can include:

Wishmaster arrives
→ eligible order verified
→ package opened in recipient presence
→ visible item and included items inspected
→ recipient accepts or rejects under marketplace rules
→ final OTP or completion step

The exact order of payment, inspection, OTP, and acceptance can depend on the current marketplace instruction and payment type.

What can Open Box help inspect?

It can support checking:

• visible product identity;
• obvious external damage;
• missing visible accessories;
• obvious mismatch.

What Open Box does not necessarily reveal

• internal defect;
• software problem;
• hidden screen defect;
• manufacturing problem;
• long-term performance;
• warranty issue;
• every missing component inside sealed internal packaging.

Ineligible Open Delivery demand

Demanding that an ineligible parcel be opened can trigger an NDR or return branch in the scoped Elite merchant workflow.

Verify eligibility in the actual marketplace order before insisting.

Open Box does not create one universal return rule

Acceptance can affect the current marketplace’s return policy, but it does not support a blanket statement that every later return or warranty claim is impossible.

Use the current order and marketplace terms.

OTP delivery verification

Where OTP can appear

OTP can be used for:

• prepaid delivery verification;
• RTO delivery to a registered Client;
• eligible Flipkart Open Box completion;
• another merchant-specific workflow.

Elite POD definition

Under the current Elite contract, OTP authentication is the scoped POD for prepaid and RTO consignments.

That is a merchant-contract definition, not one universal technical definition for every Ekart parcel.

OTP state model

OTP generated
→ OTP communicated
→ legitimate shipment and handoff verified
→ OTP supplied
→ authentication recorded

What OTP can support

OTP can support evidence that a person with access to the code authorized or completed a scoped handoff.

What OTP does not universally prove

• named buyer personally received it;
• exact physical address;
• correct product;
• complete accessories;
• undamaged condition;
• product functionality;
• no later loss;
• carrier liability;
• refund outcome.

Safe OTP handling

Never:

• enter an OTP in 11Tracking;
• publish it;
• share it only because a caller knows the tracking number;
• share it through an unverified link;
• share it when no authorized person is present to receive the parcel.

Open Box nuance

For an eligible Flipkart Open Box order, current official evidence supports inspection before the final OTP or acceptance step.

The safe guidance is:

Follow the verified order-specific process. For an eligible Open Box order, complete the authorized inspection before the final acceptance credential.

Do not turn this into a generic right to open every Ekart parcel.

OTP does not authenticate a payment request

A real OTP does not prove:

• a personal UPI request is legitimate;
• a caller is the assigned Wishmaster;
• a different parcel is authorized;
• a link is controlled by Ekart or Flipkart.

Cash on Delivery

What does COD mean?

COD means the merchant-arranged amount collected at delivery for a Cash on Delivery consignment.

It is usually the purchase amount, not an independent carrier insurance or customs fee.

Current Elite COD flow

The current Elite contract allows collection of the invoice value through methods such as:

• cash;
• card through POS

under the scoped merchant agreement.

Collected amounts are remitted to the registered Client.

COD and delivery completion

Under the scoped Elite contract, COD delivery is completed after the COD amount is received.

This confirms payment collection in that contract.

It does not prove:

• correct item;
• authentic item;
• complete contents;
• undamaged condition;
• buyer satisfaction.

Ekart does not universally verify contents

Because the reviewed contract uses a said to contain model:

COD paid
≠ Ekart verified product inside
≠ correct item
≠ genuine item
≠ complete item

COD POD in the Elite contract

Current Elite terms define COD remittance to the Client’s account as the scoped POD for COD consignments.

This is an account-side contractual evidence model.

It does not mean a public recipient can view merchant bank-remittance data.

COD not ready

A COD-not-ready reason can produce an NDR and another attempt or RTO branch under the applicable contract.

Do not promise the next attempt universally.

Unordered COD parcels

A real Ekart parcel can still come from:

• mistaken order;
• unauthorized order;
• fraudulent merchant;
• low-quality seller;
• buyer misunderstanding.

Do not pay only because:

• the carrier is real;
• the tracking number is real;
• the name and address are correct;
• the delivery partner has a parcel;
• an OTP exists.

Verify the merchant order independently.

Payment safety

Do not send payment to a personal UPI ID or bank account merely because a caller says the official payment method is unavailable.

Use the verified order and authorized collection method.

Proof of Delivery

What counts as POD in the current Elite contract?

The reviewed Elite Terms of Service define scoped POD as:

• OTP authentication for prepaid and RTO consignments;
• COD remittance for COD consignments.

They also state that digital POD can be downloaded from the registered Client’s account dashboard.

Client access is not recipient access

The Client is the registered merchant or shipping account holder.

digital POD exists
≠ recipient has Elite dashboard access
≠ POD is public
≠ 11Tracking can retrieve it

Other merchants can use other evidence

Flipkart, another merchant, or another product can maintain delivery evidence that differs from the current Elite definition.

No one universal Ekart POD format was confirmed.

What POD can support

Depending on the service, POD can support:

• OTP authentication;
• COD remittance;
• delivery timestamp;
• completion record;
• account-side delivery evidence.

What POD does not universally prove

• named buyer personally received it;
• correct physical address;
• correct product;
• complete contents;
• condition;
• authorized signatory;
• absence of later loss;
• marketplace refund outcome.

Merchant dispute deadlines are not automatically buyer deadlines

Current Elite terms contain short Client dispute and notification periods for some delivery, return, loss, and damage situations.

Those deadlines govern the registered Client contract.

The buyer should follow:

• the deadline in the actual merchant or marketplace order;
• current official support instructions;
• applicable payment or consumer process.

11Tracking cannot retrieve POD

11Tracking and USTracking cannot access:

• Elite Client dashboard;
• OTP records;
• COD remittance;
• merchant dispute records;
• private delivery evidence.

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

Can you collect an Ekart parcel from a hub?

No general public collection right was confirmed

A parcel being visible at a Mother Hub, destination hub, or delivery hub does not create a general right to walk in and collect it.

Scoped self-collect exception

Current Elite NDR terms mention a self-collect option in a specific non-serviceable PIN-code branch while the consignment is held at the delivery hub.

That is:

• exception-specific;
• merchant or account controlled;
• not a general public service;
• not proof that every hub accepts visitors.

Safe self-collection sequence

1. Verify an explicit self-collect instruction.
2. Confirm it through the merchant or official Ekart route.
3. Confirm the exact authorized location.
4. Confirm hours, identity requirements, and release authority.
5. Do not travel to a guessed hub.
6. Do not rely only on a map listing or community post.
7. Never share an OTP before the authorized handoff.

11Tracking cannot provide private hub or driver data

11Tracking cannot identify:

• internal hub address;
• live parcel shelf;
• Wishmaster phone;
• live route;
• vehicle;
• private facility contact.

Why Ekart tracking may not update

A tracking gap does not have one diagnosis.

Possible branches include:

• merchant order exists but no Ekart manifest;
• AWB created but no pickup;
• pickup attempted but goods not handed over;
• first physical scan delayed;
• facility event not synchronized;
• route is in line-haul;
• same-city or interstate misroute;
• destination hub backlog;
• Out for Delivery route did not complete;
• NDR awaits Client response;
• reschedule is pending;
• RTO was marked;
• wrong identifier entered;
• LR ID entered in parcel tracker;
• unsupported product;
• record is old;
• identifier is invalid.

Evidence-first check

1. Confirm parcel tracking number versus merchant order versus LR ID.
2. Identify the last physical event.
3. Identify whether the facility is origin, sortation, destination, or delivery hub.
4. Separate task allocation from an actual attempt.
5. Read any NDR reason without treating it as independent proof of blame.
6. Check whether RTO was marked.
7. Preserve merchant and marketplace deadlines.
8. Contact the actor controlling the current stage.

No universal waiting period

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

Some current Elite contract branches use specific internal hold periods, but those apply only to stated reasons and Client instructions.

Use Tracking Not Updating for the broader escalation model.

Ekart says Delivered, but the parcel is missing

What Delivered confirms

Delivered
→ Ekart or the publishing merchant system recorded completion
≠ named buyer personally received it
≠ correct product, contents, or condition proved

Possible delivery contexts

• named recipient;
• household member;
• building staff;
• authorized person;
• OTP-based handoff;
• COD handoff;
• eligible Open Box process;
• another contracted delivery outcome.

Evidence to preserve

Keep privately:

• exact Ekart event;
• timestamp;
• tracking number;
• merchant order;
• every parcel or piece number;
• OTP context;
• COD context;
• Open Box eligibility;
• support communication;
• available merchant-side POD.

Action sequence

1. Check household members and authorized recipients.
2. Confirm the exact merchant order and Ekart number.
3. Confirm whether the order had several pieces.
4. Do not share a new OTP.
5. Contact the merchant or marketplace immediately.
6. Ask the contract holder to obtain digital POD or open the Ekart dispute.
7. Preserve current marketplace or merchant deadlines.
8. Keep carrier investigation separate from refund or replacement.

Do not diagnose from one record

A disputed delivery can involve:

• alternate recipient;
• wrong address;
• wrong parcel;
• system error;
• unauthorized OTP use;
• theft;
• merchant fraud;
• carrier misconduct;
• another cause.

Public tracking cannot determine which.

Use Delivered but Not Received for the complete recovery sequence.

Reverse pickup, return, exchange, and quality check

Reverse pickup

Ekart markets reverse pickup as a value-added service.

A return route can follow:

merchant or marketplace return authorized
→ reverse AWB
→ pickup booked
→ pickup attempt
→ item accepted
→ return transit
→ seller or warehouse receipt
→ inspection
→ refund or replacement

Smart RVP

Smart RVP can include:

• quality-check return pickup;
• non-quality-check return pickup.

The merchant determines the applicable return criteria.

Pickup quality check does not prove refund

pickup QC passed
≠ seller received item
≠ final warehouse inspection passed
≠ refund approved

Hand-in-hand exchange

An exchange can involve:

• replacement parcel;
• old-item handover;
• item verification;
• separate forward and reverse identifiers.

Preserve both route numbers.

Open Box and return QC are different

• Open Box is a forward-delivery inspection workflow.
• Return QC is a reverse-pickup workflow.

One does not automatically replace the other.

Verify every return pickup

Before handing over an item, verify:

• merchant;
• marketplace;
• item;
• return number;
• pickup purpose;
• label;
• OTP where the legitimate process requires one.

Do not hand over a parcel based only on a generic “Ekart pickup” message.

Return pickup does not prove refund

return authorized
≠ pickup completed

pickup completed
≠ seller received item

seller received
≠ final inspection passed

inspection completed
≠ refund approved

refund approved
≠ refund paid

The merchant or marketplace controls the commercial remedy.

Claims, liability, insurance, and compensation

The most detailed official claim rules reviewed for this page are in the Elite merchant Terms of Service.

They apply to the relationship between Instakart and the registered Client. They are not universal buyer rights.

Who usually controls the carrier claim?

The contractual claimant can be:

• Elite Client;
• merchant;
• shipper;
• marketplace;
• another account holder.

The buyer normally uses:

• merchant support;
• Flipkart or marketplace support;
• refund or replacement process;
• payment remedy where applicable.

Scoped contract values are not universal buyer rules

Current Elite terms contain contract-specific provisions involving:

• invoice-value bands;
• credit notes;
• Certificate of Fact;
• Client insurance;
• lower reverse-pickup limits;
• exclusions for some reverse, liquid, fragile, or other products;
• a scoped definition of when a consignment can be treated as lost.

These provisions must not be converted into public claims that:

• every parcel is insured;
• every buyer receives a fixed amount;
• every shipment has the same liability limit;
• every recipient must wait a fixed number of days;
• every reverse pickup has the same compensation.

A 60-day contract definition is not a buyer waiting rule

The current Elite contract contains a scoped lost-consignment definition tied to the Client relationship.

Do not tell a recipient:

Wait 60 days before acting.

The buyer should preserve the merchant or marketplace deadline from the beginning.

Certificate of Fact

A Certificate of Fact can support the Client’s insurance process in certain scoped higher-value situations.

It is not:

• automatic compensation;
• buyer refund;
• public tracking proof;
• insurance itself.

Claim state model

problem reported
→ shipment and contract identified
→ eligible Client or claimant identified
→ evidence submitted
→ carrier investigation
→ liability decision
→ credit note, Certificate of Fact, or other contract result
→ merchant refund or replacement separately

Ekart does not automatically insure every parcel

The reviewed terms support a model in which the Client may need its own insurance.

Do not publish universal insurance language.

Merchant remedy differs from carrier compensation

Ekart carrier compensation
≠ Flipkart refund
≠ third-party merchant replacement
≠ payment dispute

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

Flipkart order, third-party merchant order, and Ekart inquiry

Flipkart order

For a Flipkart purchase, use Flipkart’s current official order and support flow for:

• cancellation;
• return;
• replacement;
• refund;
• item-not-received dispute;
• Open Box issue;
• seller issue.

Ekart logistics inquiry

The Ekart or Client-side process can investigate:

• pickup;
• facility route;
• attempt;
• NDR;
• POD;
• RTO;
• damage or loss;
• reverse pickup.

The processes are separate

Ekart says Delivered
≠ Flipkart automatically denies remedy

Ekart RTO
≠ Flipkart refund already paid

Ekart credit note to Client
≠ buyer receives that amount directly

Flipkart refund
≠ Ekart admitted liability

Third-party merchant order

When Ekart carries a parcel for another seller or marketplace, contact that merchant.

Do not route every Ekart buyer to Flipkart.

No universal public support number

Use the current official Ekart, Flipkart, or merchant support action instead of a phone number copied from a third-party directory.

Who should you contact?

Privacy and scam safety

Treat tracking numbers as shipment data

An Ekart tracking number can expose:

• route;
• facilities;
• timing;
• delivery outcome;
• RTO;
• return status;
• merchant context.

Do not publish a real number in:

• public post;
• review;
• screenshot;
• page URL;
• metadata;
• unnecessary AI prompt.

Never enter these in a public tracker

• Flipkart login;
• merchant login;
• Elite account credentials;
• phone number;
• full address;
• invoice;
• KYC;
• GST, CIN, or PAN;
• bank details;
• OTP;
• COD payment details;
• LR freight document;
• POD;
• NDR;
• driver details;
• claim evidence;
• return authorization.

Real carrier data does not validate the merchant

real Ekart parcel
≠ legitimate seller
≠ correct product
≠ authorized COD order

Real data does not authenticate a contact

real tracking number
≠ authentic caller

real OTP
≠ authorized request

correct COD amount
≠ official payment destination

Wishmaster label
≠ identity independently verified

Common suspicious situations

• unordered COD parcel;
• request to pay personal UPI;
• OTP requested before authorized handoff;
• fake reschedule fee;
• fake hub-release fee;
• address-update link;
• fake POD download;
• return pickup for the wrong item;
• caller claiming to stop RTO for payment.

Safe verification sequence

1. Open the merchant or marketplace independently.
2. Match the order, seller, amount, and Ekart number.
3. Verify Open Box eligibility.
4. Use the authorized delivery or payment process.
5. Do not provide OTP early.
6. Do not pay an unrelated account.
7. Verify the return item and authorization before handover.
8. Preserve suspicious communication privately.
9. Use Fake Delivery Message for the broader safety process.

Wishmaster identity is not proven by a call alone

A masked number, branded message, uniform, app screenshot, or knowledge of the tracking number does not independently authenticate the person.

Use the order-specific official process.

Frequently asked questions

How do I track an Ekart parcel?

Enter one supported Ekart ecommerce parcel tracking number, AWB, tracking ID, or consignment number.

Can I use my Flipkart order number?

Not automatically. Use the Ekart tracking identifier shown in the shipping details.

Is every Ekart parcel from Flipkart?

No. Ekart also carries parcels for other merchants and ecommerce businesses.

Is Ekart the same as Instakart?

Ekart is the public logistics brand. Current platform and Elite terms identify Instakart Services Private Limited as the operator and contractual service provider in the reviewed context.

What is Elite?

Elite is Ekart’s self-serve merchant shipping platform. Its Client terms are not automatically recipient rights.

What is a Wishmaster?

Wishmaster is a Flipkart/Ekart delivery-partner role. The title does not independently authenticate a caller or determine employment status.

What is an Ekart AWB?

An AWB is a carrier shipment identifier. It can be generated before physical pickup.

What is an LR Shipment ID?

It is a B2B, FTL, PTL, or bulk freight identifier used through a separate official tracking portal.

Can I enter an LR Shipment ID in the parcel form?

No universal support was confirmed. Use the separate official freight portal unless the runtime explicitly maps it.

Does every Ekart tracking number have the same format?

No universal official prefix, suffix, length, or regex was confirmed.

Does Shipment Created mean Ekart has it?

No. It can mean manifest, AWB, or electronic shipment data exists.

Does Pickup Attempted mean picked up?

No. It confirms an attempted collection, not successful handover.

Which event proves Ekart received the parcel?

Picked up, collected, accepted, received at facility, or processed at origin facility is stronger possession evidence.

What is an Ekart Mother Hub?

It is a major sortation or transit node. It does not automatically mean the parcel is close to the recipient.

What is a delivery hub?

It is a local or regional last-mile facility. It does not automatically mean Out for Delivery or public collection.

Does Delivery Hub mean the parcel will arrive today?

No. The parcel still needs route allocation and a final delivery outcome.

What does Out for Delivery mean?

A local delivery route is planned or active. It does not guarantee same-day delivery.

Why is Out for Delivery repeated?

Possible reasons include another attempt, reassignment, unresolved NDR, address correction, capacity, reschedule, or duplicate events.

What does Delivery Unsuccessful mean?

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

Does “No Response” prove the driver called?

No. It is an operational reason code, not independent evidence of the call or visit.

What is NDR?

NDR means Non-Delivery Report. It records a failed-delivery reason and supports merchant or Client instructions.

How many attempts will Ekart make?

No universal attempt count was confirmed. Current official Ekart FAQ and Elite contract material do not fully align, and different products and NDR reasons can use different branches.

Can I reschedule Ekart delivery?

Possibly, but the merchant or marketplace may need to submit the instruction. A request does not prove the route was changed.

Can I correct the address?

Possibly in scoped conditions. Address and PIN-code mismatches can also lead to a hub transfer, RTO, or fresh shipment. Verify through the merchant.

Can I collect the parcel from an Ekart hub?

Not as a general right. A scoped Elite exception supports self-collection for a non-serviceable PIN-code branch, but explicit authorization is required.

What does RTO mean?

RTO means Return to Origin.

Does RTO mean the seller already received it?

No. RTO marking, reverse movement, seller receipt, inspection, and refund are separate.

Can RTO be stopped?

No universal stop right was confirmed. The answer depends on route stage, merchant instruction, product, and operational feasibility.

Does RTO mean my refund is approved?

No. Refund or replacement is controlled by the merchant or marketplace.

What is Open Box Delivery?

It is a scoped marketplace workflow in which an eligible parcel is opened for visible inspection in the recipient’s presence before final acceptance.

Is every Ekart parcel eligible for Open Box Delivery?

No. Eligibility depends on marketplace, product, seller, location, route, and current program rules.

Why does Flipkart offer Open Box while Elite says it is unavailable?

Flipkart marketplace eligibility, Ekart corporate capability, and the current Elite self-serve product are different scopes.

Can I demand that every Ekart parcel be opened?

No. Demanding Open Delivery for an ineligible consignment can produce a failed-delivery or RTO branch.

When should I share the OTP?

Only in the verified order-specific handoff. For an eligible Open Box order, complete the authorized inspection before the final acceptance credential.

Does OTP prove the correct product?

No. It can support a handoff-verification step, not the contents, condition, or functionality.

What is Ekart COD?

Cash on Delivery is merchant-arranged payment collected at delivery.

Can Ekart COD be paid by card?

Current Elite terms support cash or card/POS in the scoped Client contract. The available method can depend on the route.

Does COD prove Ekart checked the item inside?

No. The reviewed contract uses a said to contain model and does not establish carrier verification of contents.

What is Ekart POD?

POD is Proof of Delivery. Under the current Elite contract, it can be OTP authentication for prepaid/RTO consignments or COD remittance for COD consignments.

Can every recipient download Ekart POD?

No. The current Elite digital POD is described as available in the registered Client’s account.

Does POD prove correct delivery?

Not universally. It does not automatically prove the named buyer, correct item, complete contents, condition, or refund outcome.

What is reverse pickup?

It is the carrier collection stage of an authorized return.

What is Smart RVP?

It is an Ekart reverse-pickup model that can include quality-check or non-quality-check return pickup.

Does return pickup mean my refund is approved?

No. Pickup, seller receipt, inspection, refund approval, and payment are separate.

Who can file an Ekart carrier claim?

The registered merchant, shipper, marketplace, Elite Client, or account holder commonly controls the carrier contract. The buyer normally uses the merchant or marketplace remedy.

Does Ekart insure every parcel?

No universal insurance promise was confirmed.

Is a fixed rupee amount the universal Ekart compensation?

No. Current liability amounts are scoped Elite Client contract terms, not universal buyer compensation.

Must I wait 60 days before reporting a lost package?

No. A scoped Elite contract definition does not replace merchant, marketplace, or payment deadlines.

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

Preserve the tracking record, confirm every piece, contact the merchant or marketplace immediately, ask the contract holder to obtain POD or open the carrier dispute, and preserve refund deadlines.

Can 11Tracking contact the Wishmaster?

No. It cannot contact the driver, merchant, Flipkart, Elite Client, or Ekart.

Can USTracking stop RTO, use OTP, collect COD, or retrieve POD?

No. It cannot act on the parcel, use credentials, handle payment, access private proof, file claims, or decide refunds.

Can a real Ekart parcel be part of a scam?

Yes. A real carrier and real tracking number do not validate the merchant, product, COD order, caller, or payment destination.

Use USTracking as a tracking companion

After identifying the correct parcel number and current route stage, USTracking may help you:

• save a supported Ekart ecommerce parcel tracking number;
• organize public route events;
• preserve verified parcel, piece, RTO, and reverse-pickup numbers;
• monitor later public updates;
• compare public hub, attempt, delivery, and return events;
• receive notifications.

USTracking cannot:

• access Flipkart, merchant, Elite, Wishmaster, hub, warehouse, POD, NDR, payment, or claims accounts;
• track by phone, address, OTP, COD reference, LR freight document, claim case, or return authorization;
• determine a universal number format;
• identify a live driver or vehicle;
• locate a parcel inside a hub;
• contact Ekart or a Wishmaster;
• arrange hub collection;
• reschedule;
• change an address;
• stop RTO;
• open a parcel;
• use an OTP;
• collect COD;
• retrieve protected POD;
• file a claim;
• recover the parcel;
• decide a refund or replacement;
• guarantee tracking completeness, pickup, delivery, RTO interception, compensation, or arrival time.

Related guides

• Package Tracking Help Center
• How Package Tracking Works
• Label Created
• Carrier Received Package
• In Transit
• Out for Delivery
• Out for Delivery but Not Delivered
• Delivery Attempted
• Delivered
• Delivered but Not Received
• Return to Sender
• Tracking Not Updating
• Tracking Number Not Found
• Wrong Address or Address Information Required
• Package Moving Away or Wrong City
• Package Damaged or Contents Missing
• Change, Reroute, or Hold a Package
• Proof of Delivery, Photo, and Signature
• Package Claim Guide
• Who to Contact About a Package
• Find the Last-Mile Carrier
• Fake Delivery Message

Scope, evidence, and limitations

This page is an English-language guide to Ekart ecommerce parcel tracking, parcel identifiers, merchant orders, LR freight identifiers, manifests, AWBs, physical pickup, facilities, Mother Hubs, delivery hubs, Out for Delivery, NDR, RTO, Open Box Delivery, OTP, COD, POD, reverse pickup, merchant claims, marketplace remedies, and responsible-party routing.

It is based primarily on current official Ekart, Instakart, Elite, Flipkart, and official field-app material reviewed on July 25, 2026.

Important limitations:

• The runtime provider, aliases, accepted parcel identifiers, merchant-order behavior, LR Shipment ID behavior, multi-piece fields, RTO fields, and sensitive OTP/COD/POD/NDR fields must be verified during implementation.
• No universal Ekart parcel-number format was confirmed.
• Generic Flipkart or merchant order support was not confirmed.
• Ecommerce parcel and B2B freight tracking are separate official workflows.
• No universal pickup-attempt or delivery-attempt count was confirmed.
• Current official Ekart FAQ, product, and contract pages contain material differences in product availability and attempt rules.
• No universal air, same-day, next-day, Open Box, OTP, COD, POD, hub self-collection, rescheduling, address-change, RTO-stop, claim, insurance, compensation, or return rule was confirmed.
• Elite contract rules govern registered Clients and do not automatically create recipient rights.
• Flipkart Open Box, return, refund, and support rules apply to eligible Flipkart orders, not every Ekart parcel.
• Public tracking can be delayed, incomplete, normalized, corrected, duplicated, or out of order.
• 11Tracking does not diagnose a specific shipment and cannot act on the parcel.

Last reviewed: July 25, 2026 Review due: October 23, 2026 Research decision: Ready to draft with explicit parcel-versus-LR identifier, manifest-versus-possession, Flipkart-versus-third-party, product-availability, OFD/NDR/RTO, OTP/COD/Open-Box/POD, return, claim, privacy, and runtime limitations