HOSPITALITY · · 10 min read

F&B ERP in KSA — built for restaurants, central kitchens and cloud kitchens.

Saudi F&B has scaled fast: aggregator-led dark kitchens, multi-brand central kitchens and family restaurant chains all need an ERP that understands recipes, modifiers, aggregator orders and ZATCA. Here's what works in 2026.

NOVASOFT · HOSPITALITY

Saudi F&B has scaled fast: aggregator-led dark kitchens, multi-brand central kitchens and family restaurant chains all need an ERP that understands recipes, modifiers, aggregator orders and ZATCA. Here's what works in 2026.

Saudi F&B is a different problem

F&B in Saudi Arabia in 2026 looks nothing like 2018. Aggregators (Hungerstation, Jahez, ToYou) drive 35–55% of total orders for QSR chains. Cloud kitchens multiply faster than physical restaurants. ZATCA Phase 2 applies to every receipt. And consumer expectations on delivery time, accuracy and loyalty have hardened.

The ERP that runs all this needs to handle recipes, modifiers, central kitchens, aggregator integration, kitchen display, loyalty, and ZATCA — all in the same database.

ANNOYA — the F&B ERP for Saudi operators

ANNOYA is Novasoft's F&B ERP add-on on top of Business Central + LS Central Hospitality. 189 features across 21 modules including:

  • Recipe + cost-of-goods-sold engine
  • Multi-modifier orders (sauces, sides, options)
  • Central kitchen production with branch distribution
  • Aggregator integration (Hungerstation, Jahez, ToYou, Mrsool)
  • KDS (Kitchen Display System) with course timing
  • Loyalty + offers for branded chains
  • ZATCA Phase 2 compliance via Novasoft's KSA extension

Typical 3-4 week go-live for a single-brand chain.

Aggregator integration without the manual re-keying

The first-generation aggregator integrations dumped orders into the POS as 'open tickets' that staff had to re-key with modifiers and special instructions. ANNOYA's integration pushes the order direct to the kitchen display with full modifier fidelity, including aggregator-specific commission and rebate accounting.

For a 50-branch QSR chain in Riyadh, this saves ~3 minutes per aggregator order in re-keying time — at 200 orders/day per branch, that's 100,000 hours of labour saved per year across the chain.

Central kitchen + branch distribution

Saudi cloud-kitchen operators run multiple brands out of one central facility. The ERP needs to:

  • Produce in batches against the day's aggregated demand forecast
  • Distribute to branches with cost-of-goods accuracy per branch
  • Track waste at every step (production, dispatch, branch sales)
  • Reconcile inter-branch transfers for VAT and ZATCA

ANNOYA handles all of this via the inherited BC supply chain and adds F&B-specific dispatch logic.

ZATCA Phase 2 for F&B — receipts and refunds

Every receipt — including aggregator orders — must clear FATOORA. ANNOYA + the Novasoft KSA e-Invoicing extension handles both standard tax invoices (B2B catering) and simplified receipts (B2C restaurant sales). Credit notes for delivery failures and refunds flow back through the same pipeline.

Loyalty + offers that make economic sense

The KSA F&B chains winning market share in 2026 have programmatic loyalty: 1 SAR spent = 1 point, redemption at multiples of 100 points, monthly tier resets. Underneath, LS Central + ANNOYA support this without custom development. Customers earn at any branch, redeem at any branch, online or offline.

Frequently asked questions

Does ANNOYA work with aggregators other than the big 4?

Yes. The integration framework supports any aggregator with REST API. We've integrated Mrsool, ToYou, Resto, Hungerstation, and Jahez for Saudi customers; can add others on request.

How does it handle multi-brand cloud kitchens?

Each brand is a 'Concept' in the system with separate menus, pricing, recipes, and P&L. The central kitchen produces against aggregated demand across all brands.

What about KDS — Kitchen Display Systems?

ANNOYA includes KDS as standard. Course timing, allergen alerts, modifier highlights all on screen. Touch-screen confirmation flows back to POS.

Is ZATCA compliance built in?

Yes — ANNOYA bundles the Novasoft KSA e-Invoicing extension. Every receipt clears FATOORA without operator action.

How fast is a typical implementation?

3–4 weeks for a single-brand 5–15 location chain. 8–14 weeks for multi-brand cloud-kitchen operators with central production.

Can we run ANNOYA without LS Central?

ANNOYA needs Business Central. The hospitality POS layer is LS Central Hospitality or a third-party POS — ANNOYA bridges to most major POS systems.

Where to go next

Read the full overview of ANNOYA F&B ERP. For a deeper dive into related capability, see Food & Beverage vertical. When you're ready to talk specifics, book a 30-minute call with a Novasoft consultant.

Link copied to clipboard
Chat with us