Virtual Makeup Try-On for Product Launches: Shade Previews Before the First Shipment

A launch is the moment when a shade exists in your catalog but nowhere else. There are no testers on a counter, there is barely any user-generated content, and the swatch photography was shot on two or three arms. Virtual makeup try-on for product launches closes that gap: the customer sees the new shade on their own face before the first order ships, and your team sees which shades people actually gravitate to while there is still time to adjust the media plan.

This article is about the operational side — what has to be ready before launch day, which channel does what, and how to read the signals that come back.

Why launches are the hardest moment to sell a shade

For an established product, the catalog page carries years of reviews, photos from customers and a stable return history. A new shade has none of that. The buyer is asked to pick between "Terracotta" and "Brick" from two rectangles on a screen, and the safest decision is to wait — to buy nothing, or to buy the one shade they already own in another brand.

Three specific frictions show up at launch:

• No social proof on varied skin tones. The hero image shows one model. A customer with a different undertone has no reference point.
• No physical testers. Even brands with retail presence usually get stock to stores days or weeks after the online drop.
• Deep ranges are hard to browse. A twelve-shade lipstick launch or a foundation range with dozens of SKUs invites paralysis, not exploration.

A preview on the customer's own face addresses all three at once, and it is one of the few launch assets you can produce before a single unit has been photographed in the wild.

Planning virtual makeup try-on for product launches

Start with the palette, not the page

The part that takes real calendar time is calibration. In MaIA Try-On, the shades rendered on a photo are tied to a project configured with your actual products — a lipstick or foundation palette, matched to the real formulas rather than to a generic colour wheel. For a launch this means your product development or colour team has to supply the shade references while the range is still in production, not the week the campaign goes live.

Practical sequence: lock the shade list, calibrate the palette in a project, run an internal review with people from marketing and product looking at the previews on their own faces, adjust, then freeze. Treat it like you would treat packaging artwork — it has a sign-off date.

Photo mode through the API

The API is photo-based: your system sends a photo and the chosen product, and the rendered image comes back. That is the form that fits launch channels where you control the backend — a campaign landing page, a WhatsApp flow, an email journey that returns a personalised image, a retail tablet. It covers lipstick and foundation, which is exactly what most colour launches are built around.

Because the output is an image, it travels. A customer who receives their own preview of the new shade is holding a shareable launch asset that your media team did not have to produce.

Live camera mode through the SDK

The browser SDK, in early access since September 2026, runs in live camera mode — the camera feed is rendered locally in the browser, nothing is uploaded — or in photo mode, and it covers thirteen products plus a combined Full Look: lipstick, foundation, blush, face powder, under-eye concealer, eyeshadow, mascara, eyebrow makeup, eyeliner, bronzer, contour, highlighter and lip liner, with any #RRGGBB colour, self-hosted by your team. For a collection launch — a holiday set, a full face campaign — the Full Look is the natural fit, because it previews the whole story rather than one product in isolation. Access is granted per account, so if the SDK is part of the plan, raise it early with the team rather than in launch week. If you are still deciding between the two forms, the comparison between photo-based try-on and AR-style experiences is a useful starting point.

Launch-week channels

Pre-launch teaser. A landing page where the shade can be previewed but not yet purchased, collecting emails for the drop. The preview is the incentive to register.

Launch day product pages. Try-on sits next to the buy button on every SKU in the new range, not only on the hero shade.

WhatsApp and CRM. For brands with an active messaging base, the launch announcement can carry the try-on itself instead of pointing to it.

In-store, before stock arrives. A tablet at the counter lets staff show the range during the window when testers do not exist yet.

Pairing the preview with a shade match

For foundation launches especially, the preview is stronger when it starts from the right shade. A selfie analysis through the beauty scan API returns skin tone and undertone with a confidence score per field, which is enough to narrow a wide range to two or three candidates before the customer tries anything. Trained on Brazilian skin, it is built for ranges where undertone matters as much as depth. It describes visible attributes in a photo — it is not a diagnosis and does not replace a professional.

What to measure, and what not to promise internally

Set expectations before the campaign brief is signed. Try-on engagement, shades previewed per session, which shades get previewed but not bought, and the ratio of previews to add-to-cart are all legitimate launch metrics. Published conversion figures from other companies are theirs, not yours: results vary with each brand's catalog, traffic and channel, and a launch is an atypical traffic moment by definition.

The most undervalued output is the shade demand signal. Knowing within forty-eight hours which three shades dominate previews tells your supply chain and your paid media team something they would otherwise learn from sell-through weeks later.

---

Planning a launch and want try-on ready for it? Create an account and get an API key, or talk to our team about calibrating your palette and about early access to the SDK.