AI for Matching Actives to Skin Type and Formula Goal

Introduction: why choosing skincare is no longer guesswork

The classic formula-development workflow looks like this: a formulator reaches for actives that "work for everyone" — Niacinamide for post-acne marks, Retinol for wrinkles, Hyaluronic Acid for hydration — and assembles a cream from a template proven on previous clients. Then comes the trial-and-error stage: testing on a panel of 15-20 volunteers, two or three formula iterations, an 8-12 week wait for results. If the skin reacts unexpectedly — irritation, comedogenicity, no visible effect — the cycle starts over. A single finished product takes anywhere from 6 months to a year and a half, and the testing budget for a large line easily exceeds the cost of developing the formula itself.

The problem isn't the formulators' expertise — it's the logic of the approach itself: a one-size-fits-all lineup of actives averages out a skin response that is, by its very physiology, extremely heterogeneous. Barrier function, microbiome, sebum secretion rate, desquamation speed and sensitivity to irritants vary so much between people with the "same skin type" on paper that the identical 2% Salicylic Acid clears inflammation in two weeks for one client and triggers dryness and flaking within three days for another.

Where the traditional matching model breaks down

The trial-and-error approach rests on three assumptions, each statistically weak:

• Skin type as a category — dividing skin into "dry/oily/combination" ignores dozens of biomarkers (transepidermal water loss, surface pH, pilosebaceous follicle density) that actually determine the response to an active;
• Transferable efficacy between people — an active's efficacy in a clinical study (per Draelos, 2018, Niacinamide efficacy ranged from 40% down to near-zero response across different panel subgroups) doesn't guarantee the same result on a specific person's skin;
• A static formula — the recipe is fixed once, while skin changes with the season, hormonal cycle and external factors — and the formula doesn't.

As a result, the cosmetics industry has spent years compensating for this uncertainty with SKU count: a line of 8-10 creams "for different needs" instead of a single formula genuinely tailored to the specific case.

What neural networks change

The thesis of this article is simple: machine learning turns active selection from categorical guesswork into a data-driven prediction task. Instead of asking "which active usually helps with acne," the model answers "which combination of actives will give the maximum effect for a specific skin profile — with a known sebum level, barrier function and response to previous products." Three classes of models are used for this:

• predictive models based on clinical and consumer data (regression, gradient boosting) that estimate the probability of irritation or efficacy of an active for a given profile;
• generative models that propose combinations of active concentrations within permitted technological ranges;
• computer vision for analyzing skin photos and extracting features (pore size, redness, pigmentation spots) that become input data for the first two model types.

This doesn't replace formula chemistry or override biochemical mechanisms — Retinol still needs time for the stratum corneum to adapt, and Ascorbic Acid is still unstable at pH above 3.5. What changes isn't the nature of the actives themselves, but the accuracy of hitting the right concentration and combination on the first try.

In the following sections we'll break down what data a model needs for accurate active selection, how algorithms match an active to a formula's task (acne, pigmentation, barrier, aging), and where the technology is already being applied in real product development — with examples accessible without a costly corporate R&D platform.

How a neural network "sees" skin: from photo to digital profile

Before an algorithm can propose a single formula, it has to turn a facial photo into a set of numbers. This process is called feature extraction, and its quality determines whether a client receives a recommendation based on the real state of her skin — rather than an averaged "one for everyone" template.

Computer vision processes a skin image through several sequential stages, each solving its own narrow task.

Stage 1: facial-zone segmentation

The first thing the system does is map the face into anatomical zones: T-zone, cheeks, periorbital area, nasolabial folds, chin. This matters because skin behaves differently across zones even on the same person: the T-zone may show oiliness with enlarged pores while the cheeks show dehydration and flaking. Without segmentation, the model would average this data and produce a contradictory recommendation.

Segmentation is performed using convolutional neural networks (CNNs) trained on annotated dermatological image databases. The model finds facial key points (landmarks) — typically 68-468 points, depending on the architecture — and builds a zone mask from them. The accuracy of this mapping in modern models reaches 95-98% under controlled lighting (per Chen et al., 2021).

