Operational automation for an omnichannel beauty business, plus a concept prototype
- Role
- Automation build and product concept design
- Years
- 2023 — 2026
- Status
- Built systems in use, plus a concept prototype
- Stack
- WooCommerce, Automation tooling, Prototype
A professional beauty-products business selling through a WooCommerce storefront, a physical shop and sales managers, with the order and customer picture split across all three. Two distinct pieces of work sit here: automation that is built and running, and a separate business-management prototype that is explicitly a concept.
The problem
Selling through a website, a shop counter and a team of sales managers means three different order intakes, three views of the customer and one accounting process expected to absorb all of it.
Loyalty and repeat purchasing are where the margin lives in this category, but they are impossible to run well when the customer record depends on which channel the person happened to buy through.
The insight
The accounting workload was a symptom rather than the problem. The real cost was that no single place described a customer or an order across the channels.
That distinction is why the work splits in two: automating what already existed and could be measured, and prototyping the unified system separately rather than pretending it was built.
What I built
- Built and operating: accounting operations automation, removing repetitive manual reconciliation from the finance workflow.
- Built and operating: a loyalty programme for customer retention across the business.
- Concept prototype, clearly labelled and not deployed: an omnichannel operations system covering unified order intake, customer and loyalty profiles, fulfilment, products and stock, sales-manager workflows, marketing segmentation and commercial reporting.
Key decisions
Ship the automation, prototype the platform
The accounting and loyalty work was deliverable immediately and paid for itself. The unified operations system was a much larger commitment, so it was explored as a concept first.
Keep the two clearly separated
Presenting a prototype as a running system is the fastest way to lose credibility. The distinction is labelled everywhere it appears, including on the screenshots.
Gallery
The public storefront and commerce context
Proves: A real omnichannel business context
Status and evidence
- The loyalty programme and accounting automation are built and in use by the business.
- The omnichannel operations system is a design and prototype exercise, labelled as a concept throughout.
What this does not claim
- The business-management system is a concept prototype. It is not deployed, not in use and produces no business results.
- Only the loyalty programme and accounting automation should be read as delivered work.