Ce que 50+ fabricants cosmétiques nous ont appris sur l’ERP en 2026

Over the past year, we have spoken with more than 50 cosmetics manufacturers across brands, subcontractors, labs, filling specialists, packaging teams, and SMEs trying to keep production under control while the commercial side keeps moving.

Across those conversations, the same breakpoints kept coming back: formula data that did not always travel cleanly into production, launch plans that lived outside the ERP, traceability rebuilt after the fact, and routine decisions carried by people because the system recorded work without taking much of it off their plate.

This article looks at the operational reasons cosmetics manufacturers need a different kind of ERP, then explains why Bonx is a strong fit for cosmetics companies that want more control without freezing the way they work.

Formulas cannot sit outside operations

Most cosmetics manufacturers already have a way to manage formulas. The problem starts when formula data and operational data drift apart.

Production, purchasing, quality, planning, and sales all need a different view of the same reality: the right version, the right inputs, the right checks, the right batch size, the right lead time, and a clear answer on what can actually be produced.

If the formula lives in one place and the ERP only sees a simplified bill of materials, the company has to bridge the gap manually. That works until launches multiply, raw materials change, packaging versions shift, or several people need to make decisions from the same information at the same time.

The ERP does not have to replace every formulation or regulatory tool. It does, however, have to carry the operational consequences of the formula: what to buy, what to produce, what to check, what to block, and what to trace.

That is where many generic ERPs fall short. They can store a product structure, but they struggle when the real process depends on versions, exceptions, substitutions, packaging variants, and quality gates that change as the business grows.

Compliance evidence has to be captured while work happens

An ERP will not make a product compliant by magic. It will not replace the safety assessor, the regulatory expert, or the tools used to prepare a product information file. But the ERP does decide whether operational evidence exists in a usable form.

Under the EU Cosmetic Products Regulation, products placed on the market need a responsible person, good manufacturing practice, a safety assessment, a product information file, and the right labeling information. The product information file must be kept for 10 years after the last batch is placed on the market. Before a cosmetic product is placed on the EU market, the responsible person also submits product information through the Cosmetic Products Notification Portal.

Those obligations depend on operational discipline. Which raw material lots went into this finished batch? Which packaging version was used? Which quality checks were passed? Which batch is blocked, released, reserved, or shipped? Can the team move from a customer complaint to the relevant batch history without rebuilding the story by hand?

Traceability is weak when it is reconstructed after production. It is much stronger when batch records, stock movements, quality statuses, and release decisions are created as part of the normal workflow. That is the ERP standard cosmetics manufacturers should expect.

Launch calendars punish rigid systems

The launch rhythm in cosmetics is brutal on old ERP logic. New formulas, limited editions, packaging changes, retailer windows, influencer-driven peaks, sampling campaigns, kits, bundles, and market-specific requirements all put pressure on the same operational core. The commercial calendar moves first. The factory has to absorb the consequences.

Traditional ERP systems usually respond in one of two ways.

1. Rigidity. The company spends months modeling workflows, approvals, variants, and exceptions. The project becomes heavy before the team sees value, and by go-live, part of the process has already changed.
2. Leakage. The ERP covers the clean layer of work, while launch readiness, artwork status, packaging decisions, quality holds, subcontractor updates, and priority changes live in spreadsheets and messages.

Neither model fits a cosmetics business that launches often. The ERP has to give structure without pretending the business is static. It needs to let teams add checks, change workflows, connect new tools, and adapt processes after go-live without turning every change into a separate consulting project.

Inventory has more statuses than available

Several cosmetics manufacturers told us some version of the same thing: the stock number exists, but nobody fully trusts what it means.

That usually happens because inventory is carrying more context than a generic ERP shows. Raw materials can expire, finished goods can be blocked pending quality release, packaging can become obsolete after a label change, and some customers require minimum remaining shelf life. Some stock exists physically but cannot be promised commercially.

When those statuses are not visible in the operational system, people compensate. They check shelves, message the warehouse, maintain side files, or reserve stock informally because the ERP is too coarse to support the decision.

The waste shows up in expired material, obsolete packaging, and the time spent verifying what the system should already know.

A stronger ERP for cosmetics manufacturing should help the team decide what can be used, what should move first, what is blocked, what must be bought, and what cannot be promised yet.

Subcontracting spreads operational truth across companies

Many cosmetics companies rely on partners for formulation, bulk manufacturing, filling, packing, testing, logistics, or part of the supply chain. That model can work well, but it creates one recurring risk: no single team owns the full operational picture.

