Everything you want to know about Wasla

In the industry 3–5% is the common range. Higher rates work only at launch.

You decide. You can cap the share of the bill paid by balance.

You decide. Allow stacking, or block it — per offer type.

Yes, it prints with the segment name so the guest understands why.

No — gift cards redeem against bills only, in line with the standard practice.

Every card is tied to a digital record, so a replacement can be reissued with the same balance.

Subscription gives a daily consumption allowance. Membership gives standing perks like a discount on every ticket, without a daily cap.

Yes. Many restaurants give members a higher earn rate on points.

No. Every program works off the phone number. No app, no sign-up — guests get a WhatsApp ping when they earn or redeem.

Yes. Run multiple programs in parallel — points on all sales, stamps on drinks only, membership for VIPs — at the same time.

Yes. Every program works across branches with real-time sync. Guests earn at one branch and redeem at another with no extra setup.

All loyalty programs are included in the standard Wasla plan — no per-program or per-customer fees.

Anytime. You can pause new earning while letting existing balances redeem, or end the program completely.

Yes. Loyalty discounts appear correctly on ZATCA-compliant e-invoices, with no manual workaround.

A common industry rule: 1 point per riyal, 100 points = 1 riyal on redemption. Start there and adjust against your margin.

You decide. Allow stacking, or block it on specific promos.

Earning works offline and syncs later. Redemption needs a live connection to verify the balance.

Yes. You can restrict stamps to drinks only, or to specific items.

There is no physical card to forget. Stamps live against the phone number.

Multiple programs in parallel — e.g. a coffee one and a dessert one — each on its own card.

Start with your top sellers and fill the rest later. We ship templates for common restaurant dishes to shorten setup.

Yes. Each ingredient has a base unit, and the system converts between units automatically (250 g ↔ 0.25 kg).

Yes. Each supplier has a full price history. The system suggests the cheapest supplier per item and flags sudden price hikes.

Yes. The cashier saves orders locally and syncs stock deductions as soon as the connection returns — no data lost.

Run a full or partial count and compare against theoretical stock — the system surfaces real waste, not noise.

Yes. Every stock movement (purchase, deduction, waste, branch transfer) lands in accounting automatically — no manual entry.

No. Start with your top sellers and most expensive items, then expand. Items without a recipe still sell normally — they just don’t auto-deduct stock.

The system uses weighted average cost. Each purchase updates the average, which in turn updates recipe cost.

Yes. Each branch can have its own recipe when needed, with a central default that can be overridden.

No. Old tickets keep the recipe that was active at the time of sale, so historical reports stay correct.

No. The system auto-generates an SKU, and you can override it if you already use your own coding.

Every item has a base unit with automatic conversions. Buy in kilos, use in grams — the system does the math (250 g ↔ 0.25 kg).

Yes. Each branch can link the item to different suppliers with different prices and terms — all on one record.

Yes. Tags let you group items flexibly (seasonal, vegan, Friday promo) without the rigidity of fixed categories.

Yes. Every branch has its own balance per item, with a unified view at the company level.

The system matches new suppliers against the existing directory before adding — if the supplier already exists, the data links to that record instead of creating a new one.

Yes. Each item keeps a full price history per supplier, so you see the trend and compare before deciding.

Yes. When you open a purchase order, the system suggests the cheapest supplier per item based on the latest recorded prices.

The system flags unusual price hikes automatically so you can review before approving the invoice.

Yes. Each supplier has its own payment terms and credit days, which surface in your accounts payable report.

Draft → submit → receive → close (or cancel when needed). Every step is documented and cannot be skipped without permission.

Yes. Receive what actually arrived; the rest stays open on the PO until later receipt or cancellation.

Cost is updated automatically using weighted average cost the moment the receipt is recorded.

Yes. The AI Bill feature extracts line items from a photo or PDF automatically and lets you review before approving.

Yes. On receipt, journal entries (inventory + payables + VAT) are posted automatically — no manual accounting work.

Yes. The system supports multiple warehouses, and each branch can be mapped to a primary warehouse while still pulling from others when needed.

Open a transfer (create → accept/decline → close), then send and receive (or return) until the transfer closes.

Receive the actual quantity; the difference is logged automatically with an optional reason (damaged, missing) and shows up in your loss report.

Yes. Weighted-average cost moves with the transferred quantity, so margin reports at the receiving branch stay accurate.

Yes, with permission. You can grant a branch visibility into other warehouses' stock to help with order planning.

No. Run a full count, a partial count for one category, or a spot check on a single item — without halting operations.