Stage 2: detection of specific features

Within each zone, the algorithm looks for specific visual patterns that are converted into measurable metrics:

• Pores — detected as local roundish dark spots of a specific diameter (typically 50-200 microns after pixel conversion); density per cm² and average size are calculated
• Redness (erythema) — analysis of the RGB red channel and its deviation from the baseline skin tone; an erythema-intensity map is built on a scale
• Sebum and shine — determined via analysis of specular reflections (glare highlights) in the image; the higher the density and brightness of the highlights, the higher the estimated sebum secretion level
• Wrinkles and creases — detection of linear structures using Gabor- or Frangi-type filters that pick out elongated dark lines against a lighter texture background
• Pigmentation and post-acne marks — clustering of irregularly shaped dark spots, distinguished from pores by size and contour

Each of these features is not just flagged as "present/absent" — it receives a numeric value: a density index, a severity degree, the affected area as a percentage of the total segment area.

Stage 3: normalization and conversion into a feature vector

Raw data from a photo is heavily dependent on shooting conditions: lighting, camera angle, screen color temperature. So before the data is fed into the active-selection model, it goes through normalization — bringing it to a single scale invariant to shooting conditions. This is often done via calibration against a reference color card (color checker) or against reference facial zones with known characteristics (for example, the eye sclera as a white reference).

After normalization, all visual features are assembled into a single feature vector — an ordered set of numbers where each position corresponds to a specific parameter: pore density in the T-zone, erythema index on the cheeks, nasolabial wrinkle depth, and so on. Such a vector typically contains 30 to 150 parameters, depending on the model's level of detail.

It is this numeric vector — not the photo itself — that is passed on to the active-ingredient selection model. The model no longer "looks" at the face; it works with structured data, comparing the client's profile to a training database where similar feature combinations were linked to specific formulas and their efficacy. That matching process is covered in the next section.

Compatibility chemistry: why not all actives can be mixed

Even an active perfectly matched to a skin type may fail to work — or sometimes cause harm — if the formula pairs it with "neighbors" it conflicts with biochemically. Before AI proposes an ingredient combination, it has to model dozens of hidden interactions: competition for the same receptors, shifts in pH, oxidative instability, competitive adsorption on the lipid barrier. This is "compatibility chemistry" — the invisible layer of constraints that determines what formulation space is even available.

Retinol and AHA: a conflict of renewal mechanisms

Retinol works by binding to nuclear RAR/RXR receptors, triggering expression of genes responsible for keratinocyte proliferation. Alpha Hydroxy Acids (glycolic, lactic acid) work differently — they break ionic bonds between corneocytes in the stratum corneum, accelerating mechanical exfoliation. The problem isn't that these mechanisms "contradict" each other — they add up, and that's exactly what's dangerous. Simultaneous use of retinol (even at 0.3%) and AHA above a 5% dosage is statistically shown to significantly increase transepidermal water loss (TEWL) and erythema frequency, as shown in Kong et al. (2021). The barrier doesn't have time to recover between two cycles of accelerated renewal.

An additional layer of complexity is pH. Retinol is stable in the pH 5.5-6.5 range, while AHA efficacy drops sharply above pH 4. A formula trying to "straddle" two environments at once usually loses stability for both actives: the retinol oxidizes faster, and the acid doesn't deprotonate to the degree needed to penetrate the stratum corneum.

Vitamin C and niacinamide: a myth that has outlived its shelf life

A classic worry: L-Ascorbic Acid and Niacinamide supposedly form niacin and cause flushing. This is true only when the mixture is heated above 60°C in an aqueous medium during prolonged incubation — a condition irrelevant to a finished cosmetic emulsion at room temperature. According to Wohlrab & Kreft (2014), the transamidation reaction between these molecules under physiological conditions proceeds so slowly that no clinically significant irritation occurs. Still, an AI model needs to account not for the reaction itself, but for the conditions that accelerate it: the manufacturing process, storage temperature, the final pH of the finished formula. If a cream is formulated with L-Ascorbic Acid at pH 3.5 (the stability optimum for this form of vitamin C), adding niacinamide at a high concentration creates an uneven buffer system where part of the molecules migrate into a suboptimal pH zone.

