Nobody is sure who lives where
Occupancy changes every week. Without a resident list by building, room and bed, laundry quotas, meals and charges are guesses.
Residents by building, room and bed; one laundry counter; meals by service date; maintenance spend. The work is repetitive and high-volume, which is exactly where notebooks and spreadsheets stop working.
Occupancy changes every week. Without a resident list by building, room and bed, laundry quotas, meals and charges are guesses.
Laundry arrives in bags with unclear ownership and leaves with arguments about what is missing. Barcode drop-off and pickup by service window leaves a record for each piece.
Daily orders by site and service date change with arrivals and departures. A kitchen working from yesterday's list produces waste or shortages.
Repairs, consumables and contractor invoices are agreed by phone and reconciled at month end, when nobody remembers what was approved.
The client or camp owner questions lines on the statement, and the evidence is in someone's notebook.
These are the Saudi regimes that touch this sector, and what the software does about each. Your proposal confirms which apply to your company. This is not legal advice; confirm obligations with your adviser.
| Requirement | What the software handles |
|---|---|
| VAT at 15% | Statements and invoices carry VAT per line and are posted to your VAT accounts. |
| ZATCA e-invoicing | Invoicing is built to work with ZATCA e-invoicing requirements. The scope for your company is confirmed in your proposal. |
| GOSI and WPS | Payroll for your housekeeping, kitchen and counter staff, with GOSI contributions and the salary file for each run. |
| Personal data of residents (PDPL) | Resident lists are personal data. Access is by role, and the hosting location is your choice, written into the agreement. |
Barcode drop-off and pickup, residents by building, room and bed, monthly piece quotas, thermal slips and a Windows desktop app for the counter.
Learn moreMeals ordered by service date, cooking sheets and packing lists per client, monthly statements with line disputes and complaints.
Learn morePurchase requests, approvals and an inventory of what the company owns and who holds it, for maintenance and supplies.
Learn moreRosters, overtime and payroll for the people who run the buildings.
Learn moreA maintenance-request portal for residents or building supervisors, built around how your operation assigns work.
Learn moreThe order differs a little by sector. The principle does not: a written scope comes first, and you test with your own data before anything goes live.
Buildings, rooms, beds, laundry counters and service windows, and who maintains the resident list when someone arrives or leaves.
We load it from your spreadsheet and agree who is allowed to change it.
Usually the laundry counter or meal ordering. One of them becomes the first milestone.
Your supervisors use it with real residents, then the other buildings follow in the order written in the proposal.
The counter runs on a Windows desktop app with thermal slip printing. How it behaves on a weak connection is confirmed at the site survey, not assumed.
Yes. Laundry Management tracks monthly quotas by number of pieces for each resident.
They are separate products and can be proposed together in one written proposal. What data they share is confirmed at scoping.
No. It suits any operator with residents in buildings, whether the housing is owned, leased or managed for a client.
A consultant from our Riyadh team replies with next steps. A written, itemised proposal follows before any work starts.