Quick Commerce

Documents Required for Blinkit Onboarding: The Complete Checklist

Blinkit approves clean files and stalls messy ones. Here is every document the platform asks for, and the mismatches that hold applications up.

Key takeaways
  • GST, PAN, and bank proof must carry the exact same legal name, or verification fails quietly.
  • FSSAI applies to anything edible, and the license must be in the seller entity's name, not the founder's.
  • A filed trademark application or a proper authorization letter on letterhead covers the brand requirement.

Blinkit onboarding is a documents exercise before it is anything else. The catalogue, the pricing, the dark store allocation all come later. First the platform checks who you are, whether you can legally sell what you make, and whether the brand on the pack is yours. Sellers who arrive with a clean file go live in weeks. Sellers who improvise lose that time to a support queue, one clarification email at a time.

The core entity documents

Three documents anchor every Blinkit application: GST, PAN, and a bank account in the same legal name. Everything else attaches to these, and the platform verifies them against government records, not against your word.

  • GST certificate. A GSTIN is mandatory. Blinkit issues tax invoices and reports transactions, so there is no path around it, whatever your turnover.
  • PAN. The business PAN for a company or LLP, the proprietor’s personal PAN for a proprietorship.
  • Bank proof. A cancelled cheque or bank statement for a current account held in the same entity name that appears on the GST certificate. Payouts go here, so a mismatch blocks money, not just approval.
  • Business registration proof. Certificate of incorporation for a company, the agreement for an LLP or partnership. For a proprietorship, the GST certificate itself usually does the work.

The single most important property of this set is that the legal name matches exactly across all of it. We have written before about the deeper GST and GTIN traps in marketplace setup, and the short version applies here too. Treat the entity name as sacred and identical everywhere.

FSSAI if anything you sell is edible

If your product goes into someone’s mouth, Blinkit will ask for an FSSAI credential before anything else moves. That covers packaged food, beverages, dairy, supplements, and most things adjacent to them. Whether you need a basic registration, a state license, or a central license depends on turnover slabs, and those slabs were revised in 2026, so check the current numbers on the FoSCoS portal rather than an old guide. What matters for onboarding is simpler. The license must be active, issued to the same entity that holds the seller account, and cover the kind of business you actually run. A license in the founder’s personal name attached to a company’s application reads as valid and still fails.

Trademark or brand authorization

Blinkit wants proof that the brand on the pack is yours to sell. If you own the brand, that means a trademark registration certificate, or in practice the acknowledgement of a filed application, since registration itself can take well over a year and platforms know it. If you are a distributor or reseller, it means a brand authorization letter from the brand owner: on letterhead, signed by someone with the designation to sign it, with a stated validity period. Platforms adjust what they accept from time to time, so confirm the current requirement on the seller portal before you apply rather than assuming last year’s rules hold.

What gets applications stuck

Most stuck applications share the same handful of causes, and none of them are exotic.

  • Name mismatch. The GST certificate says one name, the bank account another, the PAN a third. Verification fails and the error message rarely says why.
  • Missing APOB. Warehouse and inventory locations often need to be added as an Additional Place of Business under your GST registration. Skipping this stalls stock movement even after account approval.
  • Wrong-entity or expired FSSAI. The license exists, but it belongs to a different name or lapsed last quarter. Both fail the same way.
  • Weak authorization letters. Plain paper, no validity date, no signatory designation. Rejected with little explanation.
  • Missing category documents. Some categories carry extra requirements, such as BIS certification for certain products, and these surface late if nobody checked the category rules first.

Prepare the file before you open the form

The fastest onboarding is the one where every document exists before the application starts. Assemble one folder: GST, PAN, bank proof, entity registration, FSSAI where relevant, trademark or authorization, and clean, legible scans of each. Then read every document side by side and check that the legal name is identical on all of them, character for character. Requirements are updated from time to time, so confirm the current checklist on the Blinkit seller portal, and have your CA or CS look over the file once before submission, since a mismatch caught then costs an hour instead of a month. If you would rather hand the whole file to a team that does this every week, that is exactly what our Blinkit Onboarding service is for. The paperwork is unglamorous. Going live on schedule is not.

FAQ

Quick answers.

Yes. A GSTIN is mandatory for marketplace sellers regardless of turnover, because the platform issues tax invoices and reports transactions. There is no exemption path for small sellers.
Generally yes. The acknowledgement of a filed application is usually accepted while registration is pending, but policies change, so confirm the current requirement on the seller portal.
No. FSSAI applies to food, beverages, supplements, and similar edible categories. Non-food sellers skip it, though some categories carry their own certifications such as BIS.

Where Zane fits

Related insights

From the wire

India's Commerce Engine

Put it
to work.

hello@zane.marketing

Book a meeting