AI Beauty

Resources

Preparing your shade catalog for Virtual Try-On and Shade Finder

Minimum SKU fields, category priority and a pilot slice checklist for brand ops.

Try-on and shade match quality track catalog quality. This English sales-enablement guide lists the minimum SKU fields and how to pick a pilot slice — without promising “digitize everything this weekend.”

Minimum SKU fields

• Stable ID / SKU — analytics and PDP deep links;
• Display name — what the shopper sees;
• Category — lips / blush / eyes / foundation / other;
• Color reference — swatch, packshot, or internal hex/Lab;
• Finish — matte / satin / shimmer when it changes rendering;
• PDP URL — post-try-on destination;
• Status — in pilot / hidden / discontinued.

Undertone labels help when consultants already use them. Do not invent fields nobody owns.

Category priority

1. Foundations / BB — high shade risk;
2. Lips — clear try-on value;
3. Blush;
4. Eyes — if you have calibration capacity.

Pilot slice vs full catalog

Dozens of shades beat thousands of incomplete rows. Goal: prove UX, funnel and calibration process. Full catalog follows a repeatable update path (new SKU → data → QA → publish).

Related: integration guide, match-then-try workflow, pilot.

Handoff checklist

• No duplicate IDs or empty names.
• Every pilot SKU has a swatch or agreed reference.
• PDP links resolve.
• Discontinued items flagged.
• Named data owner for calibration rounds.

Send a CSV/Sheets export with the pilot line marked — we will assess readiness for Try-On and Shade Finder without dating a go-live before seeing the data.

Send a catalog for review