Product · Entitlement Engine

The rule, worked out automatically.

Every uniform item is reconciled against the employee's role, category and eligibility date before anyone clicks order.

What the engine holds

Allowance, decided before the order.

The entitlement engine keeps allocation rules for every uniform category and enforces them consistently across stores, regions and roles.

01

Eligibility

Initial issue and replacement issue are calculated from the employee's start date and the rule for their category.

02

Allocation

Company-paid allowances are tracked per employee, with remaining counts shown against what they ordered.

03

Payment split

Every item is company-paid or employee-paid at the point of ordering, so the allowance is never exceeded silently.

04

Replacement cycles

Different periods per role and category, with future rule changes applied without touching the ordering flow.

Visible before the order

The allowance is never a surprise.

Employees and the staff ordering for them see what remains, what is company-paid and when the next issue is due - before anything is submitted.

One allowance. One accountable trail.

Employee entitlement / 10482Eligible
TM
Employee entitlement

Thandi Zulu

Store general staff · Store 104

Eligible to order
Company-paid allowance4 of 6 items remaining

Next replacement in 8 months

Shirts2 / 3
Trousers1 / 2
Jacket1 / 1
Draft order3 items selected
Shirt / Navy / M Company paidTrousers / Navy / 34 Company paidJersey / Navy / M
Review order →

In practice

Rules stay consistent as teams change.

New stores, new categories and new managers do not change how the allowance is decided. The engine holds the rule; everyone works against the same one.

Two colleagues reviewing employee uniform allowances on a laptop

Entitlement Engine

Ready to run it against your uniform programme?

The portal is invitation-only and configured by the Muze team.

Access the portal ↗