Orders arrive late and by phone
Each client changes numbers on the day. Without one daily order by service date, the kitchen cooks from the last message it saw.
Meals are planned by service date, cooked from one sheet, packed per client and settled every month. When any of those steps lives in a different phone or notebook, the statement is where it shows.
Each client changes numbers on the day. Without one daily order by service date, the kitchen cooks from the last message it saw.
Cooking quantities, packing lists and dispatch are rebuilt by hand from orders, and each rebuild is a place for a mistake.
Clients question days and counts. Complaints are raised verbally and have no trail, so the discussion starts from memory.
Kitchen and service staff work rotating shifts with overtime, and working hours change during Ramadan.
Purchases are approved without knowing which client contract they serve or what budget is left.
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% | Monthly statements and invoices carry VAT per line and post 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 kitchen and service staff with GOSI contributions and a salary file per run. |
| Saudization, Iqama, Ramadan hours | Saudi and non-Saudi headcount, Iqama expiry dates and Ramadan working hours are handled in the HR module. |
| Arabic and English documents | Statements and invoices can be issued in Arabic, English or both, from the same record. |
Client, operator and internal portals with one sign-in, rotating menus, daily ordering by service date, cooking sheets, packing lists, statements, line disputes and complaints.
Learn moreRosters and overtime, attendance from any biometric terminal, Ramadan hours, GOSI and WPS.
Learn morePurchasing with budget checks, approvals and the finance side of VAT invoicing.
Learn moreConnect an accounting system you already use to e-invoicing.
Learn moreAnything specific to how you serve your clients, built next to the product.
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.
We record where you deliver, when, and what each client orders from the menu cycle.
Menu cycles are loaded and clients are given their portal, so daily numbers arrive in one place.
Cooking sheets and packing lists replace the hand-built ones, and one site runs on it first.
The first monthly statement is produced alongside your existing method so the numbers can be compared.
Yes. Sufra has a client portal for ordering and for raising line disputes and complaints, next to operator and internal portals with one sign-in.
Yes. Menus rotate by cycle, and orders are placed by service date against the menu.
Kitchen cooking sheets and per-client packing lists are produced from the same orders, so the kitchen works from the order, not from a retyped copy.
That is an integration project, scoped with the e-invoicing integration service. Which system, and what flows between them, is written in the proposal.
A consultant from our Riyadh team replies with next steps. A written, itemised proposal follows before any work starts.