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.
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.
Day view with lanes for every staff member, room, chair and machine. Drag to move with a conflict preview before commit.
A colour service holds the stylist for 30 minutes, releases them during 40 minutes of processing, then books them back for the finish.
Waiting, called, in service and ready for checkout, with a wait estimate based on the live queue and staff availability.
Customers register for a service and date window. When a slot opens they are notified with a temporary claim period.
Each occurrence is validated separately. Conflicts are 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.
Contact, preferred language, preferred staff, visit timeline, packages, payments and communication history in one view.
Service preferences, technical formulas and allergy notes. Each type has its own visibility, retention and export rule.
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, high value, birthday month. All built from transparent rules.
Identity matching and resolution across imports, 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.
Pulls straight from a completed appointment or walk-in, with staff attribution on every line.
Cash, card, QR, bank transfer, deposit allocation and package redemption on one sale.
Reason codes, permission thresholds and approval requests above the limit. Before and after values are audited.
Opening float, paid-in and paid-out with reasons, blind count option, variance threshold and a locked closing report.
References the original lines, reverses package entitlements and creates the matching commission clawback.
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 eligible services, validity rules and branch restrictions per template.
Purchase, redemption, adjustment, expiry, refund, transfer and bonus. Each entry carries actor, device, reason and approval.
Records which branch sold and which redeemed, so owners can settle between outlets properly.
Outstanding sessions and value, expiry buckets, dormant packages and manual adjustment exceptions.
Pause for medical travel, transfer between family members, upgrade or downgrade with a clear audit trail.
Recurring billing, failed payment dunning, member pricing and usage limits.
Every number shows its working
Commission events store the rule version used and a readable calculation, so a statement can be reproduced months later.
Percentage or fixed, by service, product, package sale or package redemption, varying by branch and staff role.
Primary staff and assistants share a service line according to the rule, not a manual adjustment afterwards.
Base rate, bonuses, splits and deductions listed line by line. Staff see the same view on mobile.
Estimated until the period closes, then locked. Later changes are separate, audited adjustment events.
Tiered rates, target bonuses, margin-based commission and new-customer or rebooking incentives.
Jurisdiction adapters and payroll system integrations. Nolira reports earnings; it is not a statutory payroll engine.
Retail stock and treatment stock are different problems
Service recipes deduct what a treatment actually consumes, so you can see real service cost and margin.
Receive, sale, service consumption, transfer, wastage, adjustment and return. On-hand is derived from movements.
Expected quantity per service, generated at completion, with an override that requires a reason. Compare expected against actual.
Full or cycle counts, optional blind count, variance report and approval threshold before adjustment posts.
Prioritised by service impact, so an item that blocks facials outranks a shampoo on the retail shelf.
Suppliers, goods receiving, price history, reorder suggestions and lot or expiry tracking.
Requested, approved, shipped, received, with discrepancy handling and transfer lead time reporting.
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.
Twelve role templates combined with scope: own records, one branch, selected branches, region or whole organisation.
A receptionist discounts to 10%, a manager to 25%, refunds above RM300 escalate. Limits are configuration, not code.
Actor, role, device, action, before and after, reason, approval chain and correlation ID, without storing secrets.
Where policy requires it, the person who raises a request cannot be the person who approves it.
What happened, what needs action, suggested next step and links to the evidence behind each one.
Discount rates well above branch baseline, repeated manual extensions, refunds shortly after a large commission event.
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.