BigBasket, operated by Supermarket Grocery Supplies Private Limited and owned by Tata Digital, is India's largest online grocer and now positions itself as a quick commerce platform covering food, grocery, electronics, medicines and fashion. For a brand the relationship is almost entirely first party: BigBasket buys your stock, holds it in its own distribution centres and dark stores, prices it, sells it and settles with you against goods received. That makes the objects you integrate purchase orders, goods receipt notes, fill rates, invoices and payment advices, not marketplace orders. BigBasket publishes no seller or vendor API. It runs a login walled vendor portal called BB Sambandh, and it is supported as a channel by at least one order management aggregator.
At a glance
What it is
BigBasket's own about page, read 2026-09-21, describes it as "India's leading quick commerce platform for food, grocery, electronics, medicines, and fashion", with more than 20,000 products, delivery across more than 100 cities and more than 50 million customers. It runs both slotted delivery and quick delivery. Its named brand partners include Amul, Aashirvaad, its own label Fresho, Himalaya, Cadbury, Horlicks, Nivea, LG, Apple, Samsung and, reflecting the shared Tata Digital ownership, Tata 1mg.
The sentence that determines the integration model is BigBasket's own: "Every product is carefully sourced and quality-checked". That is a retailer describing inward goods inspection, not a marketplace describing seller listings. BigBasket buys, receives, quality checks, stores and sells. A brand supplying BigBasket is a vendor.
API access
None published, and the negative evidence is reasonably strong.
Checked on 2026-09-21:
supplier.bigbasket.com,vendor.bigbasket.comandseller.bigbasket.comdo not resolve.www.bigbasket.com/sell-on-bigbasketand/supplierreturn HTTP 404.www.bigbasket.comreturns HTTP 403 to ordinary scripted requests, so the consumer site is behind bot protection and cannot be crawled for a seller link.partner.bigbasket.comresolves and redirects, via an AWS load balancer, tohttps://nucleus.bigbasket.com. That host serves an application titled BB Sambandh. It is a Flutter web application, built frommain.dart.jsandflutter.js, carrying an asset namedseller_logo_animation.gif, and it loads Google reCAPTCHA on the login screen. There is no public documentation, no API reference and no sign up flow visible without credentials.- The Internet Archive holds a capture of
nucleus.bigbasket.comfrom June 2026 and none ofpartner.bigbasket.comorsupplier.bigbasket.com.
BB Sambandh is a Flutter web application behind reCAPTCHA. That combination is close to the worst case for automation: the interface is rendered to a canvas rather than to inspectable DOM elements, and the login is deliberately bot resistant. Do not plan a screen scraping integration against it. If you need programmatic access to BigBasket vendor data, the conversation to have is about SFTP, EDI or a report email, or about routing through an aggregator.
The one positive integration signal is external. Unicommerce's public integration list names BigBasket under Quick Commerce, alongside Blinkit, Zepto, Swiggy Instamart and Flipkart Minutes. Unicommerce's partner integration documentation states the API set a channel must expose before it will integrate, so BigBasket exposes, at minimum, some authenticated interface for order or purchase order retrieval and status updates to its integration partners. That interface is not documented publicly and is not, on the evidence, offered to vendors directly.
Authentication
Not published. BB Sambandh uses a portal login with reCAPTCHA. No API key, token endpoint, signing scheme or token lifetime is documented anywhere we could read. A credential store for BigBasket holds portal credentials, issued during vendor onboarding, and nothing more.
Objects we can read: the vendor purchase order model
As with the other purchase order channels in this catalogue, the sequence is a retail supply cycle. BigBasket publishes none of these document formats, so treat the field lists as the shape to expect and confirm each name against the documents you actually receive.
Purchase orders
BigBasket's buying team raises a purchase order against your vendor code, for its own article codes, at agreed landed costs, with a delivery window and a named distribution centre or dark store. Grocery adds two constraints that general merchandise does not have:
- Delivery appointments. Receiving docks run to slots. A purchase order that misses its appointment can be turned away whole.
- Shelf life at receipt. Fast moving consumer goods and fresh categories carry a minimum residual shelf life rule, expressed as a percentage of total shelf life remaining on the delivery date. Stock inside the window is rejected at the gate. This is the single most common cause of rejections in grocery and it has no home in the unified model. Capture manufacture date, expiry date and batch on every line.
Model these as a purchase_orders table, not as orders. A purchase order has no consumer, no ship_to_address that is a customer and no payment_method.
Fields to capture: BigBasket purchase order number, vendor code, BigBasket article code, your SKU, ordered quantity, unit cost, tax, delivery window, appointment slot, destination facility code.
Dispatch and shipment
Your dispatch against the purchase order: date, transporter, lorry receipt number, per line dispatched quantity, your invoice number, and the batch and expiry per line. Map to shipments with order_id pointing at the purchase order.
Goods receipt note
The authoritative record of what BigBasket accepted. Capture goods receipt number, purchase order number, per line received, accepted and rejected quantities, rejection reason, receipt date and facility. In grocery the rejection reasons cluster into short shelf life, damage, weight or count variance, quality check failure and unappointed delivery. Store the reason code, not just the quantity, because the reason determines whether you can re present the stock.
Fill rate
Accepted divided by ordered, per purchase order line, aggregated per purchase order and per period. Quick commerce buyers weight fill rate heavily, because a stockout in a fifteen minute delivery promise is immediately visible to the customer. Compute it yourself from purchase order lines against goods receipt lines rather than waiting for a report.
Invoices
Your tax invoice against accepted quantities, with GST components. Quantity mismatches against the goods receipt are the usual cause of payment holds, and in grocery they are common because weight based lines rarely match exactly.
Payment advices and settlements
Paid on the cycle in the vendor agreement, net of debit notes. Map to settlements:
Returns
On a first party model, consumer returns are BigBasket's. Return to vendor happens where the agreement provides for it, typically for near expiry or damaged stock, and arrives as its own document with a debit note attached.
Listings and inventory
Not yours. BigBasket owns the product page, the retail price and the stock position. You can see your products on the consumer site, but you cannot address them, and the site returns HTTP 403 to scripted requests, so even monitoring requires a headless browser.
Writing back: listings, price and stock
Not available on the first party model, and not applicable. Catalogue content, retail price and promotional price are BigBasket's decisions, informed by whatever you negotiate commercially. There is no listing API, no price push and no stock push.
If part of your BigBasket business runs on a marketplace or consignment basis rather than outright purchase, that changes the answer, and the route would be the aggregator integration rather than anything direct. Establish which model your account is on first.
Webhooks and notifications
None. Purchase orders arrive in the portal or by email. The only automation available without a commercial conversation is a mailbox rule plus a parser.
Rate limits and pagination
Not applicable.
Mapping to the unified model
Beyond the settlement table above:
Gaps and open questions
- Whether BigBasket offers EDI or SFTP to large vendors is unverified, and it is the first question to ask. A grocer of this scale almost certainly does for its top suppliers.
- What BB Sambandh actually contains is unverified. It is login walled and its interface is not inspectable from outside.
- Whether BigBasket runs any genuine third party marketplace alongside the first party model is unverified. Its own description is entirely first party.
- The shape of the Unicommerce BigBasket integration, whether it carries purchase orders or consumer orders, is unverified.
- Shelf life acceptance rules, appointment policy, fill rate targets and penalty schedules are all contractual and none is published.
- EasyEcom's knowledge base at
support.easyecom.iois login walled, returning an HTTP 302 to a login page on 2026-09-21, so any EasyEcom BigBasket article could not be read.
Sources
- BigBasket about us, for the quick commerce positioning, the 20,000 product, 100 city and 50 million customer figures, the named brand partners and the sourcing and quality check statement
https://partner.bigbasket.com, which redirects tohttps://nucleus.bigbasket.com, serving the BB Sambandh vendor portal, a Flutter web application with Google reCAPTCHA, HTTP 200 on 2026-09-21- HTTP and DNS probes of
supplier.,vendor.andseller.bigbasket.comand of/sell-on-bigbasketand/supplier, all absent on 2026-09-21 - Unicommerce integrations list, which names BigBasket under Quick Commerce
- Unicommerce marketplace partner integration overview, for the minimum API set a channel must expose
- BigBasket on Wikipedia, for Supermarket Grocery Supplies Private Limited and Tata Digital ownership
- support.easyecom.io: attempted, login walled on 2026-09-21