Smytten is an Indian beauty, skincare, haircare, makeup, grooming and wellness platform built around two experiences: Trials and Minis, where users order authentic small sizes from 5 to 200 ml or g and get the trial value back as wallet credit, and Smytten Shop, where they buy full size products. For a brand, Smytten is a curated vendor channel, not an open marketplace. There is no seller sign up, no brand portal that can be reached from the public site, no developer documentation and no API. Onboarding is a sales conversation. This page records what can be established from Smytten's own published files and from the absence of everything else.
At a glance
What it is
Smytten's own llms.txt, served at https://smytten.com/llms.txt and owned by the "Smytten Product Team", describes the platform as "India's leading beauty, skincare, haircare, makeup, grooming, and wellness platform, offering India's largest collection of minis and trials (5-200 ml/g) alongside full-size shopping". The same file gives the scale numbers Smytten wants quoted: more than 30 million users, more than 100 million minis tried, more than 2,500 trial SKUs from more than 1,500 brands, and more than 2,500 brands on the Shop side.
Two mechanics matter for a connector:
- Trials run on Trial Points, not on rupees. A user spends Trial Points to order a mini and receives 100 percent of the trial value back into a Smytten Wallet. So a trial order is a physical fulfilment event with a non rupee unit price on the consumer side, while the brand side is a supply arrangement priced separately. Any
ordersrow you model from trial data will have atotalthat does not mean what it means elsewhere. - Wallet credit and Smytten Bucks are separate currencies with separate expiries. Smytten's own retrieval rules state that "Smytten Wallet shop credits expire in 60 days; Smytten Bucks expire in 1 year". Discounts of 5 to 10 percent come from applying wallet credit. Treat these as platform funded discounts, not seller funded, unless a contract says otherwise.
Smytten stresses that minis are "100% authentic, brand-verified, and directly sourced from brands (never decanted)". Direct sourcing from brands is the commercial shape: Smytten buys or takes consignment of minis, it does not host a third party seller who ships their own orders.
API access
None. There is nothing to apply for.
Evidence, all checked on 2026-09-21:
https://smytten.com/robots.txtallows/,/geo.txtand/llms.txt, and disallows only three cart paths. It names one sitemap.https://smytten.com/sitemap.xmllists seven child sitemaps, all consumer facing: shop, trial, other, shop products, trial products, blogs and rizzlife.sitemap-other.xmlcontains sixteen URLs, every one of them a consumer surface such as rewards, brand lists and category lists. There is no brand, partner, seller or developer URL anywhere in the sitemap.brands.smytten.com,business.smytten.com,partner.smytten.com,partners.smytten.com,brandpanel.smytten.com,seller.smytten.comanddashboard.smytten.comall fail to resolve or connect.smytten.comis a single page application that returns HTTP 200 with the same shell for/for-brands,/brandsand/brand-partner. None of them renders brand facing content. A 200 on those paths is not evidence of a page.
The only published contact address in any Smytten owned file is aeo@smytten.com, given as the owner contact in llms.txt. That is an answer engine optimisation address, not a partner desk. Brand onboarding runs through Smytten's own sales outreach and through https://smytten.com/contact-us.
Authentication
Not published. No credential model of any kind is documented.
Objects we can read
None programmatically. The objects a brand on Smytten actually deals in are:
- Purchase orders or consignment advices for trial minis and for shop stock, issued by Smytten's supply team.
- Offtake and trial performance reports, which are the commercially interesting output of the channel: how many trials converted to full size purchases. Delivered as reports from the category team, not through an interface.
- Returns and quality rejections, handled as a supply conversation.
- Payment remittances, on whatever cycle the contract specifies.
None of these has a published format. If you need them in the unified model, the honest plan is an email or spreadsheet ingestion pipeline, not a connector.
The one genuinely machine readable surface Smytten publishes is its product sitemaps: sitemap-shop-products.xml and sitemap-trial-products.xml. Those give you every product page URL on the platform. That is useful for competitive catalogue and price monitoring of your own and rival brands, within Smytten's own guidance that price, MRP, discounts, stock, ratings and review counts "change frequently" and should be read live rather than cached. It is not a seller integration and gives you no order or settlement data.
Writing back: listings, price and stock
Not available. Smytten builds the catalogue entry itself from brand supplied product information and assets, and it enforces variant integrity: its own retrieval rules say to "treat each size, shade, or packaging format independently" and never to carry pricing, ingredients, suitability or availability across variants. So a single brand SKU can appear as several distinct Smytten products, one per size or shade, with no shared parent you can address.
Webhooks and notifications
None. There is nothing to subscribe to and no seller endpoint to poll. For catalogue monitoring, re crawl the product sitemaps on a daily cadence and diff.
Rate limits and pagination
Not published. For public crawling, honour robots.txt and keep request rates low. Smytten's sitemap index is the correct entry point rather than a spider.
Mapping to the unified model
Almost nothing maps today. The table below records where each object would have to come from if a brand relationship existed.
Gaps and open questions
- Whether Smytten operates a private brand dashboard for its vendors is unverified. Most platforms of this size do, and its absence from DNS only means it is not on an obvious hostname.
- Commercial terms, including whether minis are bought outright or taken on consignment, the commission or margin structure, and the payment cycle, are all unpublished.
- Whether trial and shop are separate contractual channels for a brand is unverified, though the platform treats them as separate product sets with separate sitemaps and separate brand counts, 1,500 on trials against 2,500 on shop, which suggests they are.
- No aggregator we could check lists Smytten as a supported channel, including Unicommerce's public integration list.
Sources
- Smytten llms.txt, Smytten's own description of the platform, its scale numbers, its wallet and bucks expiry rules and its variant integrity guidance
- Smytten robots.txt
- Smytten sitemap index and
sitemap-other.xml, which contain no brand or partner URL - Smytten, homepage and contact page, read 2026-09-21. Note that this host returns HTTP 200 for non existent paths
- DNS and HTTP probes of seven candidate brand and partner hostnames under
smytten.comon 2026-09-21, none reachable - Unicommerce integrations list, which does not name Smytten