Flipkart Commerce Cloud Seller Portal
Confidential — For Publisher and Partner Use Only © 2026 Flipkart Commerce Cloud
About This Document
This document is the product reference for the Flipkart Commerce Cloud (FCC) Seller Portal. It covers the platform's architecture, the seller and operator experience layers, core capabilities across onboarding, catalog, orders, payments, and configuration, integration guidance, and onboarding checklist for publishers and their technical teams.
Audience: Network publishers (operators), seller operations teams, integration engineers, and e-commerce product managers.
Prerequisites: Familiarity with e-commerce marketplace concepts (sellers, listings, orders, payouts, operator-seller relationships) is helpful but not required.
Table of Contents
- Introduction
- Platform Architecture
- Seller Onboarding & Registration
- Catalog & Listing Management
- Order & Inventory Management
- Payments & Settlements
- Operator Configuration Layer
- Notifications & Communication
- Capability Summary
- Market Context and Strategic Vision
- Metrics and Measurement
- Onboarding Checklist
- Glossary
1. Introduction
Overview
The FCC Seller Portal is the primary interface through which sellers on FCC-powered operator marketplaces manage their entire business — from registration and listing to order fulfilment, payments, and day-to-day operations. It is a multi-tenant, configurable platform built on the same infrastructure that powers Flipkart's marketplace of millions of active sellers.
The quality of the Seller Portal directly determines marketplace health. Better seller experience means more sellers activating, higher GMV per seller, and lower churn. Operators who deploy FCC inherit a production-grade seller interface without building one from scratch.
The Seller Portal is not a standalone product — it is the seller-facing surface of the FCC marketplace stack, tightly integrated with FCC Catalog, Order Management (OMS), Fulfilment (WMS), and Payments. Every capability in the portal reflects real data and real state from these underlying systems.
What FCC Seller Portal Does
The FCC Seller Portal is the single operational interface for sellers on any FCC-powered marketplace. It enables sellers to:
- Register, complete KYC, and activate their selling account
- Create, manage, and edit product listings through FCC Catalog
- Track and process orders, manage fulfilment and returns
- View payout statements and settlement history
- Manage inventory levels and availability
- Receive notifications and alerts for business-critical events
- Access platform policies, guidelines, and seller support
Operators use the Seller Portal's operator-facing layer to manage their seller ecosystem — approving sellers, configuring marketplace rules, and monitoring platform health.
What FCC Seller Portal Is Not
- Not a storefront or buyer-facing interface. The Seller Portal is exclusively for sellers and operators. Buyers interact with the marketplace through the operator's storefront, which is separate.
- Not a standalone catalog system. Listing management in the Seller Portal is powered by FCC Catalog. The Seller Portal provides the UI; the Catalog system owns the product data and lifecycle.
- Not an ERP or accounting system. The portal provides payout and settlement visibility. It does not replace the seller's accounting, inventory, or ERP systems.
- Not a promotions or advertising tool. Ads and promotions management are handled through the FCC Retail Media and Promotions modules, not through the Seller Portal.
Who This Platform Is For
| Persona | Description |
|---|---|
| Sellers | Merchants listing and selling products on an FCC-powered operator marketplace — from small SME sellers to large multi-category distributors |
| Operator Marketplace Teams | Retailer or marketplace teams responsible for managing their seller ecosystem, onboarding, and marketplace configuration |
| Seller Operations (Ops) Teams | Internal teams at the operator responsible for seller support, KYC review, catalog QC, and onboarding |
| Integration Engineers | Technical teams integrating the Seller Portal with existing ERP, inventory, or fulfilment systems via API |
| E-Commerce Product Managers | Teams designing seller onboarding flows, marketplace configuration, and seller experience across verticals |
2. Platform Architecture
Overview
The FCC Seller Portal is a multi-tenant, headless, API-first platform that operates as a surface layer over the FCC marketplace stack. It does not own business logic or data — it is the interface through which sellers and operators interact with FCC's underlying systems.
Sellers / Operators
│
▼
┌──────────────────────────────────┐
│ SELLER PORTAL (UI + API) │ ← Seller-facing and operator-facing surfaces
│ Listings · Orders · Payments │
│ Onboarding · Notifications │
└──────────┬───────────────────────┘
│ API calls to FCC platform services
▼
┌──────────┴──────────────────────────────────────────────┐
│ FCC PLATFORM SERVICES │
│ │
│ ┌──────────────┐ ┌──────────┐ ┌───────────────────┐ │
│ │ FCC Catalog │ │ OMS │ │ Payments / │ │
│ │ (Listings, │ │ (Orders, │ │ Settlements │ │
│ │ Products, │ │ Returns)│ │ │ │
│ │ QC) │ │ │ │ │ │
│ └──────────────┘ └──────────┘ └───────────────────┘ │
│ │
│ ┌──────────────┐ ┌──────────────────────────────────┐ │
│ │ Fulfilment │ │ Operator Config / Admin Layer │ │
│ │ (WMS / OFC) │ │ (Marketplace rules, approvals) │ │
│ └──────────────┘ └──────────────────────────────────┘ │
└──────────────────────────────────────────────────────────┘
Important: The Seller Portal is a headless, API-first interface. It serves as the UI layer over FCC platform services. Operators receive a white-labeled instance of the portal configured to their marketplace context. Sellers on different operator marketplaces access the same portal engine with operator-specific branding, rules, and catalog schemas applied.
Key Architectural Principles
Multi-tenant by design. A single Seller Portal codebase serves all FCC operator clients. Operator-specific configuration — branding, commission rules, approval workflows, category structure, and seller eligibility — is applied at the tenant layer without platform-level customisation.
Seller-agnostic data layer. Seller data (listings, orders, payouts) is always scoped to the operator marketplace context. A seller selling on two different FCC-powered marketplaces has separate accounts and separate operational surfaces per operator — with no data cross-contamination between tenants.
Event-driven state. Business state — listing approval, order status, payout completion — is computed by underlying FCC systems and reflected in the portal in near real-time. The portal does not maintain its own state; it reads from authoritative sources.
API-first integration. All portal capabilities are exposed as APIs. Sellers and operators with technical teams can integrate portal workflows directly with their ERP, inventory, and fulfilment systems without using the UI for every operation.
3. Seller Onboarding & Registration
Overview
The Seller Onboarding module manages the end-to-end flow from a seller's first interaction with the portal to their first active listing. It encompasses identity verification, business registration, policy acceptance, and account activation.
Status: ✅ Live
3.1 Seller Registration
Sellers register on the operator's marketplace portal by providing their business identity and contact details. The registration flow is operator-configured — operators define which fields are mandatory, which business types are eligible, and what categories of sellers are permitted to register.
Registration entry points:
| Method | Description |
|---|---|
| Self-serve web registration | Seller completes registration via the portal UI using email or mobile OTP as the identity anchor |
| Operator-invited registration | Operator generates an invite link for a specific seller. Seller registers directly into a pre-approved state, bypassing the standard approval queue |
| Bulk seller import | Operators migrating from another platform can batch-import existing seller records via CSV, triggering verification flows for each |
3.2 KYC and Business Verification
After registration, sellers complete a Know Your Customer (KYC) verification step. KYC requirements are configured per operator and vary by market and seller type.
Status: ✅ Live
Standard KYC components:
| Component | Description |
|---|---|
| Business identity | Legal business name, registration number, and business type (individual, partnership, corporation) |
| Tax registration | VAT, GST, or equivalent tax ID depending on the operator's market configuration |
| Bank account verification | Bank account details for payout settlement, validated via micro-deposit or document upload |
| Document upload | Trade licence, identity documents, and any category-specific compliance documents required by the operator |
KYC documents are reviewed by the operator's seller operations team through the operator admin panel. Operators can configure document review to be manual, automated (where KYC APIs are integrated), or a combination of both.
3.3 Seller Agreement and Policy Acceptance
Before activation, sellers accept the marketplace's seller agreement and applicable category-specific policies. Policy documents are configured and managed by the operator. Acceptance is logged with a timestamp and IP address for compliance.
Status: ✅ Live
3.4 Account Activation and Seller Dashboard
Upon KYC approval and policy acceptance, the seller account is activated. The seller gains access to the full Seller Portal — catalog creation, order management, and payout views become available. The seller dashboard provides a top-level summary of account status and pending actions.
Status: ✅ Live
| Dashboard Element | Description |
|---|---|
| Account status | Active, Suspended, or Pending — with reason codes and support contact for non-active states |
| Pending actions | Outstanding tasks: incomplete KYC documents, unsigned policies, or listing rejections requiring attention |
| Recent order summary | Count of new, in-progress, and completed orders in the current period |
| Listing status summary | Count of live, draft, under-review, and rejected listings |
4. Catalog & Listing Management
Overview
The Catalog & Listing Management module is the seller's primary workspace for product creation and management. It is powered by FCC Catalog (the platform's product lifecycle management system) and exposes catalog capabilities through a seller-appropriate UI.
Status: ✅ Live
For full technical detail on the underlying catalog system — ingestion pipeline, validation rules, QC workflow, and product data model — refer to the FCC Catalog Product Documentation.
4.1 Product Listing Creation
Sellers create product listings through a guided form interface. The form structure adapts dynamically based on the vertical (product type) the seller selects — each vertical has a specific attribute schema defining which fields are mandatory, optional, or identity attributes.
Listing creation methods:
| Method | Description |
|---|---|
| Guided form (single listing) | Seller selects a vertical, fills in attributes, uploads images, and submits. Real-time validations fire as the seller fills the form. |
| Bulk upload (CSV) | Sellers upload a CSV template for high-volume listing creation. The template is vertical-specific and downloadable from the portal. |
| API integration | Sellers with technical integration can submit Product Creation Requests (PCRs) directly via the Catalog API, bypassing the UI for every operation. |
Validation feedback:
The portal provides immediate validation feedback during form completion — mandatory field indicators, allowed value dropdowns, image requirement guidance, and attribute-level error messages. This reduces post-submission rejection rates by surfacing issues before the request reaches the QC pipeline.
4.2 Listing Lifecycle and Status
Every listing moves through a defined lifecycle from draft to live. Sellers can track the status of each listing from the Catalog section of the portal.
Status: ✅ Live
| Listing State | Description |
|---|---|
| Draft | Listing created but incomplete or not yet submitted for review |
| Under Review | Submitted and currently in QC pipeline — awaiting operator or system validation |
| Live | Listing approved and discoverable on the marketplace |
| Rejected | Listing failed QC. Rejection reason code and guidance visible to seller. Seller can edit and resubmit. |
| Suppressed | Listing was previously live but has been removed from discovery — due to policy violation, stock depletion, or operator action — without being deleted |
| Inactive | Seller has paused the listing. Not discoverable but retained in the seller's catalog. |
4.3 Listing Edit and Update
Sellers can edit existing listings from the portal. Not all attributes are editable after a listing goes live — identity attributes (brand, model, EAN/GTIN) are locked post-creation. Non-identity attributes (price, description, images, optional specs) can be updated at any time and take effect after a validation pass.
Status: ✅ Live
Edit constraints:
| Attribute Type | Editable After Live? | Notes |
|---|---|---|
| Identity attributes (brand, model, GTIN) | No | Changes to identity attributes require creating a new listing |
| Mandatory attributes (title, category, key specs) | Yes | Subject to re-validation on save |
| Optional attributes | Yes | Updates reflected without full QC re-review |
| Price | Yes | Real-time; reflected on the marketplace within minutes |
| Images | Yes | New images go through media internalisation before replacing existing |
4.4 Bulk Catalog Operations
For sellers managing large catalogs, the portal supports bulk operations beyond initial upload.
Status: ✅ Live
| Operation | Method | Description |
|---|---|---|
| Bulk listing creation | CSV upload | Create multiple new listings using a vertical-specific template |
| Bulk price update | CSV upload | Update prices across multiple listings in a single file |
| Bulk availability toggle | CSV upload | Set listings active or inactive in bulk |
| Bulk status download | CSV export | Export current listing status, rejection reasons, and attribute values for the seller's full catalog |
4.5 Image Management
Images are a core attribute of every listing. The portal provides guided image upload with pre-submission validation for format, resolution, aspect ratio, and count requirements. Images are internalised into FCC's CDN upon upload.
Status: ✅ Live
Image requirements (operator-configurable by vertical):
| Requirement | Standard Setting |
|---|---|
| Accepted formats | JPEG, PNG |
| Minimum count | Configurable per vertical (typically 1 required, 3+ recommended) |
| Aspect ratio | Square (1:1) for most verticals; configurable |
| Background | White or neutral for primary image (operator-configurable) |
| Prohibited content | Promotional overlays, watermarks, or pricing text on primary images |
5. Order & Inventory Management
Overview
The Order & Inventory Management module gives sellers a unified view of their order pipeline — from new order placement through fulfilment, delivery, and returns — along with tools to manage product availability.
Status: ✅ Live
5.1 Order Management
The Orders section surfaces all orders placed for the seller's listings on the operator's marketplace. Orders are created and owned by the FCC Order Management System (OMS); the Seller Portal provides the seller-facing view and action interface.
Order views:
| View | Description |
|---|---|
| New orders | Orders placed and awaiting seller acknowledgement or action |
| In progress | Orders acknowledged and in active fulfilment — packaging, dispatch, or in transit |
| Completed | Delivered orders with payment settlement initiated or completed |
| Cancelled | Orders cancelled by buyer, seller, or operator — with cancellation reason and refund status |
| Returns & Refunds | Return requests raised by buyers — with return reason, return status, and refund state |
Order-level detail:
Each order record shows order ID, buyer location (city/state, not personal details), item details (listing ID, quantity, variant), price and platform fee breakdown, expected delivery SLA, and shipping label generation for applicable fulfilment modes.
5.2 Fulfilment Modes
The FCC marketplace supports multiple fulfilment models. The seller's applicable fulfilment modes are configured by the operator during onboarding.
Status: ✅ Live
| Fulfilment Mode | Description |
|---|---|
| Seller Fulfilled | Seller ships the order directly to the buyer using their own logistics or a third-party courier. Shipping labels generated via the portal. |
| Marketplace Fulfilled (OFC) | Seller ships inventory to an FCC-operated fulfilment centre (OFC). FCC handles pick, pack, and delivery. Faster delivery SLA; higher fulfilment cost. |
| Drop-Ship | Order details are forwarded to the seller or supplier for direct shipment to the buyer without the seller handling inventory. |
5.3 Returns and Refunds
The portal provides a return management workflow for sellers. When a buyer raises a return request, the seller is notified and can review the return reason, approve or dispute the return (within operator-configured return policy), and track the return and refund status.
Status: ✅ Live
| Return Step | Seller Action |
|---|---|
| Return request raised | Seller is notified; can view reason code and buyer's stated reason |
| Approval/dispute window | Seller can accept or dispute the return within the operator-configured SLA |
| Item received back | Seller confirms receipt; refund is initiated to buyer |
| Refund settled | Refund amount deducted from seller's next payout statement |
5.4 Inventory Management
Sellers manage product availability and stock levels from the Inventory section. Stock updates made in the portal are reflected on the marketplace listing in near real-time.
Status: ✅ Live
| Capability | Description |
|---|---|
| Manual stock update | Seller edits stock level per listing directly from the portal |
| Bulk stock update | CSV upload to update stock levels across multiple listings simultaneously |
| Listing pause / resume | Seller can set a listing to Inactive (removes from discovery) and resume without re-submitting for QC |
| Low stock indicator | Portal flags listings with stock levels below a configurable threshold |
| Out-of-stock handling | When stock reaches zero, the listing is automatically suppressed from buyer-facing discovery until stock is replenished |
6. Payments & Settlements
Overview
The Payments & Settlements module gives sellers visibility into their financial position on the marketplace — payout cycles, settlement statements, deductions, and payment history.
Status: ✅ Live
6.1 Payout Structure
Payouts are disbursed on the operator-configured payout cycle (typically weekly or bi-weekly). The payout for each order is computed as the order value minus the platform's applicable deductions.
Payout computation:
Seller Payout = Order GMV
− Platform Commission (%)
− Logistics Charge (if marketplace fulfilled)
− Payment Gateway Fee
− Returns Deduction (if applicable)
− Penalty Deductions (if applicable)
─────────────────────────────────────────
= Net Payout to Seller
6.2 Payout Statements
Sellers access their payout history from the Payments section. Each payout statement is downloadable as a PDF or CSV for the seller's accounting records.
Status: ✅ Live
| Statement Component | Description |
|---|---|
| Payout cycle | Start and end date of the settlement period covered |
| Gross GMV | Total order value for the period before any deductions |
| Total deductions | Aggregated deductions across commission, logistics, gateway, and returns |
| Net payout | Final amount disbursed to the seller's registered bank account |
| Order-level breakdown | Line-by-line view of each order included in the payout |
| Adjustment notes | Any manual adjustments or corrections applied to the period's payout |
6.3 Payment History
A chronological record of all past payouts is accessible from the portal, with filtering by date range, payout status, and order reference.
Status: ✅ Live
| Payment Status | Description |
|---|---|
| Pending | Payout cycle has closed but disbursement has not yet been initiated |
| Processing | Disbursement initiated; awaiting bank processing |
| Completed | Funds deposited to the seller's registered bank account |
| On Hold | Payout withheld pending review — reason code shown to seller with support contact |
6.4 Bank Account Management
Sellers can update their registered bank account details from the account settings section. Bank account changes require reverification to prevent fraud. The new account is verified before the next payout cycle is processed.
Status: ✅ Live
7. Operator Configuration Layer
Overview
The Operator Configuration Layer is the operator-facing surface of the Seller Portal platform. It gives marketplace operators the tools to configure and manage their seller ecosystem — defining eligibility rules, approving sellers, setting commission structures, and monitoring marketplace health — without requiring FCC engineering intervention for standard configuration changes.
Status: ✅ Live (Core configuration; advanced self-serve configuration — Coming Soon)
7.1 Seller Management Console
The Seller Management Console is the operator's primary workspace for managing their seller base.
Status: ✅ Live
| Capability | Description |
|---|---|
| Seller application review | View, approve, or reject seller registration applications. Add rejection reason codes communicated to the applicant. |
| KYC document review | Access submitted KYC documents per seller. Approve, request additional documents, or reject with reason codes. |
| Seller status management | Activate, suspend, or deactivate sellers with documented reason codes. Suspended sellers cannot list or fulfil orders. |
| Seller search and filter | Search the seller base by name, ID, registration status, GMV, or category. |
| Seller profile view | Full view of a seller's registration details, KYC status, listing count, order metrics, and payout history. |
7.2 Commission and Fee Configuration
Operators configure the platform fees applied to each seller payout. Fee structures are set at the category level and can be varied by seller tier.
Status: ✅ Live
| Fee Type | Configuration Scope |
|---|---|
| Platform commission | Configured as a percentage of GMV per category or subcategory |
| Logistics charge | Fixed or variable rate applied for marketplace-fulfilled orders |
| Payment gateway fee | Pass-through or absorbed by operator — configurable |
| Penalty rules | Late dispatch, SLA breach, and return-related penalties — rates and triggers configurable |
7.3 Category and Eligibility Rules
Operators configure which sellers are permitted to list in which categories. Eligibility rules can be based on seller tier, KYC status, GMV history, or category-specific compliance requirements.
Status: ✅ Live
| Configuration | Description |
|---|---|
| Category access by seller type | Different seller types (individual, registered business, brand-authorized) may have different category access |
| Mandatory compliance documents | Operators specify documents required per category (e.g., FSSAI licence for food, BIS certification for electronics) |
| Seller tier thresholds | GMV and performance thresholds that govern tier assignment — which determines fee structures and visibility boosts |
7.4 Approval Workflows
Operators configure whether seller registration, listing submissions, and category applications follow automatic or manual approval flows.
Status: ✅ Live
| Workflow Type | Description |
|---|---|
| Auto-approve | Applications meeting defined criteria are approved without human review |
| Manual review | All applications enter a queue for operator ops team review |
| Conditional auto-approve | Applications meeting criteria are auto-approved; exceptions are routed to manual review |
7.5 Operator Reporting
The operator admin panel provides summary-level reporting on marketplace and seller health.
Status: ✅ Live
| Report | Description |
|---|---|
| Seller onboarding funnel | Registration → KYC submission → KYC approved → First listing → Active seller conversion rates |
| Seller GMV summary | GMV by seller, category, and period. Exportable as CSV. |
| Order metrics | Orders created, fulfilled, cancelled, and returned by period. Seller-level drill-down available. |
| Payout disbursement log | All payouts processed in a period — amount, status, and seller breakdown |
8. Notifications & Communication
Overview
The Notifications module delivers business-critical alerts to sellers and operators through in-portal notifications and email. Notifications are event-triggered — they fire when a relevant state change occurs in an underlying FCC system.
Status: ✅ Live
8.1 Seller Notifications
| Event Trigger | Notification Channel |
|---|---|
| New order placed | In-portal + Email |
| Order cancellation | In-portal + Email |
| Return request raised | In-portal + Email |
| Listing approved / rejected | In-portal + Email |
| KYC status update | In-portal + Email |
| Payout processed | In-portal + Email |
| Account status change (suspension, reactivation) | In-portal + Email |
| Policy update requiring seller acknowledgement | In-portal + Email |
8.2 Operator Notifications
| Event Trigger | Notification Channel |
|---|---|
| New seller registration application | In-portal |
| KYC documents submitted | In-portal |
| Seller SLA breach threshold reached | In-portal |
| Payout batch processing complete | In-portal + Email |
8.3 Notification Configuration
Operators can configure which notification types are active, the email sender identity, and the content of standard notification templates. Template customisation is available for all standard notification types.
Status: ✅ Live
9. Capability Summary
| Capability | Module | Status |
|---|---|---|
| Self-serve seller registration (web) | Onboarding | ✅ Live |
| Operator-invited seller registration | Onboarding | ✅ Live |
| Bulk seller import | Onboarding | ✅ Live |
| KYC document upload and review | Onboarding | ✅ Live |
| Seller agreement and policy acceptance | Onboarding | ✅ Live |
| Account activation and seller dashboard | Onboarding | ✅ Live |
| Seller onboarding < 48hr activation | Onboarding | 🔜 Coming Soon |
| Guided form listing creation (single) | Catalog | ✅ Live |
| Bulk listing creation (CSV) | Catalog | ✅ Live |
| API-based listing creation | Catalog | ✅ Live |
| Listing lifecycle tracking (status, reason codes) | Catalog | ✅ Live |
| Listing edit and attribute update | Catalog | ✅ Live |
| Bulk price and availability update | Catalog | ✅ Live |
| Image upload and validation | Catalog | ✅ Live |
| Listing Quality Score + AI fix suggestions | Catalog | 🔜 Coming Soon |
| AI Listing Assistant (auto attribute fill) | Catalog | 🔜 Coming Soon |
| Order view (new, in-progress, completed, cancelled) | Orders | ✅ Live |
| Seller-fulfilled and marketplace-fulfilled modes | Orders | ✅ Live |
| Returns and refund workflow | Orders | ✅ Live |
| Manual and bulk inventory update | Inventory | ✅ Live |
| Low-stock indicator and out-of-stock suppression | Inventory | ✅ Live |
| Payout statements (with deduction breakdown) | Payments | ✅ Live |
| Payment history and status | Payments | ✅ Live |
| Bank account management and verification | Payments | ✅ Live |
| Net payout per SKU (pre-listing fee calculator) | Payments | 🔜 Coming Soon |
| Seller management console (approve / suspend) | Operator Config | ✅ Live |
| Commission and fee configuration per category | Operator Config | ✅ Live |
| Category eligibility and compliance rules | Operator Config | ✅ Live |
| Manual and auto approval workflow configuration | Operator Config | ✅ Live |
| Operator reporting (GMV, orders, payouts) | Operator Config | ✅ Live |
| White-label branding configuration (self-serve) | Operator Config | 🔜 Coming Soon |
| No-code operator commission and workflow builder | Operator Config | 🔜 Coming Soon |
| Event-triggered seller notifications (in-portal + email) | Notifications | ✅ Live |
| Notification template customisation | Notifications | ✅ Live |
| Advanced Analytics Dashboard (GMV, orders, returns) | Analytics | 🔜 Coming Soon |
| Seller Homepage Dashboard v2 with AI action feed | Dashboard | 🔜 Coming Soon |
| Competitive Pricing Intelligence | Intelligence | 🔜 Coming Soon |
| Peer Benchmarking | Intelligence | 🔜 Coming Soon |
| Seller App (iOS + Android) | Mobile | 🔜 Coming Soon |
10. Market Context and Strategic Vision
The Opportunity
Marketplace software is a $3.5B global market growing at 12–15% CAGR, driven by the rapid expansion of third-party (3P) marketplace models among traditional retailers globally. FCC's primary geographies — MENA, APAC, LATAM, ANZ, and US — represent the fastest-growing segments of this market.
| Geography | Key Driver | FCC Positioning |
|---|---|---|
| MENA (UAE, KSA, Kuwait) | Retail digitalisation; 3P marketplace adoption by hypermarkets and fashion retailers | Active deployments; pipeline in Gulf markets |
| ANZ (Australia, New Zealand) | Established retail marketplace market; competitive with 3P models | Active pipeline; go-live speed advantage vs local alternatives |
| APAC (Singapore, SEA) | High mobile commerce penetration; regional marketplace expansion | Pipeline; language adaptation investment planned |
| LATAM | VTEX-dominated; composable stack demand growing | Pipeline; composability story resonates |
| US | Largest mid-market retail tech market; Mirakl displacement opportunity | Active enterprise pipeline |
FCC's Right to Win
| Differentiator | Description |
|---|---|
| Battle-tested at scale | Seller Portal infrastructure built on Flipkart's live marketplace — proven at millions of sellers and hundreds of millions of SKUs. No startup can replicate this foundation. |
| 10-week go-live | Fastest enterprise go-live in the market — 10 weeks vs 16–24+ weeks for Mirakl and VTEX. A direct commercial advantage in every deal. |
| 1P + 3P native | FCC natively supports both first-party and third-party inventory in one platform. Competitors require workarounds. |
| Integrated stack | Seller Portal, Catalog, OMS, Fulfilment, Payments, and Retail Media in one integrated stack. Lower TCO than assembling point solutions. |
| Operator configurability | Each FCC operator runs a fully isolated, configurable instance. No seller data, pricing, or business logic crosses tenant boundaries. |
Competitive Landscape
| Competitor | Profile | FCC Differentiation |
|---|---|---|
| Mirakl | $203M ARR; 450+ enterprise clients; 350+ seller network (Mirakl Connect) | FCC wins on go-live speed (10 wks vs 16–20 wks), 1P+3P native, and platform scale proof. Mirakl leads on analyst recognition and operator config depth — gaps FCC is closing. |
| VTEX | Dominant LATAM enterprise base; headless composable | FCC's integrated OMS + WMS + Seller Portal is a lower-TCO alternative. VTEX has stronger LATAM relationships. |
| Spryker | B2B + B2C composable architecture; EU-focused | FCC wins on speed and integrated logistics moat. Spryker has B2B catalog depth advantage. |
| In-house builds | Operators who have built proprietary marketplace platforms | FCC displaces these with a faster, lower-cost, higher-capability alternative — especially for operators approaching scale. |
Strategic Vision
The FCC Seller Portal's north star is to be the most capable, easiest-to-use seller interface for multi-tenant marketplaces globally — closing the experience gap with Amazon Seller Central and Shopify while delivering capabilities no single-tenant platform can match.
Three investment themes define the roadmap:
Seller Intelligence. Move from a transactional interface (do the task) to an intelligent one (surface the right action at the right time). Analytics, benchmarking, and AI-generated recommendations are the priority gap to close.
Operator Configurability. Eliminate the dependency on FCC engineering for marketplace configuration changes. Every standard configuration — commission rules, approval workflows, branding, category eligibility — should be self-serve through the operator admin portal.
Multi-Market Readiness. Ensure the Seller Portal works without modification across MENA, APAC, LATAM, and ANZ — supporting local languages, currencies, tax regimes, and logistics providers.
11. Metrics and Measurement
Seller Engagement Metrics
| Metric | Definition | Target Direction |
|---|---|---|
| Seller activation rate | % of registered sellers who complete KYC and create their first live listing within 30 days | Maximise |
| Time to first live listing | Days from seller registration to first listing approved and live | Minimise |
| Daily active seller rate | % of active sellers who log into the portal on a given day | Maximise |
| Session depth | Average number of pages or actions per seller session | Track; low session depth indicates confusion or poor UX |
| Seller NPS | Net Promoter Score collected from sellers at defined intervals | Maximise |
Catalog and Listing Quality Metrics
| Metric | Definition | Target Direction |
|---|---|---|
| Listing submission-to-live rate | % of submitted listings that reach Live state without seller resubmission | Maximise |
| First-attempt QC pass rate | % of listings that pass QC on first submission | Maximise |
| Listing rejection rate | % of submitted listings rejected at QC | Minimise |
| Average time to listing approval | End-to-end time from PCR submission to Live state | Minimise |
| Suppression rate | % of live listings suppressed due to stock, policy, or operator action | Track |
Order and Fulfilment Metrics
| Metric | Definition | Target Direction |
|---|---|---|
| Order dispatch SLA compliance | % of orders dispatched within the operator-configured SLA | Maximise |
| Cancellation rate | % of orders cancelled (buyer + seller cancellations) | Minimise |
| Return rate | % of delivered orders returned by buyers | Minimise |
| Seller-induced cancellation rate | % of cancellations initiated by the seller (vs. buyer) | Minimise |
Financial and Payout Metrics
| Metric | Definition | Target Direction |
|---|---|---|
| Payout accuracy rate | % of payouts disbursed correctly without adjustments | Maximise |
| Payout dispute rate | % of payouts disputed by sellers | Minimise |
| Average GMV per active seller | Total marketplace GMV ÷ active seller count for the period | Maximise |
| Seller revenue retention | % of sellers who maintain or grow GMV quarter-over-quarter | Maximise |
Operator Configuration and Health
| Metric | Definition | Target Direction |
|---|---|---|
| Operator onboarding time | Weeks from contract to first live marketplace | Minimise (target: 10 weeks) |
| Seller ops ticket volume | Volume of seller support tickets per active seller per month | Minimise |
| Seller onboarding funnel conversion | % conversion at each step: registered → KYC submitted → KYC approved → first listing live | Maximise at each step |
12. Onboarding Checklist
Overview
Standard FCC Seller Portal operator onboarding takes approximately 8 to 10 weeks from contract finalisation to first live seller and first live listing, depending on integration complexity, catalog schema setup, and KYC workflow configuration.
Phase 1: Marketplace Configuration
| Task | Owner |
|---|---|
| Define seller types and eligibility criteria for the marketplace | Operator + FCC |
| Configure KYC document requirements per seller type and category | Operator + FCC |
| Set up commission and fee structures per product category | Operator |
| Configure approval workflow: auto-approve, manual review, or conditional | Operator + FCC |
| Define payout cycle (weekly, bi-weekly, monthly) and payout computation rules | Operator + FCC |
| Configure category-level compliance document requirements | Operator |
| Set up operator branding on the Seller Portal (logo, colors, domain) | Operator Engineering + FCC |
Phase 2: Catalog Schema Setup
| Task | Owner |
|---|---|
| Define taxonomy structure and initial verticals for the marketplace | Operator Catalog Ops + FCC |
| Configure attribute schemas per vertical (mandatory, optional, identity attributes) | FCC + Operator |
| Set image requirements per vertical (format, count, aspect ratio) | Operator + FCC |
| Configure QC modes per vertical (Strict, Relaxed, Eventual) | Operator + FCC |
| Create bulk upload CSV templates per vertical for seller distribution | FCC |
| Validate end-to-end PCR flow in staging: submission → AV → QC → Live | Operator Engineering + FCC |
Phase 3: Technical Integration
| Task | Owner |
|---|---|
| Integrate Seller Portal with operator's identity provider (SSO, if applicable) | Operator Engineering + FCC |
| Configure email sender identity for seller notifications | Operator |
| Customise standard notification email templates (order, payout, KYC) | Operator |
| Set up Seller Portal API integration for sellers using API-based listing | Operator Engineering + FCC |
| Integrate Payments system: seller bank account verification, payout API | Operator Engineering + FCC |
| Configure OMS integration for order routing from marketplace to Seller Portal | Operator Engineering + FCC |
| Validate end-to-end order flow in staging: order placed → seller notified → fulfilled → payout | Operator Engineering + FCC |
Phase 4: Seller Operations Setup
| Task | Owner |
|---|---|
| Set up operator seller ops team access to the admin console | Operator |
| Train seller ops team on KYC review, listing moderation, and seller management workflows | Operator Ops + FCC |
| Onboard first cohort of pilot sellers (5–15 sellers recommended) | Operator Ops |
| Monitor KYC approval TAT and listing approval rates for first two weeks | Operator Ops + FCC |
| Review seller feedback from pilot cohort; resolve configuration issues before full launch | Operator + FCC |
| Establish seller support SLA and escalation path | Operator |
Phase 5: Go Live
| Task | Owner |
|---|---|
| Launch marketplace with pilot seller cohort; monitor order flow and payout cycle | Operator + FCC |
| Open self-serve registration to broader seller base | Operator |
| Establish weekly marketplace health review cadence (seller activation, GMV, NPS) | Operator + FCC |
| Plan first payout cycle disbursement and validate accuracy | Operator + FCC |
| Define quarterly seller satisfaction measurement approach | Operator + FCC |
Glossary
| Term | Definition |
|---|---|
| Active Seller | A seller with at least one live listing and at least one order in the measurement period |
| Approval Workflow | Operator-configured rules governing whether seller registrations, listings, or category applications are auto-approved, manually reviewed, or conditionally routed |
| BAL | Brand Authorization Letter — a document submitted by a seller to prove they are authorized to sell a registered brand's products |
| Commission | The percentage of order GMV retained by the operator as the platform fee for facilitating the sale |
| Draft | A listing state representing an incomplete or unsubmitted product record. Not discoverable by buyers. |
| FCC | Flipkart Commerce Cloud |
| GMV | Gross Merchandise Value — the total value of goods sold on the marketplace before any deductions |
| KYC | Know Your Customer — the identity and business verification process sellers complete before their account is activated |
| Listing | A seller's record of intent to sell a specific product at a specific price and availability on the operator's marketplace. Distinct from the product entity, which is managed by FCC Catalog. |
| Live | A listing state indicating the listing has been approved and is discoverable by buyers on the marketplace |
| MACH | Microservices, API-First, Cloud-Native SaaS, Headless — the architectural standard the FCC Seller Portal is built on |
| Multi-tenant | An architecture where a single platform instance serves multiple operator clients, each with fully isolated data and configuration |
| Net Payout | The amount disbursed to a seller after all deductions (commission, logistics, gateway fees, returns) are subtracted from gross GMV |
| OFC | Operator Fulfilment Centre — a warehouse operated by or on behalf of the operator. Sellers ship inventory to the OFC; the operator handles pick, pack, and delivery. |
| OMS | Order Management System — FCC's system responsible for order creation, routing, status management, and cancellation |
| Operator | A retailer or marketplace that has deployed FCC's platform to power their multi-seller marketplace. The operator is the FCC client. |
| PCR | Product Creation Request — the event triggered when a seller submits a new product for listing on the marketplace |
| Payout Cycle | The operator-configured period (weekly, bi-weekly, monthly) at the end of which net earnings are calculated and disbursed to sellers |
| Payout Statement | A per-cycle financial document showing a seller's gross GMV, itemised deductions, and net payout amount |
| QC | Quality Check — the process of validating that a seller's listing meets the operator's catalog quality and compliance standards before going live |
| Rejection | A listing state where the submitted listing has failed QC. The seller receives a reason code and can edit and resubmit. |
| Return Rate | The percentage of delivered orders that are returned by buyers within the operator's return policy window |
| Seller | A merchant who registers on an FCC-powered marketplace to list and sell products to end buyers |
| Seller Fulfilment | A fulfilment mode where the seller packages and ships orders directly to buyers using their own or a third-party courier |
| Seller Tier | A classification assigned to sellers based on performance metrics (GMV, fulfilment rate, return rate). Tier determines fee rates, listing visibility boosts, and access to marketplace features. |
| SLA | Service Level Agreement — the time-bound commitment for a specific action (e.g., seller must dispatch an order within 48 hours of placement) |
| Suppressed | A listing state where a previously live listing has been removed from buyer-facing discovery — due to stock depletion, policy violation, or operator action — without being deleted |
| Tax ID | VAT, GST, or equivalent tax registration number required from sellers during KYC for the operator's market jurisdiction |
| Vertical | The lowest level of product taxonomy — a homogenous grouping of products (e.g., Mobile Phones, T-Shirts, Televisions) with a defined attribute schema |
| White-label | The operator's ability to present the FCC Seller Portal under their own brand identity — with their logo, domain, color scheme, and fonts — rather than FCC's branding |
| WMS | Warehouse Management System — FCC's system for managing inventory receipt, storage, pick, pack, and dispatch at operator fulfilment centres |
© 2026 Flipkart Commerce Cloud — Confidential. For Publisher and Partner Use Only.