selfie skin analysis to reduce returns
Selfie Skin Analysis to Reduce Returns in Beauty E-commerce
Foundation and concealer returns are almost always shade errors, not logistics failures. How to use selfie skin analysis at the three moments of the purchase flow — before, during and after — and how to measure the effect without fooling yourself.
In face makeup, most returns are not a carrier problem: they are a decision problem. The customer chose a shade that wasn't theirs, found out when they opened the product and raised a ticket. That is why selfie skin analysis to reduce returns is not an after-sales tool: it is an intervention at the exact moment the person is still choosing, when correcting course costs a recommendation instead of a reshipment.
Why a foundation return is not a logistics problem
When an e-commerce team looks at the return rate by category, it usually finds the same pattern: lipsticks and mascaras come back rarely; foundations, concealers and pressed powders come back far more often. The difference isn't in the packaging or the shipping, it is that lipstick tolerates error and foundation doesn't. A shade half a step too light or with the wrong undertone is visible in the bathroom mirror and causes immediate dissatisfaction.
That changes where you need to act. Improving the exchange policy, shortening the refund window or automating the return label reduces friction in the process, but it doesn't reduce the number of wrong choices. For that you have to intervene earlier: give the customer information about their own skin that they can't translate on their own. Few people can say whether their undertone is warm, cool or neutral, but almost everyone can take a selfie.
The three costs of a badly handled return
A foundation return costs reverse logistics, it costs product that often can't be resold and it costs trust. The third cost is the most expensive: a customer who got the shade wrong and had to manage a return is unlikely to buy foundation online from that brand again. That is why the goal is not just to lower the percentage, it is to turn the return into a targeted exchange — or avoid it beforehand.
Selfie skin analysis to reduce returns: where it acts in the flow
Before the purchase: turning the photo into a profile
MaIA Scan receives a selfie via API and returns a beauty profile in JSON: skin tone and undertone, visible skin type and condition, hair attributes and a confidence level per field. The model was trained on Brazilian skin, which matters in Latin American markets where the range of tones and undertones is wide and global catalogs usually fall short.
With that profile, the product page stops asking "what is your shade?" and starts suggesting two or three compatible SKUs, with the most likely one highlighted. The customer still chooses, but chooses within a set that has already been filtered by their own skin.
During the purchase: visual confirmation before paying
A suggested shade is more convincing when it can be seen. With MaIA Try-On the brand can send the customer's photo via API and receive the image with the lipstick or foundation applied, with palettes calibrated to the project's real products. It is a photo-based try-on, not a generic simulation: the colour the customer sees corresponds to the SKU going into the cart. In the browser SDK, in early access since September 2026, the same flow can happen in live camera mode, rendered locally, without the image leaving the device.
The combination matters: the profile narrows the range of options and the visualisation confirms the choice. A customer who saw the shade applied before paying opens fewer tickets afterwards.
After the purchase: a targeted exchange instead of a refund
When the error has already happened, the profile is still useful. If the customer stored in the CRM has an associated beauty profile, the customer service team doesn't need to start from scratch: it can propose the right neighbouring SKU in the same channel where the complaint arrived. A return that turns into an exchange preserves the revenue and, above all, preserves the relationship.
What the API returns and how to use it to decide
The most underestimated field is the confidence per attribute. A selfie with poor light, a filter or makeup can produce a tone with low confidence; that is the moment to ask for another photo or to show a range of shades instead of a single one, rather than pushing a fragile recommendation.
A practical rule to start with: high confidence, a single highlighted recommendation; medium confidence, two or three neighbouring options; low confidence, ask for a new photo with simple instructions (natural light, face without makeup, facing the window). This logic is written once in the backend and reused on the site, in the app and on WhatsApp.
How to measure the effect without fooling yourself
Don't measure the store's overall return rate: measure it by category and by cohort. Compare customers who used selfie analysis before buying foundation with customers who bought the same category without using it, in the same period. Look at three numbers of your own: return rate for the reason "wrong shade", percentage of returns converted into exchanges and ninety-day repurchase in the same category.
Avoid comparing your result with third-party figures. Any effect depends on the catalog, the traffic, the channel and the quality of the photos your customers send; two brands with the same integration can get different results.
What this technology doesn't do
MaIA describes visible attributes in a photo. It is not a clinical assessment of skin conditions, it does not replace a health professional and it doesn't promise that no customer will ever get it wrong again. Nor does it replace a good product listing: consistent swatch photos, finish descriptions and a clear coverage guide are still part of the job.
If your catalog has few shades, the analysis will show it clearly. That is useful information too: knowing which undertones you aren't serving is a product input, not just an e-commerce one.
Start with a narrow case
Pick a single product family — foundation or concealer — connect selfie analysis on that product's page and measure eight weeks against the previous period. Create your account and your API key in the MaIA documentation, or talk to our team if you want to design the recommendation and after-sales flow together with your catalog.
Frequently asked questions
Why are foundations returned more than other makeup products?
Because a shade error is immediately visible and not tolerated: half a shade lighter or the wrong undertone shows in the mirror. A lipstick allows for variation; a foundation hardly does.
Does selfie analysis guarantee the customer gets the shade right?
No. It narrows the range of options and provides information the customer can't translate on their own, but the final choice is still theirs and depends on photo quality, lighting and the available catalog.
What exactly does the MaIA Scan API return?
A JSON with skin tone and undertone, visible skin type and condition, hair attributes and a confidence level per field, from a selfie sent by the customer.
How do I use the confidence level in the recommendation?
With high confidence you can highlight a single SKU; with medium confidence it is best to show two or three neighbouring shades; with low confidence, ask for a new photo in better light before recommending.
Can this be used to assess skin problems?
No. MaIA describes visible attributes in a photo for product recommendation purposes; it does not treat anything, it is not a clinical assessment and does not replace a health professional.