Tutorials¶
Our tutorials use fictitious scenarios to walk you through the various flows in the FMSAPIs.
Tutorial - Order Management Notifications¶
A customer can partially or fully cancel their orders before the order is marked “Ready to dispatch”. This tutorial uses two scenarios to demonstrate order cancellation and the associated notifications.
Note
If the customer cancels the order after it is marked “Ready to dispatch”, it is addressed in the returns flow.
Usecase 1: Full Cancellation¶
A customer has ordered four headsets and cancels it before it is marked “Ready to dispatch” by the seller.
Usecase 2: Partial Cancellation¶
A customer has ordered four headsets. She changes her mind and wants three headsets, so she cancels a part of the order. The seller has now packed the order with three headsets. The customer cancels another piece again and now, wants only two headsets in the final order.
Here, the buyer makes the second cancellation request after the seller sends the label request to the Flipkart System. The shipping label now contains the order details as recorded before the second cancellation, that is, for three headsets. In this case, a message to reprint the label (with the updated order details for two headsets) is displayed to the seller during “Request to dispatch”.
Tutorial - Seller FTP¶
This tutorial describes a scenario where a fictitious online retailer, Example.com, wants to start selling books in the Flipkart Marketplace. They are looking for a convenient solutions to exchange data between their domestic system and the Flipkart Marketplace.
Usecase: List Product and Post Stock and Price¶
Example.com has an inventory management system where they maintain the inventory for multiple online sales channels such as their Website, the Flipkart Marketplace, and so on. They intend to:
- List books using ISBN
- Post stock and price using the SKU ID
They have received their credentials for the Flipkart Marketplace FTP account from their account manager, which includes the following details:
- Username: This is the seller ID. For this tutorial, we will be using
ftplistingexample - Password: System generated password
- Account Address: The FTP account address. For this tutorial, we will be using ftplistingexample@cms.flipkart.com
They authenticate using the above credentials and set up the system scheduler to prepare the csv format bulk feed as:
| Flipkart Serial Number | Seller SKU ID | MRP | Your Selling Price | Local
Shipping
Charge
(per qty) |
Zonal
Shipping
Charge
(per qty) |
National
Shipping
Charge
(per qty) |
Your Stock Count | Procurement SLA | Listing Status | Selling Region Restriction | Procurement Type | Processing Errors |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 9780060007362 | 9780060007362 | 150 | 115 | 40 | 70 | 70 | 25 | 5 | Active | none | REGULAR | Listing Status is not Allowed to be updated. |
They upload the bulk feed to the input folder of their FTP account.
The Flipkart scheduler picks up the input file every 1 hour from each of these accounts and releases 2 outputs, one with the passed listings and one with the failed listings, in output folder. The following screenshot shows an FTP browser displaying the relevant files and folders, including the input and output folders and the input folder contents.
