Keep tables turning.
Not guests waiting.
QR menus, configurable items and clear kitchen tickets. Take orders at the table or the counter, with one menu behind both.
The whole hospitality toolkit
Built for the floor.
Not the back office.
From a quiet lunch to a full-house Friday. YallaBill brings the pieces of service together, so your team can focus on the people in front of them.
Ashik Lounge is a real menu running on this deployment: browse, build a cart, pick a table and watch the order tracker. Payments are processed only after the restaurant connects its payment account.
Keep tables turning.
Keep the tab open.
And the night going.
Staff-managed rounds, dedicated bar queues and shared bills. Guests can settle their part while their friends stay for another.
Big table.
Small payment drama.
Item shares, equal splits and custom contributions. Personal tips and receipts, without making one guest cover everyone else.
All the moving parts. One connected service.
Small details.
Big difference.
Capabilities below reflect the existing application. This standalone sales site doesn't connect to a live restaurant or process payments.
| The feature | What it does for your service | Good to know |
|---|---|---|
| AI menu studio | Extract photos and PDFs into editable menu drafts. Review OCR warnings, categories, item descriptions, prices and modifiers. | Azure OCR + model setup |
| Menu management | Publish reviewed drafts; manage availability, images, station routing, item taxes and modifiers. Import/export validated JSON. | Review required before publish |
| Mobile ordering | Browse by category, choose add-ons and quantities, leave notes, tip, check out and follow an order. No guest app installation. | Guest ordering requires a live app |
| Table QR & website menu | Use permanent ordering QRs for tables; share a restaurant link or generate an iframe snippet with a direct-link fallback. | Embedding needs verification |
| Counter POS | Named staff PIN access on authorized kiosks. Create dine-in or pickup orders, collect payment now, or keep a dine-in tab open. | Owner authorization + individual PINs |
| Open tabs & rounds | Add batches without duplicating sent tickets. Settle a frozen combined bill or use a live shared tab for individual contributions. | Two distinct settlement modes |
| Shared & split bills | Choose items or portions, divide equally, contribute a percentage or custom amount, or pay the remainder. Each guest reviews their share. | One platform fee per shared tab |
| Kitchen & bar boards | Accept and prepare tickets by station. Follow the oldest orders first, keep rejection/refund states clear and enable optional sound alerts. | Active screens refresh every 3 seconds |
| Runner workflow | See upcoming and ready orders, claim delivery, complete applicable age/service checks and mark delivered. | Readiness estimates need history |
| Call a server | Guests send table-linked service requests; staff acknowledge and resolve them alongside the ongoing service. | Valid table context required |
| Connected payments | Stripe-hosted Checkout, server-confirmed payment status, eligible Apple Pay, payment links and item/full refunds. | Eligible Stripe account + webhooks |
| Payment-link SMS | Send a checkout link with the guest's explicit consent. QR and copy-link remain available without SMS configuration. | Optional Twilio setup; delivery not guaranteed |
| Team & devices | Owner, manager, main, kitchen and runner access. Register real tablets and see connected, stale and offline states. | Not offline-first; connectivity required |
| Reports & reconciliation | Separate sales, taxes, tips, platform fees and refunds. Trace split-bill allocations, export transactions and review service completion history. | Processor settlements remain authoritative |
| Food, drinks & hookah | Organize menus and route tickets to the correct preparation station, including age-restricted items where lawful and approved. | Merchant licensing + processor approval |
| Tap to Pay & Terminal | Hardware and native phone acceptance are not implemented. Current payment collection uses hosted payment links. | Coming soon / not available |
Straight-up platform fees
The bill for the bill.
No guessing.
Current application fees in USD, paid by the restaurant. These are platform fees — not payment-processor fees or a full hosting/service quote.
$1.00
per checkout or combined frozen billOne order. Or one final tab.
- Ordinary guest checkout
- One fee for a combined frozen tab, not per round
- No YallaBill surcharge added to the guest's order
- Restaurant pays Stripe processing separately
$1.50
total per shared tabMore friends. Not more platform fees.
- One fee, not a fee per guest or new round
- Item shares, equal splits and custom amounts
- Each guest reviews and tips independently
- Stripe processing fees apply separately to payments
The $1.00 and $1.50 are alternative application-fee policies, not stacked fees. Restaurant-added service fees, if enabled and permitted, are separate and disclosed to guests. Hosting, AI and optional SMS costs are separate. Confirm commercial terms and processor eligibility before launch. Read the payment and refund details.
A few things, before you go
Good questions.
Straight answers.
Is this website the live POS?
Both live on the same deployment. These pages are YallaBill's sales, documentation and guided-tour site; the working application is behind Merchant sign-in and the public storefront links such as Ashik Lounge. The guided tour on the homepage is a simulation, but the Ashik Lounge menu is served by the real ordering system.
Do guests need an account or an app?
No guest app is required for table ordering or a shared bill. A phone camera opens the QR link in a browser. Staff still use authenticated role-based workspaces and authorized POS devices.
Does AI publish my menu automatically?
No. AI creates a draft for human review. Check prices, tax, modifiers and availability before publishing. Never rely on AI to infer allergens, ingredients or dietary suitability from names alone.
Can customers pay with Apple Pay?
Stripe-hosted Checkout may show Apple Pay for eligible devices, browsers, accounts and transactions. Card entry remains available. This is not a custom Apple Pay integration, Stripe Terminal or Tap to Pay on iPhone; those hardware options are not implemented.
Can guests pay their part while the tab stays open?
Yes, with a live shared tab. Staff can add rounds while guests settle reviewed contributions. A zero balance does not automatically release the table: staff explicitly closes the tab when service is finished.
Will it replace my inventory system or existing POS integration?
The application is a standalone restaurant ordering and service system. It does not depend on or currently integrate with Toast, SpotOn or an inventory platform. No stock-management or offline-payment capability is being promised.
Can I use it for alcohol or hookah?
Only where lawful, appropriately licensed and approved by your payment provider. Staff must complete applicable age and service checks. An approval setting records a merchant's approval reference; it does not grant approval. Wallet payments do not verify age.
Where is YallaBill going to live?
It lives at pos.ashik.ai: the marketing pages, the merchant workspace, staff boards and every restaurant storefront are served from that single HTTPS origin, hosted on Azure Container Apps with a managed PostgreSQL database.
Bring your kind of hospitality
Make service
your superpower.
Try the live Ashik Lounge menu on your phone, then follow the operator playbook from menu setup to a fully settled table.