Flipkart connects by API and syncs nightly, like Amazon. Meesho and the quick-commerce platforms (Blinkit, Zepto, Swiggy Instamart, JioMart) don't publish seller APIs, so their sales come in by CSV upload — Finocket detects which report you brought. Everything lands in the same place: orders, settlements, GSTR-8 reconciliation.
How do I connect Flipkart?
- Register a seller app in Flipkart Seller Hub → Developer Center. You get an App ID and App Secret.
- Open Settings → Selling channels → Flipkart → Connect.
- Paste the App ID, App Secret and your first-sync-from date. Finocket verifies the credentials against Flipkart before saving — a typo fails immediately, not silently at night.
- Done. The nightly sync pulls your orders and settlements from then on.
Credentials are encrypted (AES-256-GCM) before storage and never shown again. Disconnecting removes the connection and cached data.
How do I bring Meesho sales into Finocket?
Meesho has no seller API, so the connection is a bookkeeping row plus CSV imports:
- On Integrations, connect Meesho — no credentials, just a display name.
- Open the Import CSV screen from the Meesho row (its own page under Integrations).
- In your Meesho Supplier Panel, download the Tax Invoice Report (per-shipment sales and returns with HSN and tax break-up) or the TCS Report (marketplace-collected TCS per period).
- Drop the file on the upload zone. Finocket reads the header row, detects which report it is, and ingests it as orders/returns or settlements accordingly.
Re-uploading the same file is safe — rows are matched on the sub-order number, so nothing duplicates.
How do quick-commerce imports work (Blinkit, Zepto, Instamart, JioMart)?
Each platform has its own page under Integrations, all working the same way:
- Connect the platform — display name only, no credentials.
- Open its Import CSV screen and drop your monthly export from the seller panel.
- Finocket sniffs the header row: order-shaped columns (order id, date, amount, state) ingest as orders; settlement-shaped columns (TCS amount, period) ingest as settlements. If neither matches, you get a hint to check the header.
Column names differ per platform; Finocket keeps a per-platform alias table plus a generic fallback. If a column comes through blank (say, state shows "—" everywhere), send us the header row via Raise a request and we'll add the alias.
What about Zomato and Swiggy (food delivery)?
Zomato and Swiggy adapters are visible on the Integrations page but marked coming soon — they aren't connectable yet. The restaurant vertical has a different tax structure (5% GST without ITC), so it needs its own treatment.
What about Myntra, Ajio, Nykaa and Tata Cliq?
You can't connect these yet, and the honest reason is worth knowing before you buy anything to work around it. None of them offers a seller API you can sign up for on your own, so the usual route is an order-management hub such as Unicommerce or EasyEcom, which sits between you and several marketplaces at once.
Finocket cannot connect to either hub today. Two things are missing, and only one of them is a subscription. Finocket holds no account with either vendor — but the harder problem is that an order arriving through a hub has nowhere to record which marketplace it actually came from. Every connection in Finocket today is one marketplace, so the marketplace's name is also the name of the connection.
That matters for your GST return, not just for a label. Tax collected at source is collected and reported by each marketplace separately, so filing a Myntra order under the hub's name would report one marketplace's TCS as another's.
Half of that problem is now solved. Every order Finocket records carries the operator it came through, and an order is now identified by that operator as well as by its own order number. So the same order number arriving from two different places can no longer overwrite anything — which used to be the reason filing a hub order under the marketplace's own name was unsafe.
What is still missing is the connection itself: there is no hub connection to switch on yet, and the TCS question above — which marketplace a hub order should be reported under — is a filing decision, not a storage one. So nothing changes in what you can connect today.
Until it's resolved, bring these sales in the way you already bring in Meesho — export the order report from the marketplace's own seller panel and upload the CSV. Your books, GST and reconciliation all work the same way; only the automatic nightly pull is missing.
Related: Connect Amazon, GSTR-8 reconciliation.