Enterprise retail software, sized for an independent boutique
A multi-tenant SaaS platform giving boutiques and fashion retailers the ERP, CRM and HRM tooling normally reserved for chains.
The challenge
Fashion retail has operational problems that generic retail software handles badly — size and colour variants multiplying SKUs, alterations and tailoring as a service attached to a sale, returns and exchanges that behave differently from other categories, and stock moving between outlets constantly. Independent boutiques were choosing between enterprise systems priced far beyond them and simple billing apps that ignored half of how they work.
Our approach
We built Vastr as a multi-tenant SaaS product rather than a series of bespoke builds, so the economics work for a single-outlet boutique while the capability holds for a growing chain. The product was designed around the workflows that generic retail software gets wrong, because those are precisely the ones that decide whether a boutique adopts a system or abandons it.
What we actually did
Multi-outlet inventory with inter-branch transfer tracking, purchase orders and procurement, low-stock surfacing, and a product model built for fashion variants rather than retrofitted onto a generic SKU. Sales, returns and exchanges are handled as distinct flows because in this category they genuinely are.
A boutique-oriented POS with discounts and coupons applied at the counter, plus a dedicated tailor and alterations module — the piece almost every generic system omits, and the one that ties a customer to a store.
Customer records built from transactions, with WhatsApp marketing integrated directly — the channel that actually works for boutique retail in this market, rather than an email tool nobody in the segment uses.
A configurable dashboard covering sales trend, payment-mode mix, low stock and recent purchase orders, alongside staff management. The calendar and quick-notes panel exists because owners were tracking follow-ups on paper next to the till.
The outcome
Multi-outlet ERP, CRM and HRM delivered as SaaS, putting tooling within reach of independents who could not justify an enterprise licence.
Alterations, exchanges and variant-heavy inventory handled natively rather than worked around, which is what drives day-to-day adoption.
Stock transfers, per-outlet reporting and role-based access built in, so growth does not trigger a migration.
ERP, CRM and HRM in a single product, removing the integration work that usually falls on the retailer.
Vastr shows what happens when software is designed around one industry's real workflows instead of a generic retail model. Building it as SaaS rather than bespoke turned a single operator's hard-won process into a product the whole segment can buy.
Does any of this sound familiar?
This project started from a specific set of symptoms. If you recognise several of these in your own business, the problem is probably closer to Vastr's than it looks.
If your operational knowledge is genuinely better than the software available in your industry, that is a product, not just an internal tool. We would look at whether your workflow is specific enough to be defensible and general enough to sell — and if it is, build it multi-tenant from the start rather than as a bespoke system you later try to resell.
Other client work
A tax filing service losing people mid-journey — rebuilt around clarity, trust and a single obvious next step.
Read the case study
CarZScrapA scrap car platform with no brand recognition — given an identity, a lead engine, and a site built to capture intent in one screen.
Read the case study Orbynx84An end-to-end operations platform for a café group — POS, kitchen display, inventory and reporting in one system instead of five.
Read the case study
