Myntra V4 Integration

Integration Overview

This integration supports only B2C orders' fulfillment using Increff integration with Myntra systems
It works on both PULL and PUSH based API models which means Myntra can push order updates to Increff system and the Increff can pull forward orders and returns from Myntra systems
Passing Tagloop information is present in this Integration
Geography → India

Workflow Breakdown

Think of workflows as specific actions that happen within the integration. Here's a breakdown of each supported workflow and what it means for you:

Workflow	Description	Supported	Remarks

Workflow	Description	Supported	Remarks
Inventory Sync	Inventory update flow to the Myntra in a batch of size 10	Yes	Rate limit is 200 API calls sent/min
Forward Orders Sync	Myntra pushes us one order at a time to Increff systems along with the customer address (mobile, email are dummy)	Yes	For priority orders the SLA time will be 2 seconds less than that of normal orders.
Routing & Splitting	Not supported	Not supported	Not supported
Forward Order Acknowledgement	No updates sent to Myntra from Increff’s end	Yes	NA
Shipment Processing (Packing and Invoicing)	Increff sends `Ready to dispatch` notification to Myntra system In case tagloop data is captured in Increff system then the same will flow to Myntra system in this notification Myntra system generates the customer invoices once the shipment is marked as Packed , Increff system fetches the invoice copy from Myntra in `/getInvoiceDetails` call Increff system fetches the shipping label from Myntra in `/shippingLabel` call	Yes	NA
Manifest	This API workflow is not supported at Myntra’s end.	No	NA
Handover	This API workflow is not supported at Myntra’s end.	No	NA
Forward Order Customer Cancellation	Myntra systems notifies increff system once customer cancellation is received	Yes	NA
Forward Order Seller Cancellation	Increff system send the list of items which could not be fulfilled (rejected items) to Myntra, and in response we get the new location mapping of the rejected lines.	Yes	New order is created with updated location for rejected items
Replacement/Exchange Order Sync	Myntra generates a new order and cancels the original order. So this is just like a new order for Increff.	Yes	No mapping kept within Increff systems between original order and replacement order
Return Order Sync	Myntra system sends the Return order information to Increff system once it is created by Customer	Yes	NA
Return processed notification updates	This API workflow is not supported at Myntra’s end.	No	NA
Return Order Cancellation	Myntra system sends the Return order cancellation update to Increff system once it is Cancelled by Customer	Yes	NA

Visualizing the Flow

Workflow between Myntra and Increff systems.

Marketplace-Specific Details

Property	Values	Remarks

Property	Values	Remarks
Cancellation Reasons	`Customer Request-Incorrect size ordered` `Customer Request-Dope Order Cancellation Post Cod Conversion` `Customer Request-Ordered By Mistake` `Customer Request-Duplicate Order` `Customer Request-Cash Issue` `Customer Request-Wants to change style/color` `Customer Request-Product not required anymore`	These are currently not being captured the in Increff systems
Return Reasons	`Size is too Small` `Size is too Large` `Customer Request-Incorrect size ordered` `Received a poor quality product` `Customer Request-Product not required anymore` `I did not like the fit` `It did not look good on me` `Others` `null` `I do not need it anymore` `Product image was better than the actual product` `Different product was delivered` `Customer Request-Delayed Delivery Cancellation`	These are currently not being captured the in Increff systems
Replacement Orders	Myntra sends Increff a new order when customer requests for replacement and cancels the older order in Increff systems
Cancellation Support	Customer cancellation is supported till Ready to dispatch (Pack) update at marketplace	Sometimes customer cancellation can also be triggered from Myntra to Increff system after shipment is manifested. In such cases operations team can create manual RTO from Increff system.
API Performance	Hourly metrics - Inventory - 152850 inventory updates Order sync - 3000 orders Returns - 1879 returns Average time taken for calls - `/getInvoiceDetails` - 190 ms (milliseconds) `/shippingLabel` - 370 ms `/reject` (Seller rejection) - 280 ms Customer cancellations - 225 ms

Onboarding

For onboarding a client on channel there are certain credentials that are to be exchanged between Increff and Myntra

Credential identifier used by Myntra	Credential identifier used at Increff	Owner
`merchant_id`	`VENDOR_ID`	Myntra
`secret_key`	`ACCESS_SECRET`	Myntra
`x-partner-store`	`USER_ID`	Myntra
`authUsername`	`authUsername`	Increff
`authPassword`	`authPassword`	Increff

Returns authorisation required from Myntra.
1. Myntra needs to authorise the client(vendor id) to use recon apis for fetching returns.
Courier Code to Transporter code mapping Configuration
1. The default value of transporter code is set as “Myntra logistics” therefore if for any courier code received by the myntra proxy if the mapping does not exist then the transporter code will be sent as “Myntra logistics“ by default.
2. If default courier code is not coming from myntra we will have to toggle a configuration in Myntra integration to allow capturing new courier code, and in case we want to send a different transporter code
  in shipping label, we will have to map courier code to custom transporter code.

Myntra Tag Loop Configuration

Myntra tag loops are small, plastic tags with a unique, scannable barcode attached to products before they are shipped to customers. Essentially, they act as a security seal and a product identifier.

Tag Loops are designed to enhance security by preventing product counterfeiting and the return of used items. They feature a unique barcode that enables traceability throughout the product's journey from the warehouse to the customer. An intact tag loop provides customers with the assurance that they are receiving a new, authentic product. These tag loops are mandatory for certain product categories to ensure the integrity of Myntra's supply chain. These also help to reduce loss for a seller by ensuring the products being returned are in best condition.

To enable this feature please reach out to Increff Customer Support team by creating a support ticket by following steps mentioned here

FAQs

What if tagloop is not scanned for an order line where myntra expects tagloop?
1. If the seller has configured tag-loop as mandatory, then an error will be thrown from integration telling which order lines are not having tag-loop scanned. The error will be thrown even if packing is retried, and until tag loop is scanned.
2. If the seller has configured tag-loop as non-mandatory, then the above error will be thrown in first packing attempt, but packing will be successful in next attempt even if tag-loop was not scanned.
Who generated secret_key and vendor_id which is needed while onboarding?
1. Myntra generates the secret_key and vendor_id and shares with us.
What is merchant_id?
1. Myntra gives a unique identifier to each seller account registered on its system. It is an alphanumeric value, within Increff it is called vendor_id.