Skip to content
Iterna
Spa, salon & wellness

Spa and salon management software, built in Malaysia

Spa and salon management software should do more than take bookings. It should know who was rostered, who actually turned up, whether the treatment was done the way it should be, what they sold, what commission that earned, and what has to reach KWSP and PERKESO at the end of the month. We build that as one system, because we run one.

Tell us your problem

How this usually runs today

  • Bookings in a platform that charges per booking and owns your customer list
  • Staff schedules on a printed sheet or in a WhatsApp group
  • Attendance in a spreadsheet, reconciled by memory
  • Commission calculated by hand, differently depending on who’s calculating
  • Prepaid packages tracked in a notebook, because the booking system can’t
  • Payroll assembled from all of the above on the last two days of the month
  • The standard for a treatment held in the head of whoever has been there longest
  • Complaints reaching the owner through a public review, a week after the visit

What we’d build

  • Bookings and a public booking page

    Your own, on your own domain, with your customer list staying yours.

  • Rosters

    Who’s working which shift, at which branch, visible to staff on their phones.

  • Attendance

    Clock in and out, tied to the roster, not floating on its own.

  • SOP checklists

    What “done properly” means, attached to the shift and the role rather than to a person.

  • Deviations and violations

    Recorded against the shift, so a branch slipping shows as a pattern instead of a hunch.

  • Customer feedback

    Comments reach someone whose job it is to answer them, and the recurring ones become changes.

  • Commission

    Calculated from what was actually sold, at the actual discount, by payment method.

  • Packages and prepaid

    Balances that decrement correctly and can’t be double-spent.

  • Point of sale

    Services, retail products, gift cards and packages in one transaction.

  • Loyalty

    Points or stored value that the front desk can actually explain to a customer.

  • Payroll

    Hours, overtime, commission and statutory contributions in one run.

The parts that are harder than they look

  1. 01

    The service standard drifts, and nobody can prove where.

    Every owner knows one branch is slipping and cannot say which shift or which step. When the standard lives in people rather than in the system, the only evidence is a public review, and by then the visit is over. It has to be recorded at the point of work, against the shift, or it is not evidence at all.

  2. 02

    Overtime isn’t a clock problem, it’s a roster problem.

    A weekend opening shift runs longer than a weekday one, so a flat daily threshold either underpays your staff or overpays them. Overtime has to be calculated against the shift someone was rostered for, together with what the attendance record says.

  3. 03

    Commission has more variables than anyone expects.

    What was sold, at what discount, paid how — and prepaid packages behave differently from ordinary sales. One rule produces the wrong number for someone every single month.

  4. 04

    Unpaid break time differs by role, and it has to be changeable by a manager.

    A therapist and a receptionist can’t share a rule, and neither should need a developer to change one.

  5. 05

    Freelancers and employees can’t share a payroll path.

    They’re paid differently and treated differently under the law, so the system needs two paths that still roll up into one set of numbers.

  6. 06

    Statutory files get rejected without telling you why.

    EPF, SOCSO, EIS and PCB have to reach the portals in exact formats — fixed-width records, zero-padded fields, correct line endings, a trailer row that reconciles. Getting those accepted is unglamorous, invisible in a demo, and the difference between software that looks finished and software that is.

Proof

We didn’t research this sector. We run a spa on the system we built for it.

Operiq handles bookings, rosters, attendance, overtime, commission and Malaysian statutory payroll for a working spa, and produces the export files that KWSP and PERKESO portals accept.

See the Operiq case study

FAQ

Questions we get asked

  1. 01

    Can we keep our existing booking platform and connect it?

    Sometimes, if it offers a way to get bookings in and out. It is worth asking what you gain: most of the difficulty in this sector is what happens after the booking — roster, attendance, commission and payroll — and that chain works better when the booking is part of it rather than arriving from outside.

  2. 02

    What happens to our customer data if we move off a booking app?

    That depends on the platform, and it is worth checking before you need to know. Some let you export a full customer list, some export very little. We look at what can be extracted, migrate what exists, and from then on the list sits in your own system.

  3. 03

    Can it handle more than one branch?

    Yes. Rosters, attendance, stock and reporting are per-branch, with company-wide settings above them, so a second outlet does not mean a second system. Operiq was built multi-tenant from the first version.

  4. 04

    Does it calculate EPF, SOCSO, EIS and PCB?

    Yes, and it produces the export files the portals accept. That last part is the work: the calculation is arithmetic, while the file format — fixed-width records, zero-padded fields, a trailer row that reconciles — is what gets a submission rejected.

  5. 05

    Can freelance therapists be paid through it?

    Yes, on a separate path from employees. Their hours and commission are calculated automatically, but they sit outside the employee payroll run because they are treated differently under the law.

Tell us how your spa runs today.

How many branches, how commission works, and what happens in the last week of the month. That is enough for us to tell you what to build first.

Tell us your problem