Vinculum Knowledge Central

MYNTRA OMNI 

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 Pretr/Omni
  
• Myntra FBM
• Myntra JIT
• Myntra PPMP

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

2. 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.

3. 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.  

4. 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). 

For Myntra Omni, 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)

10. Order hopping

 SKU Pull is not available in Myntra PPMP as Myntra do not have any API for this.

 Prerequisites

Order Pushed by Myntra to Vin e-Retail using Myntra API only.  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.

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.  

• Merchant Id: This is the Merchant Id of the client/Seller provided by the client to Vin e-Retail account manager. 
• Secret Key:  This is the Secret Key of the client/Seller provided by the client to Vin e-Retail account manager. (Seller Panel URL: https://partnerportal.myntra.com/)
• Warehouse Id: This is the Warehouse Id Provided by Myntra to the Client and client must share that with us. (In case if Myntra asking this). 
• Fulfilment SLA (in Days): By default, the Seller is configured with the Fulfilment SLA as 2 days. (For Default case this should be left Blank) However, If the client or Myntra requested us to increase the Fulfilment SLA of the Orders to more than 2 days than we must put the no. of days in numeric format and after updating this, execute the inventory recon.
• Is Omni Channel: This Flag is configured only for those clients where the client is using stores also for order fulfilment and the account manager also have email confirmation from Myntra about taking the client live on Omni Model. 
• Allow Order Rejection for Omni: This Flag enables the Store users to Reject the order on marking the order as cancelled in Vin e-Retails or on online POS. (This Flag should be enabled on all the channels created for stores).
   

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 setup helps the seller 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 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.
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.
8	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) 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)

Channel Mappings  

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

PROCESS FLOW

Important Note: Every Channel Order Fulfilment Warehouse and Inventory sync dedicated warehouse Should be mapped with correct Vin e-Retail’s LOCCODE/WAREHOUSE/STORE.

•  If the client is going live on 100 stores, Myntra will provide 100 store Ids/location Ids. Using these location Ids, 100 Channels are created in Vin e-Retail. Here the Merchant Id and Secret Key should be constant. Only the Store Id varies for every channel. 
• Client/Vin Account Manager must do the Channel Mappings manually after creating the channel. 
• Once the customer places the order on Myntra website, that order will be pushed by Myntra to Vin e-Retail depending on the nearest store or warehouse/available inventory etc.

Work –Flow

• When Store 1 has procured the inventory of the same SKU within the Order SLA breach, that inventory will be pushed to Myntra and Myntra will assign this order to Store 1. Now, This order will be visible as Allocated on Store 1 again  (Here the order will be created with seller_Order_id~Counter (here seller_order_id is the Myntra seller order Id and the counter is the no. of times the order is hopped/rejected) If the seller_order_id is asdfs-sfgd-sdfg and the order is hopped 2 times and assigned back to the same location where it was cancelled earlier, the new order will be visible like asdfs-sfgd-sdfg~2). 
• We are keeping the ~ Separated value because we cannot create the same order with same Order Id again on the same location against same channel code.
• In Omni channel, sometimes order is created in NO STORE TO SERVICE only and no warehouse/store is assigned to that order. All such orders will be visible on Head Office account only. 
• After some time, when the inventory is pushed from any location, Myntra pushes the order to that Store/warehouse and that store or warehouse must fulfill the order.

 Common issues and their resolution in Myntra (internal use only)

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

 Alerts for Myntra Omni Channel (Account Manager can configure this for the client – For internal use only) 

• For the Head office users/Account managers, it is difficult to track the order pendency. Kindly subscribe the alert with alert Id: 11135 to the client (keep all stakeholders in CC). 
• If the cancellation of any order is not pushed to Myntra, to track the same, subscribe the alert 11136.