datawebotFlipkart data: FSN, seller listing and SKU
Understand Flipkart product IDs, seller listings and seller SKUs. Separate Affiliate API 1.0 feed scope from seller-authorized fields and the platform’s access terms.
Flipkart Platform and Affiliate API terms
The flipkart.com Terms page reviewed September 29, 2026 showed no last-updated date. It lists deep-linking, page-scraping, robots, spiders and other automated or similar manual methods used to access, acquire, copy or monitor Platform content to obtain material not purposely made available. Separate Affiliate API Terms govern that API. The Affiliate overview names shopping-comparison sites/apps among possible projects, while its Terms say the API may not be used in a similar or competitive platform. Those pages do not resolve how a particular service or use is categorized; this guide reports each statement without interpreting it.
Scroll to compare →
| Official source | Documented boundary | Keep distinct |
|---|---|---|
| Flipkart Platform Terms · observed Sep 29, 2026 | Lists page-scrape, robot, spider, automatic methods and similar manual processes for obtaining content not purposely made available through the Platform. | The page showed no update date; attribute and date this observation. |
| Affiliate API overview | Describes APIs for registered program users and includes comparison-shopping sites/apps among possible projects. | This overview does not replace the separate API Terms. |
| Affiliate API Terms | Scope is in conjunction with Flipkart platform/services/apps; the usage guidelines prohibit use in a similar or competitive platform. | Keep the API overview and these API Terms together; the reviewed pages do not explain how their provisions apply to a particular service or use. |
Match the marketplace product to a seller listing
Flipkart’s Marketplace Seller Platform defines a product and a sellable seller listing at different levels. Keep the product identifier separate from each seller’s listing key and SKU; Affiliate API identifiers are a separate namespace unless a current official schema documents a mapping.
Scroll to compare →
| Entity level | Official identifier | Relationship |
|---|---|---|
| Marketplace product | FSN (Flipkart Serial Number) | The Seller Platform overview identifies a product by its FSN. |
| Seller listing | listingId | A listing is the seller’s buyer-facing offer and has its own listing ID. |
| Seller catalog key | skuId | The Seller Platform says a listing ID maps to that seller’s SKU ID. |
| Affiliate feed item | productId | Preserve the Affiliate API identifier and feed context; the reviewed docs do not establish that it is an FSN. |
Keep Affiliate product feeds and offers program-scoped
The Affiliate API overview describes product information in actively marketed categories, keyword and product-ID queries, and active-offer or Deals of the Day APIs for registered program users. Its API 1.0 product reference contains feed limits and versioned endpoint notes; record those as documentation details, not as a live service promise.
Scroll to compare →
| Affiliate API detail | What the API 1.0 docs state | Evidence rule |
|---|---|---|
| Product scope | Products in actively marketed categories, with product and offer APIs described separately. | Do not treat the Affiliate product feed as seller-account inventory. |
| Feed batch | The reference says a product-feed response contains 500 items by default. | Attribute to the API 1.0 reference observed Sep 29, 2026. |
| Feed URL lifetime | The reference says product-feed URLs are valid for 10 hours. | Treat as a statement in that API documentation version. |
| Keyword search | The reference states a maximum of 10 products per search; some older search/feed endpoints are marked deprecated. | Keep the limit version-scoped and do not promote deprecated routes as a current integration. |
Seller listing fields stay with the seller’s account
The Marketplace Seller APIs document resources for the registered seller account and require an authorization header. Keep listing prices, stock and fulfillment attributes tied to the seller listing and source context; they are not fields for another seller’s private inventory.
Scroll to compare →
| Seller listing field | Documented meaning | Record boundary |
|---|---|---|
| selling_price and mrp | The glossary defines a seller’s selling price and maximum retail price separately. | Do not collapse them into a buyer’s order total or an Affiliate API offer. |
| stock_count | The glossary contains more than one stock_count description in its listing/order terminology. | Retain exact API context and source wording; do not publish one reconciled meaning or a current quantity. |
| Shipping charge fields | local_shipping_charge, zonal_shipping_charge and national_shipping_charge are seller-defined charge fields. | Keep the named zone and seller/API scope; do not describe them as universal checkout shipping. |
| Listing and procurement status | The glossary includes listing_status, procurement_sla/type and selling_region_restriction. | Preserve seller settings and enum/source labels; do not treat them as marketplace-wide product attributes. |
| Seller access | The Seller API details endpoint requires authorization and accepts up to 10 SKU IDs per request. | Treat this as a request limit documented for the named endpoint. |
Interpret feed indicators and offer fields in context
Affiliate product feeds and seller listings describe different records. The Affiliate reference documents product-feed fields such as productId, product price/MRP, offers and an inStock indicator. The seller glossary separately describes seller listing price, inventory and shipping fields. Keep each group with its own API, seller/program scope, market and observation time.
Scroll to compare →
| Record | Field group | Interpretation |
|---|---|---|
| Affiliate product feed | productId, category, product title/brand, price/MRP, inStock and offers. | Keep values with the feed/API version and timestamp; inStock is not a seller stock quantity. |
| Seller listing | FSN, listingId, skuId, seller price, inventory and shipping fields. | Keep the authenticated seller and listing context; do not infer competitor values. |
| Freshness and geography | Feed links have a documented validity period; seller charges are divided by local, zonal or national scope. | Retain observation time, currency and applicable market/zone when supported by the record. |
| Not a public checkout quote | Product feeds, seller listing fields and an order-specific buyer total are distinct data contexts. | Do not promise live prices, exact buyer totals, shipping, availability or current offers on this guide. |
Keep private seller, order and buyer data out
Flipkart’s Seller APIs also document seller-account and order workflows. Those transaction and account records are separate from a public product-identity reference and should not appear as catalog fields or examples here.
Scroll to compare →
| Out-of-scope data | Why it is separate | Page boundary |
|---|---|---|
| Seller credentials and account records | Seller API access is authenticated and scoped to seller resources. | Do not request, expose or imply possession of seller credentials or private account data. |
| Orders and order items | Seller docs define order and shipment records apart from the product and listing entities. | Exclude order IDs, quantities, fulfillment events and related transaction details. |
| Buyer and location information | Platform and seller records can involve customer, delivery and seller-location details. | Exclude names, contact/address data, GSTIN and private location identifiers. |
| Live commercial values | Price, offers, stock and shipping values are changeable and scope-specific. | This page is an information guide, not a current quote or data-availability statement. |
Content reviewed 2026-09-29.