How to evaluate cosmetics PLM vendors: 24 questions for manufacturers

What makes cosmetics PLM evaluation different? 

Cosmetics and personal care product development involves requirements that generic PLM evaluations may not examine in sufficient depth. 

Formulations are ingredient-level and percentage-based, with calculations updated as ingredients, concentrations, variants, or target markets change. Ingredient naming follows INCI conventions that differ from raw material naming, and the mapping between them has to be maintained. Regulatory obligations vary by market and change frequently — EU Cosmetics Regulation 1223/2009, FDA OTC monograph requirements, China NMPA registration, ASEAN cosmetic directives, and regional restricted and positive substance lists all operate on different rules and different update cycles. 

A platform may perform well against bill-of-materials criteria while still lacking the formulation depth required in production.

How do you use this checklist? 

Work through each question during vendor demos, RFP responses, and reference calls. For each question, record whether the vendor meets, partially meets, or does not meet the requirement. 

Then score each vendor 1–5 per category, using the same panel for every vendor. A score below 3 in any category should be treated as a red flag. 

Takeaway: Same questions, same panel, same scale, for every vendor on the list. 

01. How do you assess cosmetics industry expertise and domain knowledge?

Does the vendor have a proven track record specifically in cosmetics, personal care, and beauty — not just general manufacturing or discrete industries such as fashion and apparel? 

Platforms built for discrete manufacturing are often centered on assemblies and bills of materials rather than percentage-based formulation, ingredient traceability, or multi-market regulatory logic. Where these capabilities require extensive customization rather than standard configuration, the implementation effort, cost, and long-term maintenance requirements may increase.

Can the vendor demonstrate native support for cosmetics formulation management, INCI calculations, multi-market regulatory compliance, and ingredient traceability — rather than workarounds built on a non-formulation platform?

Ask to see it in the product, not in a slide. Capability that is native on day one behaves differently under change than capability assembled during implementation, and the difference only becomes visible when a regulation moves.

How long has the vendor served cosmetics and personal care manufacturers, how many cosmetics customers do they have today, and can they provide named references in your specific product category — skincare, color cosmetics, fragrance, or personal care?

A reference in an adjacent category answers a different question than the one you are asking. Ask for a customer who makes what you make, at roughly your scale, and who has made the same move you are about to make.

03. How do you assess formulation management and product documentation?

Does the platform support the formulation workflows relevant to your product categories, including formula versioning, trial and variant management, formula comparison, product requirement traceability, and compliance checks during formulation?

Cosmetics formulation is iterative. Platforms that treat formulas as static records rather than versioned objects with variant management and linked compliance checks create a bottleneck at every reformulation cycle.

Can the system automatically generate INCI declarations, Product Information Files, Safety Data Sheets, Technical Data Sheets, and product labels directly from the formulation of record — and do those documents update automatically when a formula changes?

Manual compilation does not scale across multi-market launches, and it creates audit exposure the moment documentation falls out of sync with the formulation it describes. Ask specifically about the update behavior, not just the generation.

Does the platform integrate with cosmetics ingredient databases to give formulators searchable raw material data, sustainability attributes, and supplier information inside the formulation workflow?

Ask whether formulators can search ingredient data, review supplier information, and create new ingredient records without repeatedly transferring data between external sources and the PLM.

04. How do you assess ERP integration and supplier collaboration?

Does the platform offer true bi-directional ERP integration with your specific ERP, so formulation changes, bills of materials, and packaging data flow both ways without manual re-entry? 

One-way integrations create version-control problems and a silo between R&D and operations. Ask about your ERP by name and version, not about ERP integration in general. 

Does the platform include a built-in supplier collaboration portal where suppliers upload raw material specifications, safety data, certifications, and compliance documentation — with automated validation and expiry tracking?

Where supplier data is managed by email, outdated specifications find their way into active formulations and expired certifications surface during audits. Expiry tracking is the part most often missing.

How are API updates and integration maintenance handled when your ERP or other enterprise systems upgrade — does the vendor manage this, or does it fall to your IT team?

Integration maintenance is one of the most consistently underestimated cost lines in a PLM investment. Get the answer in writing, and get it before the contract rather than after the first ERP upgrade.

05. How do you assess implementation, support, and long-term partnership?

What does onboarding look like — is there a structured methodology with a dedicated implementation team, defined milestones, and data migration support?

Unstructured implementations are a leading cause of PLM project overrun and low adoption. Ask who does the implementation: the vendor’s own team, or a third-party partner — and who is accountable when the two disagree.

What are the support SLAs for critical issues, and does the vendor provide dedicated account management, in-house regulatory expertise, and proactive customer success — or only ticket-based support?

