What is the difference between an AWB number and a tracking ID on XpressBees?
On XpressBees the AWB number and the tracking ID are the same number. One consignment gets one Air Waybill number when its label is generated, and every screen that says "tracking ID", "AWB" or "waybill number" is pointing at that single string. The difference that actually produces a blank tracking result is a different one: between the carrier's AWB and the marketplace's own order ID, which sits in the same order screen, looks equally official, and resolves on a completely different page. An Indian ecommerce parcel routinely carries three or four identifiers issued by three different parties, and only one of them returns carrier scans.
Who issues each number, and at which moment
Three separate systems mint a number at three different moments in the life of one order, and none of them can read the others' identifiers. The sequence in which they are created is what makes them easy to mix up, because the buyer only ever sees them together, side by side, after the fact.
The marketplace issues the order ID first, at checkout. It exists before any carrier has been chosen, before a warehouse has picked the item, and often before the seller has seen the order. It identifies a commercial transaction rather than a physical parcel, which is why it survives cancellation, refund and reorder while nothing ever moves.
The marketplace issues a sub-order or item reference second, when an order containing 2 or more items is split across sellers, warehouses or dispatch dates. Each fragment becomes a separately shipped consignment, and each fragment gets its own carrier booking later.
The carrier's number is issued last, when the shipping label is generated. That happens either inside XpressBees systems or inside the seller's shipping software, which draws the number from a block XpressBees has allocated to it. This is why a label can exist hours or days before a parcel does: the AWB is created at booking, not at pickup, and until a rider scans the barcode the number returns a booking record with no movement behind it.
On Amazon India's Self Ship programme the transport arrangement belongs to the seller rather than to the marketplace, and Amazon's seller documentation states that "you will deliver your products to the customers using your delivery associates/a third party carrier" (Amazon Seller Services India, shipping and fulfilment overview, accessed July 2026). The consequence for identifiers is direct: the number displayed against that order was minted by the courier, not by the marketplace, so the platform can show it but cannot explain it. The separate question of which marketplaces XpressBees delivers for is answered on its own page.
The numbers on one XpressBees parcel, and what each one opens
A single delivered parcel leaves behind up to 5 distinct references, and they are not interchangeable in either direction. The table sets out who mints each one, the moment it comes into existence, and the only lookup that will accept it.
Identifier | Issued by | Created at | Where it appears | What it resolves |
|---|---|---|---|---|
Order ID | The marketplace or online store | Checkout, before any carrier is involved | Order confirmation email and the order list in the account | The order page in the buyer's account, and seller support. No carrier scans |
Sub-order or item reference | The marketplace | When an order of 2 or more items is split for dispatch | Under the individual item inside the order | The status line for that one item, not for the whole order |
AWB number, also labelled tracking ID | XpressBees, or seller shipping software drawing on an XpressBees number block | Label generation, which can precede pickup by a full business day | Under the barcode on the label, and in the order field labelled AWB, tracking ID or waybill number | Carrier scan history on the XpressBees tracker and on universal trackers |
Return AWB | XpressBees | When a return or exchange pickup is scheduled, usually 1 to 2 days before collection | The return confirmation in the marketplace app | The reverse leg only. It shows nothing about the original delivery |
Tax invoice number | The seller | Invoicing, at or just before dispatch | The invoice inside the parcel and the downloadable invoice file | Accounting and warranty claims. It is not a tracking reference at all |
The rule that falls out of the table is that the AWB is the only one of the 5 that a carrier system has ever seen. Everything else was minted by a party that does not run vehicles.
Why a parcel that never flies carries an air waybill number
The Air Waybill is an air cargo document, and the name reached Indian road parcels by inheritance rather than by description. In its original sense the AWB is the legal instrument that governs a shipment carried by an airline, and the International Air Transport Association defines it in exactly those terms:
"The Air Waybill (AWB) is a critical air cargo document that constitutes the contract of carriage between the 'shipper' and the 'carrier' (airline)."
International Air Transport Association, Electronic Air Waybill programme, accessed July 2026
Express couriers borrowed the term for the consignment note they raise against every shipment regardless of mode, and it stuck. XpressBees issues 1 AWB per consignment across services that have nothing to do with aviation, including a hyperlocal arm that moves parcels inside a single city by bike or van, often within hours. A number labelled AWB therefore says nothing about how the parcel travels, only that a carrier has accepted it and opened a record against it.
That has one practical consequence worth holding on to. Because the AWB is the consignment note, it comes into existence when the carrier accepts the booking, not when it takes possession. A newly issued AWB with no scans behind it is a normal state that can last a full business day, and it is the most common reason a perfectly correct number looks broken.
How a standardised identifier differs from a courier's own number
Two identifier schemes in logistics are genuinely global, and a domestic courier AWB is neither of them. The Universal Postal Union maintains the S10 identifier carried by international postal items, specified tightly enough that any operator can validate a number without contacting the sender:
"This tool checks the validity of an S10, 13-character identifier by calculating the check digit in character position 11."
Universal Postal Union, technical standards, accessed July 2026
The UPU also publishes separate identification standards for each layer of a postal movement, covering "postal consignments, postal despatches, postal receptacles, postal items" as 4 distinct things needing distinct codes. That is the ecommerce buyer's problem stated formally: an order, a consignment and an item are different objects, and giving all of them one shared number was never available as an option.
A domestic courier AWB sits outside both schemes. It is proprietary to the carrier that issued it, no cross-carrier check digit rule applies to it, and no registry maps a number back to the company that owns it. That is why a string returning a full scan history on one carrier's tracker returns nothing on another's, and why a universal tracker has to work out the carrier before it can ask the right system anything.
Which number works on which tracking page
Only 1 of the identifiers attached to an order will produce carrier scan events, and pasting any of the others returns an empty result rather than an error that explains itself. Each lookup is built against a single issuer's database and has no visibility into the others.
The carrier tracker, whether the XpressBees page or a universal tracker, is built on the AWB. It reads the scan log written by hubs and riders, and holds no record of the marketplace order that caused the shipment. The marketplace order page is built on the order ID, shows the commercial state of the purchase, and mirrors carrier scans only as far as the marketplace has ingested them.
The reliable way to choose the right string is to read the field label rather than the number's shape. An order screen labels the carrier number "AWB", "tracking ID" or "waybill number", and labels the other one "order ID" or "order number". On the physical label the carrier's barcode sits above the seller's order reference, and the 2 numbers are printed close enough together that reading the wrong one is the usual mistake. A fuller walkthrough of where the tracking number appears covers each surface in turn.
On a Meesho order the courier and its AWB become visible only once the shipment has been booked, so an order placed minutes earlier shows an order ID and nothing else. That gap is not a fault in the tracking. No carrier has been assigned yet, and there is genuinely no AWB in existence to display.
Why one order can end up with more than one AWB
A single order produces 2 or more AWBs whenever the parcel count changes, which happens in four recognisable situations. Each new consignment is a new booking, so each one carries its own number and its own independent scan log.
Split dispatch. An order of 2 or more items sourced from different sellers or warehouses ships as separate consignments. Two AWBs, two delivery dates, one order ID covering both.
Returns and exchanges. A return pickup is booked as a fresh consignment travelling in the opposite direction, and XpressBees normally schedules the rider within 1 to 2 days of the request. The reverse AWB shows statuses such as "Out for Pickup" and reveals nothing about the forward leg.
Return to origin. When delivery fails after repeated attempts, the parcel is sent back under an "RTO Initiated" status on the original AWB rather than under a new number. The same string keeps updating, which is why an AWB can show fresh movement days after the last failed attempt.
Cross-border handoff. On international movements the consignment passes to a partner carrier or the destination postal operator once it leaves India, and the final-mile number is issued by that operator instead. The original AWB stops updating at the handover point.
What an AWB number does not tell you
An AWB identifies a consignment and settles nothing else about it. It carries no information about who is answerable for the order, which is a separate relationship entirely: the sale contract sits between the buyer, the seller and the marketplace, so refunds, replacements and wrong-item claims are resolved there even when every scan on the timeline was written by the carrier.
It is also not a delivery forecast. Transit scans on intercity lanes refresh roughly every 24 to 48 hours, so a status that has not moved since yesterday describes the scanning interval rather than the parcel's progress. Standard XpressBees B2C delivery runs 2 to 5 business days across a network of more than 20,000 pin codes, and only an "Out for Delivery" scan indicates an attempt on the current day.
Finally, the number does not identify the marketplace the item was bought from. AWBs are issued per consignment by the carrier, so 2 parcels bought on entirely different platforms can carry numbers of identical structure. Understanding what a tracking number is in general terms is the fastest way to stop reading meaning into the string itself.
When a number returns nothing, and who to contact
Three thresholds separate a normal scan gap from a case worth raising, and all of them are measured from the last event rather than from the order date. Checking the number itself comes first, because a mistyped string or one copied from the wrong field accounts for a large share of blank results.
Allow 1 full business day after a label is created for the first pickup scan. A booked AWB with no movement usually means the parcel has not been collected yet, not that the number is wrong. Allow 2 to 3 days between scans on an intercity leg, where the parcel moves between hubs without a customer-visible event. Treat a status frozen for more than 5 to 7 days, or a "Delivery Attempted" that repeats without contact, as a case to open rather than to wait out.
Who to approach follows from who booked the shipment. On a marketplace order the booking party is the marketplace or the seller, so their support desk is the one that can raise a formal query against the AWB, and the AWB is the reference they will ask for. Approach the carrier directly only for matters it alone controls: a delivery slot, an address correction on a live consignment, or a reattempt after a failed delivery. For a refund, a missing return pickup, or an item marked delivered but not received, open the case with the marketplace and supply the AWB as evidence.
Identifiers an XpressBees AWB gets confused with
At least 6 other numbers circulate around the same parcel, and 3 of them belong to systems that run their own tracking pages. The table separates them by the system that owns the number, which is what decides whether a carrier tracker can do anything with it at all.
Identifier | System it belongs to | What it identifies | Accepted by an XpressBees tracker |
|---|---|---|---|
IATA air waybill number | Air cargo, under the IATA air waybill scheme | An air cargo contract of carriage between shipper and airline | No. A different document type that shares the name |
UPU S10 item identifier | International post | One postal item, as a standardised 13-character code | No. It resolves on postal operator trackers |
Consignment ID or article number | India Post track and trace | A domestic postal consignment, including the remote pin codes private carriers do not serve | No. It belongs to the postal network |
Marketplace order ID | The marketplace | A commercial transaction, created before any carrier booking | No. It has never entered a carrier system |
Aggregator shipment reference | Shipping software used by the seller | The booking record inside the seller's own shipping platform | No, although the same platform also holds the carrier AWB |
Tax invoice number | The seller's accounting system | The billing document for the sale | No. It is a financial reference |
India Post runs its own lookup with fields labelled "Consignment ID" and "Article Number" (India Post, track and trace services, accessed July 2026), a useful reminder that operators name the same idea differently while meaning one thing: the number the carrier itself assigned. The label above the box is a more reliable guide than the digits inside it.
How to read both timelines instead of the last line
A parcel with 4 identifiers has 2 timelines, and reading only one of them produces the impression that tracking has stopped. The marketplace timeline records commercial events such as order confirmed, packed and dispatched. The carrier timeline records physical events such as picked up, reached hub and out for delivery, and it is written by barcode scans rather than by status updates.
The two run at different speeds. A marketplace can mark an order dispatched the moment a label is generated, while the carrier record stays at booking level until a rider physically collects the parcel, a gap that routinely reaches a full business day. Comparing them side by side locates the parcel: a dispatched order with no pickup scan is still sitting with the seller, while a picked-up consignment with no hub scan for 48 hours is moving between facilities.
Paste the AWB from the label or from the order's shipment details into the tracker on this page to pull the carrier's scan history into a single timeline.