Almost every cosmetics business starts formulation in Excel, and a surprising number of nine-figure brands are still there. The reason is obvious: a spreadsheet is free, flexible, and every chemist already knows how to use one. The reason it eventually breaks is that a cosmetic formula is not a spreadsheet. It is a regulated artifact with versions, parent-child relationships, ingredient provenance, country-specific restrictions and a direct line into the Product Information File.

The symptoms are familiar. Three chemists each holding a slightly different copy of "MOIST_SERUM_v17_FINAL_real.xlsx". An ingredient that turned out to be restricted under Annex III at a different concentration in China than in the EU, discovered the week before launch. A CPSR signed off against a version of the formula that no longer matches what production is making. An auditor asking "show me the trail from this batch back to the formula version that was assessed" and a regulatory lead opening their email archive.

The cost is not the spreadsheet. The cost is rework, delayed launches, recalls, and the regulatory headcount you have to hire to brute-force what the software should do automatically.

Five criteria separate serious cosmetic formulation platforms from glorified ingredient lists. Use them as a scoring rubric in every demo.

1. Regulatory coverage. Does the tool understand EU 1223/2009, the UK Cosmetic Regulation, MoCRA, China NMPA, Japan's Standards for Cosmetics, ASEAN and the major Annexes (II, III, IV, V, VI)? Does it pull updates from the regulators or rely on you to keep a static list current? Does a formula change automatically flag every market where it is now non-compliant?

2. Ingredient databases. INCI names, CAS numbers, function, allergens (the EU's 26, now 80+ under the 2023 amendment), nanomaterials, fragrance composition, supplier specs. Is this structured data, or are you pasting from supplier PDFs? Can you trace a single ingredient from a batch back to a supplier lot and the original CoA?

3. Workflow. Trial creation, iteration, stability testing, cost rollups, scale-up, regulatory review, sign-off. Does the tool model that workflow, or is it a database that you bolt your process around?

4. Collaboration. R&D, regulatory, QA, procurement and marketing all touch a formula. Can they work in one place, with role-based visibility, comment threads, and a real audit trail, or are they emailing spreadsheets again?

5. Integrations. ERP for cost and procurement, MES or batch records for production, LIMS for stability and microbiology, supplier portals for CoAs and SDSs, artwork systems for labels. A formulation tool that lives alone forces re-entry at every handoff.

Excel and Google Sheets. Fine for the first ten formulas. Painful by fifty. Dangerous by a hundred and fifty, because the regulatory and audit obligations have not scaled with the team. There is no version control that survives a chemist leaving, no link between a formula and the regulatory file it backs, and no way to answer "what changed between v12 and v14" without opening both side by side.

Generic PLM (Centric, PTC, Siemens). Designed for apparel and electronics. The data model assumes BOMs of parts, not percentage compositions of substances with cumulative restrictions. Regulatory is an afterthought, and the implementation tax to bend the system to cosmetics is real. Teams end up tracking restricted substances in, you guessed it, a spreadsheet attached to the PLM record.

Ad-hoc Access or Notion databases. A common stop on the way out of Excel. Better for collaboration, no better for regulatory. The same gaps remain on Annex restrictions, multi-market notifications, and the audit trail.

Formulation-only desktop tools. Some chemistry software is genuinely good at cost rollups and iteration, but it stops at the lab door. It does not generate a PIF, it does not notify CPNP, it does not connect to the ERP, and it does not know what MoCRA is.

The market is wider than it looks, because the products on it serve quite different problems. Three archetypes, honestly described.

Legacy PLM platforms. Enterprise suites that started in apparel or general manufacturing and were extended to cosmetics. Strong on workflow, lifecycle management and integration with corporate IT. Weak on cosmetic-specific regulation. Implementations are typically 12 to 24 months and seven figures. Right answer for a top-20 conglomerate with a dedicated regulatory team that can fill the gaps. Wrong answer for almost everyone else.

Formulation-only tools. Lighter platforms aimed at the bench chemist. Good at trial management, cost rollups and stability tracking. Often cheap and quick to adopt. The trade-off is that regulatory, manufacturing and commercial workflows live somewhere else, so the integration tax shows up later, usually at the worst time (a market launch or an audit).

Compliance-driven cosmetic platforms. Built from the regulatory file outward. Formulation lives inside a model where every ingredient, every concentration and every change is evaluated against the regulations of every market the product is sold in. PIF, CPSR, CPNP / SCPN, MoCRA listing and label artwork are generated outputs, not separate projects. This is the category Worldover sits in, and the category we think serious brands and contract manufacturers should be evaluating in 2026.

Worldover is built for beauty brands and cosmetics manufacturers who treat regulatory as a product capability, not a back-office cost. The formulation workspace is connected, by design, to the regulatory content engine and to the operations layer of the platform.

That means a chemist can iterate on a formula and see, in the same view, whether the new concentration of phenoxyethanol is compliant in every target market, whether the cost has shifted, whether the supplier lot is in stock, and whether any of the assessed allergen labelling thresholds have been crossed. The PIF and CPSR drafts update from the formula. CPNP and SCPN notifications are generated, not re-typed. Label artwork pulls the latest compliant INCI list. MoCRA facility and product listings stay in sync.

Worldover also pairs the platform with Willow, our AI co-worker for regulatory and operations, which handles the repetitive work (drafting assessments, parsing supplier documents, flagging changes in regulator feeds) so the team can focus on the judgement calls.

See it in context on the cosmetic formulation software solution page, and read how it sits alongside the cosmetic ERP and MoCRA compliance modules. The Iconic London case study is a good worked example of a brand making this move.