Vinculum Knowledge Central

MYNTRA PPMP

INTEGRATION DOCUMENT

About Myntra

Myntra is an Indian fashion e-commerce company headquartered in Bengaluru, Karnataka, India. The company was founded in 2007 to sell personalized gift items. In May 2014, Myntra.com was acquired by Flipkart. IN 2014.

Models of Myntra

There are 4 models of Myntra.

• Myntra PPMP
• Myntra JIT
• Myntra FBM
• Myntra Pretr/Omni

We have 4 models of Myntra. 

1. Myntra PPMP is a pure-play marketplace model i.e., Dropship, and supports multi-location Order creation and inventory Push. (This Model is live with 50+ clients in Vin e-Retail). 

2. Myntra JIT is a PO-Backorder Type Marketplace Model in which based on customer Orders (saved as Backorders), Myntra will raise Purchase Order to Brands which is reflected as a Sales order in our system. 

3. Myntra FBM is an STN-Backorder Type Marketplace Model in which based on customer Orders (saved as Backorders), Myntra will raise Stock Transfer Order to Brands which is reflected as Sales Order in our system. 

4. Myntra also have Omni Channel Marketplace Model in which orders are fulfilled from stores.

In this document, we are going to discuss Vin e-retails Integration with the Myntra PPMP model.

Integration Highlights:

For Myntra PPMP, we have

1. Order Pull 

2. Order Pack/Invoice/Shipping Label generation 

3. Order Shipment 

4. Inventory Push

5. Inventory Reconciliation 

6. Order Pre-fetch

7. Order Acknowledgment/Accept

8. Order Returns

9. Order Cancellation (From Vin e-Retails to Myntra OR from Myntra to Vin e-Retails)

SKU Pull is not available in the Myntra PPMP model as Myntra does not have any API for this. 

Prerequisites

Order is pushed by Myntra to Vin e-Retail by using Myntra API;  so, we must share 1 Order Push token for Myntra Pretr. The Account Manager must get in touch with Vin e-Retail Product Integrations team to get the Token.

The client must get in touch with his account manager to enable the APIs for the seller. Once the APIs are enabled Seller must share the below-mentioned Credentials and these are mandatory to configure the Myntra PPMP channel for any client.  

• Is Omni Channel: Select No for PPMP model. 

CONFIGURING INTERFACE

Below is all about how to configure Myntra PPMP in Vin e-Retails for Order Management. Inventory management and Return Management. 

1. Once all the above IDs are gathered, open your vin e-retail instance, Go to “Manage Channels” under the sales section.

2. Go to the top right-hand side of the window and click on “Add New.”

3. Select the correct Myntra channel option from the list.

4. Fill in all the details like Channel Name, order Source WH, Order Sync from date, Return Sync from Date, Inventory Sync Method, Enable Inventory Reconciliation, etc.

5. Click on Configure Interface.

6. Enter the configuration details as mentioned in the Prerequisites section. 

g. Once the details are saved, a channel is created.

Channel Maintenance Window

Channel Maintenance set up helps the seller to reduce manual intervention and avoid the multiple usages of the marketplace seller portal. With the selection of below options at the Channel Maintenance window (Sales > Manage Channels > Add New > Select Amazon India) get the advantage of using multiple features of Vin E-retail:

S.No.	Features	Where to Click on Channel Maintenance	Dropbox/Checkbox	Details
1	SKU Pull	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	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	Prefetch Shipment Label	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 shipment Labels and Invoices at the same time of picklist generation instead of during Pack calls. 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.
4	Ready to Ship Status at	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
5	Use Market Place Shipping Label	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.
6	Inventory update	Inventory > Inventory Sync		If selected "Yes" from the dropdown box, it automatically pulls and updates the inventory.
7	Inventory Reconciliation	Inventory > Enable Inventory Recon		By clicking Inventory Recon as “Yes,” it enables Vin E-retail to reconcile the inventory. (* It is only scheduled for once/day)

Channel Mappings  

Myntra’s SKUID needs to be mapped as ChannelSKUcode and Channel Product Id against the Vin e-Retail SKU code. 

Common issues and their resolution in Myntra 

 • Myntra APIs are highly stable APIs. There are very rare cases where issues do occur. Sometimes, the order moved into pack in progress status with the error description as “Error while Updating order” or “Error while processing request”. Such Orders automatically gets processed after a wait of 1-2 orders (this issue comes in 1 order out of thousands of orders). 

• Same issue occurred in case of cancellation also sometimes where we are getting the error: “Error while Updating order” or “Error while processing request”, cancellation here refers to Cancellation push from Vin e-Retail to Myntra. Such records need manual retries for posting the cancellation again.