Flipkart Omni
About Flipkart
Flipkart is an Indian e-commerce company, headquartered in Bangalore, Karnataka, India, and registered in Singapore. The company initially focused on online book sales before expanding into other product categories such as consumer electronics, fashion, home essentials, groceries, and lifestyle products.
Flipkart has both Inventory based model and Marketplace model. In inventory-based model, they create their own Inventory of products and dispatch the order from their own warehouses while Marketplace model has the main role of sellers. They pass on the order to the seller and take commission or selling fee in return and order is to be picked from the sellers’ centre and then delivered to the customer. Flipkart follows a crystal-clear Business-to-Consumer model or commonly known as a B2C model. It works as a Marketplace which means that it a middle platform that connects all interested sellers to various customers and assists in making the sale. With over 80 categories, Flipkart has sellers for all items, ranging from groceries, toiletries, clothes, books, shoes, furniture, electronics, etc.
Below are the List of Integration available for Flipkart Marketplace to configure in Vin-eRetail:
1. Flipkart v3.0 (Multi Warehouse)
2. Flipkart Assured
3. Flipkart Smart
4. Flipkart 2Gud
5. Flipkart Omni
Now this document is all about how to configure Flipkart Omni in Vin-eRetail for Product listing, Order Fulfilment and Return Management.
Flipkart Omni is basically a Ship by seller/Self Ship program of Flipkart.
For this Model we have:
1. SKU Pull
2. Order Pull/Create
3. Order Cancellation/Rejection Push (Make sure Push Item cancellation Flag on Manage Channel Screen is enabled).
4. Order Shipment
5. Order Return
6. Inventory Update
7. Inventory Reconciliation
Prerequisites
Email Needs to be set to seller-api-queries@flipkart.com having the seller Id and the Seller panel login user Id with the Mail Subject: Enable V3 Flag and the Email Body:
Hi Team,
Kindly enable the V3 flag for the below seller: -
Seller Id: (seller id of that client)
Seller Login Email Id: (seller login Id of that client)
(Or if the details shared to the client by Flipkart account manager that means that the V3 flag is also enabled, in that case there is no need to send any email to Flipkart)
Please use the Flipkart V3 channel only to configure Flipkart Omni as well.
Below mentioned Credentials are mandatory and required to configure Flipkart Omni for any Customer.
1. Flipkart User Id / Password - This required credential will be shared by seller/Brand once it is registered on Flipkart Marketplace.
2. Seller Id - Unique Id generated for each seller by Flipkart and same will be provided by seller for Channel configuration in Vin-eRetail.
3. Is Self-Ship – This flag should always be set to YES as this is a Self-ship channel.
4. Pull Completed Returns – This should also be set to YES.
5. API Key / API Password -Below are the steps that are involved to generate API Key and API Password itself through Flipkart Seller Portal login details shared by customer
a. Visit the given link - https://api.flipkart.net/oauth-register/login
b. This will navigate to the API generation page of Flipkart.
c. Now login to the panel with the given Username and password by the seller
d. Click on the “Register new application” for Application ID and Secret Key generation as shown below.
And fill the below details e. Enter the Application name and Application description as “API” and Register this application. As soon as you will register this application your Application Id (API Key) and Secret Key (API Password) will be visible to you.
f. Location ID – Location Id can also be retrieved from Flipkart Seller Portal under Manage Profile Pickup location section where all warehouse Location Pickup Address and Location Id available for Registered Seller [Refer below highlighted Snapshot for reference] . Make Sure before doing this configuration you already confirmed and discussed with customer for correct location setup
Or if the location Id is not present there then follow the below step: Go to Orders > Cancelled Orders screen > Select the location from the Location/Warehouse dropdown and then a URL will appear on the Browser having location ID in it as mentioned in the screenshot below:
Copy the Location Id between two forward slashes i.e., / and use the same in channel config. To Fetch the seller Id: a. Go to Orders Section. Right Click and select the Inspect Button.
b. Go to Network Section:
c. Click on fetch?sellerid= and scroll down and you will get the seller Id.
Once all configuration steps have been completed, then same details will be used to configure channel setup in Vin-eRetail [Refer below screenshot].
Channel Mappings
Flipkart Seller SKU code to be mapped in Channel SKU Code and Flipkart FSN id to be mapped in Channel Product ID.
Other details about Flipkart Omni Integration: (SKU Pull is running on non-API based method – Chances that SKUs are not pulled automatically so if the SKUs are not pulled automatically, please do the SKU Mappings manually).
• Multi-product shipments are NOT allowed in the Self-ship model
• COD orders are NOT allowed in Self-ship model.
• Fulfilment of an order/shipment must happen from a single store only. If a single store cannot fulfil the complete order, then the seller must cancel the order.
• Location Id in all the Flipkart APIs refers to the actual location for which the order was created at first. The location Id of the actual store from where the shipment is dispatched is taken in /dispatch API and used only for invoicing. e.g., if an order OD1 is created at location LOC1 and later dispatched from a store belonging to LOC2, then for all reporting purposes OD1 will be part of LOC1 only.
1. Once all the IDs are gathered, open your Vin eRetail instance and go to Sales>Manage Channel screen.
2. Go to the top right side of the window and click on “Add New.”
3. Select Flipkart Omni
4. Fill all the details like Channel Name, order Source WH, Order Sync from date, Return Sync from Date, SKU Pull from Date, Inventory Sync Method, Enable Inventory Reconciliation etc.
5. Click on “Configure Integration” and enter the details.
If Enable the is Self-Ship Flag to “YES” If the client is using the seller Ship mode Else select this as NO If the order is Ship by Marketplace.
6. Click on “OK” and “Save” the channel configuration.
7. The channel is successfully created and will be visible in manage channel screen.
Channel Maintenance
Channel Maintenance set up helps the seller to reduce manual intervention and avoid the multiple usage of marketplace seller portal. With the selection of below options at Channel Maintenance window (Sales>Manage Channels>Add New>Select FlipkartV3.0 Multiwareouse) in Vin E-retails instance, User can get the advantage of using multiple features of Vin E-retail:
S.No. | Feature(s) | Where to Click | Dropbox/Checkbox option | Details |
1. | SKU Pull | Channel Maintenance> Channel SKU>SKU Sync>Pull/Push |
| SKU Sync: SKU Sync between Channel and e-Retail can be done via PULL & PUSH. User can choose Pull to Pull the SKU’s from the channel to e-Retail panel. And User can choose Push to send the SKU data or changes from e-Retail to the channel.
|
2. | Order Pull/Order Pack/Invoice/Order Shipment/Shipping label generation | Channel Maintenance>Orders>Order Sync>Yes/No |
| Order Pull: User can choose to sync the order from the channel to e-Retail by managing this option. If this is disabled, the Order pull will not happen also the shipping label/Invoice and manifest will not get generated. |
3. | Order Return | Channel Maintenance>Orders>Return Order Sync |
| User can click this option to sync Return Orders. Important Note: In Return Pull Services, the “Return” is always created in Confirmed status. User need to do an inbound from Return Inbound functionality available on Application.
|
S.No. | Feature(s) | Where to Click | Dropbox/Checkbox option | Details |
4. | Prefetch Shipment Label | Channel Maintenance<Orders<PrePack Enabled checkbox |
| PrePack Enabled: User can enable prepack for the order from here. To avoid delay in Order processing and Shipment fulfilled with in a provided SLA, we have a feature to pull Flipkart shipment Label and Invoice at the same time of picklist generation instead of during Pack Call. To use this functionality, we just need to enable Prepack checkbox available under Channel Configuration set up screen and user need to click on Prefetch deliveries during pending picklist status available on Picklist enquiry screen.
|
5. | Ready to Ship Status at |
Channel Maintenance>Orders>Ready to Ship At
|
| User can choose to mark the status of ready to ship at any of the two events: -at Manifest or -at Pack
|
6. | Use Market Place Shipping Label | Channel Maintenance>Orders>Use Marketplace Shipping Label checkbox |
| User can check this option to notify the Shipping label by marketplace and then opt from the Shipment label drop box.
|
7. | Inventory update | Channel Maintenance>Inventory Sync |
| Automatically pull and update the inventory |
8. | Inventory Reconciliation | Channel Maintenance>Enable Inventory Recon |
| Despite Inventory Sync, at times, there is a possibility of Inventory mismatch which can lead to penalty by Flipkart as seller continues to receive the order for which the physical inventory is not available. By clicking Inventory Recon as “Yes,” it enables Vin E-retail to reconcile the inventory. (* It is only scheduled for once/day) |
Channel Mappings
Flipkart Seller SKU code to be mapped in Channel SKU Code and Flipkart FSN id to be mapped in Channel Product ID.
Other details about Flipkart Omni Integration: (SKU Pull is running on non-API based method – Chances that SKUs are not pulled automatically so if the SKUs are not pulled automatically, please do the SKU Mappings manually).
• Multi-product shipments are NOT allowed in the Self-ship model
• COD orders are NOT allowed in Self-ship model.
• Fulfilment of an order/shipment must happen from a single store only. If a single store cannot fulfil the complete order, then the seller must cancel the order.
• Location Id in all the Flipkart APIs refers to the actual location for which the order was created at first. The location Id of the actual store from where the shipment is dispatched is taken in /dispatch API and used only for invoicing. e.g., if an order OD1 is created at location LOC1 and later dispatched from a store belonging to LOC2, then for all reporting purposes OD1 will be part of LOC1 only.