How AI models these constraints

A generative model doesn't "invent" a formula freely — it operates within a constrained optimization space, where each active ingredient is described not just by its usage rate but also by a vector of physicochemical parameters: stable pH range, decomposition temperature, redox potential, known incompatibility pairs from the literature and patent databases. In practice this is implemented as a penalty-function system: if the algorithm tries to combine retinol and AHA above a threshold concentration, the overall "formula score" drops, and the model searches for an alternative combination — for example, encapsulated retinol or PHA instead of glycolic acid, which is milder in its irritation mechanism.

That's exactly why the solution space AI actually sees is much narrower than it first appears: out of thousands of theoretical active combinations, usually no more than 15-20% remain chemically compatible once pH, temperature and oxidative stability are taken into account. More on this in the article on cosmetic formula stability.

Recommendation-engine architecture: from user data to a finished formula

Under the hood of any "AI picks your cream for you" service is not one model but a pipeline of several data-processing stages. Each stage solves its own narrow task, and only their sequential chaining turns disparate inputs — a photo, a questionnaire, complaints — into a specific list of actives with usage rates. Let's break down this pipeline link by link.

The input layer: what the model receives

The recommendation system works with three types of data, which are merged into a single feature vector before being fed into the model:

An important nuance: questionnaire data and the photo embedding live on different numeric scales, so before merging them normalization is applied (usually z-score or min-max) — otherwise one data source starts dominating the other purely due to the range of its values, not its actual importance.

Model block one: profile classification

The first stage solves a multi-class or multi-label classification task: the system doesn't assign the user's skin to a single type (a simplification from 1990s skincare questionnaires), but to a combination of states — for example, "seborrheic T-zone + peripheral dehydration + post-acne pigmentation." Gradient boosting (XGBoost, CatBoost) on tabular features is often used for this, or a small fully connected network if the input is a merged photo-plus-questionnaire embedding. The accuracy of this classification in published pilots ranges from 78-89% when checked against a dermatologist's assessment (per Kim et al., 2022) — higher than questionnaire self-diagnosis, but lower than a professional exam under a Wood's lamp.

Block two: the recommendation engine for active selection

After profile classification, a second model kicks in — the actual recommendation engine, which works on logic close to e-commerce product recommendations, but with strict chemical constraints. Two approaches are used here, often in a hybrid:

• Content-based filtering — matching the skin profile against a knowledge base of actives: each ingredient is pre-tagged with target conditions, mechanism of action, effective concentration range, and known incompatibilities.
• Collaborative filtering — training on historical data about how similar users responded to similar formulas (only works with a sufficiently large base of reviews and repeat purchases — tens of thousands of profiles).

The content-based component answers "what theoretically fits"; collaborative filtering answers "what actually worked for similar people." Without the first, the system recommends unsafe combinations; without the second, it loses sensitivity to real skin-response patterns that don't always match the theory.

The constraint layer: why the model can't just maximize efficacy

The final list of actives isn't chosen purely on "what will give the maximum effect" — sitting downstream of the recommendation model is a rule-based constraint layer that filters combinations by chemical compatibility, the formula's total acidity, and the maximum allowed concentration of irritating actives for a given sensitivity level. This is exactly the layer that stops the system from simultaneously assigning 10% Niacinamide and a high dose of pure acids to skin showing signs of a compromised barrier.

The output layer: what the user sees

The end result of the pipeline isn't a text description — it's a structured list with usage rates and application order:

This level of detail is a direct consequence of the architecture: the system doesn't "guess a product" — it assembles a formula from atomic decisions, each of which has passed through classification, recommendation, and a compatibility filter. More on how these percentages map to real lab usage rates is covered in the piece on active-ingredient dosage rates.

