Flipkart B2C Dropship

Inventory Sync

Inventory update goes to the channel in a batch of 10

YES 

For inventory update, we need the product_id (the channel serial no of CIMS) and the channel_sku_id.

Forward Orders Sync

• Order Fetching: By status, time, location ID

• Shipment Details: Retrieved from Flipkart API, includes address

• Order State: New orders are APPROVED

• Processing:

  • Channel → Intergration → DB

  • Syncs to CIMS in configurable batches (default: 100)

 YES

• Order ID:

  • shipment_id as channel order ID

  • parent_order_id for Flipkart order ID

• API Calls:

  • Retrieves 20 orders per call

  • Provides nextPageUrl for the next batch

• Error Handling:

  • If fetching fails, return successfully received orders

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:

• PACK_CONFIRM: to mark shipment as packed on flipkart

If DISPATCH_IN_PACK is true

• CREATE_MANIFEST call is made to channel

YES

• Get order by shipment_id

• Verify no line items are cancelled and quantity is correct

• Mark shipment as packed using API

• Status changes from APPROVED to PACKED on the channel

• External shipment ID is the channel order ID for Flipkart

Invoicing

Multiple calls made to Flipkart marketplace to:

• Get invoice and shipping label pdf

• Get invoice details

 YES

• The invoice and shipping label documents are the same.

• Delays in receiving the invoice can cause a PACKING IN PROGRESS error from Flipkart marketplace, which resolves automatically.

• After packing, the AWB number and transporter details are updated in the shipment details on the marketplace.

Manifest

Call made to Flipkart marketplace to:

• CREATE_MANIFEST (Marketplace creates manifest at their end)

• Get order status call to check if all line items are moved to RTD(READY_TO_DISPATCH)

 YES

• Create manifest call is made in batches of 20.

• Verify all orders are PACKED before marking as RTD.

• In Flipkart marketplace, moving an order to RTD adds it to an open manifest based on the transporter.

• Generate an external manifest ID using an order ID and epoch time for tracking.

Handover

API call from Increff to Flipkart systems:

• GET Vendor data (vendor details like transporter code, isMPS, pickup details are fetched)

• GET manifest PDF(manifest pdf created by marketplace is fetched)

 YES

• Flipkart marketplace fetches manifest documents by transporter/vendor group codes.

• One open manifest per transporter/location at a time.

• To fetch a manifest, integration used the vendor group code(seller code) from the vendor data channel API.

• Increff provides the external manifest ID, integration maps transporters to vendor group codes.

• Manifest can only be fetched if the vendor data API shows open manifests for the transporter.

Forward Order Customer Cancellation

• Flipkart marketplace pushes customer cancellations to the integration in the forward order notification call.

• Cancellations are also retrieved via the get cancellation call.

 YES

Cancellations are fetched for the last 5 hours via a paginated API call.

Forward Order Seller Cancellation

• Partial seller cancellation is supported.

• Seller cancellations are permitted only before the packing stage.

Replacement/Exchange Order Sync

Forward order mapping to replacement orders is supported if replacements are enabled in the integration.

Return Order Sync

• Pull call is get return orders API 

• Flipkart marketplace also pushes return orders to integration, in return order notification which is synced to CIMS in batches (100 default)

• The API fetches returns from the previous day; longer periods may timeout.

• Each call returns 25 orders, integration uses the next page URL for more.

• No location filter, removes non-relevant returns in the integration.

• For multiple quantities, integration creates separate line items with unique IDs, adding suffixes like "_1".

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 update return order push call.

 YES

Cancellation Reasons

• SELLER_REJECTED: Cancellation initiated by seller.

• MARKETPLACE_CANCELLATION: Cancellation initiated by marketplace.

Return Reasons

• Customer return in case of Size, colour etc mismatch

• RTO in case of three delivery attempt failure

• RTO in case of courier rejection

Replacement Orders

• Replacement orders are treated as new orders.

• Parent order code is same for both others and charge for replacement order is 0.

Cancellation Support

Cancellation is supported until order is PACKED

API Performance

1. UPDATE_INVENTORY : 500 ms

2. PULL_ORDERS : 500 ms

3. PACK_ORDER : 200 ms

4. PUSH_ORDERS : 30 ms

5. MANIFEST : 400 ms

Seller onboarding credentials 

 Seller’s Flipkart Account Username and Password