A cosmetics business is a substance business in operational drag. The portfolio runs to hundreds or thousands of SKUs across multiple brands, each formulated to different regulatory rules in every market it ships to. Raw materials have lots, expiries, retention samples and certificates of analysis that all need to travel with the batch. Finished goods are recalled by lot, not by SKU, which means the lot genealogy has to be live, not reconstructed.

On top of that, regulation moves. A new SVHC addition, a revised Annex III concentration limit, a MoCRA guidance update or a Chinese NMPA change can make a formula and therefore a batch and therefore a label non-compliant overnight. An ERP that does not know about the regulatory file cannot propagate that change to operations, so the regulatory team ends up chasing batches with email.

ERP software for the cosmetic industry is the answer when it is built for the industry, not bent into shape from a generic mid-market ERP. The difference shows up at audit, at recall, and at launch.

Inventory and batch management. Raw materials, semi-finished bulks, finished goods and components managed by lot, expiry and location. Multi-warehouse and multi-site with real-time stock. Production work orders that pull components by lot, capture deviations, and close the batch record electronically against ISO 22716 and MoCRA cGMP expectations.

Lot traceability and recall readiness. Full genealogy from raw material lot through bulk and fill to the customer despatch line. A recall query that takes seconds, not days. Retention samples linked to batches, batch records linked to the formula version that was assessed, and the formula version linked to the PIF and CPSR that approved it.

Procurement and supplier management. Supplier specs, CoAs and SDSs captured as structured data, not PDF attachments. Goods receipt QC linked to the spec, with automatic flagging of out-of-spec lots. Spend and price history per supplier and per material.

Integration with regulatory content and formulation. The ERP shares its data model with the cosmetic formulation software and the regulatory file. A formula change updates the BOM. An ingredient restriction flags every affected batch. A label artwork update triggers a version on the next production run. No re-keying, no parallel spreadsheets.

Finance, despatch and customer. Sales orders, despatch, EDI to retailers and 3PLs, invoicing and an open API into the corporate finance ledger (Xero, NetSuite, SAP, Dynamics) if you would rather keep the books elsewhere.

The platform is built so regulatory updates feed into operations as a first-class workflow, not a quarterly content release. Regulator feeds from ECHA, MHRA, FDA, NMPA and MHLW are ingested into the substance master. When a substance moves on Annex II, III or VI, when a new SVHC is added, or when MoCRA guidance changes, every affected formula, batch, label and notification is flagged automatically.

That means the regulatory lead does not have to email the production manager to halt a batch. The batch flags itself. The CPSR refresh queues. The CPNP or SCPN notification update drafts. The label artwork team gets the new INCI list. The recall workflow is already armed with the lot list, should it come to that.

See the cosmetic compliance software buyer's guide and the ERP vs PLM vs compliance explainer for the wider context.

Cosmetic manufacturers and CMOs. Multi-customer, multi-brand production with customer-specific specs, regulatory ownership models (manufacturer-held vs brand-held PIF / responsible person), tolling workflows and the lot traceability customers will audit you on.

Brand owners. A single operating system across in-house and contract-manufactured production, with the regulatory file owned in one place regardless of who makes the product. Direct line of sight into CMO batches, lot status and document compliance without a chain of spreadsheets.

Private label partners. Manage hundreds of customer variants of base formulations, with customer-specific INCI ordering, claims, labels and notifications generated automatically from the parent formula. The platform tracks which customers received which version, and when their next notification update is due.

The Iconic London case study is a worked example of a fast-growing brand consolidating operations and regulatory on one platform.