Does XpressBees deliver for Flipkart, Amazon, and Meesho?
XpressBees delivers for Amazon India and Meesho, and only rarely for Flipkart, because Flipkart hands almost every marketplace order to its own logistics arm, Ekart. The split is not about carrier quality. It is about who owns the decision: on Flipkart the marketplace controls the last mile outright, on Amazon India the seller's fulfilment programme decides, and on Meesho the platform allocates the order to a partner carrier the supplier never picks. The same seller can ship half its catalogue with XpressBees on one platform and never once encounter it on another.
Who owns the courier decision on each platform
Indian marketplaces run three distinct logistics models, and each one puts the carrier decision in a different pair of hands. Which model an order falls under is the single fact that determines whether an XpressBees rider will be the one at the door.
The first model is marketplace-operated logistics. The platform runs its own pickup, sortation and last-mile network, the seller has no carrier choice, and a third-party courier appears only where the platform's own network does not reach. Flipkart works this way through Ekart, and Amazon India works this way through Amazon Logistics on its Fulfilment by Amazon and Easy Ship programmes, a network Amazon puts at 99.9 percent of the country's serviceable pin codes.
The second model is a marketplace-brokered carrier panel. The platform still arranges the shipment, but it buys capacity from several external logistics companies and assigns each order to one of them by algorithm. Meesho operates this way, and it is the model under which XpressBees carries the largest share of its marketplace volume.
The third model is seller-selected logistics. The seller books the courier itself, either directly through a carrier account or through a shipping aggregator, and the marketplace only records the resulting tracking number. Amazon India's Self Ship programme and every independent Shopify or WooCommerce store fall here, and this is where a seller can choose XpressBees outright.
Marketplace by marketplace, and the programme that decides it
Across the four platforms buyers ask about most, XpressBees appears on two of them as a routine carrier and on the other two only at the edges. The table maps each programme to the party that arranges the delivery and to what the buyer actually sees in the order screen.
Platform and programme | Who arranges the delivery | Where XpressBees can appear | What the buyer sees |
|---|---|---|---|
Flipkart, Flipkart Fulfilment and seller-fulfilled | Ekart, the Flipkart group's in-house logistics arm | Rare, and normally on lanes or pin codes outside Ekart's own coverage | Tracking stays inside the Flipkart order page, usually with no external courier named |
Amazon India, Fulfilment by Amazon | Amazon, from its own fulfilment centres | Not used; Amazon Logistics and its contracted delivery service partners carry it | An Amazon tracking ID beginning with a letter block, not a courier AWB |
Amazon India, Easy Ship | Amazon Logistics, which collects from the seller's address | Not used on the Amazon leg | Amazon-branded tracking covering more than 99 percent of serviceable pin codes |
Amazon India, Self Ship | The seller, using its own staff or a third-party carrier | Common; the seller books XpressBees directly or through an aggregator | A 14 to 15 character XpressBees AWB pasted into the order's shipment details |
Meesho | Meesho, which allocates the order to a partner carrier or to its own Valmo network | Common, alongside other national and regional partners | A named courier and AWB on the Meesho order tracking screen |
Myntra | Flipkart group logistics for most inventory | Occasional, on third-party seller consignments | In-app tracking, with the courier named only on some shipments |
Independent D2C store | The brand, usually through a shipping aggregator | Common; XpressBees is one of the standard panel options | An XpressBees tracking link sent by email or SMS |
Flipkart routes almost everything through Ekart
Flipkart is the one platform of the three where the honest answer is mostly no, because Ekart carries the overwhelming majority of Flipkart marketplace orders end to end. Sellers in standard categories do not select a courier at all: Flipkart schedules the pickup, moves the parcel through its own sortation network, and delivers it with its own last-mile staff.
The scale of that in-house network is why there is little room for an external carrier. Flipkart's own newsroom put a number on the quick-commerce side of it in mid-2026:
"1,000 Micro Fulfilment Centers across 130+ cities and 8,000+ PIN codes."
Flipkart Stories, "1,000 Micro Fulfilment Centers in 2 years: The Flipkart Minutes Story", 26 June 2026
Two situations still produce a non-Ekart label on a Flipkart parcel. The first is coverage: where Ekart does not serve a destination pin code directly, the leg can be handed to a partner network, which is also why Flipkart shows "not deliverable at your location" on some addresses while a rival platform accepts the same address. The second is category: bulky goods, installation-linked appliances and a handful of specialist categories are moved by seller-arranged or brand-arranged transport rather than by the marketplace's parcel network.
For a buyer this has a practical consequence. If a Flipkart order shows a courier name at all, that name is the exception rather than the rule, and the tracking number it carries belongs to that courier's system rather than to Flipkart's.
Amazon India: the fulfilment programme sets the carrier
Amazon India splits seller logistics into three programmes, and only one of them leaves the carrier choice with the seller. Fulfilment by Amazon and Easy Ship are both Amazon-operated, and the Easy Ship pickup network alone reaches more than 99 percent of India's serviceable pin codes.
On Easy Ship, Amazon's own seller documentation is explicit about who collects and who delivers:
"your orders are picked up from your location by an Amazon Logistics delivery associate and delivered to the buyers' doorstep"
Amazon Seller Services India, Easy Ship programme page, accessed July 2026
Self Ship is the opening. Amazon leaves the entire transport arrangement to the seller, and names third-party carriers as an accepted route:
"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
That single sentence is why XpressBees turns up on Amazon.in orders. A Self Ship seller books the consignment on its own XpressBees account or through a shipping aggregator, uploads the resulting AWB against the order, and Amazon simply displays it. The buyer sees an Amazon order page with a courier name and a number that Amazon's own tracker cannot resolve, because the scans live in the carrier's system.
Meesho assigns the courier, and the supplier cannot override it
Meesho is the platform where an XpressBees delivery is most likely of the three, and it is also the one where nobody in the transaction chose XpressBees. Meesho arranges the shipment centrally: the supplier prints a Meesho-generated label, a partner courier collects it, and the allocation between partners is made by Meesho rather than by the supplier or the buyer.
Meesho buys that capacity from several logistics companies at once, XpressBees among them, and since 2023 it has also routed a growing share of volume through Valmo, its own asset-light logistics network built from regional pickup, sortation and delivery partners. Both routes are invisible at the point of order. The courier name appears only once the shipment is booked, and it can differ between two items bought in the same session from two different suppliers.
The practical effect is that a Meesho buyer cannot request a carrier and a Meesho supplier cannot refuse one. XpressBees reaches more than 20,000 pin codes across every Indian state and union territory, which is the reason it is on the panel at all: Meesho's demand is weighted towards tier-2 and tier-3 towns where the national e-commerce carriers compete on reach rather than on speed.
How to tell which courier is actually carrying your parcel
The courier is identified by the tracking number, not by the marketplace's branding, and the two are stored in different fields. Every Indian marketplace shows an internal order reference that looks like a tracking number and is not one, so the first step is to find the field labelled "tracking ID", "AWB" or "waybill number" inside the order's shipment details.
An XpressBees consignment can be identified from 4 signals, listed in the order they are worth checking:
The field the number sits in. A carrier consignment number appears under a label reading AWB, AWB number or waybill number, while the platform's own reference sits under order ID or order number. The label identifies which number is which; the length of the string does not, because seller shipping platforms issue numbers of their own in several shapes.
The carrier code in a seller or supplier panel. Panel codes abbreviate the carrier name, so any code containing XPBEES refers to XpressBees regardless of the prefix or suffix around it.
The label itself. A physical XpressBees label carries the carrier's own barcode above the seller's order reference, and the two numbers are not interchangeable.
The carrier's own tracker. XpressBees accepts either the AWB or the order ID on its tracking page, so a number that resolves there is an XpressBees consignment.
If the number resolves nowhere, it is almost always the marketplace order ID rather than a carrier AWB. That number is useful for finding the order with the seller and useless for a carrier scan lookup.
What an XpressBees label does not tell you
An XpressBees AWB identifies who is moving the parcel and nothing about who is answerable for it. The contract for the sale sits with the seller and the marketplace, so a refund, a replacement or a wrong-item claim is settled there even when every scan on the timeline was made by XpressBees.
It also does not tell you the parcel was chosen to travel that way. On Meesho the platform allocated it, on Amazon Self Ship the seller's shipping software allocated it by rate card, and in neither case does the choice say anything about the priority given to the order.
Finally, an XpressBees scan is not a delivery promise. Transit scans on intercity lanes refresh roughly every 24 to 48 hours, so a status that has not moved since yesterday is normal rather than a sign of a stuck shipment. Only "Out for Delivery" indicates a same-day attempt, and even that can end in a reattempt if the address is unreachable or a cash on delivery amount is not ready.
Why the same marketplace sends a different courier next time
Carrier allocation is decided per consignment, so two orders placed on the same platform on the same day routinely travel with different couriers. Five variables drive the outcome, and none of them is visible to the buyer at checkout.
Origin pin code. The seller's dispatch location decides which carriers can collect at all, and a supplier in Surat and a supplier in Guwahati will not share a panel.
Destination serviceability. XpressBees reaches more than 20,000 pin codes, while a platform's in-house network may reach a smaller set, so the destination alone can force a third-party handover.
Payment mode. Cash on delivery requires the carrier to collect and remit money, and not every carrier on a panel is enabled for it on every lane.
Weight and category. Parcels above a carrier's weight band, fragile goods and restricted categories are routed to whichever partner accepts them.
Peak-season capacity. During Flipkart Big Billion Days and the Amazon Great Indian Festival, overflow volume is spread across more carriers than usual, and standard 2 to 5 business day timelines stretch by roughly 1 to 3 business days.
When to contact the seller, the marketplace, or XpressBees
The rule that resolves most cases is that whoever booked the shipment can escalate it, and the buyer usually did not. On a Flipkart, Amazon or Meesho 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.
Reasonable thresholds before escalating are straightforward. Allow one full business day after the label is created for the first pickup scan, since a booked AWB with no movement usually means the parcel has not been collected yet. Allow 2 to 3 days for a gap between intercity scans. Treat a status frozen for more than 5 to 7 days, or a "Delivery Attempted" that repeats without a call, as a case to raise rather than to wait out.
Contact XpressBees directly only for matters the carrier alone controls: a delivery slot, an address correction on a live consignment, or a reattempt after a failed delivery. For a refund, a return pickup that never happened, or an item marked delivered but not received, open the case with the marketplace first and give the carrier's AWB as evidence, because the marketplace holds both the payment and the commercial relationship with the carrier.
Carriers XpressBees gets confused with
Six carrier names circulate around the same three marketplaces, and only two of them are independent third-party logistics companies. The table below separates them by ownership, which is the distinction that decides whether a seller could have chosen the carrier at all.
Carrier | Who it belongs to | Where a buyer meets it |
|---|---|---|
XpressBees | Busybees Logistics Solutions Private Limited, an independent 3PL | Meesho allocations, Amazon Self Ship consignments, D2C store shipments |
Ekart | The Flipkart group's in-house logistics arm | Nearly every Flipkart order, and most Myntra shipments |
Amazon Logistics | Amazon's own delivery network and its contracted delivery partners | Fulfilment by Amazon and Easy Ship orders on Amazon.in |
Valmo | Meesho's own asset-light logistics network, launched in 2023 | A share of Meesho orders, in place of a national 3PL |
Delhivery and Ecom Express | Independent 3PL companies, direct competitors of XpressBees | The same marketplace panels, on lanes where they win the allocation |
India Post | The Government of India's postal operator | Remote pin codes no private carrier serves, on all three platforms |
The distinction matters when something goes wrong. An Ekart or Amazon Logistics problem is a marketplace problem with a single support desk. An XpressBees, Delhivery or Ecom Express problem has two desks, the seller's and the carrier's, and the AWB is what connects them.
Who owns XpressBees, and how big its network is
XpressBees is the trading name of Busybees Logistics Solutions Private Limited, a company incorporated on 12 August 2015 and headquartered in Pune, Maharashtra. It began as a spin-off of the delivery operation built for the online baby and kids retailer FirstCry, and was co-founded by Amitava Saha and Supam Maheshwari. It is a registered logistics operator rather than a marketplace brand, which is why its name appears on parcels bought from platforms that have no other visible connection to each other.
The network behind that name completes more than 3 million shipments a day across over 20,000 pin codes, operated from roughly 250 hubs and about 4,500 service centres with more than 28,000 delivery partners. The company organises its work into four lines: B2C express for online sellers and marketplaces, B2B express cargo, third-party logistics covering warehousing and fulfilment, and cross-border shipping, all four of which are set out on its own B2C logistics services pages.
That reach is the whole reason the answer differs by platform. A marketplace that has already built a comparable network of its own, as Flipkart has, has no reason to buy capacity from a rival. A marketplace that has chosen not to build one, as Meesho has, buys it every day. Amazon India sits between the two, running its own network for the programmes it controls and letting sellers bring their own carrier for the one it does not.
Whichever platform the order came from, the AWB printed on the label is the identifier that resolves the question. Paste it into the tracker on this page to pull the carrier's scans together with the marketplace's own updates in one timeline.