Everything the branch runs on, and nothing it does not need.
Nolira is not a general ERP. It covers the operations that decide whether a beauty chain makes money, in the depth those operations actually require.
This is the whole design, not a description of today. Of the 44 capabilities below, 1 are live, 23 are built and waiting for the app stores, 2 are in build and 18 are planned. Every card says which, in the same four words used on the integrations and product pages.
- Live
- Working today. You can use it.
- Awaiting store
- Built and working in the app. Waiting for the app store to publish it.
- In build
- Written and under test. Not reachable from the apps yet.
- Planned
- Designed and specified. No code written yet.
Slots you can actually deliver
Availability is calculated against staff skill, rooms, chairs, machines, processing stages and buffers, not just empty space in a calendar.
A column for every person working the day, each treatment placed at its time. Book, mark arrived, start, finish, cancel or mark a no-show from the grid. Two visits at once sit side by side.
A colour service holds the stylist for the application, releases them during processing, then books them back for the finish.
Waiting, called and in a chair, with a wait estimate from the live queue and who is free.
Nolira Book: a link customers open from WhatsApp or Instagram, offering only times the same engine says the outlet can deliver, with a link to cancel.
Dragging a visit to a new time with a conflict check before it commits. Today a visit is cancelled and booked again.
Customers register for a service and date window. When a slot opens they are notified with a temporary claim period.
Each occurrence validated separately, with conflicts reported instead of silently created.
Linked participants across staff and rooms, with course and package scheduling.

One profile across every outlet
The same client is the same record whether they visit Bangsar or Johor Bahru, with permissions controlling who sees what.
Name, phone, email, preferred language and one general note, with the packages and memberships they hold. A number already on file is caught before a second record is made.
When a customer asks to be forgotten, their name, number, email and note are erased. Their bills stay for the accounts, under "Erased customer".
Technical formulas and allergy records, each with its own visibility and retention. Today the one general note is deliberately not the place for allergies.
Photos tied to a consent record. Stored as a service record, not marketing material, unless consent says otherwise.
Relate accounts so a mother's package can cover a daughter's session where the template allows it.
Due for rebooking, inactive 90 days, package expiring, birthday month. Built from transparent rules.
Joining two records for the same person, performed by authorised staff with a full audit record.

Accounting-grade, without being an accounting system
A finalized sale is immutable. Every correction is a compensating transaction, so the record always reconciles.
Started from a visit or from nothing, with staff attribution on every line and the outlet's own prices.
Cash, card, QR e-wallet, bank transfer, store credit and package redemption on one sale.
Every discount carries a reason. Above the shop's limit the bill is held until somebody else approves it, and nobody can approve their own.
Opening float, paid-in and paid-out with reasons, an optional blind count, and a difference that has to be explained before the day closes.
Against the original lines, agreed by a second person, giving package sessions back and clawing back the commission they paid.
Numbered without gaps per chain or per outlet, printed on the counter's own Windows printer.
Payment adapters, settlement import and terminal integration, added one provider at a time per market.

A ledger, not an editable number
This is where most beauty businesses lose money and trust. The balance is a projection of immutable entries. Nobody can quietly overwrite it.
Fixed sessions or monetary credit, with the services each one covers and whether any outlet may redeem it.
Purchase, redemption, adjustment, expiry and refund, each entry carrying who did it and why.
A package can be redeemed at another outlet when its template allows it, and the ledger records which outlet sold and which redeemed.
Sessions and value still owed to customers, and what is about to expire.
Plans with a term, a price and benefits in your words, sold at checkout, with the direct debit reference kept on the term.
Pause for travel, transfer between family members, upgrade or downgrade with a clear audit trail.
Recurring billing, failed payment follow-up, member pricing and usage limits.

Every number shows its working
Commission events store the rule revision used and a readable calculation, so a payslip can be reproduced months later.
A percentage or a fixed sum per item, on services, products, package sales, memberships or sessions taken from a package, for the chain or one outlet, from a day you choose.
What the rules earned and what people adjusted, kept apart. Staff see their own on their phone.
Open a period, close it, have every payslip signed, settle it and export it for the bank.
Primary staff and assistants sharing a service line according to the rule.
Tiered rates, target bonuses and new-customer or rebooking incentives.

Retail stock and treatment stock are different problems
Stock is a ledger of movements, so what is on the shelf is always the sum of what happened to it.
Receive, sale, write-off and adjustment. On-hand is derived from movements, never typed in.
Counted shelf by shelf, an optional blind count, and a difference that needs explaining before it is approved.
Written and tested on the server. Desk does not offer it yet.
What a treatment is expected to use, deducted when it is done, compared against what was actually used.
Suppliers, goods receiving, price history, reorder suggestions and lot or expiry tracking.

Permissions, approvals and an audit trail that holds up
Sensitive actions need permission, a reason and sometimes a second person. Every one of them is recorded.
Built-in roles, or your own started from one and changed a tick at a time, each granted over the person's own records, one outlet or the whole chain.
Discounts above the limit, refunds, voids and changes to a payslip wait for somebody other than the person who asked.
Every sensitive action is recorded with who, when, from which device and why. Desk has no screen to read it yet.
What happened, what needs action and links to the evidence behind each one.
Discount rates well above an outlet's usual, repeated manual extensions, refunds soon after a large commission.

Which of these do you need first?
Most chains start with packages and commission, then grow into the rest. A demo maps your current workflow onto what Nolira already does today.