The daily problems

Where the work usually goes wrong.

01

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.

02

The kitchen sheet and the order disagree

Cooking quantities, packing lists and dispatch are rebuilt by hand from orders, and each rebuild is a place for a mistake.

03

Statements are disputed line by line

Clients question days and counts. Complaints are raised verbally and have no trail, so the discussion starts from memory.

04

Shifts, overtime and Ramadan hours

Kitchen and service staff work rotating shifts with overtime, and working hours change during Ramadan.

05

Ingredient purchasing is not tied to contracts

Purchases are approved without knowing which client contract they serve or what budget is left.

Saudi requirements

What the software handles for you.

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.

RequirementWhat the software handles
VAT at 15%Monthly statements and invoices carry VAT per line and post to your VAT accounts.
ZATCA e-invoicingInvoicing is built to work with ZATCA e-invoicing requirements. The scope for your company is confirmed in your proposal.
GOSI and WPSPayroll for kitchen and service staff with GOSI contributions and a salary file per run.
Saudization, Iqama, Ramadan hoursSaudi and non-Saudi headcount, Iqama expiry dates and Ramadan working hours are handled in the HR module.
Arabic and English documentsStatements and invoices can be issued in Arabic, English or both, from the same record.

Saudi compliance

How a project starts

From first call to a working system.

The 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.

  1. List clients, sites and service windows

    We record where you deliver, when, and what each client orders from the menu cycle.

  2. Set up menus and ordering

    Menu cycles are loaded and clients are given their portal, so daily numbers arrive in one place.

  3. Run the kitchen from the sheet

    Cooking sheets and packing lists replace the hand-built ones, and one site runs on it first.

  4. Close the first month together

    The first monthly statement is produced alongside your existing method so the numbers can be compared.

Questions

What buyers in this sector ask.

Can clients order and raise complaints themselves?

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.

Can we run rotating menus?

Yes. Menus rotate by cycle, and orders are placed by service date against the menu.

Do kitchen staff get their own view?

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.

Can it connect to the accounting system we already run?

That is an integration project, scoped with the e-invoicing integration service. Which system, and what flows between them, is written in the proposal.