Data enrichment for beauty brands, built on one approved INCI record
A single ingredient change can leave an old INCI list on your site, a marketplace and three retailer files. We build a master product record approved by your regulatory lead, enrich it with shades, sizes, warnings, period-after-opening and approved claims, push it to Shopify and marketplaces, fill retailer templates from it and flag any channel where the data differs. A typical build costs $1,000 to $2,500 per workflow and takes about four to five weeks.
The problem
Why INCI lists drift out of date across channels
Beauty product data is unusually unforgiving. The EU Cosmetics Regulation requires the ingredient list in descending order of weight, a batch number, the responsible person's name and address and either a date of minimum durability or a period-after-opening symbol, and customers with allergies read the INCI list on your product page as if it were the label.
Yet the data lives in a formulation sheet, a PIM or spreadsheet, the store admin, marketplace listings and a different template for every retailer. When a formula is updated, nobody can say with confidence which copies changed. In the US, MoCRA product listings with ingredients must also be updated annually with FDA.
What we build
What our cosmetic product database build includes
Master product record
One record per SKU and shade with INCI list, size, warnings, PAO or durability, responsible person and approved claims.
Change control
Any edit to ingredients, warnings or claims needs regulatory approval before it flows anywhere.
Channel sync
Approved data pushed to Shopify metafields, marketplaces and your PIM.
Retailer templates
Retailer data files filled from the master record, with gaps listed instead of guessed.
Difference report
A weekly check comparing live channel data with the master and flagging mismatched INCI lists or claims.
Regulatory data pack
Ingredient and product data exported in the shape your regulatory lead needs for MoCRA listings, CPNP or SCPN updates.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Change requested
A formula, shade or claim change is entered in the master record.
-
02
Team review
Approval routed
The change is routed to the regulatory lead with a side-by-side difference.
-
03
Automated
Channels updated
Approved data is pushed to the store, marketplaces and PIM.
-
04
Automated
Differences checked
A scheduled job compares every live channel with the master and flags mismatches.
-
05
Founder or regulatory lead decides
Regulatory sign-off
Filings, label artwork and claim approvals are decided by the regulatory lead.
How it behaves
How INCI list syncing behaves
What the customer sees
- The same ingredient list on your site, marketplaces and retailer pages
- Warnings and usage information as text, not just in a photo
What the team sees
- One master record per SKU and shade
- Approval requests with a side-by-side difference
- A weekly mismatch report by channel
What the automation does
- Pushes only approved data
- Compares live channels with the master
- Logs every change with who approved it
Edge cases and fallbacks
- Old stock with the previous formula still selling
- Both versions are kept with batch ranges, and the channel shows the version in stock.
- Retailer field has no match in the master
- Listed for the team to fill once; never guessed.
- Marketplace rejects an update
- The error is logged and the team is alerted; the master is not changed.
- PIM or store API outage
- Pushes queue and retry; the difference report marks the channel as not checked.
Architecture
One INCI record feeding every channel at a glance.
- Input
- Data
- People
- Logic and services
- Output
- AI step
How it flows
- 1 Formula, shade and size data enter the master record.
- 2 The regulatory lead approves any change to ingredients, warnings or claims.
- 3 n8n pushes approved data to the store, marketplaces and retailer templates.
- 4 A scheduled comparison flags any channel where live data differs from the master.
Project planner
How the project runs, phase by phase.
INCI & product data enrichment project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Where product data lives today, channels, retailer templates and approval steps.
-
02
Design
2 to 3 days
Master data model, approval rules, channel mappings and comparison rules.
-
03
Build
About 2 weeks
Master record, approval routing, channel sync, templates and difference report.
-
04
Shadow run
About 1 week
A full catalog comparison run; the team fixes mismatches before sync goes live.
-
05
Launch
1 to 2 days
Switch on approved pushes for one channel, then the rest.
-
06
Support
Ongoing
New retailers, new fields and regulatory updates.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Data model, approvals and channel mapping.
$200 – $400
-
Build
Master record, approval routing, sync and comparison.
$500 – $1,300
-
Integrations
Store, PIM, marketplaces and retailer templates.
$150 – $400
-
Testing and shadow run
Full catalog comparison before sync goes live.
$100 – $250
-
Launch and training
Staged switch-on and team walkthrough.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. PIM and n8n costs are billed to you directly. Each extra retailer template format may add to scope.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- PIM: Your PIM vendor's own plan, if you use one.
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
EU: cosmetic labelling
Article 19 of Regulation 1223/2009 requires the responsible person's name and address, a batch number, a durability date or period-after-opening symbol, precautions and an ingredient list in descending order of weight.
Source: eur-lex.europa.euUS: MoCRA product listing
Each marketed cosmetic product must be listed with FDA, including its ingredients, and the listing must be updated annually.
Source: www.fda.govUK: SCPN notification
A UK-established responsible person must notify new products through the Submit cosmetic product notifications service before they are placed on the GB market.
Source: www.gov.ukEU: CPNP notification
Under Article 13 the responsible person notifies the Commission electronically before placing a product on the market and updates changes without delay.
Source: eur-lex.europa.euFree tools
Try these first, free.
Guides to read first
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
INCI & product data enrichment questions, answered.
It means building complete, accurate product records (INCI lists, shades, sizes, warnings, claims, images and identifiers) and keeping them identical wherever the product is sold. We automate the syncing and checking; your regulatory lead approves the facts.
We compare INCI lists across channels and against your master record and flag differences. Whether an ingredient name or order is correct is a regulatory judgement your lead or consultant makes.
No. Listings are submitted through FDA Cosmetics Direct by your team or consultant. We prepare the product and ingredient data in a clean, consistent format so filing is faster and matches your labels.
If your PIM has an API, such as Akeneo's REST API, we connect to it. Smaller catalogs often work well from a structured Google Sheet as the master record.
We map each retailer's template to your master record and fill it automatically, listing any fields the master does not hold so you can supply them once.
Number of channel mismatches found and fixed, time from approved change to live everywhere, retailer file turnaround and listing errors returned by marketplaces.
Free 20-minute call
Want this for your beauty & cosmetic?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for beauty & cosmetics
All servicesBeauty CRM & replenishment flow automation
One customer profile across store, subscriptions, reviews and support, with replenishment reminders timed to each product's real usage, shade-aware cross-sell and flows that pause when a customer reports a problem.
From $1,000 · About 4 weeks Details
Batch, expiry & logistics automation for beauty
Line up lot numbers, expiry dates and shipments between your store, 3PL and batch records, catch short-dated stock before it ships, answer order status questions and be ready to trace any batch fast.
From $1,000 · About 4 weeks Details
Influencer content & claims review workflow
Collect creator drafts in one place, check them against your approved claims list and disclosure rules, route anything doubtful to a reviewer and keep a record of what was approved and when.
From $1,000 · About 4 weeks Details