Oacer Web Services
All case studies
Vastr

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.

Client
Project
Vastr — SaaS ERP for fashion retail
Our role
SaaS Product Development — ERP, CRM & HRM
Industry
SaaS · Fashion & Retail

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

01
Retail ERP core

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.

02
Point of sale & tailoring

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.

03
CRM & WhatsApp marketing

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.

04
Owner dashboard & HRM

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

Enterprise capability, boutique pricing

Multi-outlet ERP, CRM and HRM delivered as SaaS, putting tooling within reach of independents who could not justify an enterprise licence.

Fashion-specific workflows

Alterations, exchanges and variant-heavy inventory handled natively rather than worked around, which is what drives day-to-day adoption.

Multi-outlet from day one

Stock transfers, per-outlet reporting and role-based access built in, so growth does not trigger a migration.

One platform, three systems

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.

Your software forces workarounds for the parts of your business that make you money.
Stock counts differ between outlets and nobody can say which one is right.
You run a service alongside your product — alterations, fitting, installation — and no system tracks it.
You have separate tools for billing, customers and staff, and they never reconcile.
You have a workflow good enough to sell to others in your industry, but no product to sell it in.
Where we'd start

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.