Purplle

Purplle is one of India's two large beauty and personal care commerce platforms, alongside Nykaa. It sells makeup, skincare, haircare, fragrance and grooming products through an app and website, runs its own private label brands, and operates a growing number of physical stores. The legal entity behind it is Manash Lifestyle Private Limited. For a brand, Purplle is predominantly a buyer rather than a marketplace: Purplle onboards the brand, buys stock against purchase orders, owns the listing and sets the shopper price. There is no public seller API, no developer portal, and no integration with the Indian order management systems that cover the mainstream marketplaces.

At a glance

What it is

Purplle is an inventory-led beauty retailer with marketplace characteristics rather than a pure marketplace. It buys the majority of what it sells, holds it in its own warehouses, and controls assortment, pricing and promotion. It also owns and operates house brands, which is the same structural pattern as every other beauty retailer of its size: the retailer's own margin comes partly from private label, so third-party seller tooling is not a priority.

The consumer site's footer is instructive. It carries About Us, Our Team, Careers, Press, Sitemap, Investor Relations, Privacy Policy, Terms of Use, Return and Cancellation Policy, FAQs and Contact Us. There is no Sell on Purplle link, no seller help centre, no vendor portal link and no developer link. purplle.com/sell-on-purplle carries no seller content either.

API access

None. This is not a case of a partner-gated API that we could not see: the evidence points to there being no programmatic seller surface at all.

The clearest single data point is that seller.purplle.com does not host a portal. On 2026-09-21 it returned an HTTP 301 redirect straight to a Google Form titled "Onboarding Form 2026", owned by Manash Lifestyle Pvt. Ltd. The form asks a brand for:

• brand and company name, and country of origin
• product categories (skincare, makeup, haircare and so on)
• SKU count, average selling price and annual turnover
• which other channels the brand already sells on, including Nykaa, Myntra, Amazon, Flipkart and Blinkit
• contact details for the brand owner and the sales head
• website and social media links

That is a commercial lead-capture form for a category buyer, not a technical onboarding step. A platform that intends brands to integrate does not route its seller subdomain to a spreadsheet.

Supporting negative evidence:

• EasyEcom's public knowledge base holds 328 articles, including dedicated guides for Nykaa, Nykaa Fashion, Myntra, Tata CLiQ, FirstCry, Smytten and the quick commerce platforms. There is no Purplle article.
• Unicommerce's integrations directory lists Nykaa and Nykaa Fashion but not Purplle.

Two OMS vendors that both built Nykaa connectors skipping Purplle is the strongest signal available. Their customers are beauty brands; if Purplle had an integrable seller API, it would be on those lists.

Authentication

Not applicable. There is no credential to obtain, no token endpoint, no key. A brand's people get a human login to whatever vendor-facing screens Purplle's category team grants them, and none of that is documented publicly or designed for machine access.

Objects we can read

Nothing is readable programmatically. What a Purplle vendor actually holds:

• Purchase orders. Raised by Purplle's category or planning team against the agreed trading terms. Delivered as documents or downloaded from a vendor-facing screen. These are the only order-shaped artefacts a brand sees.
• Order items. PO lines carrying Purplle's internal article code, a description, quantity and rate. The article code is not a GTIN and must be mapped to your SKU once per article.
• Products and listings. Not readable. Purplle writes the listing content, chooses the images, sets the MRP display and sets the selling price. A vendor has no listing object and no visibility of listing status except by looking at the site.
• Inventory. Not readable. Once goods are received, the stock is Purplle's and warehouse-level availability is not exposed.
• Shipments. Outbound from your side only: your delivery against the PO, your invoice, your e-way bill. Receipt is confirmed by a goods receipt note.
• Returns and cancellations. Not readable. The vendor-relevant events are PO cancellation, short receipt, quality rejection and, for beauty specifically, near-expiry and shelf-life rejections, which are a real and recurring category of loss.
• Payments and settlements. Not readable. Reconciliation is invoice against remittance, with debit notes for shortages, damages, expiry claims and any agreed marketing or listing contributions.
• Customers. None. Purplle is the merchant of record and no consumer data reaches a vendor.
• Locations. Purplle warehouse addresses appear on the PO. Keep a local lookup table; there is no location feed.

Writing back: listings, price and stock

Not available by any mechanism. A brand cannot create a Purplle listing, change its price, or set stock. Assortment and price are the category buyer's decisions. Listing content is created by Purplle's cataloguing team from the assets the brand supplies, usually over email or a shared drive at onboarding.

The one place a brand has genuine influence is the onboarding form data itself and the trading terms that follow: SKU set, landed cost, margin, and any agreed promotional support. That is a negotiation, not an endpoint.

Webhooks and notifications

None. There is nothing to subscribe to and nothing to poll.

If Purplle volume justifies tracking, the practical pipeline is the same as for any document-driven vendor channel: ingest POs from a dedicated mailbox, parse them, write them into the orders table tagged channel = purplle with a provenance flag marking them document-derived, and reconcile monthly against the remittance advice. A nightly scrape of your own listings' public prices on purplle.com is a legitimate way to monitor shopper-facing price and availability, since that is public information, but it is observation, not integration, and it should be rate-limited and clearly labelled as such in the data model.

Rate limits and pagination

Not applicable.

Mapping to the unified model

Gaps and open questions

• Whether Purplle operates any vendor-facing portal at all for approved brands, and at what address. Nothing is publicly linked, and the one obvious subdomain is a redirect to a form.
• Whether Purplle issues POs in a structured format rather than PDF. Worth asking the category buyer, because it halves the ingestion work.
• Whether Purplle runs a genuine third-party seller model anywhere in its assortment, alongside the vendor model. The public evidence only supports the vendor model, but the two can coexist and the site does not distinguish them.
• The share of Purplle's assortment that is private label, which bounds how much third-party supply tooling it has any incentive to build.
• Whether the "Onboarding Form 2026" is the only intake route, or whether large brands are onboarded through a different path.

Sources

• seller.purplle.com, which returned HTTP 301 to a Google Form on 2026-09-21: seller.purplle.com
• "Onboarding Form 2026", owned by Manash Lifestyle Pvt. Ltd., the entity behind Purplle: the onboarding form
• Purplle consumer site and footer, which carries no seller, vendor or developer links: purplle.com
• EasyEcom knowledge base, all 328 published articles enumerated on 2026-09-21: no Purplle article exists, although Nykaa, Nykaa Fashion, Myntra and Smytten all have one. support.easyecom.io
• Unicommerce integrations directory, which lists Nykaa and Nykaa Fashion but not Purplle: unicommerce.com/integrations