In this guide 6 sections
Make each shade a variant of one parent product, with its own SKU, swatch image, stock count and tags for depth, undertone and finish. Then build a short match quiz that reads those tags and returns two or three close shades, with a reason for each. Track wrong-shade returns by variant. The weak shades will show up.
Step one: make each shade a variant, not a product
Create one parent for each formula, such as a liquid foundation. Hang every shade beneath it as a variant. Reviews, ingredients and the application video then live in one place, not copied across a long run of near-identical pages.
Each variant needs its own SKU, barcode and stock count. Name the shade the way the pack does, because shoppers match the name printed on the box against the one on the screen. One set of fields serves lipstick, concealer and foundation.
Keep sold-out shades on the page. A notify button turns a lost sale into a count of how many tubes the next production run should cover.
- One parent product per formula, never per shade
- SKU pattern that shows formula and shade code
- Barcode and stock count on every variant
- Shade name spelled as it appears on the box
- Sold-out shades stay visible with a notify option
Step two: tag depth, undertone and finish
Depth runs from fair to deep. Undertone runs from cool to warm, with neutral and olive between. Someone who has swatched the shade on real skin should set these tags, not the person who typed the product name into the admin screen.
Keep every list fixed. Lipsticks take different tags: a colour family such as nude, rose, red or berry, plus finish and intensity, since depth and undertone describe skin, not lips. Concealers should also carry the foundation shades they pair with, since many shoppers add both to one basket and wonder whether the two match.
Review the tags with a second pair of eyes. Two staff swatching the same tube under one light will sometimes disagree on undertone, and that argument is cheaper before launch than after.
- Depth scale from fair to deep, one value per shade
- Undertone: cool, warm, neutral or olive
- Finish chosen from a short fixed list
- Colour family and intensity for lip products
- Paired concealer shade for each foundation shade
Step three: photograph swatches the way skin shows them
Phone screens bend colour. Shoot every swatch in the same daylight setup, on a forearm, against a neutral card, with identical camera settings. Add a small colour chip for the selector, so the shade appears before the full photo has loaded on a slow mobile connection.
Show each shade on models of different depths. A lipstick that reads plum on a fair lip can turn brown on a deep one, so a single studio photo misleads buyers at either end. Name each file with model and shade code.
Capture the packaging too. A bullet, a pan and a cap each show a different colour from the one on skin, so the swatch should come first and the pack photo second.
- Same light, same card, same camera settings
- Swatch chip for the selector, full photo on click
- Models across depths, shade code in the filename
- Close-up of the bullet or pan for lipsticks and palettes
Step four: build a short match flow
Open with a question shoppers can answer without guessing: which foundation do you wear now, and from which brand? Behind it sits a lookup table. It maps popular shades from other ranges to your own variants, and your team builds it once from swatches laid side by side.
Follow with two plain questions on undertone and depth, such as how skin looks in sunlight and whether silver or gold jewellery suits it. Return two or three shades. Give one line of reasoning for each. Keep a “not sure” route that leads to a mini sample set, because a wrong guess costs a return.
Test it on colleagues of every depth. Record the shade each person is given, then compare it with the shade they actually wear, and rewrite any question that sends testers to the wrong shade.
Step five: let the returns data correct the setup
Add “wrong shade” to the return reasons. Tie each return to its variant. A report can then rank every shade by how often it is sent back, and the worst offenders tend to share a lighting problem or a tag error. After a season, sort by variant. A shade that keeps coming back is usually mis-tagged or badly photographed, and the formula itself is rarely at fault.
Watch for pairs: a shopper who orders two neighbouring shades in one basket is hedging, and the match flow has failed them. Start this week. List the three variants with the most wrong-shade returns and swatch them again beside the shade a customer chose instead.
Shade tagging sheet
A spreadsheet with one row per variant. The columns are parent product, variant SKU, shade name, depth, undertone, finish, swatch file name, closest shade from another brand and stock count. A second tab holds the allowed values for depth, undertone and finish. Nobody invents a new tag.
Open a blank worksheet to printQuestions owners ask
How many depth levels should a range use?
Use enough that neighbouring levels look different on a screen. Use no more than your range can fill. Too many levels leave empty buckets, and a shopper who filters to a page with zero results rarely tries a second time.
Can lipsticks use the same tags as foundation?
Partly. Finish and stock fields carry over. Depth and undertone suit lip colour less well, so add a colour family such as nude or berry, plus an intensity tag.
Does virtual try-on replace a shade quiz?
It helps with lip colour and eyeshadow more than base. Camera light and screen settings shift skin tone. Test any tool on staff of several depths and in both daylight and indoor light before you trust it for foundation matching.
Should returned shades go back on sale?
Opened makeup is usually unsaleable. Your hygiene policy and the rules in your market decide the exceptions, such as a sealed unit returned unopened. Record the shade and the reason. Write the unit off so the counts stay true.