After you enter the counts, the system shows a variance report comparing actual to theoretical and the cost impact.

Yes. Every stock adjustment (quantity or cost) is posted to the ledger automatically, with the reason captured.

Yes. Set a reorder point per item; you get an alert the moment it's breached — and the system can even draft the PO for you.

Counting is open to any permission you choose, but final adjustment approval needs manager rights to keep dual control.

When you prepare an intermediate ingredient in-house (a sauce, a dough, bread) and then use it across multiple recipes. Production converts raw materials into a finished prep with accurate compound cost.

Output cost = sum of input costs (using weighted average). Any change in raw-material price flows into the produced item's cost automatically.

Yes. Logging a production run deducts the inputs from stock and adds the produced quantity in one step.

Yes. Each run is logged with date, quantity, and operator — so you can review it and analyze efficiency later.

Yes. A produced item can itself be an input in another production run, supporting compound recipes (dough → bread → sandwich).

Line items, quantities, prices, totals, and VAT — from a photo or PDF of the supplier invoice.

No. The extracted invoice lands in a review screen; you approve it after checking the numbers and matching to the right items.

The system suggests the closest matches in your catalog, or lets you create a new item on the spot — no data is lost.

Yes. On approval, stock is added, weighted-average cost is updated, and the journal entries post in one step.

Processing is asynchronous and usually takes a few seconds. You get a notification the moment it's ready to review — you don't have to wait around.

Yes, the cashier runs offline and syncs transactions automatically when the connection returns.

Depends on your plan. Starter includes one device; higher plans support multiple connected devices.

No. It runs on the same device you already use as a cashier. You can add an optional iPad at the entrance later, but it isn’t required.

Set a default grace period (ten minutes, for example). If the guest doesn’t arrive within it, the system auto-marks them as no-show and the host can call manually in one tap from the queue screen.

Yes. The interface is bilingual (Arabic and English) with full RTL support, and every customer-facing message template is written in Modern Standard Arabic.

Wasla and its core features — including queue management — are fully free. Our business model relies on optional advanced add-ons you pay for only when you need them.

Queue management needs a live connection to send notifications reliably and keep lists in sync across devices. During short outages, additions are stored locally and sync when connectivity returns.

For most small-to-medium restaurants and cafes, yes. Wasla’s queue is a complete alternative to paid third-party apps and works directly inside the POS your team already uses.

Yes. Create an account, activate queue management, and start instantly — no credit card and no setup fees.

Sold at the cashier like any other order. The guest phone is captured, a subscription card is issued to their account, and it appears immediately on any subsequent redemption.

Yes. Every plan has its own rules covering items, categories, branches, and time windows. A plan can be limited to a specific cup size or bread type, or valid at one branch only.

You choose: from purchase date, or from first use. The latter is better for guests who buy today but start tomorrow.

The card expires automatically and the report retains the full usage history. The guest can buy a new plan anytime.

Yes, a manager can cancel and refund per your policy. Transfers between guests are not supported to keep reports accurate and prevent abuse.

Yes. Subscriptions run alongside gift cards and discounts without conflict in the check calculation.

Redemptions require a live connection to keep balance accurate across branches. Sales work offline and sync later.

Yes. Tables are added and edited directly in the back office with drag-and-drop — no technical team needed.

Yes. Every branch has its own layout and sections, and editing one branch does not affect the others.

From the queue screen, pick the next guest and tap the right table. The table auto-switches to occupied and a new order opens linked to the guest’s profile — no re-entering data.

Yes. You can move the whole order to another table, or merge two tables onto one check without cancelling the order.

Yes. Table management is part of Wasla’s core POS and requires no extra subscription.

Yes. We issue invoices and submit them to the Fatoora platform per ZATCA’s Phase 1 and Phase 2 requirements.

No. Enter your VAT number and business details and follow the onboarding steps. Wasla handles the rest.

When you enter a business customer’s VAT number, a tax invoice is issued and cleared before it’s printed.

Selling and printing continue. Invoices are submitted to Fatoora automatically as soon as the connection returns.

Yes. All your invoices are stored and organized, ready to download or share with your accountant any time.

Yes. Each item has a default price that can be overridden per branch, plus time-based pricing (e.g. a different price during breakfast or peak hours).

Every item can carry modifier groups, and each option has its own price and recipe — so cost and stock stay accurate when guests pick add-ons.

Yes. Product groups bundle several items at one price, and the system still deducts each item's ingredients from stock.

