virtual makeup try-on on the product page
Virtual Makeup Try-On on the Product Page: Where to Put the Button and What Comes Next
The PDP is where the shade question shows up. Here's where to place virtual makeup try-on on the product page, when to use photo or live camera mode, and how to connect the render to the cart.
Most colour decisions happen on a single screen: the product page. That's where the shopper looks at a swatch, compares it with the model's photo and tries to picture the result on her own skin. Virtual makeup try-on on the product page exists to shorten that imaginative leap — and, placed well, it stops being decoration and becomes part of the purchase flow.
This article is about practical decisions: where to put the trigger, which format to use in each context, what to do with the result and which mistakes kill usage.
Why the PDP concentrates the shade question
On the home page and category pages, the shopper is still browsing. On the PDP, she has already chosen the product and is stuck on one specific question: does this shade work on me? When the answer doesn't arrive, one of three things happens — abandonment, a hesitant purchase with return risk, or a message to customer service asking for help.
The exact moment
The friction point is usually the shade selector. The shopper taps three or four variations, sees names like "Rosé Nude" and "Caramel Nude", and can't tell them apart. That's the instant virtual try-on needs to be visible — not in the footer, not behind an "extra content" tab.
Virtual makeup try-on on the product page: where to put the button
Three positions work well, and they aren't mutually exclusive:
1. Right next to the shade selector. The trigger sits on the same visual line as the variations, with a direct label: "See it on me" or "Try this shade". This is the highest-intent position, because it answers the question at the moment it appears.
2. Over the main image. A discreet button overlaid on the gallery, which the shopper finds while exploring the photos. It works especially well on mobile, where the gallery takes up almost the entire first fold.
3. Near the buy button. A last check before adding to cart. Here the label changes tone: "Confirm the shade before buying".
What doesn't work: hiding the experience behind a menu, using an icon with no text, or opening a new page that pulls the shopper out of the product context. The render should happen in an overlay or side panel, keeping price, variations and buy button accessible.
Photo or live mode: what each format solves
MaIA Try-On exists in two forms, and they serve different scenarios within the same PDP.
The API, photo-based
The shopper sends a photo, the product — lipstick or foundation — is rendered on it and the image comes back ready. Palettes are calibrated from the brand's real products in a project, so the shade that appears is your SKU's shade, not a generic approximation. It's the natural route when the render also needs to exist outside the browser: inside the app, in a conversation, in an email or in a service flow. Because the result is an image, it can be reused in any channel.
The browser SDK
In early access since September 2026, the SDK runs on the brand's own page and covers thirteen products — lipstick, foundation, blush, face powder, under-eye concealer, eyeshadow, mascara, eyebrow makeup, eyeliner, bronzer, contour, highlighter and lip liner — plus the combined Full Look. It works in live camera mode, rendered locally in the browser with nothing uploaded, or in photo mode. Any #RRGGBB colour can be loaded, and hosting belongs to the brand.
In practice: PDPs in categories the API doesn't render (eyeshadow, blush, eyeliner) call for the SDK. Lipstick and foundation PDPs can use either, depending on where else the render will circulate. If the question is conceptual, the comparison between photo-based try-on and other approaches helps settle the choice.
What happens after the render
An isolated render is a trick. The value appears when it connects to the rest of the page.
Switching shades without starting over
After the first result, the shopper should be able to switch variations with one tap, without re-uploading a photo or reopening the camera. This is the interaction that generates the most engagement on the PDP: comparing three shades in a row.
A direct path to the cart
The shade tried on must be the shade selected. It sounds obvious, but it's a common mistake: the shopper tries "Caramel Nude", closes the overlay and the selector is still on the default shade. Sync the two states.
A bridge to the beauty profile
If the brand already uses selfie-based skin analysis, undertone and skin tone can sort the variations before the first render even happens, putting the most likely candidates up front. That reduces the number of attempts before a choice and makes use of data the brand already has.
Mistakes that kill usage
- Poorly communicated perceived latency. Any wait without visual feedback feels like a freeze. Show a loading state.
- Asking for signup before trying on. A login in the middle of the flow wipes out a good share of sessions. Ask afterwards, if you need to.
- Camera permission with no explanation. In live mode, a short sentence before the permission prompt — explaining that rendering is local — changes the acceptance rate.
- A palette misaligned with the catalog. If the render doesn't match the physical product, the result is a return. Calibrating from real SKUs is not optional.
- A desktop-only experience. The beauty PDP is mostly mobile. Design for the small screen first.
How to start without rebuilding the PDP
You don't need to redo the whole template. Start with one category — lipstick is usually the simplest, because colour variation is obvious — on a limited set of SKUs. Decide in advance what you'll watch: how many try-on sessions happen per PDP visit, how many shades are tested per session, and how pages with try-on behave compared with pages without it. With that scope, the decision to expand to foundation, eyeshadow and Full Look becomes a conversation about internal numbers, not impressions.
Want to put virtual makeup try-on on the product page of your e-commerce? Create your account and API key in the documentation, or talk to the B4A team about calibrating your palette and early access to the SDK.
Frequently asked questions
Where is the best place for the virtual try-on button on the PDP?
Right next to the shade selector, because that's where the colour question appears. Complementary positions are a trigger over the main image and another near the buy button, as a last check before adding to cart.
Does virtual try-on need to open in another page?
No, and it's better if it doesn't. An overlay or side panel keeps price, variations and the buy button accessible, preserving the context of the decision.
What's the difference between the MaIA Try-On API and SDK on the product page?
The API is photo-based and renders lipstick and foundation, returning an image that can be used in any channel. The SDK runs in the brand's browser page, covers thirteen products plus Full Look, and works in live camera mode or photo mode, with local rendering.
Do the render colours match the brand's real products?
In the API, palettes are calibrated from the brand's real products inside a project. In the SDK, any #RRGGBB colour can be configured by the brand, which makes it possible to mirror the catalog.
Does the shopper's photo leave the device in live mode?
In the SDK's live mode, rendering happens locally in the browser and nothing is uploaded. In the API's photo flow, the image is sent for processing and comes back rendered.