Package leakage costs more than you think
4 August 2026 · Nolira Team
Almost every beauty business that sells prepaid packages believes its balances are broadly correct. Very few can prove it. The gap between those two positions is where the money goes.
Leakage is rarely theft
When owners imagine package loss they picture a dishonest employee. In practice most leakage is procedural. A session gets redeemed twice because two staff wrote it down separately. A balance is adjusted by hand to settle a customer complaint and never recorded anywhere. A package sold at one branch is honoured at another with no record flowing back. None of that requires bad intent, and all of it is invisible in a sales report.
The four places it happens
- Double redemption: the same session deducted twice, or not at all, because the record lives in more than one place.
- Silent adjustment: a balance edited directly to resolve a dispute, with no reason, approver or trail.
- Cross-branch drift: sold in Bangsar, redeemed in Subang, settled between the two branches never.
- Expiry ambiguity: nobody is certain whether a package lapsed, so it is quietly honoured, indefinitely.
Why a ledger fixes it
The fix is structural rather than procedural. If the balance is a number stored in a field, someone can change it. If the balance is a projection of an append-only ledger, changing it requires adding an entry, and every entry carries who, when, why and which approval authorised it. The balance becomes an outcome of recorded events instead of an opinion.
That is how Nolira models packages. Purchase, redemption, adjustment, expiry, refund, transfer and bonus are all entries. Nothing is edited in place. When a customer disputes a balance, you show them the history rather than argue about memory.
What to check this week
Pick ten active packages at random. For each one, try to reconstruct every redemption from your records: which service, which staff member, which branch, which date. If you cannot do that for all ten, you do not have a package problem yet, but you do have a package risk.