Skip to content
Kuality.ai
ERP & OperationsSyriaMaqali

A fast Arabic POS with real accounting underneath: kitchen board, recipes, stock and daily closing.

Maqali: Restaurant POS & Accounting
Client
Maqali
Sector
Food & beverage · POS · Accounting
Market
Syria
Platforms
Web app (Arabic RTL) · Kitchen display
Users
Admins · Accountants · Cooks · Customers, via the public menu
Technology
Next.js 14TypeScriptTailwind CSSFirebase AuthFirestore
Overview

A simple, fast system for a small falafel and sandwich restaurant that still follows strict accounting rules. Cashiers sell from a quick POS screen, the kitchen sees a live order board, and managers get purchases, suppliers, inventory, prepared materials, expenses, cash box, reports and daily closing, all in an Arabic right-to-left interface. Financial documents are never deleted, only cancelled with a reason, and every reference number is generated inside a Firestore transaction.

0
Hard deletes of financial records
3
Stock layers, from ingredient to product
6
Auto-numbered document series
3
Roles: admin, accountant, cook
The challenge
  • A small falafel and sandwich restaurant needed a till fast enough for the counter, with accounting underneath that stays correct.
  • Cash moves in many ways in a day (sales, purchases, supplier payments, expenses, salaries, owner deposits and withdrawals), and the cash box had to agree with every one of them.
  • Recipes are written in grams while stock is bought by the kilo, and some ingredients are prepared in-house in batches, so the cost of each product had to be worked out through every layer.
  • Delivery platforms pay later while counter sales are cash, and the two could not be mixed in the cash box.
  • Mistakes had to be correctable without rewriting history, and a day once closed had to stay closed.
Our approach
01

Every money movement is one all-or-nothing step: the document, its cash entry, its stock moves and its audit record are saved together or not at all.

02

Cash has one place that writes it, and cash and supplier balances are calculated from the records, never stored as separate totals.

03

Nothing financial is deleted. Records are voided with a reason, a closed day blocks every change, and a purchase correction posts only the difference, previewed for the admin to confirm.

04

The accounting formulas live in one module, apart from the screens, and are covered by automated tests. The app is a static Next.js build on Firebase, in Arabic, right to left.

What we built

Sales & kitchen

  • POS orders, with voids that restore stock
  • Optional customer book with statements
  • Delivery channels settled in cash or as receivables
  • Live kitchen board that shows the cook no amounts

Stock & recipes

  • Three layers: inventory, prepared materials, products
  • Recipes in any unit, with g/kg and ml/L conversion
  • Batch production with yield, unit cost and circular-recipe checks
  • Low-stock alerts and stock value

Purchasing & cash

  • Purchase invoices, supplier payments and statements
  • Admin-only corrections, previewed before posting
  • Cash box with owner deposits and withdrawals
  • Expenses, monthly payroll, and daily closing and reopening

Reports & records

  • Reports that open on today, with yesterday, week, month and custom periods
  • An hour window for analytics
  • Audit log and six auto-numbered document series
  • Excel and CSV exports of what is on screen

Public menu

  • Open to customers, no sign-in
  • Cart sent to the restaurant as a WhatsApp message, then entered by the cashier
  • Search-ready: structured restaurant and menu data, Open Graph previews and a sitemap

We make your competitors jealous.Don’t wait, call us

You’re one click closer to having your technology partner. Tell us about your idea, and we’ll come back with a plan, not a pitch.