Services for beauty and cosmetics brands

Beauty brand automation for launches, product data and regulated records

Make It Flow builds automated business solutions for skincare, makeup, haircare and fragrance brands: a beauty CRM with replenishment flows timed to how long each product lasts, INCI and product data kept identical on every channel, batch and expiry-aware logistics, creator content checked against approved claims, an AI beauty advisor that answers from your own shade and ingredient data, a safety inbox that never lets a possible reaction slip, and launch plans that run on time. Your regulatory lead and founder keep every claim and safety decision.

One approved source for every product fact

INCI lists, shade names, claims and warnings come from your master product record, approved by your regulatory lead. Every channel, chatbot and retailer file is fed from that record, never rewritten freehand.

Claims and safety stay human

Automation checks, routes and reminds. It never approves a claim, never decides whether a reaction is serious and never gives skin or health advice; your safety contact and regulatory lead make those calls.

Built for the markets you sell in

We design around MoCRA in the US, the EU Cosmetics Regulation and the UK SCPN regime, FTC endorsement rules and the ASA, so records and approvals are ready when someone asks for them.

Services

Cosmetics automation, from formula sheet to front door.

Each one is a focused project with a fixed quote, a written plan and a handover you own.
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 fe... How we built it

Case Study

Case Study: Beauty Brand Product Data & Safety Automation

Read the full case study

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.

Master record INCI, claims Store and subs Orders, Recharge Inboxes Desk, reviews, DMs n8n Five workflows AI checks Claims, reactions Klaviyo Flows, pauses 3PL and ledger Lots, expiry Ops and care Queues, alerts Regulatory lead Claims, safety Logs and reports Dated records
  • Input
  • Logic and services
  • AI step
  • Data
  • People

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.

Platform integrations

The software you already use, connected.

Practice systems, CRMs, phones, payments and reviews, connected through documented APIs, webhooks, n8n and custom code.
All integrations

Shopify

Store platform

Orders, products, metafields for INCI and shade data, and customers.

Shopify Admin GraphQL API and webhooks.

Recharge

Subscriptions

Subscriptions, charges, skips and swaps for replenishment flows.

Recharge API (V2) and webhooks.

Klaviyo

Email and SMS marketing

Profiles, events, replenishment flows and suppression.

Klaviyo REST API (profiles and events).

Okendo

Reviews

Review answers (shade, skin type) for personalisation and reaction monitoring.

Okendo Merchant REST API; access level depends on your plan, confirmed per project.

Gorgias

Help desk

Tickets for safety intake, order status replies and hand-offs.

Gorgias REST API.

Zendesk

Help desk

Tickets and webhooks for brands on Zendesk.

Zendesk Support API and webhooks.

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 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. 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. 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. 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

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

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

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

Tech we work with

Any language, any stack.

Make It Flow delivers automated business solutions: workflows, integrations, AI assistants and the apps around them. Our team works in whatever language and stack fits the job and the systems you already run.

Automation

n8nWebhooksREST and GraphQL APIsScheduled jobs and queues

Backend

PythonPHP and LaravelNode.js and TypeScriptJava

Data

SQL (MySQL, PostgreSQL)Google Sheets and AirtableData sync and ETLReporting dashboards

Frontend and mobile

JavaScript and TypeScriptTailwind CSSJava and Kotlin for AndroidBrowser extensions

AI

Claude, Gemini and OpenAI modelsRetrieval on your own documentsModel Context Protocol (MCP)Evaluation sets

Cloud and DevOps

DockerLinux serversGitHub ActionsMonitoring and backups

FAQ

Beauty brand automation answered.

The repeatable work around the product: customer lifecycle and replenishment flows, product and INCI data across channels, order and batch tracking with your 3PL, creator content checks, routine customer questions, safety report intake and launch task tracking. People still approve claims, formulas and safety decisions.

Our fixed quotes run from $1,000 to $2,500 per workflow and $2,500 to $7,500 for an AI beauty advisor. A connected set of five workflows usually lands between $5,000 and $12,500. Platform subscriptions such as Klaviyo, Recharge, your PIM and n8n are billed to you directly by each vendor.

We build the data and workflow side: keeping product listings, ingredient data and adverse event records organised so your regulatory lead or consultant can file accurately. We do not give regulatory advice or file on your behalf.

There are many logistics platforms; what most beauty brands lack is the glue. We connect your store, 3PL and batch records so lot numbers, expiry dates and shipments line up, using AI only where it helps, such as classifying delivery issues.

This hub covers product brands that formulate, sell and ship cosmetics. Salons and spas are covered on our local services hub, where booking, reminders and reviews matter most.

Yes. We work remotely with brands worldwide and design for the rules in each market: FDA and FTC in the US, the EU Cosmetics Regulation and GDPR in the EU, and the UK cosmetics regime, ASA and UK GDPR in Great Britain.

Free 20-minute call

Walk us through your next launch

Book a free 20-minute call. Tell us how product data, creator content, customer questions and safety reports move today; we will point out what is worth automating and give you a fixed quote.

Book a free 20-minute call