Technology Evidence · Project 2026

Turning operating rules into working automation tools

The project starts with real beauty-commerce workflows and turns recurring decisions across products, inventory, orders and exception handling into transparent, testable and iterative browser tools.

Self-built prototypeVisible rulesRuns locally in the browser

Evidence, Not Claims

Two working examples

This is not a concept poster. You can switch operating scenarios, recalculate inventory coverage, process order exceptions and export the demo result. Every number is explicitly illustrative and does not represent real operating performance.

01

Product and inventory signals

Calculate days of cover from inventory, daily sales and replenishment lead time, then return urgent, replenish, watch or healthy states with suggested quantities.

02

Order exception routing

Prioritise inventory mismatch, incomplete address, fulfilment SLA risk and payment review, mapping each exception to a clear next action.

03

Transparent boundaries

The current demo uses local browser data only. It does not connect to a marketplace, ERP or real order. The data layer can later be replaced with authorised APIs.

Commerce Workflow Lab

Operations automation workspace

Inventory signal analysis + order exception queue

Interactive demo: All data is illustrative and calculated in this browser. It does not connect to a real store, order, consumer record or third-party production system. Ten SKUs and ten order exceptions load by default, so results are visible immediately.
Default analysis loaded
Demo SKUs10In the rule run
Inventory signals8Need attention
Order exceptions10Still open
Actions completed0This session

Tool 01 · Inventory Signals

Product and inventory signal analysis

Days of cover = current stock ÷ scenario daily sales

SKU / Demo productStockDaily salesCoverageStatusRule output

Tool 02 · Exception Routing

Order exception routing

Sort by business risk and map each exception to the next action

Demo orderExceptionPrioritySuggested actionProcess

Architecture

From interactive prototype to connected system

Interface logic and demo data are separate. With proper authorisation, data sources can be replaced progressively with marketplace APIs, ERP, CSV or internal services, followed by access control, audit records and task queues.

01Data inputs

Marketplace API, ERP, CSV or authorised manual input

02Unified data layer

Products, inventory, orders and fulfilment status

03Rules and workflows

Coverage, exception priority and task routing

04Operating outputs

Alerts, replenishment advice, queues and exports

Project & Team

Project started in 2026

Led by founder and project lead Lu Guangzhe, the initiative continues to develop around beauty operations, supply-chain coordination and workflow automation.