Where do I find my XpressBees tracking number?
An XpressBees tracking number reaches four buyer-visible surfaces, and they do not fill in at the same moment: the seller's dispatch email or SMS, the shipment details panel inside the marketplace order, the shipping label taped to the parcel, and the courier or aggregator panel used by whoever booked the consignment. Which route is fastest depends on what you already have open. A buyer looking at an order screen should open the individual shipment and read the field labelled AWB, tracking ID or waybill number. A recipient holding a parcel should ignore the screens entirely and read the string printed with the barcode on the label.
The order in which each surface receives the number
The 4 surfaces populate in a fixed sequence, and up to 1 full business day can separate the first of them from the last. Nothing about that sequence is visible to a buyer, which is why a field that is simply empty looks like a field that is hidden.
The number lands first in whichever system generated the label, either an XpressBees account or the shipping software the seller books through. It reaches the marketplace second, pushed over an integration within minutes of label generation, and it sits in the order record from that moment whether or not the buyer has been told.
The buyer notification is third, fired on the dispatch event rather than on label creation, so hours can pass between the number sitting in the order record and an email announcing it. The printed label is last in practical terms, because the only copy the buyer can read arrives with the parcel at the door.
The consequence is worth stating plainly. Checking the order screen 10 minutes after placing the order will find no tracking field at all, and checking it the following morning usually will. That is the propagation sequence rather than a fault, and refreshing the page does not shorten it.
Every surface that carries an XpressBees tracking number
Seven surfaces can hold the number, and only 3 of them are visible to a buyer before delivery day. The table gives the label to look for on each one and the string most often grabbed by mistake instead.
Surface | What to look for | Who can see it | When it appears | The string sitting next to it |
|---|---|---|---|---|
Seller or marketplace dispatch email | A courier name followed by a tracking ID, or a track link containing the number | The buyer, at the address used at checkout | On the dispatch event, hours after the label is generated | The order number, usually in the subject line |
Dispatch SMS | The number itself, or a shortened tracking link | The buyer, if a mobile number was captured | The same event as the email, sometimes minutes apart | The alphanumeric sender header, which is not a tracking number |
Marketplace order detail, shipment details panel | A field labelled AWB, tracking ID or waybill number | The buyer, signed in to the account that placed the order | As soon as the shipment is booked | The order ID at the top of the same screen |
The shipping label on the parcel | The human-readable string printed with the carrier barcode | Anyone holding the parcel, including a recipient who ordered nothing | At the door, on delivery day | The destination pin code, the route or sort code, and the seller's order reference in its own box |
The tax invoice inside the parcel | A transport document or AWB row, where the seller populates one | The recipient, after opening the parcel | At the door | The invoice number and the seller's GSTIN |
Seller panel, manifest and bulk label file | The AWB column of the order list, and one line per consignment on the manifest | The seller or supplier only | At label generation, before the parcel exists as a parcel | The aggregator's own shipment reference |
Return or exchange confirmation | A pickup reference presented as a return AWB | The buyer who raised the return | When the reverse pickup is scheduled | The forward number from the original delivery |
Every one of the 7 prints the tracking number within a line or two of something that is not it, which is the second problem this page has to solve.
The dispatch email and SMS, and why one of them may never arrive
Two channels push the number to you rather than waiting for you to look, and they fail for completely different reasons. The email fails by being filed somewhere you did not check. The SMS fails by not being sent at all.
Search the mailbox for the courier name rather than the seller's. The word XpressBees appears in the body of a dispatch notification even when the sender is the marketplace, so it is a sharper search term than a brand that also sends promotions and invoices. If that returns nothing, repeat the search against the order number, which is the one string guaranteed to appear in both the order confirmation and the dispatch notification.
Many dispatch emails carry a track button instead of a visible number. The number is still there, inside the link target, and copying the link address rather than clicking it exposes it. That matters when the link opens a tracking page holding no scans yet, because the string itself is what you need in order to look it up anywhere else later.
The SMS is the weaker of the 2 channels in India, because commercial messaging runs as a registered-sender regime rather than an open one. Business messages are sent under registered alphanumeric headers rather than from an ordinary phone number, and the framework governing them is the Telecom Commercial Communications Customer Preference Regulations, notified on 19 July 2018 and amended most recently by the Second Amendment Regulations released on 12 February 2025 (Telecom Regulatory Authority of India, regulations register, accessed July 2026).
Two practical effects follow. A dispatch SMS arrives from a short alphanumeric header, so a handset files it wherever it files unknown business senders rather than into a thread with the seller. And where a marketplace masks the buyer's mobile number, the courier has no route to the real handset, which leaves the order screen and the label as the only surfaces that will ever show that buyer the number.
The shipment details panel inside the marketplace order
Every major Indian marketplace stores the courier's number one level deeper than the order list, so reaching it takes 3 steps rather than one. The order list shows a status word and a date; the number lives inside the individual shipment.
The path is the same across platforms even where the wording differs: open the account's order history, open the specific item rather than the order as a whole, then open the panel called track, shipment details or delivery details. That panel is where a carrier name and a carrier number appear together. An order split across 2 or more sellers has one such panel per shipment, each with its own number, which is why a buyer who found a number for one item and not for another has not found a bug.
Where the marketplace arranged the delivery itself, the tracking presented in that panel belongs to the platform. Amazon India describes order tracking as a property of the fulfilment programme rather than of any courier:
"Easy Ship allows your customers to track their orders and delivery date."
Amazon Seller Services India, Easy Ship programme page, accessed July 2026
Where the seller arranged it, the same panel shows a courier name and a string the seller entered against the order. On a Meesho order the courier and its number appear only once the shipment has been booked, so an order placed the same afternoon shows a status line and nothing else. If no account was ever created, because the purchase went through guest checkout, the order confirmation email carries an order lookup link that opens the same panel without a password.
Reading the number off the label on the parcel
The label is the only one of the 7 surfaces that travels with the goods, which makes it the answer for a recipient who has no account, no email and no idea who ordered the parcel. It is also the only surface that still holds the number after a marketplace order has been archived.
Carrier labels print the human-readable number immediately with the barcode that encodes it, so the string to copy is the one directly above or below the black bar block rather than any of the larger type around it. The largest text on an Indian parcel label is normally the destination pin code and the route or sort code, because those are printed for staff working a sortation belt rather than for the addressee.
The seller's own order reference sits in a separate box, often near the address block or alongside a small second barcode. Two barcodes on one label is the normal case rather than the exception, and choosing between them is the commonest reason a correctly copied string returns nothing. Why the two behave differently is set out in full on the difference between an AWB number and a tracking ID.
Many ecommerce parcels carry the label in a clear pouch with the tax invoice folded behind it. The invoice is not a substitute: its own invoice number is an accounting reference that belongs to no carrier system.
One habit removes most of the problem. Photograph the label before the packaging is thrown out, because a return raised a week later, a warranty claim, or a dispute over an item marked delivered will each ask for the number, and by then the box is gone. India Post underlines how loosely the field is named by accepting several different labels for the same idea on one lookup form:
"Consignment ID", "Article Number", "Reference Number"
India Post, track and trace services, accessed July 2026
The lesson transfers directly to a private courier. Operators name the same field differently, so the durable instruction is to take the string printed with the barcode, whatever the box above it happens to be called.
The order shows a courier name but no number
A named courier with an empty tracking field is the commonest failure state, and it usually resolves within 1 business day. Four situations produce it, and they can be told apart from the order screen itself.
The allocation is recorded but the label has not been pushed back. The platform knows which carrier will collect before the carrier's number has been written into the order. The courier name appears first, the number follows, and the gap is measured in hours.
The number belongs to a sibling shipment. On a split order the panel you opened may be the item that has not shipped yet. Open each item in the order rather than the order header, because a 2 item order has 2 panels and only one of them may be populated.
The seller confirmed dispatch without entering the number. Where the seller books the transport, the tracking field is filled by the seller rather than by the platform, so a seller who marked an order shipped and skipped the field leaves a courier name with nothing behind it. This is the one case that does not resolve by waiting.
The platform names the carrier but does not expose the carrier's own reference. Some order screens show who is carrying the parcel while keeping tracking inside the platform's own timeline. Which platforms behave that way is covered on whether XpressBees delivers for Flipkart, Amazon and Meesho.
Allow 1 full business day from the dispatch notification before treating an empty field as an error, then raise it with whoever sold the item rather than with the carrier, since the seller is the party who can read the number straight out of its own panel.
When the marketplace shows only its own reference
Some orders never expose a carrier number to the buyer at all, and no amount of searching the account will produce one. The platform arranged the delivery through logistics it operates itself, so the reference on screen is a platform reference and the timeline beside it is a platform timeline.
The reach of those in-house networks is why this is common rather than exceptional. Amazon India's seller-facing material presents tracking as an attribute of the platform-operated route, listing among its advantages the "availability of order tracking for customers with assured delivery date" (Amazon Seller Services India, shipping and fulfilment overview, accessed July 2026), and the pickup network behind that route covers more than 99 percent of serviceable pin codes. A buyer on it is not missing a courier number. There is no third-party courier number attached to the shipment to miss.
Three things still work in that situation. The platform's own timeline is authoritative for the parcel and is written from the same physical scans. The label at the door carries whatever number the carrier that actually moved it issued, so delivery day is the point at which a carrier reference becomes readable. And the seller can be asked directly, because whoever handed the consignment over holds the number regardless of what the buyer's screen shows.
A string that returns nothing on a courier tracker but resolves inside the marketplace app is not a broken tracking number. It is a reference belonging to a system that is not the carrier's, and a general account of what a tracking number is covers why 1 string works on a single lookup and nowhere else.
Finding the number in a seller panel, a manifest or a bulk label file
A seller holds the number before the buyer does, in at least 4 places inside their own systems, and those places do not all agree at every moment. Knowing which one is definitive matters when a buyer asks and the order screen looks wrong.
The order list in the courier account or the shipping aggregator carries an AWB column, filterable by date and exportable to CSV, and it is the fastest way to pull numbers for a range of orders at once. The bulk label file is the second place: labels are generated as a single PDF covering the whole batch, so every number in that batch stays readable from the file even when the panel is unavailable.
The pickup manifest is the definitive record. It lists 1 line per consignment, it is produced at handover, and the rider signs it, which makes it the document that establishes which numbers physically left the premises on a given day. An order that appears in the panel but on no manifest was never collected, and that is a different problem from a missing number.
The fourth place is the settlement paperwork. Cash on delivery remittance statements and carrier invoices reference consignments by their AWB, so a number that has disappeared from an archived order can usually be recovered from a monthly statement months afterwards. For a seller that is the practical answer to a buyer asking about a shipment from last quarter.
One caution for sellers reading a number back to a buyer. Take it from the manifest or the label file rather than retyping it off a screen, because a single transposed character produces exactly the same blank result as a wrong number and is far harder to diagnose from the buyer's side.
The recipient who never got an email at all
Four situations leave someone holding a parcel with no notification behind it, and none of them is fixed by searching harder. In each case the notification went somewhere, just not to the person holding the box.
The first is a gift or a household order, where the buyer's account holds every screen described above and the recipient holds none of them. The second is guest checkout with a mistyped address, which produces an order that exists and a mailbox that will never receive anything about it. The third is a drop-shipped order, where the storefront that took the payment did not generate the label, so the notification is issued on a schedule the storefront does not control. The fourth is an office or apartment building delivery, where the notification reached the buyer and the parcel reached a mailroom.
Three retrieval routes stay open. Ask whoever placed the order to open the shipment details panel, which takes them the 3 steps described above. Wait for the delivery attempt itself, because the rider's call or message is tied to the consignment and the label at the door carries the number in printed form. And where a delivery was attempted and failed, the attempt notification is the one message that goes to the delivery address rather than to the billing address.
If the parcel is already in hand, none of this is needed. The label answers the question in 1 step, and the account screens are only a way of learning the number before the parcel arrives rather than after.
When two surfaces show different strings
Across the 6 surfaces a buyer or seller is likely to read, the tracking number is always printed close to something that is not it, and separating them is positional rather than a matter of inspecting the characters. The table sets out what sits alongside the number on each surface and how to tell which is which without guessing.
Surface | The other string printed alongside | How to tell them apart there |
|---|---|---|
Dispatch email | The order number, normally in the subject line and the header block | The tracking number sits in the body beside the courier name and the track link, never in the subject |
Marketplace order detail | The order ID, printed at the top of the screen | The carrier number is one level deeper, inside the shipment panel, under a label naming AWB or tracking ID |
Shipping label | The seller's order reference in its own box, plus the route or sort code | The carrier number is the string printed with the main barcode; the sort code is printed for sorters and is much shorter |
Tax invoice in the parcel | The invoice number and the seller's GSTIN | An invoice number appears on a document, never underneath a scanning barcode |
Return or exchange confirmation | The forward number from the original delivery | The reverse number is shown against the pickup, and it reports the return leg only |
Seller or aggregator panel | The aggregator's internal shipment reference | The AWB column names the carrier; the internal reference names the software |
The rule the table encodes is that field labels are more reliable than the look of a string. Two numbers of similar length sitting a centimetre apart on a label belong to two different systems, and reading the box they sit in is faster than judging by their shape.
What to do once you have the number
A number taken from any of these 7 surfaces is the same number, so the surface it came from does not change what it will do. Copy it without spaces, check it once against the source, and paste it into the tracker on this page to pull the carrier's scan history into a single timeline.
If it returns a booking record and no movement, that is normal for the first business day after the label was generated and is not a sign the number was read from the wrong place. If it returns nothing at all, go back one surface: the string printed on the label is the one the carrier's own systems wrote, and it outranks anything retyped into an order screen.