PIM for cosmetics: shades, ingredients and variants
Plan cosmetics product data around shades, ingredient sources and variant identity, then verify that channels publish the right product facts.
- Published
- Last updated
PIM for cosmetics needs to keep each sellable shade and size tied to its manufacturer’s product information. Product information management (PIM) must preserve that identity when ingredients change or a channel publishes a different image. A complete family record can still send the wrong formula to a customer if its variants inherit the wrong fields.
Build the model around the item your warehouse supplies. Then follow one changed variant through approval to its product page and every downstream feed.
Define the cosmetics variant
Separate the product family from the item a customer can buy. A lipstick range can share a brand and description while its shades have different swatches and ingredient references. A gift set needs its own sellable record even when its contents already exist individually.
Use these fields to decide where information belongs.
| Record or field | What to store | Mistake to prevent |
|---|---|---|
| Product family | Manufacturer range and shared description | Treating the family as the item ordered |
| Shade | Manufacturer shade code and display name | Matching two products by colour name alone |
| Finish | Manufacturer’s finish description | Replacing a finish with an image-derived guess |
| Size | Quantity and unit for the sellable item | Combining a travel size with the full-size item |
| Sellable identifier | Retail stock keeping unit (SKU), manufacturer identifier and barcode where supplied | Updating a sibling variant or a gift pack |
For a real example, Clinique’s Australian Almost Lipstick page names Black Honey, Pink Honey and Nude Honey. It displays a 1.9 g size and a soft-shine finish. Store those as distinct data fields instead of making a product title carry the whole relationship.
Wrong mapping: every shade receives the first variant’s image and ingredient reference. Correct mapping: shared fields inherit from the family, while shade-specific facts belong to the manufacturer’s identified variant. Promote a field to the family only after confirming that it applies to every child.
Model sourced ingredients and assets
Keep the manufacturer’s ingredient text with its source document and revision reference. Preserve ingredient order and any supplied qualifications. A searchable ingredient field can sit beside that text, but it must retain a link to the source record.
Clinique’s limited-edition Black Honey page publishes an ingredient list with reference ILN52393. It also directs customers to the received packaging because ingredient lists can change. This is a reason to record which formula and market a supplier file covers, even when the shade name stays unchanged.
Keep the market distinction explicit. A US ingredient page is not evidence that an Australian shipment has the same formula. Resolve conflicting packaging and supplier files with the manufacturer before replacing the published ingredient record.
Give each asset its own relationship to the product. A swatch needs a shade identifier. A pack image needs the corresponding size and packaging version. Lifestyle photography can apply to a family, while an ingredient-panel photograph belongs to the packaging it shows. Store usage rights and the approved channel for each asset.
Claims need separate fields for the manufacturer’s wording and its supporting evidence. An ingredient’s presence does not establish a therapeutic effect or an allergy-safety promise. Keep claims review with the person authorised to approve that wording, and prevent generated descriptions from adding effects that the source does not establish.
Map channel fields individually. The product page can show the full ingredient text while a feed uses an approved description and variant image. Record omitted fields so an answer source never fills a missing ingredient list from another shade.
Verify each published variant
Use a fictional lipstick range called Harbour to check the handover. Its Rose shade has a satin finish, a 4 g size and retailer SKU HAR-ROSE-4. The manufacturer later renames that shade Rosewood and issues formula reference F2. The Sand shade keeps its existing name and formula F1.
Before editing, establish which stock the new formula applies to. If old and new packs are sold together under one identifier, resolve how the warehouse distinguishes them. A catalogue edit alone cannot identify which formula a customer receives.
Run the following check on the resolved records.
- Import the Rosewood proposal against HAR-ROSE-4 using the supplier’s identifier mapping. Confirm that Sand remains unchanged.
- Compare F2’s ingredient text with the source document. Attach the new swatch and pack image to Rosewood, preserving F1 in the revision history.
- Approve the changed fields and export them to a test storefront and feed. Record the export result against that revision.
- Select Rosewood on the product page. Confirm the chosen item’s identifier, size, image and ingredient text match the approved record.
- Inspect the feed row and refresh the catalogue used for product answers. Ask for Rosewood’s ingredients, then repeat for Sand. Each answer must use its own approved formula reference.
If the page shows Rosewood but retains Rose’s old swatch, inspect the asset mapping and cache refresh. If Sand acquires F2, inspect parent inheritance before repeating the export. Give the failed check to the owner of that mapping and keep the affected update out of publication until corrected.
Compare the operating requirements
Evaluate a PIM against your supplier changes and channel handover, using the same sample variants for every candidate. Ask the supplier-import owner to demonstrate a rejected update as well as an accepted one.
Akeneo’s variant documentation distinguishes common product-model attributes from a variant’s own attributes. Its Supplier Onboarder review documentation describes mandatory review of supplier proposals before they affect PIM data. It also covers proposed assets and separate model or variant changes. Those are concrete behaviours to compare with your requirements, not evidence that every PIM edition includes the same workflow.
| Operating requirement | Demonstration to request | Owner of an exception |
|---|---|---|
| Supplier import | An existing shade update matches one identifier and leaves siblings intact | Supplier-data owner |
| Approval | A rejected ingredient change stays out of the next export | Product-data approver |
| Translation | A revised source description flags its translated versions for review | Localisation owner |
| Digital assets | A replacement swatch changes only the intended shade and channels | Asset owner |
| Channel delivery | An export failure identifies the variant and can be retried without duplicating records | Integration owner |
Include responsibility for formula questions in the operating agreement. Decide who contacts the manufacturer, who approves the corrected record and who confirms the channels received it. Keep those responsibilities beside the broader PIM industry requirements when different catalogue teams share the system.
Choose the model and workflow that can carry Harbour’s isolated shade change through to the customer’s selected item. Make a correct ingredient answer and an unchanged sibling variant part of the acceptance check.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.