Skin types through the algorithm's eyes: oily, dry, combination — and what the model sees

When a user checks "I have oily skin" on a questionnaire, she's describing a subjective feeling — shine by midday, clogged pores, foundation "sliding off" by evening. The algorithm works with a different layer of reality: it operates with measurable physiological parameters that don't depend on mood, the weather outside, or how much coffee was drunk that morning. The gap between these two pictures of reality is exactly why neural-network skin-type classification is consistently more accurate than self-reporting.

Three markers the model looks at

Most algorithmic skin classifiers are built on three physiological variables that dermatologists have measured instrumentally since the 1980s, and which neural networks have learned to estimate from photos and indirect signs:

• Sebum rate — the rate and volume of sebum production by sebocytes. Measured clinically with a sebometer (in μg/cm²); from a photo the algorithm estimates it indirectly — via specular-glare patterns in the T-zone, the size and density of visible pores, and local pixel texture around the nose and forehead.
• Transepidermal water loss, TEWL — the rate of water evaporation through the stratum corneum, a key indicator of lipid barrier integrity. High TEWL signals dryness and heightened skin reactivity even when the skin looks normal visually. From a photo this is read via microtexture: flaking, uneven relief, areas with a matte, "tight" surface.
• Elasticity and firmness — the skin's ability to return to its original position after mechanical deformation, linked to the state of the dermis's collagen and elastin matrix. Measured instrumentally with a cutometer; the algorithm estimates it from wrinkles, microrelief and contour sagging over time (if a series of photos or video is available).

The combination of these three parameters produces not a single label of "oily/dry/combination" but a vector of values — for example, sebum rate 68% (high), TEWL 12 g/m²/h (normal range 4-10 g/m²/h), elasticity 0.75 (reduced). Classification is built on this vector, not on a visual "looks like oily skin."

Why self-assessment systematically gets it wrong

The gap between what people think about their own skin and what instruments show is a documented fact. According to Youn et al. (2002), self-diagnosed skin type matches objective sebometer measurements in fewer than 60% of cases; the biggest confusion is between "combination" and "oily" skin, and between "normal" and "dry." The reasons are predictable:

• Sebum output fluctuates by 20-40% throughout the day, so an "eyeballed" assessment in the morning and evening gives different answers.
• Dryness is often confused with dehydration (a lack of moisture in the stratum corneum rather than lipids) — these are two different mechanisms requiring different actives.
• Combination skin is statistically the most frequently misdiagnosed type: people either overestimate T-zone oiliness or don't notice cheek dryness because their attention is drawn to visible problems (pores, shine).
• Seasonality and "masking" makeup: foundation or a mattifying primer visually normalize the skin in the moment, distorting perception of its baseline state.

Combination skin: why it isn't "two types in one"

The algorithm treats combination skin not as a mix of oily and dry, but as zonal heterogeneity within the same set of parameters. The model divides the face into segments (T-zone, cheeks, periorbital area) and calculates its own sebum/TEWL/elasticity vector for each. The resulting profile isn't an averaged value but a map of differences: the T-zone may show a 70% sebum rate at 6 g/m²/h TEWL, while the cheeks show 25% sebum rate at 14 g/m²/h TEWL. This is critical for formulation: a serum with a single Niacinamide concentration for the whole face performs worse than a zone-specific active distribution, a point covered in detail in the piece on ingredient compatibility (/blog/himiya-sovmestimosti-aktivov).

Practical takeaway for formulation: the accuracy of skin-type classification directly determines the permissible active concentration range. A 15-20% error in TEWL estimation could lead to a formula with 2% Salicylic Acid being recommended for skin with an already compromised barrier — and instead of clearer pores, the user ends up with irritation and heavier flaking.

The formula's task: how AI tells "anti-acne" apart from "for radiance"