Yes. Every item supports allergen and nutrition fields, and they surface to guests on the digital menu and on delivery platforms.

Yes. Your menu syncs to the Meta catalog automatically — items show with correct prices and images on WhatsApp and Instagram with no manual entry.

Yes. The change propagates to every POS in every branch in seconds — no cashier restart needed.

Yes — dine-in, takeaway, and delivery, each with its own flow and reports.

Yes. Refunds work at the line-item level — refund one dish from a ten-item ticket without voiding the whole order.

Every refund is logged with a full audit trail (who, when, which line) and surfaces in a dedicated report at any time.

Yes, with manager permission. The change is logged and the kitchen gets an immediate alert so nothing slips.

Yes. The cashier stores orders and payments locally and syncs them as soon as the network returns — no data lost.

Keeta integration is live, and we are rolling out the other major aggregators next. Every integration is built on the platform's official API.

No. Orders flow straight from the platform into the cashier and print in the kitchen automatically — no copy-paste, no missed orders.

Each Wasla branch maps to its matching store on every platform via a simple setting in the back office — editable any time.

Order volume, value, cancellation rate, and prep time per platform and per branch — all in one unified report.

Yes. Push menu updates to every platform at once from Wasla — no need to open each app on its own.

Reservations can be taken at the cashier by a host or via a public booking link. The guest picks date, time, and party size and gets an instant WhatsApp confirmation.

The host taps Seat and the table auto-switches to occupied with a new order opened against the guest's profile.

Mark the booking as no-show in one tap. It is saved on the guest profile to help you assess booking behavior over time.

Yes. Every booking ties to the customer, so you see their full history, visit count, and average spend before they reach the table.

Yes. Both run side by side, and you see booked tables alongside the live queue on one unified screen.

No. Audit runs in the background. You only open it when an alert hits or you want to review a shift.

They do not see flags or thresholds, but they know every action is logged — which by itself reduces attempts.

Yes, a flag can be linked to camera time so you jump straight to the moment of the incident rather than scanning hours of footage.

Yes — a downtown branch may need a higher void threshold than a quiet one. Every threshold is per-branch tunable.

Yes. You can edit any preset role or clone it to create a custom version without touching the original.

There is no limit on the number of roles. Create as many as your team structure needs.

Some advanced features require a higher plan, but role and permission management is available on every plan.

Update the branch scope on the user profile and the change takes effect immediately across all devices.

From the back office in one click. Enter its details (name, address, hours, payment methods) and it's ready to operate within minutes — no field technician.

Yes. Each branch can enable its own payment methods, discounts, and tags without affecting the others.

Yes. Each branch has its own sections and table map, edited via drag-and-drop in the back office.

Pick the matching Google Location from a dropdown in branch settings — Google reviews are then aggregated automatically.

Yes. Real-time sync pushes every edit (menu, prices, payment methods, permissions) across every device in the branch.

Create the user profile (name, phone, branches, role) in the back office. They get a direct login link and start immediately.

Each user can carry both a cashier role and a separate back-office role. The split keeps you from granting more access than needed.

Yes. Each cashier has a short PIN for fast switches between shifts — no long passwords.

Update the branch scope on their profile and the change applies instantly across all devices — no need to recreate the account.

Yes. Deactivating blocks login without deleting the record, so the full history stays for reports and audits.

They link an event to an automatic action. For example: "if stock drops below a threshold → WhatsApp the manager," or "if a customer crosses a spend tier → tag VIP and send an offer."

Order created, stock below threshold, customer reaching a spend tier, high-value invoice issued, and more — with precise filters.

Send WhatsApp, apply a discount, tag the customer, mark an order for review, or alert a manager — all without a human in the loop.

Both. Choose each rule's scope: one branch, a group of branches, or the whole company — whatever fits.

No. Rules are built in a simple interface: "if X happens, run Y." No code, no scripts.

Every action by every user: who, what, when, and on which device. It covers menu edits, voids, discounts, price changes, and more.

Yes. Filter by user, branch, date, action type — or any combination — and reach the answer in seconds.

Yes. Export to CSV for internal investigations or to share with an external auditor on request.

The log is retained for an extended period per Wasla's data retention policy, so you can look up any old action easily.

No. The log is immutable — no user, not even top admins, can edit or delete it — to keep audit integrity intact.

Yes. Modern iPads and tablets are built for sustained use, run offline, and are instantly replaceable. Many large global chains run entirely on them.

They all connect to the tablet over Bluetooth or the network. No tangled cables to a single terminal. The setup is simple and easy to extend later.

