Challenge
Separate systems left staff checking inventory, re-entering orders, and carrying information between sales and finance.
Portfolio · Enterprise UX · 2026
I designed a connected ERP for DEF Beauty Supply, bringing customer ordering, inventory, fulfilment, and invoicing around shared business records.
Challenge
Separate systems left staff checking inventory, re-entering orders, and carrying information between sales and finance.
Solution
A connected customer storefront and ERP, with local delivery rules and records that continue from ordering through fulfilment and invoicing.
Outcome
In a one-week sample about a month after launch, 86% of orders were placed by customers themselves. Orders now enter the ERP directly, order errors have almost disappeared, and sales can focus on customers.
Deliverables
01 / Overview
DEF Beauty Supply sells professional beauty products to salons in Italy. Customers browsed a WeChat mini-program catalogue, then messaged sales to order. I designed and built the ERP behind a new storefront: ordering, sales, inventory, fulfilment and invoicing on shared records. It is live.
02 / The problem
The same product information was repeatedly checked, communicated, and entered as work moved from one person to the next.
Of 12 business domains, 7 existed in only one system. The other 5 existed in both, with different data.
03 / Research
I interviewed one person per role, recorded and transcribed each, used AI to cluster repeated problems, then checked every finding against the transcript. Findings went into one file, UX.md, with every line tagged: interview, code, decision or assumption. Tags let a rule be overturned cleanly when a later interview contradicts it.


Often a customer is still adding items right up to the second before loading. The system only gets in the way.
Sales interview, May 2026, translated from the transcript.
Hide real stock from customers.
The owner disagreed: customers can see it, opened up by login and order history later.
Visibility is a per-identity policy (anonymous, signed in, has ordered), never hard-coded.
UX.md · sales → ownerInvoice the moment an order closes.
Finance: B2B customers pay in batches, then ask for an invoice.
Invoice from paid orders, merge several orders, skip lines already invoiced.
UX.md · financeLock the order after approval, then issue the delivery note.
Customers add goods until the second before loading. Staff cope by reopening a new order.
Delivery notes are decoupled from the order; shipments are tracked per delivery, partial included.
UX.md · salesThe owner’s top pain is the whole picture.
Sales named a different pain: order and delivery-note coupling. Neither was wrong.
Solve both. The channel gap (stock, orders) and the loading-day edits each got a fix.
UX.md · owner vs sales04 / Principles
Product and order data carry through sales, dispatch and invoicing. No retyping between roles.
Stock, delivery options and shipping costs are rules. Payment review, fulfilment exceptions and invoice adjustments stay with staff, and are recorded.
Purchase totals copy the supplier invoice’s rounding order, because a €0.03 gap breaks every reconciliation. Simplifying the maths would defeat the page.
Anything on the sales path is timed by the customers waiting behind. Hold and resume stay one step; no dialogs there.
OCR writes into editable inputs and flags gaps. It never submits.
05 / Iteration
Jun 2026
Pick a sales order first; one return per order.
Pick the customer, search SKUs into a cart, return across several orders.
Jul – Oct
Units attached loosely to products; fields drifted.
Pricing fields consolidated; default unit synced with SKU price and barcode.
Oct 6 – 12
Tested standalone product rows against the SPU / SKU picker.
Ended the trial and removed the variant; kept the original picker and row-merging rules.
Sep 2026
Browser confirms with “Are you sure?”.
A shared dialog that lists consequences before stock or money moves.
Jun – Sep
One page for every login.
Role dashboards on one skeleton, then real data, chart and filter polish.
Counts and dates from the project’s git history, 25 May to 7 Nov 2026, matched by commit-message keyword.
06 / Design system
Written rules plus reusable components give design and the coding agent one shared reference. Step through it below; the controls and patterns are live and use demonstration data.
People first, then ERP rules.
Fourteen rules, one source of truth.
07 / The solution
The storefront and internal teams now work from shared ERP records. Product and inventory data support customer ordering, and the same order continues into fulfilment and invoicing.
The platform supports three ways to create an order, all feeding the same ERP records:
Trade-off: how to join two systems. Linking the two tools would have been quicker; one platform meant a longer build but a single set of records.
Each role sees a different view of the same business data. Admin monitors the business overall, sales focuses on orders and customer follow-ups, warehouse tracks stock and dispatch tasks, and finance reviews payments and invoices. A shared layout keeps the system familiar while making each role’s priorities visible.


Before: one Dashboard page for every login, mixing task types that belonged to different jobs. After: the same shell, reweighted per role — this is the Admin view.




Two trade-offs shaped the sales screens: how packaging units are modelled, and when the system asks before acting.
Trade-off: when to ask “are you sure?” Committed stock and money actions have no undo, so the default is to confirm and state the consequence. The sales counter breaks the rule on purpose: a customer is waiting.
Editing draft rows. Applies instantly, no dialog.
Switching single / multi-SKU mode drops selections. Confirm, and say what is lost.
Confirm shipment, post a stocktake, void an invoice. Danger dialog listing consequences, with a reason where it applies.
Hold, resume, add an item while a customer waits. Instant action and a toast, no confirmation.
About to: · Adjust stock for 12 SKUs · Record €340.50 in losses (posts to finance) · This cannot be undone
These are the real pages running on demonstration data, played one module at a time. Watch, or move your pointer in and use them yourself. Nothing is saved.
One search, two ways to add.
Broad search groups shades; exact search finds the SKU.
Purchase orders carry product and quantity information through supplier confirmation and receiving. The main trade-off was how much approval a small team needs. The demo below uses the real pages on demonstration data; nothing is saved. For the complete procurement workflow and its AI-assisted optimisation, see AI Procurement Agent for DEF Beauty Supply.
Edit lines in place.
Stock and sales beside each line.
Finance creates invoices from existing sales orders, reusing product details, quantities, prices and tax rates.
Trade-off: when an order becomes an invoice. The one documented conflict between roles. I did not side with either.
The real invoicing page on demonstration data; nothing is issued.
Paid orders, waiting for an invoice.
Start from orders, not a blank invoice.
Staff edit the mini-program home page module by module, with the real mini-program as the preview, and link each customer’s WeChat account to their ERP record.
Edit right, see it on the phone.
The phone preview is the real mini-program.
Salons already ordered through a WeChat mini-program. The goal was to get every flow working and live quickly, so each choice below favours speed and familiarity, and names what it gave up.
Home
Sign in
Account
The mini-program Home, Sign in and Account screens, before and after. Drag the handle to compare. The layout stayed familiar on purpose, while each block is now configured from the ERP.
Explore the customer-facing screens below. Each phone keeps its header and bottom navigation in place while its content scrolls independently; customer support stays within reach on Home. These read-only previews use demonstration data.
08 / Results
The 86% comes from a one-week sample about a month after launch. Improvements in order errors and stockouts are reported qualitatively, not as counts, and customer acquisition gains have not been measured.
09 / Reflection
The purchasing and receiving workflow, including document checks, partial arrivals, and discrepancy handling, is covered in AI Procurement Agent for DEF Beauty Supply.