# AI for Cosmetics and Personal Care ERP: Formulas, MoCRA and Lot Traceability

> Source: https://netray.co/erp-ai/ai-erp-cosmetics
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: AI for ERP

## Short answer

AI for a cosmetics ERP answers questions across formulas, INCI ingredient lists, batches, packaging components and complaints, so regulatory and operations teams can support MoCRA and EU requirements faster. Run privately and read-only, it keeps formulations confidential and leaves safety and labeling decisions to qualified people.

## Kind

industry

## Erp Family

multi-erp

## Erp Products

- SAP Business One
- Microsoft Dynamics 365 Business Central
- NetSuite
- Odoo
- Sage X3

## Industries

- Cosmetics
- Personal Care
- Beauty Manufacturing

## Region

Global

## Persona

Regulatory Affairs Manager / Operations Director

## Eyebrow

Cosmetics ERP + AI

## Intro

Cosmetics manufacturers manage an unusual mix: formulas expressed in percentages, hundreds of shade and size variants of one base, packaging components that outnumber raw materials, and short product lifecycles. The ERP typically holds the formula, bill of materials, batches and stock, while safety assessments, supplier specification sheets and consumer complaints are held elsewhere. When regulatory asks which products contain an ingredient being restricted, the answer needs a join across all of it.

Regulation has tightened. In the US, the Modernization of Cosmetics Regulation Act of 2022 introduced facility registration, product listing, safety substantiation and adverse event reporting, with serious events reported within 15 business days. In the EU, Regulation 1223/2009 requires a product information file and notification, and ISO 22716 is the common GMP reference. These obligations rest on records that live partly in the ERP.

Netray builds private AI over the ERP and related documents. Formulas, which are the core trade secret in this industry, never leave your infrastructure. The AI retrieves, cross-references and summarizes, and runs read-only so that regulatory, quality and safety staff stay in control of every determination.

The sections below cover practical use cases, deployment, compliance boundaries and honest limits.

## Pain Points

### Ingredient-in-product searches are slow

**Detail:** When a substance is restricted or a supplier changes, finding every formula, version and live SKU that contains it requires joining formula lines, INCI names and product listings.

### Formula versions multiply with shade and size variants

**Detail:** A single base can feed many finished items. Tracking which version of which formula went into which lot, and which markets it was approved for, is error-prone.

### Regulatory records span many systems

**Detail:** Safety assessment reports, product listings, supplier documents and adverse event files are rarely linked to the ERP's item and lot numbers.

### Complaints are hard to connect to batches

**Detail:** Consumer complaints arrive by email or a service tool, and linking them to lot numbers, packaging components and filling lines is manual, which slows trend detection.

### Packaging components drive stockouts

**Detail:** Bottles, pumps, caps and cartons have long lead times and many substitutions. Shortages are seen late because component demand is spread across many finished SKUs.

## Use Cases

### Ingredient impact search

**Description:** Find all formulas, active versions, finished items and recent lots that contain a given INCI name or CAS number, with market and status.

**Erp Objects:** Formula lines, item master, INCI attributes, BOM where-used, lot records

**Outcome:** Impact assessments that took days of cross-checking become an initial list in minutes for regulatory review.

### Formula version and approval trace

**Description:** Show which formula version produced a given lot, who approved it, and which market registrations relate to it.

**Erp Objects:** Formula versions, production orders, lot master, approval fields

**Outcome:** Faster investigation, with gaps in version control made visible.

### Complaint to lot correlation

**Description:** Match complaint records to lots, filling lines and component suppliers, and flag clusters by product or batch.

**Erp Objects:** Lot master, production orders, packaging component receipts, complaint references

**Outcome:** Trends such as a pump supplier issue are spotted earlier than from reading complaints alone.

### MoCRA record support

**Description:** List products and facilities and check that listing fields and adverse event references are present, ready for human review and submission.

**Erp Objects:** Item master, facility and site records, product category fields, customer return references

**Outcome:** Staff start from a consolidated record set and an exception list instead of manual compilation.

### Packaging component shortage forecast

**Description:** Roll up component demand across all SKUs using the component, and show weeks of cover with supplier lead times.

**Erp Objects:** BOM components, planned orders, purchase orders, lead time fields

**Outcome:** Earlier visibility of shortages across variants, bounded by forecast quality.

### Shelf life and period-after-opening labeling checks

**Description:** Compare item shelf-life and PAO attributes to label records and flag inconsistencies.

**Erp Objects:** Item shelf-life fields, label master, lot expiry dates

**Outcome:** Inconsistencies are caught before printing, supporting a human label review.

### Supplier specification change review

**Description:** When a raw material specification changes, list affected formulas and finished lots in stock for review.

**Erp Objects:** Vendor specifications, item master, formula where-used, inventory by lot

**Outcome:** Change impact is scoped quickly so quality can decide what to hold or retest.

## Architecture

**Overview:** Read-only access to ERP formula, BOM and lot data plus regulatory documents, indexed privately and answered by a locally hosted open-weight model.

**Layers:**

#### ERP and PLM connectors

