Flipkart Seller API integration for order and warehouse management
Flipkart integration: in production use.
Yes, Flipkart has a seller API: the Flipkart Marketplace Seller APIs (v3), which let a seller's systems search orders, print labels and invoices, and move orders through their life cycle (Flipkart Seller API docs, Nov 2026). Fretron CommerceOS runs Flipkart in production: self-ship and Flipkart-shipped orders are pulled in, the catalogue is imported and mapped to your SKUs, inventory is published back automatically, and packing, labels, manifests, dispatch and returns run from the same record.
Book a demo →How Flipkart's API is set up
- Your seller login isn't API access. Flipkart says the username and password from seller registration don't give API access (Flipkart Marketplace Seller APIs overview, Nov 2026).
- Two kinds of application. A seller's own app is created under Seller Dashboard → Manage Profile → Developer Access. Partners use a third-party application, and Flipkart verifies partner profiles within 72 hours.
- Tokens expire. Access tokens usually last 60 days.
- Two fulfilment flows. In Standard fulfilment, Flipkart's logistics partner collects and delivers; in Self Ship, the seller packs, dispatches and delivers (Flipkart Order Management API, Nov 2026).
- You can't decline an order. If you show positive inventory at a location and a customer orders, you have to fulfil it; cancellations above a threshold can deactivate the account or location (Order Management API, Nov 2026).
What CommerceOS runs on Flipkart
| Operation | In CommerceOS |
|---|---|
| Order poll | Standard (Flipkart-shipped) and Self Ship orders are pulled in |
| Catalogue import | Your Flipkart listings are imported and mapped to your SKUs |
| Inventory push | Stock is published back automatically, 10 SKUs per call, the batch size Flipkart allows |
| Pack and label | Labels and invoices are requested and downloaded per shipment |
| Manifest and dispatch | Shipments are marked ready to dispatch and the manifest is downloaded for handover |
| Returns | Flipkart returns are received against the original order |
| Ekart | Ekart can be booked, labelled, tracked and manifested from the order screen |
How a Flipkart shipment moves
Flipkart's API works at shipment level, and each state gates the next (Order Management API, Nov 2026):
- APPROVED. New shipments arrive. You can act only after their dispatchAfterDate and when Flipkart's hold flag is false.
- PACKING_IN_PROGRESS. You request labels and invoices. Flipkart says they usually take 5–10 seconds, and up to 30 minutes under load.
- PACKED. Labels and invoices are ready to download.
- READY_TO_DISPATCH. You mark it ready, which triggers the pickup request, then download the manifest for the handover.
- SHIPPED, DELIVERED or CANCELLED. Cancellation is possible only before shipping.
CommerceOS shows each shipment's Flipkart state on the order, so the floor team can check it before picking.
Worked example: a 1,500-order sale day
A footwear brand lists 600 SKUs on Flipkart. On the first day of a sale it takes 1,500 Flipkart orders, against its usual 250. Illustrative numbers.
Inventory updates. Flipkart accepts 10 SKUs per inventory call (Listing Management API reference, Nov 2026), so a full refresh of 600 SKUs is 60 calls. CommerceOS sends updates in those batches from the same stock record the warehouse picks from. Pushes are queued and batched, so the brand keeps its last few units of the top 20 SKUs off the website during the sale, a decision it makes itself.
Labels. By 1 pm, 1,100 shipments are past their dispatchAfterDate. Label requests go out in blocks. Flipkart says most come back in 5–10 seconds and some take up to 30 minutes under load (Order Management API, Nov 2026), so the packing plan leaves slack before the pickup slot.
Cut-off. Packing runs in waves by pickup slot. At 4 pm, 1,060 shipments are packed and marked ready to dispatch; the manifest is downloaded and the Ekart rider signs for it. The remaining 440 go into the next morning's first wave.
Returns. Three weeks later, 61 returns have come back; each is received against its original order, through QC on the same record.
Setup prerequisites
- An active Flipkart seller account.
- Authorize the Fretron CommerceOS app for Flipkart Seller API access from your Flipkart seller login. No application ID or secret is needed.
- Your fulfilment locations mapped, since Flipkart inventory is set per location.
Frequently asked questions
- Does Flipkart have a seller API?
- Yes: the Flipkart Marketplace Seller APIs, documented at seller.flipkart.com/api-docs, covering listings, orders and reports (Flipkart Marketplace Seller APIs overview, Nov 2026).
- How does inventory sync with Flipkart?
- Through the listings inventory call, at most 10 SKUs per request and set per location (Listing Management API reference, Nov 2026). In CommerceOS, inventory is published back automatically from the warehouse's stock record.
- Self-ship vs Flipkart-shipped orders?
- Flipkart-shipped (Standard) orders are collected by Flipkart's logistics partner; Self Ship orders are delivered by the seller, who also confirms dispatch and delivery (Order Management API, Nov 2026). CommerceOS pulls in both.
- How are Flipkart returns received?
- Against the original order, through QC on the same record, with the disposition decided per line.
Sources
Partner and marketplace details were read on their own pages on 5 Nov 2026. Check them before you rely on them.
- Flipkart Marketplace Seller APIs overview: https://seller.flipkart.com/api-docs/FMSAPI.html
- Order Management API: https://seller.flipkart.com/api-docs/order-api-docs/OMAPIOverview.html
- Listing Management API reference: https://seller.flipkart.com/api-docs/listing-api-docs/LMAPIRef.html
Plan your next Flipkart sale on one stock record.
We'll walk your SKU count through the inventory, label and manifest steps.
Book a demo →