The real cost of an ERP implementation for a cosmetics contract manufacturer.

A tier-one ERP licence for a 200 to 1,000 person cosmetics CMO sits in the 200,000 to 600,000 GBP per year range. The implementation, the line item nobody quotes upfront, sits at 1.5 to 3 million GBP for the first cut and another 500,000 GBP per year in steady-state customisation and support.

The breakdown looks roughly like this for a typical 18-month deployment:

• Systems integrator (SI) hours: 50 to 60 percent
• Internal team time (operations, IT, quality, finance running in parallel): 20 to 25 percent
• Data migration (substance, formula, lot, customer, supplier, financial): 10 to 15 percent
• Custom configuration (batch genealogy, electronic batch records, GMP workflows): 8 to 12 percent
• Licence: 10 to 20 percent

The licence, the figure that appears on every comparison spreadsheet, is rarely the dominant cost. The integrator hours are. That is the leverage point.

Generic ERP implementations cost what they cost. A cosmetics CMO has four extra cost centres that show up nowhere in the standard quote.

Batch genealogy. Every lot needs forward and backward traceability to raw material lots, intermediate batches, finished goods batches and customer shipments. Generic ERPs handle this with custom build, usually at 200,000 to 400,000 GBP of SI work.

Electronic batch records. A GMP-compliant electronic batch record with electronic signatures, exception handling and audit trails is rarely native. Budget another 150,000 to 300,000 GBP.

Regulatory integration. Customer-specific declaration packs, CPNP and SCPN flows, MoCRA registration, and the inevitable Prop 65 customer communications. Generic ERPs send you to a regulatory point tool, which is another licence and another integration.

Customer data formats. Each major customer (the global beauty brand, the prestige retailer, the indie disruptor) has its own EDI, its own portal, its own declaration template. Mapping that to your ERP is custom every time.

The cost line that finance teams routinely miss is the internal cost: the operations lead, the quality lead, the finance lead, the IT lead and the two or three SMEs who spend 12 to 24 months in parallel with the SI. At 0.5 to 1 FTE per workstream, fully loaded, that is 600,000 to 1.2 million GBP of internal time over the deployment.

This is real money. It also has a real opportunity cost: those people are not running improvements to the existing business while they are implementing the new system. The case for a fast deployment is partly the licence saving, mostly the recovered internal capacity.

Three structural shifts reduce the total cost meaningfully, not marginally.

Vendor-led implementation. A platform whose vendor implements it directly removes the SI markup. The implementation team is the team that built the product, so the discovery work is shorter and the configuration is sharper.

Native cosmetics depth. Batch genealogy, electronic batch records, CPNP, MoCRA and Prop 65 native to the platform remove the custom-build line items entirely.

AI agents that do the data work. Substance master ingestion, lot record mapping and customer declaration template wiring are agent-led with human review, not consultant-led with manual entry. This compresses the data migration from quarters to weeks.

In practice, a 300 to 600 person cosmetics CMO can be live on a modern platform in three to six months at 500,000 to 1.2 million GBP all-in, against 2 to 4 million GBP on a legacy stack over 12 to 24 months.

When the CFO asks for a number, give them all of these, not just the licence:

• Five-year licence cost, escalations included
• Implementation cost, broken down by SI hours, internal hours, data migration and custom configuration
• Integration cost to the rest of your stack (3PL, retail EDI, finance close, e-com)
• Ongoing licence and support escalation (typically 5 to 8 percent annually)
• Internal run team after go-live (typically two to four FTE)
• The cost of the year you spend deploying it (lost projects, deferred improvements)

Then ask each vendor to commit to the deployment timeline and the total five-year cost in writing. The ones who will not commit are telling you what the project actually looks like.

A practical checklist for the sponsor and steering committee. Score each item red / amber / green before signing.

Sponsorship and governance

• Executive sponsor named, with authority to make trade-offs
• Named leads from operations, quality, regulatory, finance and IT
• Steering cadence weekly for the first 12 weeks, then bi-weekly
• Change control process agreed before scope opens

Scope and data

• Phase 1 scope written as a single page, with what is explicitly out
• Substance master source identified (existing PLM, spreadsheets, supplier data)
• Formula and BOM data audited for completeness before migration
• Customer, supplier, lot, batch and financial migration plans owned by name
• Regulatory files (PIF, CPSR, notifications) baseline captured

Cosmetics-specific readiness

• Batch genealogy requirements documented per customer
• Electronic batch record templates agreed per line
• MoCRA / CPNP / SCPN filing responsibilities assigned
• Customer declaration templates (top 10 customers) collected
• Retailer EDI and portal requirements mapped

Integrations

• Finance ledger integration confirmed with the FD
• 3PL / warehouse integration listed with volumes
• E-commerce and marketplace integrations listed
• Retained best-of-breed tools listed with integration owner

Go-live and cutover

• Parallel run window defined and bounded (usually 2 to 4 weeks)
• Cutover weekend rehearsed
• Support model (vendor, internal) agreed for first 90 days
• Success metrics defined and measurable at day 30, 60, 90
• Hypercare exit criteria agreed in writing