2Gud Flipkart
Integration Document
About 2GUD Flipkart
Walmart owned Flipkart is turning its refurbished goods portal 2GUD into an unbranded lifestyle and fashion platform. 2GUD is basically a Multi warehouse dropship fulfillment method in which the retailer processed the order and delivered it to the buyer via Flipkart's own logistic Ekart (80% and other 3PL partners also like Delhivery etc 20% Approx) and this process is known as the B2C Model.
*Drop shipping: a fulfillment model that allows you to buy products individually from a wholesaler and ship them directly to your customer.
2GUD Flipkart Business Model
2GUD Flipkart is a Marketplace model. In this model, they pass on the order to the seller and take commission or selling fee in return and the order is to be picked from the seller center 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 is a middle platform that connects all interested sellers to various customers and assists in making the sale.
Below is the List of Integration available for Flipkart Marketplace to configure in Vin e-Retail:
1. Flipkart v3.0 (Multi Warehouse)
2. Flipkart Assured
3. Flipkart Smart
4. 2GUD Flipkart
*In this document, we will learn about the integration of the Flipkart 2Gud (multi-warehouse) model.
Integration Highlights
In this integration with Flipkart 2GUD, we provide the below services:
1. SKU Pull
2. Order Pull and Order Fetch
3. Order Pack/Invoice/Shipping Label generation
4. Shipment Label Prefetch
5. Order Shipment
6. Download Marketplace Manifest
7. Order Return
8. Inventory Update
9. Inventory Reconciliation
Prerequisites
Mandatory Credentials
1. An email needs to be sent to seller-api-@flipkart.com with seller ID and Seller Panel login User ID with the mail Subject: “Enable V3 flag for 2GUD”
2. 2GUD User ID/Password - This required credential will be shared by the seller/Brand once it is registered on Flipkart Marketplace.
3. Seller Id - Unique Id generated for each seller by Flipkart and same will be provided by seller for Channel configuration in Vin-eRetail.
4. API Key / API Password -Below are the following steps are involved to generate API Key and API Password itself through Flipkart Seller Portal login details shared by the customer.
a. Visit the given link - https://seller.api.2gud.com/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. Enter the details as follows:
- Application Name: Vinculum
- Application Description: API
- Application Type (dropdown): Select the dropdown option “self_access_application”
- Click on the “Register new application.”
- As soon as you will register this application your Application Id (API Key) and Secret Key (API Password) will be visible to you. (Note: *For confidentiality reasons, we do not share these details in the snapshot.)
5. Location ID – Login to the https://seller.2gud.com/ with the 2gud user name and password. After clicking on the inventory tab, the location details can also be taken from the URL.
OR if the Location ID is not present there then follow the below steps:
To fetch the location id, kindly follow the below steps:
a. Login to https://seller.2gud.com/
c. Go to the “Orders” Section.
d. Click on Right mouse Click on the webpage and select the Inspect button
e. Go to the “Network” section
f. Select Location from the dropdown
g. Click on fetch?sellerid=
h. Scroll down and you will get the location Id and seller Id both in the header section.
Once all the above credentials are available, go to Vin E-retails and enter the details.
Channel Configuration
Once all the above IDs are gathered, open your vin e-retail instance (ERP)
a. Go to Sales > “Manage Channels”
b. Go to the top right-hand side of the window and click on “Add New.”
c. Select the required channel from the list.
d. Fill in 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.
e. Click on Configure interface link. Fill in all the credentials generated from the Flipkart API and Flipkart Seller portal.
f. 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.
g. Enter the Seller ID, API Key, If Self Ship, Username (2GUD ID), API Password, Location ID, and 2GUD Flipkart User ID password.
h. Click “OK” and hit the “Save” button. The channel is successfully created and will be visible in the manage channel screen.
Channel Maintenance
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. Users can choose to Pull the SKU’s from the channel to the 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: The 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 |
| Users can click this option to sync Return Orders. Important Note: In Return Pull Services, the “Return” is always created in Confirmed status. User needs to do an inbound from Return Inbound functionality available on Application. |
4. | Prefetch Shipment Label | Channel Maintenance > Orders > PrePack Enabled checkbox |
| PrePack Enabled: The user can enable prepack for the order from here. To avoid delay in Order processing and Shipment fulfilled within 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 the Prepack checkbox available under the Channel Configuration setup screen and the user needs to click on Prefetch deliveries during the pending picklist status available on the Picklist enquiry screen.
|
5. | Ready to Ship Status at |
Channel Maintenance > Orders > Ready to Ship At
|
| Users 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 |
| Users can check this option to notify the Shipping label by the marketplace and then opt from the Shipment label dropbox. |
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 a penalty by Flipkart as the 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) |
Additional Key Benefits: -
1. SKU Pull: From 2GUD SKU Pull Service, we are pulling 2GUD SKU Code and Flipkart Serial Number (FSN) as a PID and which user needs to map against eRetail SKU code from Unmapped tab available on SKU Channel Listing Screen. (Sales > SKU Channel Listing > Unmapped SKU
2. Marketplace Manifest: Instead of downloading Flipkart Manifest from Seller Portal, our system is also integrated to pull Flipkart Manifest from the Seller portal. It will be downloaded from the Application once the order is moved in Shipped Status. (WMS > Order Processing > Delivery Shipping > Download Marketplace Manifest > Show pending records)
Common Issues and errors:
1. Issue in Inventory Push: There are cases where we send 0 inventory successfully still Pending stock orders are coming in ERP. This is a known issue at 2GUD’s end where they allow the customers to place the order even after having zero inventory and later on mark the order as Marketplace Cancelled (No penalty charged from the seller for such cases).
2. Error in Order Pack:
• Pack Label Not Found AuthExceptionError_| 400: Bad Request. with Flipkart Error:-INVALID_SHIPMENTS|Invalid shipment Ids passed
This error occurred because on 2GUD also the label status is “label generation in progress”
Below is the screenshot to check the same.
• Call to dependent system failed|500 Internal Server error
This is the error coming from 2GUD when the API is down, or some tech issue occurred at 2GUD/Flipkart’s end. In such case, we have to contact Flipkart Tech Team or Flipkart API Team at: Seller Support API Mailbox: seller-api-queries@flipkart.com