A manufacturing and retail system built around the way a kidswear brand actually works: design, colour, size, configurable production routes, tailor output and one unified stock pool.
Little Lore manufactures in-house with tailors, then sells through retail and exhibitions. There was no central system showing where a garment was in production.
The business could not see true cost per piece from materials and the labour of that specific day. Stock by design, colour and size was not one reliable record.
The replacement had to match how the workshop speaks and works. A generic SKU list and one rigid production sequence would only move the translation burden onto staff.
Manufacturing, stock and financial records in one system.
The model follows the workshop, not the conventions of generic ERP software.
Stages are admin-editable. Every product code follows its own configurable route, stored as ordered join rows.
Two designs can move through the workshop differently without a code change. Their kanban state still carries a full stage history.
A tailor’s daily wage is divided by the pieces they finished that day, then split proportionally by quantity across every code they touched.
True cost per piece is that labour allocation plus the bill of materials. It changes from day to day because that is what the day actually cost.
Large cards. The short code the team already uses. The quantity. One way to mark progress. There is no pricing, cost data or general navigation.
The simplification is the product. An ERP that tailors will not touch is a spreadsheet with extra steps.
Inventory, variants and stock are keyed the way the business already thinks. The system does not flatten those dimensions into a generic SKU that staff must translate in their heads.
Show us the registers, spreadsheets and hand-offs that hold the operation together. We will map where a custom system would pay for itself.