Yes — every invoice is compliant out of the box, and phase updates are pushed automatically with no on-site technician.

The cashier keeps running offline — orders and payments continue. Data syncs automatically once the network returns.

Usually a single shift. The interface mirrors the apps your team already uses on their phones.

Yes. We move your menu, items, branches, and customers, and help you launch the first branch within days.

Quotes flow draft → accepted, then convert to an invoice in one click. Invoices flow draft → submitted → authorized → voided.

Yes. Every invoice is issued in line with ZATCA Phase 1 and Phase 2 requirements and submitted to Fatoora with no manual step.

Authorized invoices are not edited directly to keep integrity. Issue a credit note and then a new invoice for the correct amount.

Yes. Invoices can be issued in any currency and are translated to your base currency in the ledger automatically using the exchange rate.

Yes. Send by email or WhatsApp on approval, or keep it as a tax copy to print at handover.

From their account they submit the claim with attachments, and it routes to the manager for approval or rejection with notes. Every step is logged.

An expense is usually a cash or employee-card spend awaiting reimbursement. A supplier bill is a commercial liability with credit terms that hits accounts payable.

Use a credit note. It reduces the liability to the supplier and posts to the ledger and AR/AP balances automatically.

Yes. Record a prepayment to a supplier and match it against the invoice once issued — no manual journals.

Yes. Each expense can be tied to a cost center (branch, department, event) so reports show the true profitability of each unit.

Yes. You start with a chart tailored to F&B and can customize it to your business.

A cost center represents a measurable unit (branch, department, event). Tag transactions to it to see the profitability of each unit independently.

No. The system auto-codes the account by sequence, and you can override it if you already use your own coding.

Yes. Each account can hold balances in multiple currencies with automatic FX revaluation.

Yes. Locking a period or fiscal year blocks any retroactive entries to keep approved reports accurate.

Import your statement as CSV or OFX directly from your bank — the system detects the columns automatically.

Yes. Clear transactions match automatically, and ambiguous ones are surfaced for manual review with smart suggestions.

Rules that tell the system: "if you see this description, code it to this account." Set them once and matching runs automatically every time.

Via per-till cash codes, so each shift's flows stay separate and surface clearly in reconciliation.

Yes. Each line carries an internal discussion thread, so the accountant and till operator can comment without mixing up notes.

Monthly, quarterly, or annual. Pick the period that matches your business and the level of detail you need.

Yes. Spread the budget evenly or by custom weights (e.g. peak season) in one click.

The budget-vs-actual report shows variance by amount and percent, filterable by account, branch, or period.

Yes. Copy last year's budget and apply a growth rate — you skip the blank-page start.

Yes. Each branch has its own budget with a consolidated view at the company level.

P&L, balance sheet, trial balance, general ledger, aged receivables and payables, customer statements, VAT return, plus detailed branch and shift reports.

Yes. It exports in the format required by ZATCA — no manual collation.

Yes. It classifies items into stars, plowhorses, puzzles, and dogs — so you know what to promote, what to re-price, and what to drop.

Yes. It reconciles card payments at the till against what actually landed from the acquirer, surfacing any fees or gaps.

Yes. Schedule any report to land in the inbox of the people you choose — daily, weekly, or monthly.

Wasla is an approved official WhatsApp provider. Build the template, pick the audience, and send — all inside the system, no external tools.

Yes. Filter by any criterion: last visit date, total spend, branch, favorite category, or your custom tags.

It depends on your plan. Your SMS quota and usage show in real time before you send any campaign.

Yes. Build the campaign now and set the send time — it goes out automatically when your audience is most likely to read it.

Yes. The AI assistant drafts professional Arabic and English copy, which you can edit before sending.

Percent off, fixed amount off, free item, or buy-one-get-one. Each type has its own controls and validity.

Yes. Set both a total usage cap and a per-customer cap so coupons can't be abused.

Yes. Coupon validity and conditions are checked live at the cashier before being applied to the ticket.

Yes. Every offer has a validity window (dates, weekdays, time of day), and it disables automatically outside it.

Yes. The discount appears clearly on the ZATCA-compliant e-invoice with no manual workaround.

A simple public page per branch that gathers all the important links (menu, booking, delivery, branches, contact, maps) in one easy-to-share place.

No. Edit it yourself from the back office in minutes — the page renders professionally and matches your brand.

Yes. Each branch has its own page with its own URL, so you can route guests to their nearest branch.