Where compliance deadlines are fixed, reactive ticket-based support is a risk. Ask who you call, in what language, in what time zone, and what the response commitment is in writing.

How does the vendor communicate roadmap changes, and how does customer feedback reach the product? Can they show features built in response to cosmetics customer needs?

A roadmap shaped primarily by customers in other industries leaves you managing workarounds as your requirements change. Ask for two or three specific examples with dates.

06. How do you assess scalability, AI, and future readiness?

Can the platform scale to support new product categories, additional markets, a growing supplier network, and brand acquisitions without re-implementation or major customization?

PLM decisions outlast the business case that justified them. A platform that cannot absorb a new category or an acquisition forces a re-selection earlier than planned — which is how most companies end up running an evaluation they did not budget for.

Which AI capabilities are available in production today, for example specification data extraction, regulatory analysis, or formulation assistance? For each capability, ask which data it uses, how outputs are traced and validated, where human review is required, and which capabilities remain on the roadmap.

Separate what is live from what is planned. Ask which capabilities are in production with named customers today, how their outputs are governed and traceable, and whether the vendor can demonstrate the capability with your own data rather than only a demo dataset.

Does the vendor support flexible deployment — cloud, on-premises, private cloud — and can you integrate third-party tools, AI models, or sustainability databases as requirements evolve?

Deployment and integration flexibility is what protects you from a vendor switch when a new obligation arrives that the platform does not natively cover.

07. How do you assess packaging data governance?

Packaging is where cosmetics evaluations most often stop short. Packaging specifications, artwork versions, and approval trails commonly sit outside the PLM — in a separate system, or in files. That works until a reporting obligation requires packaging composition data tied to a specific product in a specific market.

The EU Packaging and Packaging Waste Regulation (PPWR), Regulation (EU) 2025/40, has applied generally since 12 August 2026 and replaces Directive 94/62/EC. It covers packaging placed on the EU market and includes extended producer responsibility provisions, although specific requirements follow the timelines set out in the Regulation and its implementing measures.

Are packaging component specifications managed natively in the platform, or through an integration or a partner tool?

Where packaging lives outside the product record, every packaging-linked question becomes a reconciliation exercise between two systems that were updated at different times. 

Can material composition, weight, and recyclability attributes be recorded against each component and rolled up per product and per market? 

PPWR and national EPR schemes increase the need for reliable packaging data. Manufacturers should determine which composition, weight, material, recyclability, market, and producer data must be maintained for their packaging portfolio under the requirements applicable to them. 

Is artwork version control and approval native, including proofing and sign-off trails? And when a packaging component changes, does the change propagate automatically to every affected product record

Artwork errors are among the most expensive to correct after production. Ask what the system does automatically when a component changes, and what still depends on someone remembering. 

08. How do you assess multi-category scope and analytics?

Businesses change shape. Brands acquire, enter adjacent categories, take on private label work, or expand into personal care, home care, or food supplements. A platform selected for a single category behaves differently once the portfolio widens.

Which product categories does the platform support natively, using the same data model and the same regulatory engine? 

Native means one data model and one regulatory engine, not a second module with its own rules. Ask which categories share the engine and which are handled separately.

If we add a category outside cosmetics, is that a configuration, a separate module, or a separate implementation? And can multiple business units run on one instance with separate governance but shared master data?

The answer determines whether growth is a change request or a project. Ask what an existing customer with two categories actually runs — one instance or two. 

Is portfolio and compliance reporting native, or does it require export to a separate analytics tool? And what is total cost of ownership across the full contract term if the portfolio expands into a second category?

Reporting that depends on monthly exports is reporting that is always slightly out of date. Ask for total cost across the contract term under a growth scenario, not first-year license cost under today’s scope.

How should you score vendors?

Score each vendor 1–5 in every category, where 1 does not meet requirements and 5 exceeds them. Use the same panel for every vendor. 

Treat any score below 3 as a red flag. A vendor with a strong total score but a score below 3 in cosmetics industry expertise or regulatory intelligence is a poor fit for a cosmetics manufacturer regardless of other strengths. 

Score your incumbent alongside every other vendor. If the incumbent is not on the scorecard, the exercise is a formality rather than an evaluation. 

What should you do once the scoring is done?

1. Compare total scores and category scores side by side. A high total masking a sub-3 score in a foundational category is not a pass.
2. Look at where the gaps cluster. Gaps concentrated in one category are a negotiation. Gaps spread across several are a fit problem.
3. Re-check your scope. If categories 07 and 08 scored low across every vendor on your list, the shortlist was built for a narrower scope than the business needs.
4. Ask each finalist for a migration timeline only after they have completed a data assessment — and ask what the estimate is based on.