| Table of Contents | ||
|---|---|---|
|
Marketplace Overview
Flipkart
...
Model Type
...
B2C Dropship
Seller Fullfillment Non FBF
...
Geo
...
South Asia
...
Applicable
Countries
...
India
...
Integration
provided by MP?
...
Yes
...
Increff Integrations Status
...
Live
...
Integration Type
...
API
...
Integration Mechanism (Standard, Omni Magic)
...
Standard
...
OMS
...
Marketplace OMS - Order routing splitting is done by MP
...
Spl Remarks
...
Seller Fulfillment (Smart 3.0): Based on the performance of the Seller and respective listings, Flipkart awards F-Assured status to these automatically to the listings, while in Seller Fulfillment model. This model works on the same Seller Fulfillment APIs and is integrated with Increff Omni. Click here for further details. You may need seller panel credentials to access this link.
...
Guardrails for Special Status
...
MP Guardrail for Gold Status:
Revenue more than 50 Lakhs or Units more than 6,000
Seller Cancellation - Less than 0.15%
RU >= 20%
RTD Breaches - Less than 1%
Customer Returns - Vertical benchmark
Product Rating - Vertical benchmark
Mp Omni Guardrial for Gold Status:
Seller Cancellations - 1.5%
Dispatch SLA breach - 7%
https://docs.google.com/presentation/d/1IVuRiklQvkP8VC1DWlcCcV7XacKpybD0Z2XkHOE9KlM/edit?usp=sharing
...
Benefits for Seller
...
Payment will be 7 days after delivery instead of 15 days.
20% discount on forward shipping fee.
Priority Support (Flipkart CareTouch) for issues raised. Resolution timelines reduced to few hours from standard SLA of 24 to 48 hours.
Higher visibility for Gold Seller's products vs Silver and Bronze.
Account Manager assigned to Gold Tier Sellers.
Gold Tier Sellers can participate in Exclusive Flipkart Events
...
Seller Rating Rivision Frequency
...
Every 3 months
...
Suspension Criteria
...
i) Seller Cancellations Rate: 0.25%. Failing to maintain the benchmark percentage will result in account suspension for a minimum period of 3 days.
ii) RTD Breach Rate: 0.5%. Failing to maintain the benchmark percentage will result in account suspension for a minimum period of 1 day.
iii) Reattempts Rate: 2%. Failing to maintain the benchmark percentage will result in account suspension for a minimum period of 1 day.
...
Inventory
Update
...
Yes
...
Order
Creation
...
Yes
...
Acknowledgment
...
No
...
Hold
...
No
...
Unhold Order
...
NO
...
Customer
Cancellation
...
Yes
...
Seller
Cancellation
...
Yes
...
Create
Shipment (Pack)
...
Yes
...
Fetch
Invoice
...
Yes
...
Fetch
Shipping Label
...
Yes
...
Create
Manifest
...
Yes
...
Fetch Manifest Document
...
Yes
...
Handover
Update
...
No
...
Return
Order
Creation
...
Yes
...
Return
Processed
...
No
...
Search
Inventory
...
No
...
Update Order Properties
...
Yes ( Push based only)
...
Partial Customer Cancellation
...
Yes
...
Partial Seller Cancellation
...
Yes
...
Expiry Feature
Supported?
...
No
...
Client Names
( Many or specific if less)
...
Integration integrates Flipkart marketplace with Increff Omni for Flipkart’s B2C Dropship Model
Flipkart marketplace uses both push and pull models for order updates
Push Flow: Order updates are pushed directly from the Flipkart marketplace to the Flipkart integration.
Pull Flow: integration requests order updates from the marketplace based on filters (e.g., status, time).
Geography: India
Workflow Breakdown
Workflow | Description | Supported | Remarks |
|---|---|---|---|
Inventory Sync | Inventory update goes to the channel in a batch of 10 | YES | For inventory update, we need the |
Forward Orders Sync |
| YES |
|
Routing & Splitting | NA | NO | NA |
Forward Order Acknowledgement | Flipkart marketplace doesn’t have the functionality of acking the orders | NO | Used to pack the order if required |
Shipment | API Calls made from Increff to Flipkart sysetm:
If
| YES |
|
Invoicing | Multiple calls made to Flipkart marketplace to:
| YES |
|
Manifest | Call made to Flipkart marketplace to:
| YES |
|
Handover | API call from Increff to Flipkart systems:
| YES |
|
Forward Order Customer Cancellation |
| YES | Cancellations are fetched for the last 5 hours via a paginated API call. |
Forward Order Seller Cancellation |
|
|
|
Replacement/Exchange Order Sync |
|
| Forward order mapping to replacement orders is supported if replacements are enabled in the integration. |
Return Order Sync |
|
|
|
Return processed notification updates | The marketplace pushes return order updates to the integration, which syncs them to Increff omni system. | YES |
|
Return Order Cancellation | Synced to Increff system in the | YES |
|
Visualizing the Flow
| Drawio | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Marketplace-Specific Details
Property | Values |
|---|---|
Cancellation Reasons |
|
Return Reasons |
|
Replacement Orders |
|
Cancellation Support | Cancellation is supported until order is PACKED |
API Performance |
|
Channel Onboarding Details
Onboarding Steps
Seller Account Creation : A seller should have a seller account on Flipkart. With this seller account login they can register a third party application to it’s account. This registration will enable Increff’s Flipkart integration to access Flipkart APIs for that seller.
Seller Migration Managed by Increff: For this client needs to share the seller credentials with increff
Pull Flow onboarding:The Increff onboarding team uses the shared credentials to log into the Flipkart seller panel, request authorization, and obtain a code to generate access and refresh tokens, which are then used for API calls to the Flipkart marketplace.
Push Flow onboarding: Mail is sent to Flipkart marketplace to enable push notifications with the seller's registered email, notification URLs for orders and returns, location IDs, application ID, and client name.
Information required from Client for Channel Onboarding in Increff
Configuration Parameter | Remarks |
|---|---|
Seller onboarding credentials | Seller’s Flipkart Account |
Estimated Timeline
Pull Flow → 2 Business Days
Push Flow → 7-10 Business Days
FAQs
Q : Why do the channel credentials expire for Flipkart Marketplace and how is it fixed?
A: The refresh token for Flipkart expires after 180 days. When this happens, the Increff success team login to the Flipkart seller portal to generate a new token. Increff has alerts configured to notify the team whenever a call fails, ensuring the issue is resolved promptly.
Q: Can a client use both push and pull mechanisms simultaneously?
A: Yes, a client can use both push and pull mechanisms simultaneously. Both flows operate independently, ensuring that if an order is received through one mechanism, the other handles it idempotently.
Q: What is the PACK_IN_ACK flow and how does it work?
A: The Flipkart Marketplace often requires up to 4 hours to generate a shipping label after the pack confirmation call. To prevent delays, Increff mocks the pack confirmation call to the marketplace as soon as the inventory is allocated to the respective order. This helps streamline the process and avoid operational bottlenecks.
Q: How do replacement orders flow and how are they related to the original order?
A: Replacement orders are treated as new orders but share the same parent order code as the original order. Despite having the same parent order code, the original and replacement orders are treated independently in all other respects.