Home · Modules
Explore the platformEvery module writes to the same record, so a measurement taken at the counter is the measurement the cutting master works from — not a copy of it.
A permanent profile for every client, holding the measurement ledger that made their last garment fit. When she comes back in eighteen months for her sister's wedding, the numbers are still there — and so is the note about what she asked to be changed last time.
Every order moves through named stages, and each stage carries an owner, a start time, a completion time and an SLA. The difference between who a stage was assigned to and who actually performed it is recorded, because on a real floor those are not always the same person.
Task queues for the people doing the work, reachable from a phone. A cutting master does not need a dashboard — they need to see the next job, mark it done, and move on. A QC record stands between the last stitch and dispatch.
Collections, design assets and reference boards, with an approval step before anyone cuts fabric. Designs carry an estimated stitch time, which is what makes a delivery date a forecast rather than a guess.
Know what is on the shelf before you promise it, and what a garment consumed after. Stock lives against locations, so "we have it" means a specific shelf rather than a general feeling.
A tracking link the client opens without an account, a finished-garment gallery you publish deliberately, and status messages you send from your own WhatsApp number.
Fabric, embroidery, customisation and tailoring are costed as separate lines, because they are separate decisions. When a client asks why a blouse costs what it costs, the breakdown is already there.
Advances and balances sit against the order, so the outstanding list is a query rather than a memory test.
Every boutique gets its own isolated PostgreSQL schema — not a tenant column in someone else's table. Your clients, measurements, designs and prices are separated by the database itself.