ERP for cosmetics manufacturers: what an ERP system covers and where product development begins

An ERP (enterprise resource planning) system maps the commercial and operational processes of a company. In cosmetics manufacturing that mainly means purchasing and supplier orders, inventory for raw materials, packaging and finished goods, production planning with bills of materials and manufacturing orders, batch management, sales, shipping and financial accounting.

Industry solutions for process manufacturing add functions a generic ERP does not have: formulas rather than plain bills of materials, shelf life and expiry dates in the warehouse, batch traceability from raw material to shipped product, and support for documentation under cosmetic GMP (ISO 22716).

Start with traceability: for a shipped batch, can you find every raw-material batch that went into it, and the other way round? That is the basis of a recall and is what auditors ask for.

Then check the formula logic. Cosmetics are formulated in percent and phases but produced in kilograms per batch. A suitable system converts between the two, accounts for yield and overfill, and manages several valid versions of a formula.

Further points are shelf life and blocked stock, contract manufacturing with customer-supplied materials, connections to an online shop or retail, and the effort of implementation and customisation. For smaller manufacturers the last point often decides.

An ERP expects master data that is settled. Development is the opposite: a formula goes through many variants and most are discarded. Each variant comes with lab batches, observations, stability and challenge tests, cost snapshots, raw-material alternatives and a regulatory assessment.

That data has no natural place in an ERP. In practice it ends up in spreadsheets, lab notebooks and email threads. The outcome is familiar: nobody can say for certain which version was tested, why a raw material was replaced, or which documents belong to the approved formula.

A clear division of labour works best. The development system owns everything up to approval: brief, formula versions, raw-material data with INCI and limits, tests and the approval decision. On approval, exactly the data the ERP needs for purchasing and production moves across: the formula as a bill of materials, the raw materials, the manufacturing instruction.

Three questions should be answered before any rollout. Which system owns which data object? What triggers the hand-over? And what happens in the ERP when an approved formula changes later?

Very small manufacturers with a few products often manage with a lean ERP or inventory system and carefully kept formula sheets. Once several people develop, customer projects run in parallel or audits are due, development becomes the bottleneck and a dedicated system pays off.

Contract manufacturers reach that point earlier than brands: they develop for many clients at once, must keep their formulas strictly separate, and need to evidence samples, approvals and changes per customer.

VYVA is not an ERP. The platform covers product development: projects and briefs, formulas with versions, raw-material and INCI data, testing and stability, manufacturing protocols and development batches, approvals and a customer portal. Purchasing, inventory, order processing and accounting stay in the ERP. An API for handing approved data over to an ERP is planned but not available yet. Which data is kept in which system is defined together during onboarding.