One partner has the production status, another has the test result, another has the stock, and the brand owns the customer promise. The ERP is supposed to connect those realities, but traditional systems often reduce subcontracting to purchase orders and receipts, which is not enough.

Cosmetics manufacturers need to track outsourced work as part of the same flow as internal work: supplier orders, manufacturing orders, subcontracted steps, batch information, quality release, stock receipt, and shipment readiness. Otherwise, the company spends too much time asking for updates and too little time acting on them.

The more the business grows, the more expensive that fragmentation becomes.

Why Bonx fits the pattern we heard

Bonx is an AI-native manufacturing ERP. For cosmetics manufacturers, it brings fast implementation, adaptable workflows, connected operations, traceability built into daily work, and less manual coordination as the business grows.

Bonx covers the operational backbone of manufacturing: order management, inventory, purchasing and supplier management, planning, production, quality, and logistics. It also connects to the tools already in the stack, including customer relationship management, e-commerce, and accounting tools, instead of forcing every team into one monolithic system.

The bigger difference is that Bonx is built as a system of action, not just a system of record. A traditional ERP waits for people to enter, check, and move information. Bonx can take routine operational work into the system itself, from manufacturing orders and procurement suggestions to stock-production coordination, while surfacing the exceptions that actually need a human decision.

Bonx customers go live in 1 to 3 months, not after a year of workshops and configuration. For a cosmetics manufacturer with launches, suppliers, and production constraints already moving, that speed is not a nice bonus. It changes whether the ERP project can keep up with the business.

The adaptability matters even more after go-live. When a process changes, teams can adjust the system to fit the new way of working. That is the opposite of the old ERP bargain, where the company pays once to implement the system, then keeps paying every time operations evolve.

Proof from similar operational environments

The best proof comes from manufacturers facing the same operational pressures: batch traceability, shelf life, fast growth, subcontracting, customization, and demand peaks.

At L'Atelier du Ferment, a fast-growing food manufacturer where volumes doubled every year across four workshops, Bonx helped structure production, purchasing, shelf-life management, cold storage, and full batch traceability. The company tracks more than 100,000 bottles from fermentation to cold storage, connects operations to Sidely and Pennylane, and uses Bonx to generate manufacturing orders and procurement suggestions based on sales, shelf life, and cold storage capacity.

That example matters because the operating constraints are familiar to cosmetics manufacturers: ingredients, batches, shelf life, quality, demand peaks, and the need to grow without losing traceability.

At Feroce, a fast-growing brand that had to preserve batch traceability during a tenfold order surge, Bonx went live in 42 days without interrupting operations. When orders surged after a national TV appearance, every package stayed traced to the same standard, while cold storage capacity grew from 9 square meters to 100 square meters with no loss of visibility.

Cosmetics brands know that kind of pressure. A product can jump after a campaign, retail launch, press mention, or creator post. The question is whether the operation can absorb the spike without breaking batch control, stock visibility, or customer promises.

At Amantys, a custom jewelry house coordinating two boutiques and one production workshop, Bonx connected sales, workshop, and finance with zero re-entry between HubSpot, production, and Pennylane. Each custom order creates a full work order with variants, technical details, instructions, and deadlines. The sector is different, but the operating lesson is useful for cosmetics personalization, limited runs, kits, and made-to-order workflows: the ERP has to carry order-specific detail without burying the team in manual coordination.

At La Maillecotech, where operators helped shape the system around real production work, Bonx reduced daily data entry from one hour to a few minutes and improved efficiency by 10%. For cosmetics manufacturers, adoption matters because traceability only works if people use the system during the shift, not later when the details are already fading.

The buying rule for cosmetics ERP

The wrong ERP question is: can this system manage cosmetics? Almost every vendor will say yes. The better question is whether the system can carry the specific operational proof your cosmetics business depends on, while still letting the business change.

That means testing real flows before buying:

• A formula change that affects production, purchasing, and documentation.
• A batch quality hold that blocks shipment.
• A packaging version change during launch preparation.
• A subcontracted production step with batch information coming back into the system.
• A direct-to-consumer demand spike that changes production priorities.
• A retailer order with shelf-life or labeling constraints.
• A traceability exercise from finished product back to raw material lots.

If the demo turns those flows into custom development, manual exports, or future-phase promises, the system is already telling you something.

The cosmetics manufacturers we spoke with were not looking for more software theory. They wanted a system that could hold formula-driven production, batch traceability, quality control, supplier work, launches, and channel complexity together without slowing the business down. That is the bar. Anything less just moves the work back onto the people the ERP was supposed to help.