Skin type sets the formula's baseline constraints, but it's the target task that determines which actives make it into the composition first. For the algorithm this isn't a text label like "acne" or "radiance" — it's a vector of clinical endpoints, a set of measurable parameters against which an ingredient has proven its efficacy in studies. The model matches the user's request against this vector, not against a problem name.

From a query to a clinical vector

When a user writes "I want to get rid of breakouts," the system's NLP module translates the request into a combination of features: follicular hyperkeratinization, Cutibacterium acnes colonization, local inflammation, excess sebum production. A "for radiance" request decomposes differently: uneven stratum corneum, slowed cell turnover, micro-dullness from collagen glycation. This difference in request decomposition is the first level at which tasks are distinguished.

From there, each feature searches for a match in the actives database, where every ingredient is tagged not by marketing claim but by mechanism of action confirmed in studies:

Importantly, the same ingredient can appear across several tasks with a different weighting function. Niacinamide works on acne (sebum regulation), pigmentation (inhibiting melanosome transfer) and barrier repair (stimulating ceramide synthesis) alike — per Bissett et al. (2004) and subsequent studies. The algorithm doesn't pick an ingredient "for a task" — it sums its mechanisms' contribution across all of a user's active target vectors at once.

How clinical data calibrates the weights

Every "active → effect" link in the database carries not a binary value (works/doesn't work) but a numeric efficacy coefficient derived from meta-analyses. For example, for Azelaic Acid at 15%, the reduction in inflammatory acne lesions after 12 weeks is recorded at around 40-50% (per Sieber & Hegel, 2014), whereas Salicylic Acid at 2% gives a more modest but faster effect against comedones. The model accounts not only for whether something works, but for the speed of response — critical when setting user expectations.

A second calibration source is aggregated feedback. When thousands of users with similar digital skin profiles report changes in specific parameters (oily shine, papule count, skin tone) after 4, 8 and 12 weeks of use, the system recalculates recommendation weights. This works like a Bayesian update: clinical data sets the prior efficacy distribution, and behavioral feedback provides a posterior correction for the real user population — not just for laboratory-study conditions.

Conflicting tasks within a single formula

Complexity arises when a user states two goals at once — "clear acne and add radiance." The vectors partially overlap (both goals need desquamation) but partially conflict: aggressive sebum regulation can worsen the dryness and dullness the user is trying to fix. The algorithm resolves this by prioritizing based on condition severity — active inflammation gets a higher weight than an aesthetic goal, while supporting actives (antioxidants, for instance) are introduced at a supportive rather than a therapeutic concentration. More on how the system resolves such overlaps at the ingredient-compatibility level is covered in the piece on active-compatibility chemistry.

Limitations and risks: when the algorithm gets it wrong

A recommendation system is only as good as the data it was trained on. This rule sounds banal, but it explains most of the systematic errors in AI active selection. The model doesn't "understand" skin — it finds statistical patterns in a sample, and if the sample is skewed, so is the result.

Bias by phototype and ethnicity

Most open dermatological datasets used to train computer-vision models for skin analysis have historically consisted predominantly of images of lighter phototypes (I-III on the Fitzpatrick scale). Post-inflammatory hyperpigmentation, common in phototypes IV-VI, is detected worse by such models: the algorithm confuses it with an inflammatory lesion or fails to flag it as a distinct issue altogether. Per Adamson and Smith (2018), the lack of diversity in dermatological image datasets systematically lowers diagnostic accuracy specifically on medium and dark skin tones. For active selection this creates a risk: the system may fail to recommend brightening ingredients like Tranexamic Acid or Alpha Arbutin where they're objectively needed, simply because it didn't recognize the pigmentation pattern as pathological.

Overfitting to marketing data

Some recommendation services are trained not on clinical data but on product-listing copy, reviews, and brand marketing descriptions. In such a dataset, words like "hydrates," "minimizes pores," "evens out tone" appear far more often than actual TEWL (transepidermal water loss) or sebumetry measurements. The model starts overfitting to the seller's rhetoric rather than to the ingredient's biochemistry. The result: the system confidently recommends a formula with 2% Niacinamide "for pore minimizing," even though a clinically noticeable effect on sebum secretion is recorded starting at 4-5% (per Draelos et al., 2006) — and the packaging doesn't even list the concentration.

Lack of medical history

None of the mass-market consumer skin-photo-analysis systems has access to a history of allergic reactions, systemic medications (isotretinoin, anticoagulants, hormone therapy), or coexisting dermatoses — rosacea, perioral dermatitis, atopy. The algorithm sees texture and color, but doesn't "know" that a user is taking warfarin, or that a high concentration of Retinol combined with acid exfoliants will raise irritation risk on top of a fine vascular network. No visual analysis replaces a patch test and history-taking.

Why dermatological validation is needed

A model that shows high accuracy on an internal test set isn't automatically clinically valid. The gap between accuracy on a dataset and real diagnostic value is a standard ML-in-medicine problem, described for instance in Kim et al. (2019) with respect to dermoscopic CNNs: models trained on one population lose up to 20-30% accuracy when transferred to a different ethnic or age group without additional calibration. For cosmetic recommendation systems, this means a claimed "90% accuracy" almost always refers to a narrow sample and doesn't guarantee the same result on a specific user's face.

Practical takeaway for anyone designing or using such systems: an AI recommendation is a formula draft that requires verification on real skin, a patch test, and — in borderline cases — a dermatologist consultation. Automation speeds up active selection, but it doesn't remove responsibility for the final decision from the person composing the formula.

The future of personalization: from recommendation to made-to-order production

Everything described above — skin recognition, active-compatibility checks, formula-task matching — operates within the existing assortment: the algorithm picks a finished product or, at most, suggests "mixing serum A with cream B." The industry's next step is to remove the intermediary of a ready-made product line altogether. Instead of a recommendation, the system is handed the authority to generate a composition from scratch for a specific digital skin profile — and then manufacture exactly that formula as a single unit.

This is a fundamentally different business architecture: not "10,000 identical jars" but a micro-batch for one person — a batch of 1 to 50 ml, assembled to parameters that no other client shares. Technically, this became possible thanks to three converging directions: generative models capable of proposing not a finished product but a vector of concentrations; modular production lines with dosing units that blend actives in real time; and 3D printing of cosmetic forms, where the printer serves as the final assembly step.

Generative selection instead of classification

Current recommendation systems solve a classification task: "this skin profile fits product X from the catalog." A generative model solves an optimization task: "which combination of 15-20 permitted actives, in what proportions, gives the maximum expected effect at zero incompatibility risk." The input is the same digital skin profile (texture, sebumetry, hydration, response history), but the output isn't a product name — it's a numeric vector: for example, Niacinamide 4%, Sodium Hyaluronate 1%, Panthenol 3%, base to 100%. This approach is being tested in lab pilots at several major manufacturers (per Guo et al., 2022, generative models built on formulation databases predict stable active combinations with an accuracy comparable to human formulators' solutions within limited categories — moisturizing emulsions and antioxidant serums).

3D printing: from concept to shelf

3D printing of cosmetics is no longer a futuristic metaphor — extrusion printers for semi-solid textures (balms, masks, sticks) handle a viscosity of 5,000-50,000 mPa·s and allow different actives to be layered within a single item: for example, a zone with an elevated Salicylic Acid concentration across the T-zone of a mask, and a zone with Ceramide NP around the face's periphery. Printing temperature ranges are limited by the thermal sensitivity of the actives: most peptides and vitamin C in the form of Ascorbic Acid can't withstand extrusion above 40°C, which pushes manufacturers toward stable derivatives — Sodium Ascorbyl Phosphate or Ascorbyl Glucoside, stable up to 60-70°C.

What still has to mature in biotech

Generative personalization is held back less by model power and more by the constraints of chemistry and biotech. Three bottlenecks:

• Stability at small volumes. A micro-batch without a preservative system designed for industrial scale spoils faster — new preservative-selection protocols are needed (for example, Phenoxyethanol combined with Ethylhexylglycerin) for a 10-50 ml volume, given a 2-4 week usage window.
• Biosensors for input data. A generative formula's accuracy depends directly on the accuracy of the skin profile: wearable biosensor development (real-time TEWL, pH, microbiome measurement) needs to catch up with the algorithms' ambitions.
• Regulatory framework. Cosmetics legislation (in the EU, Regulation 1223/2009) was written for serial production with a fixed composition; there is still no clear safety-certification protocol for formulas that change with every customer's unique batch.

A realistic horizon for the mass shift from recommendation to made-to-order production is 5-8 years, and the first to adopt it won't be mass-market brands but niche dermatology clinics and premium labs, where the cost of a single micro-batch is justified by medical precision. For specialists learning to formulate by hand today, this trend isn't a threat — it's a shift in role: from creating one formula for thousands of people to setting the rules by which an algorithm creates thousands of formulas for one person.

Conclusion: trust the algorithm or trust your skin

Across nine sections we've traced the path from a skin photo to a production line capable of assembling a serum around a specific data set. But the ultimate question is always the same: who decides what ends up on a face — the model or the person. The answer isn't binary. The algorithm is precise about what's measurable: Niacinamide concentration, Retinol-and-AHA compatibility, the pH window for Ascorbic Acid stability. It's blind to what requires context — hormonal background, pregnancy, isotretinoin use, a person's psychological relationship to a product's texture and scent.

What the algorithm does better than a person

A neural network never tires of cross-checking dozens of parameters at once and isn't subject to cognitive biases like "this ingredient is trendy, so it must be good." It holds the entire active-compatibility table in memory and recalculates the formula in seconds if even one input parameter changes — regional humidity, season, a new sebumetry reading. It's physically hard for a person to hold 40+ variables of INCI compatibility in mind during every single consultation.

A practical model: algorithm as draft, human as editor

The working scheme that emerges from everything covered above looks like this: AI generates a composition hypothesis based on the digital skin profile and the stated task, and a specialist — a cosmetologist, dermatologist, or a sufficiently informed user — makes corrections the model couldn't account for. This isn't unlike how a GPS navigator works: it proposes a route based on map and traffic data, but the driver sees a closed road that isn't in the database and adjusts the route manually.

• Step 1. The algorithm analyzes the photo and questionnaire, outputs 2-3 formula options with key actives and their usage rates.
• Step 2. A cosmetologist or the user checks the option for obvious incompatibilities with the current routine — for example, prescription Tretinoin already in use, which the algorithm may not know about.
• Step 3. A patch test is run on the inner forearm for 48 hours, regardless of how "safe" the algorithm labeled the composition.
• Step 4. The skin's response is recorded and fed back into the system as a new data point for the next recommendation iteration.

What this means for those who formulate and sell cosmetics

For specialists developing formulas, AI-assisted selection isn't a threat to the profession — it's an expansion of the toolkit, comparable to the shift from manual emulsion calculations to software-based stability modeling. Understanding how a model interprets skin data and why it sometimes gets things wrong (see the section on limitations) is becoming part of a formulator's basic literacy — just like knowing emulsifier chemistry or the temperature regimes for Phase A and B.

The bottom-line position that holds up against both data and practice: the algorithm can be trusted with compatibility calculations and a first-pass concentration selection, but the final arbiter of safety and comfort remains a person — either a specialist with a medical background or the user herself, armed with an understanding of her own skin and the basic principles of active-ingredient chemistry. The technology shortens the guesswork, but it doesn't remove the need to listen to the skin's response here and now — it updates faster than any model can retrain.

Selecting actives is only the beginning — verifying compatibility and working concentrations comes next. The AI Chemist in the Walker Formulation Academy Club does this based on a verified INCI/CosIng database, not guesswork, and flags where actives conflict. If you want to master active selection systematically, the club offers a program with a live instructor.