Case Study
Case Study: Beauty Brand Product Data & Safety Automation
We built a connected set of automations for an independent skincare brand selling online in the US, UK and EU: one approved INCI and product record feeding every channel, batch-aware logistics with its 3PL, a creator content review workflow, a safety inbox that catches possible reactions anywhere, and a CRM with replenishment flows that pause when a customer reports a problem. The regulatory lead now reviews what matters instead of chasing copies of the same data.
- Business type
- Independent skincare brand selling direct and through retailers
- Team involved
- Founder, regulatory lead, operations, customer care, influencer manager
- Systems connected
- Shopify, Recharge, Klaviyo, Okendo, Gorgias, a PIM, a 3PL, Asana, n8n
- Delivery
- Scrum, 1-week sprints, about 8 weeks to full launch
The challenge
Where the practice started
After a reformulation, the INCI list was updated on the website but not on a marketplace and two retailer files, and nobody could say which copy was current.
The 3PL recorded batches on receipt but not at dispatch, so answering "which batch did this customer receive?" took days.
Creator content was approved over DMs, and possible reactions arrived in reviews, emails and social messages with no single log for the safety contact.
Replenishment emails went out on a fixed schedule regardless of product size, and reached customers with open complaints.
Goals
What the project had to change
- One approved product record, with every channel checked against it.
- Every order traceable to its batch, and short-dated stock caught early.
- Creator drafts checked against approved claims and disclosure rules before posting.
- Every possible reaction in front of the safety contact quickly, with deadlines visible.
- Replenishment flows timed to real usage that pause for open complaints.
What we built
What we built, as one connected system.
CRM and replenishment
We joined Shopify, Recharge, Okendo and Gorgias data in Klaviyo, set usage estimates per product size and paused marketing for any customer with an open case.
Service detailsMaster product record
A PIM-based master record approved by the regulatory lead now feeds the store and marketplace, fills retailer templates and runs a weekly mismatch check.
Service detailsBatch-aware logistics
The 3PL began recording lots at dispatch; orders are linked to lots in a trace ledger and short-dated stock triggers alerts.
Service detailsCreator review
Creators submit drafts in one place; captions and transcripts are checked against the approved claims library and disclosure rules, and every decision is logged.
Service detailsSafety intake
Help desk, reviews and social inboxes are scanned for reaction language; cases open with order and batch attached and deadline countdowns for the safety contact.
Service detailsArchitecture
How the brand's workflows connect
- Input
- Logic and services
- AI step
- Data
- People
How it flows
- 1 The master record, store and subscription data, and every inbox feed one n8n instance.
- 2 Five workflows sync channels and the CRM, link orders to lots and run AI checks on claims and reaction language.
- 3 Ops and care work clear queues; the regulatory lead decides claims and safety cases.
- 4 Every approval, case and change is stored in dated logs.
How it behaves
How the system behaves day to day
What customers see
- The same ingredient list everywhere they look
- Replenishment reminders around when they run out
- A calm, quick reply if they report a problem
What the team sees
- A mismatch report instead of manual checks
- A trace report for any batch in minutes
- Creator drafts that already passed the basics
- One case log with deadlines
What the automation does
- Syncs approved data and compares channels
- Links orders to lots and watches expiry
- Scans, flags, routes and logs on schedule
Edge cases and fallbacks
- Old-formula stock still selling
- Both INCI versions are kept by batch range and the channel shows the one in stock.
- Reaction mentioned in a WISMO ticket
- Routed to the safety inbox, never answered automatically.
- Creator claim allowed in the US but not the UK
- The claims library flags the market difference for the regulatory lead.
- Batch unknown for an older order
- The case requests the batch code from the customer.
- PIM, 3PL or n8n outage
- Pushes and alerts queue, nothing is changed from partial data, and the ops lead is alerted.
Integrations
What we connected
Shopify
Store platformOrders, products, metafields for INCI and shade data, and customers.
Shopify Admin GraphQL API and webhooks.
Recharge
SubscriptionsSubscriptions, charges, skips and swaps for replenishment flows.
Recharge API (V2) and webhooks.
Klaviyo
Email and SMS marketingProfiles, events, replenishment flows and suppression.
Klaviyo REST API (profiles and events).
Okendo
ReviewsReview answers (shade, skin type) for personalisation and reaction monitoring.
Okendo Merchant REST API; access level depends on your plan, confirmed per project.
Gorgias
Help deskTickets for safety intake, order status replies and hand-offs.
Gorgias REST API.
Akeneo
PIMMaster product record with INCI, claims and retailer attributes.
Akeneo PIM REST API.
ShipBob
3PLInventory, lots and shipments for traceability and expiry alerts.
ShipBob developer API; lot fields confirmed per project.
Asana
Project managementLaunch templates, tasks, gates and nudges.
Asana REST API and webhooks.
n8n
Automation platformRuns every workflow, self-hosted or on n8n Cloud.
Your own n8n instance; we hand over every workflow.
How we delivered it
Week by week, one workflow at a time.
Delivery timeline
Typical time to launch: about 8 weeks, then support
-
01
Discovery
Week 1
We mapped product data copies, batch handling with the 3PL, creator approvals and every inbox where complaints arrive, and agreed roles with the regulatory lead.
-
02
Design and access
Week 2
Master data model, approved claims library, reaction terms and case fields approved, API access granted and the 3PL agreed to record lots at dispatch.
-
03
Sprint 1: master record
Week 3
Built the master record, approval routing and a full catalog mismatch report; the team fixed mismatches.
-
04
Sprint 2: safety intake
Week 4
Channel sync went live. Built inbox monitoring and the case log; historical messages scanned and compared.
-
05
Sprint 3: logistics
Week 5
Safety intake went live. Built lot sync, the trace ledger and short-dated alerts; ran a mock batch trace.
-
06
Sprint 4: creator review
Week 6
Logistics alerts went live. Built creator submission, claims checks and the approval log.
-
07
Sprint 5: CRM
Week 7
Creator review went live. Built the profile sync, usage-based replenishment and suppression rules.
-
08
UAT and handover
Week 8
The team ran acceptance testing on every workflow, then we switched everything on, handed over run books and trained the team.
-
09
Support
Ongoing
Weekly check-ins during stabilisation and a review before the next launch, then monthly care.
Who does what
What the team does, and what automation does.
Automation does
- Pushes approved product data and flags channel mismatches
- Links orders to batches and flags short-dated stock
- Checks creator drafts against approved claims and disclosure rules
- Scans every inbox for possible reactions and opens cases
- Times replenishment reminders and pauses marketing for open cases
The team does
- Fix mismatches and supply missing product data
- Handle allocations and 3PL issues
- Approve clear creator drafts and send feedback
- Confirm case details with customers
Founder or regulatory lead decides
- Approves every ingredient, warning and claim change
- Decides new claims and effect visuals in creator content
- Decides whether an event is serious and whether to report it
- Makes recall, withdrawal and go-live decisions
Compliance handled
Privacy, consent and safety, built in.
Serious adverse events in the US
Cases show a 15-business-day countdown so the regulatory lead can meet MoCRA reporting if an event is serious.
Source: www.fda.govSerious undesirable effects in the EU
Cases flagged for EU customers note the without-delay notification duty under Article 23.
Source: eur-lex.europa.euCreator disclosures
Drafts are checked for clear #ad or "Ad:" disclosure at the start, in line with FTC guidance.
Source: www.ftc.govFilters in UK content
Effect visuals are flagged for evidence review, following the ASA position on beauty filters.
Source: www.asa.org.ukHealth data access
The case log holds minimal fields with restricted access, as reaction reports are special category data.
Source: gdpr-info.euNo automated safety or claim decisions
Every claim approval and safety decision is made by the regulatory lead.
Outcomes
What changed for the practice
- Ingredient lists now match across the website, marketplace and retailer files, and differences are caught weekly.
- Any batch can be traced to the orders that received it in minutes rather than days.
- Creator drafts arrive pre-checked, and every approval is on record.
- Possible reactions reach the safety contact quickly, with deadlines visible on each case.
- Replenishment reminders follow real usage, and customers with open cases no longer get promotions.
What we track
The measures the practice watches.
Data consistency
Channel mismatches found and time from approved change to live everywhere.
Traceability
Orders with lot data and time to produce a batch trace.
Creator review
Drafts approved first time and time from submission to approval.
Safety intake
Time from first mention to case opened and to safety contact review.
Retention
Replenishment conversion per product and subscription churn.
Cost estimate
What a project like this costs
-
Discovery and design
Data mapping, claims library, reaction terms and the backlog.
$1,000 – $2,000
-
Master record module
Approval routing, channel sync, templates and mismatch report.
$800 – $2,000
-
Safety intake module
Inbox monitoring, cases, follow-ups and deadlines.
$700 – $1,700
-
Logistics module
Lot sync, trace ledger and short-dated alerts.
$800 – $2,000
-
Creator review module
Submission, checks and approval log.
$500 – $1,300
-
CRM module
Profile sync, replenishment and suppression.
$700 – $1,600
-
Integrations
Store, subscriptions, reviews, help desk, PIM and 3PL.
$200 – $400
-
Testing, UAT and launch
QA, acceptance testing, launch and training.
$300 – $1,500
-
Total project estimate
$5,000 – $12,500
Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: five workflows at our fixed per-workflow range. Every brand gets its own fixed quote after a free call.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
- Klaviyo, Recharge, Okendo, Gorgias and PIM: Each vendor's own plan.
- AI and transcription usage: Pay-per-use fees for claims checks and reaction flags, usually small at brand volumes.
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
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.
Tools we built
Free tools we built and use every day.
The Make It Flow platform
Website audits, monitoring and reports
- Website Speed Test FreeLighthouse score, Core Web Vitals and ranked speed fixes
- SEO Audit FreeTitles, meta, headings, indexability, sitemaps and schema
- Competitor Comparison Audit your site against a competitor across every category
- AI Search Readiness FreeCheck access for Google AI, Copilot, ChatGPT and Perplexity bots
Free website tools for practices
Services in this case study
Beauty 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
INCI & product data enrichment
Keep INCI lists, shade names, sizes, warnings and claims identical across your store, marketplaces, retailer templates and regulatory records, with every difference flagged before it goes live.
From $1,000 · About 4 to 5 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
Adverse event & complaint intake
Catch possible reactions mentioned in emails, reviews, chats and social messages, route them to your safety contact with order and batch details attached, and keep a dated case log with MoCRA reporting deadlines visible.
From $1,000 · About 4 weeks Details
Founder or regulatory lead decides
-
Cosmetics Product Launch Checklist: A Workflow From Formula to ShelfAutomation · 11 min read
-
Cosmetics Advertising Rules in the UK: A Guide for Beauty Brand WebsitesGuides · 10 min read
-
Supplement Claims Review Workflow: Checking Product Pages Before They Go LiveAutomation · 8 min read
-
Ecommerce Automation: A Practical Guide for UK Online ShopsAutomation · 9 min read
-
Product Image Size Guide: Shopify, WooCommerce, Amazon and Google ShoppingGuides · 10 min read
-
What Are AI Agents? A Plain-English Guide for Small BusinessesAutomation · 10 min read
-
How to Warm Up a New Email Domain or IP AddressEmail Deliverability · 7 min read
Free 20-minute call
Want this built 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.
Sources we checked
Rules and product facts on this page come from these pages, checked in November 2026. This is general information, not legal advice; confirm the rules that apply to your practice with your own adviser.
- FDA: Modernization of Cosmetics Regulation Act of 2022 (MoCRA)
- FDA: Cosmetics Direct
- Regulation (EC) No 1223/2009 on cosmetic products (Articles 4, 13, 19, 20, 23)
- GOV.UK: Submit a cosmetic product notification
- FTC: Endorsement Guides, what people are asking
- ASA: The (mis)use of social media beauty filters when advertising cosmetic products
- FTC: Mail, Internet, or Telephone Order Merchandise Rule
- FTC: CAN-SPAM Act compliance guide
- Google: Email sender guidelines
- UK PECR regulation 22
- GDPR Article 9
- EU AI Act, Article 50
- Shopify Admin GraphQL API
- Recharge developer docs
- Klaviyo API overview
- Okendo Merchant REST API: reviews
- Gorgias API introduction
- Zendesk API reference
- Akeneo PIM API
- Amazon Selling Partner API
- ShipBob developer docs
- ShipStation API
- Asana developer docs
- n8n pricing
- Google autocomplete phrasing checked for keywords (beauty crm, replenishment email flow, inci list, mocra adverse event reporting, ai beauty advisor, ai shade finder, influencer marketing compliance, cosmetic product launch)