Yes. The URL is short and stable — perfect for Instagram bios, official WhatsApp lists, and paid ads.

Yes. Any edit to branch info (hours, address, phone) reflects on the page instantly — no manual republish.

Multiple choice, short text, long text, star rating, file upload, date, and more — enough for any form you need.

Yes. Conditional logic builds a smart form that shows only the relevant question based on the guest's answer, so it stays short.

Every form has a public URL — share it on WhatsApp, Instagram, a QR code on the table, or by email.

All responses land in one central place inside Wasla, with Excel export and automatic linking to the guest profile when a phone number is provided.

Yes. Ready templates (experience feedback, job application, new-menu poll) get you started quickly.

Just the phone number at the till. The profile is created automatically and enriched with purchase history, tags, and spend tiers on every visit.

Yes. One profile across all branches — you see the full history regardless of which branch they visited.

The system checks each phone number's status before any campaign and excludes ineligible numbers to avoid rejections.

Yes. Each profile shows charts of visit frequency, average ticket, favorite categories, and the customer's own peak hours.

Yes. Build dynamic segments (e.g. VIP, this-year, dormant) plus manual tags, and target each in your campaigns.

Yes. Once a Google Location is assigned to each branch, new reviews are pulled in automatically and surface in a unified dashboard.

Yes. Reply to Google reviews directly from the system; the reply appears on Google with no separate dashboard.

The system sends post-visit feedback requests to guests selected by AI, and classifies responses by experience aspect (food, service, cleanliness).

Yes. Comments are classified as positive, neutral, or negative, with recurring keywords surfaced — so you know what guests love and what bothers them.

Yes. Review reports break down by branch so you can compare performance and act on the gaps precisely.

Useful for any service with a fixed time: private rooms, cooking experiences, menu consultations, VIP hosting. Flexible for F&B needs.

Each staff member has an availability schedule with overrides (leave, urgent block-out), and bookings can't be made outside the available windows.

Book → confirm → start → complete (or cancel or no-show). Every step is logged and surfaces in performance reports.

Yes. An automatic WhatsApp reminder fires before the appointment by a window you customize — no-shows drop noticeably.

Yes. A calendar view shows appointments by day, week, or month, filterable by staff or service type.

Hour, day, week, month, branch, item, category, sales channel (dine-in / takeaway / delivery), and payment method — and every report cross-cuts.

Yes. Reports support drill-down to ticket level, so you can investigate any standout number.

Pick the two periods (e.g. this month vs last month) and the report shows the variance by amount and percent.

Yes. Hour-and-day reports reveal the true peak hours per branch — perfect for planning shifts and promos.

Live. Every sale shows in the reports immediately, so you watch performance during the shift without waiting for the next day.

The COGS report shows each item's cost within the ticket and net margin — winners and losers, clearly.

It classifies your menu into four quadrants: stars (high demand + high margin), plowhorses (high demand, low margin), puzzles (high margin, low demand), and dogs (low both). It guides keep, re-price, or drop decisions.

Yes. Count waste, manually-logged waste, and theoretical-vs-actual variance all surface with a clear money value.

Yes. Reorder forecasts use your historical consumption to suggest the right quantity per item — so you avoid both stockouts and pile-ups.

Yes. Cost figures come from real inventory and accounting entries, not estimates — so you trust the numbers without manual reconciliation.

Hours, total sales, average ticket, void count, discount count, and refunds.

Yes. A per-branch leaderboard ranks the top performers by whichever metric you choose.

Yes. Sort staff by voids or discounts to spot suspicious behavior before it becomes a problem.

Yes. Every report exports to PDF or Excel, or schedules to a branch manager by email automatically.

Yes. Clock-in and clock-out come from the cashier login — no separate time-attendance device needed.

MCP (Model Context Protocol) is the open standard that connects your AI assistant straight to your Wasla data. You ask from inside Claude, ChatGPT, or Gemini — no exporting files, no middle dashboards.

Claude, ChatGPT, and Gemini via connectors. Mobile connect is available today in the Claude app; the others work over the web and developer tooling, depending on your plan with each assistant.

No. Access is read-only: no create, update, or delete. The connector reads your data only to analyze it.

Sales, inventory, the menu, customers, and accounting within your account, under the same user permissions as the dashboard — so it never sees more than it should.

Your dashboard gives you a read-only access token and your account's connection link, which you add as a connector in your assistant. A few minutes, no developer.

Yes. The assistant only reaches your account's data, it is never shared with another business, and you can revoke the token anytime from the dashboard to cut off access instantly.