**Detail:** Read-only connectors to formula, BOM, batch and stock data, and to a formulation tool or PLM if present.

#### Regulatory document index

**Detail:** Safety assessments, product information files, supplier specs and listings tied to item and INCI identifiers.

#### Role-aware retrieval

**Detail:** Formulas visible only to authorized roles, with contract manufacturer and brand-owner data separated.

#### Open-weight model serving

**Detail:** Models served on your GPUs or private cloud, with ingredient matching based on normalized identifiers, not model guesses.

#### Answer with sources and logs

**Detail:** Each result lists records used and is logged for review.

## Deployment Options

### On-premise

**Fit:** Brands whose formulas are their core IP

**Detail:** Local GPU server with no external calls.

### Private cloud

**Fit:** Cloud-ERP users such as NetSuite or Business Central customers with strict IP policy

**Detail:** Isolated GPU instances with private connectivity to ERP APIs.

### Contract manufacturer segregation

**Fit:** Contract fillers serving multiple brands

**Detail:** Separate indexes and access scopes per brand client.

## Compliance

### The AI helps compile and cross-check registration, listing and adverse event records. Submissions and safety substantiation remain the responsible person's duty.

**Framework:** MoCRA (US)

### Supports retrieval across the product information file and ingredient restrictions, while the responsible person makes determinations.

**Framework:** EU Regulation 1223/2009 and CPNP

### Read-only retrieval of batch and deviation records helps audit preparation without altering records.

**Framework:** ISO 22716 GMP

### Formulas stay inside your boundary, access is role-limited, and every query is logged.

**Framework:** Trade secret protection

## Integration Notes

- Normalize ingredient identifiers first: INCI names vary by spelling and supplier trade names, so map to CAS or a master ingredient list.
- Store formulas as percentages with a clear basis, and keep batch scaling in SQL.
- Link complaint records to lot numbers at intake, otherwise correlation depends on free text.
- Use BOM where-used queries for packaging components rather than letting the model infer relationships.
- NetSuite and Business Central expose APIs that are rate limited, so batch indexing runs off-hours.
- Keep read-only mode at launch. Drafted regulatory records should be reviewed by humans before entry.

## Product Fit

### ERPray

**Why:** Questions and dashboards over formulas, lots, shortages and returns.

### DataRay

**Why:** Chat over safety assessments, supplier specifications and listing files.

### Custom build

**Why:** Ingredient impact agents and complaint correlation tailored to your product structure.

## Engagement

### Data and identifier review

**Duration:** 2 weeks

**Deliverables:**

- Formula and ingredient data assessment
- Identifier normalization plan
- Access model

### Pilot on ingredient search and lot trace

**Duration:** 4 to 5 weeks

**Deliverables:**

- Connectors to formula and lot data
- Ingredient impact queries
- Validation with regulatory staff

### Complaints and components

**Duration:** 4 weeks

**Deliverables:**

- Complaint to lot correlation
- Component cover view
- Shortage alerts

### Operate

**Duration:** Ongoing

**Deliverables:**

- Usage and accuracy review
- New market rule updates
- Additional brand onboarding

## Buyer Questions

- How are ingredient names normalized across suppliers and formulas?
- Do formulas ever leave our infrastructure?
- Can contract manufacturing clients be separated?
- How are complaint records linked to lots?
- What regulatory determinations does the tool avoid making?
- How does it handle formula versions across markets?

## Faq

### Can AI do our MoCRA submissions?

**Answer:** It can help compile and check records, but submissions, safety substantiation and the responsible person role remain with your team. Treat the AI output as a draft or an exception list for review, not as a filing.

### How does it find ingredients across formulas?

**Answer:** By querying normalized ingredient identifiers in formula lines and BOM where-used, then explaining the result. Matching on INCI text alone is unreliable, so the first step is cleaning identifiers.

### Is it safe for formulas?

**Answer:** With on-prem or private cloud hosting, formulas stay on your infrastructure and are not sent to a public model provider. Access is limited by role and each query is logged.

### Which ERPs do cosmetics firms use?

**Answer:** A mix: Business Central, NetSuite, SAP Business One, Odoo, Sage X3 and specialized formulation tools. We connect through APIs or reporting views and confirm the data model first.

### Can it help with shade variants?

**Answer:** Yes, for impact and shortage queries across variants, because where-used queries expose which finished items share a base or component. It does not design shades.

### Will it spot complaint trends?

**Answer:** It can cluster complaints by lot, line or component supplier when complaints are linked to lots. Quality and safety staff still assess seriousness and reporting duties.

### Is there a minimum size?

**Answer:** No fixed minimum, but small brands often get more from cleaning identifiers and using standard ERP reports first. AI adds most where formula and SKU counts are large.

## Search terms

AI for cosmetics ERP, MoCRA ERP software AI, cosmetics manufacturing ERP, ingredient search formula ERP, cosmetic formula management AI, INCI ERP AI, personal care manufacturing ERP AI, ISO 22716 ERP, cosmetics lot traceability, private AI cosmetic formulas, beauty manufacturer ERP AI, complaint lot correlation cosmetics

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json