Set up today.Done in 10 minutes.Here's how.

One workspace. Five roles. Every screen has a name.

Your merchant workspace lives at pos.ashik.ai. Sign in at Merchant sign-in with your e-mail address and a password of at least 12 characters. A session lasts 12 hours. The first page an owner sees is Get Started, an 11-step checklist saved per location that tells you what is ready and what is still blocking launch.

The workspace, left to right

• Get Started — your setup checklist (owner only).
• Overview — today's service at a glance.
• Orders — every ticket, every status, service requests and refunds.
• POS counter, Kitchen display, Bar display, Runner station, Customer board — the station screens you open on tablets and TVs.
• Menu studio and AI menu imports — build, import and publish the menu.
• Tables & QR — create tables and print their QR cards.
• Device status — which tablets are online, stale or offline.
• Sales reports — payments, tips, tax, refunds and CSV export.
• Team members — staff logins and POS PINs (owner only).
• Restaurant profile — name, address, time zone, tax default, ordering switch and payment settings.

Who can open what

Create each person in Team members with their own name, e-mail, role and starting password, and share it privately. Owners, managers and main staff can also be given a six-digit POS PIN there; that PIN is what unlocks the counter tablet. There is no default PIN and existing PINs can't be viewed, only reset.

Restaurant profile

Fill this in before anything else. Location name and Address appear on your guest storefront. Storefront slug is set when the location is created and becomes your permanent menu link, pos.ashik.ai/s/your-slug. Time zone decides when your business day rolls over (5:00 AM). Acceptance timeout (minutes) is how long a new ticket may sit unacknowledged before Orders flags it as waiting too long (default 10). Default tax rate for new items (%) is applied to items you add or import; it does not change items that already exist. Enable online ordering pauses guest ordering without touching your published menu. Owners also see the Stripe connected account and hookah approval fields covered under Connect payments.

Four ways in. One draft. You decide when it goes live.

Everything you do to a menu happens in a draft. Guests only ever see the published version. Nothing you import, generate or edit reaches a guest until you press Publish menu and confirm.

1. Build by hand. In Menu studio, add a category and choose its section: Food, Drinks or Hookah. Add items with a name, description, Customer price (USD) and Tax included (%). Prices are all-in: the number you type is the number the guest pays, and the tax portion is calculated from it at checkout.
2. Upload an existing menu. On the AI menu imports page, upload a PDF, PNG or JPEG (up to 10 MB), choose which section it belongs to, and let the extraction build a draft for you to review. Details in How we use AI.
3. Use JSON or an external AI. Get Started offers a Sample JSON, a JSON schema and an AI prompt you can paste into any assistant you already use to convert your menu into our format. Back in Menu studio, paste or upload the file and press Validate & load into editor. Download current JSON gives you a backup any time.
4. Chat with the menu assistant. Open Build your menu with AI in Menu studio and describe changes in plain English. You review a proposal before anything is saved.

What an item can carry

Tax, in one paragraph

Each item has its own Tax included (%). Set Default tax rate for new items in Restaurant profile so new and imported items start with the right rate, then use Apply default tax in Menu studio when you want every draft item to match it. The app shows Alexandria, VA as an example (11% on meals, 6% on hookah) but never picks a rate for you. When you've checked every published item, tick Tax configuration reviewed in Restaurant profile; that box records your review, it doesn't calculate anything.

Six places AI shows up. Zero places it acts alone.

YallaBill uses AI to take busywork off your plate: reading your old menu, writing descriptions, drawing a picture of a dish, and helping a guest pick something. It never publishes, never charges and never changes a price without you seeing it first. Here is every place it appears and exactly what it is allowed to do.

Getting good results

What AI is never allowed to do

• Publish a menu, change a live price, or move money.
• Set a price it didn't read on your document or in your request.
• Add allergen, dietary or health claims that weren't in your source. "Reduced-risk" or "safer" hookah language is rejected outright.
• Remove an age restriction from a hookah item, or set a negative tax.
• Delete or rename existing items, or edit their modifiers.
• Read anything about your guests: menus and prompts are the only things sent, and the consent checkbox asks you not to include customer or private information.

Your Stripe account. Your money. Our job is to stay out of it.

1. In Get Started, open Connect your Stripe account. Choose your business country and tick: "I authorize connecting this business to Stripe and will complete the hosted account setup. Identity and banking details go directly to Stripe."
2. Press Create and connect Stripe account (or Continue Stripe setup if you started before). Stripe's own pages collect your identity, business and bank details. We never see them.
3. Come back and press Recheck after returning from Stripe. You are ready when Stripe reports charges enabled, payouts enabled, details submitted and card payments active. Until then you'll see "Stripe is verifying submitted details. Return here after verification; a completed form is not proof payments are enabled."
4. Review payment readiness again after any change at Stripe. The connected account ID appears for the owner in Restaurant profile under Payments & restricted products.

What a guest pays, and what you pay

Refunds, plainly

• One line. On a paid ticket, staff press Reject & refund line. That line stops being prepared and its price and allocated tax go back to the guest's card. The tip and the platform fee stay. On an unpaid open-tab ticket the button reads Remove unpaid line and nothing is charged.
• The whole order. A full refund returns everything left on the order, tip included, and returns our platform fee for that order.
• Combined bills and shared bills. A combined tab bill refunds as a whole; refund individual items on the underlying tickets instead. Shared-bill contributions refund per contribution, with that guest's share of any service fee.
• Status. Refunds show pending, succeeded or failed. A failed refund gets a Retry refund button. Stripe keeps its original processing fee on refunded payments; plan for that.

Receipts come from Stripe to the e-mail the guest enters at checkout. The Sales reports page is a payments report, not a bank statement; use your Stripe dashboard for payout timing and settlement. Read how Stripe handles connected-account charges. ↗

Every table gets a code. Every code lands at the right seat.

1. Publish the menu from Menu studio. Your storefront at pos.ashik.ai/s/your-slug goes live the moment a published menu and Enable online ordering are both in place. Restaurants with a published menu and ordering switched on are also listed in the live storefront directory on this website.
2. Create tables. In Tables & QR press Add table and give it the name printed on the physical table: "Patio 4", "Bar 2", "Booth A". Each table gets a private code inside its link, so a scan tells the kitchen exactly where the order goes.
3. Print the cards. Each table has a QR card with Download (PNG), Copy link and a Print QR cards action that prints every active table at once. Scan one with your own phone; the storefront should greet you with "You're ordering to Patio 4".
4. Retire or reissue. Disable a table and its QR stops working immediately; guests who scan an old card see "This table QR is not valid. Ask your server for a current table code." Enable it again and it receives a brand-new code, so reprint the card.

Phone or counter. Same menu, same tickets.

From the guest's phone

1. Scan the table QR (or open the menu link and pick a table or Pickup). Browse by category, or search "dishes, drinks, flavors…".
2. Tap an item to open it: photo, description, required and optional choices, Special instructions ("Allergies or a special request? Please also let your server know."), quantity, and Add to order. Age-restricted items say so: "Staff must verify your ID and eligibility before service."
3. Open Your order, add a name, an e-mail for the Stripe receipt, and a tip. Press Continue to secure payment. Card details are entered on Stripe's page, never ours.
4. After payment the guest lands on a tracking page with their ticket code (a letter and two digits, like B07, with a color name) and live steps: Received, Accepted, Preparing, Ready, On its way, Delivered. They can also press Call service from here.

Prices, availability and modifiers are rechecked when the order is submitted. An order that isn't paid doesn't exist to your kitchen: tickets are released only after confirmed payment, never when a checkout page is merely opened.

From the counter tablet

1. Authorize the device once. An owner or manager signs in on the counter tablet, opens POS counter, names the kiosk and presses Authorize & sign out of management. That signs the manager out and turns the tablet into a kiosk for 30 days.
2. Unlock with a PIN. Staff pick their name and enter their six-digit POS PIN. The tablet locks itself after 5 minutes of inactivity and the staff session ends after 15 minutes; enter the PIN again and your draft is still there.
3. Build the order. Tap items, set quantity, choices and notes. Enter the Guest / tab name, choose Dine-in (pick an Active table) or Pickup.
4. Choose how it's handled. Pay now: "Guest pays by QR / link. Preparation waits for confirmed payment." Show the guest a QR, copy the link, or text it to them. Keep tab open · dine-in only: "Send this unpaid batch to kitchen / bar / hookah. Settle all batches later." See Open tabs.

Accept. Prepare. Ready. Claim. Deliver.

Every paid ticket moves through the same five steps, and every station only sees the part it owns. Timers run on every card, and a ticket that sits unacknowledged past your Acceptance timeout turns red with "waiting too long".

Fixing a ticket mid-service

Kitchen, bar and managers can remove a single line from any ticket that hasn't been delivered: Reject & refund line on a paid ticket, Remove unpaid line on an open-tab ticket. The rest of the ticket carries on. If every line is removed the ticket is marked Rejected. See refunds for what goes back to the card.

At the end of the night a manager presses End service & clear stack in the service panel. That archives the shift's closed tickets and average time under Archived services; it doesn't touch payments or reports.

Round after round. One bill at the end.

1. Open the tab. On the counter tablet enter the guest or tab name, choose Dine-in and an Active table, pick Keep tab open and send the first batch. The kitchen and bar get that ticket immediately, unpaid.
2. Add rounds. Reopen the tab from the tab list, add items to New batch only and send. Each batch is its own ticket with its own number; tickets already sent are read-only and are never re-sent.
3. Settle. Enter the Guest-approved tip (USD) and press Freeze bill & get payment link. A combined bill is created covering every saved batch. "Once checkout begins, amounts and items cannot change."
4. Hand over the link. Show the QR, Copy link, or Send payment-link SMS after ticking that the guest explicitly agreed to one transactional text. The guest pays on their phone at Stripe's page; the bill and every ticket beneath it flip to paid.

Let the table pay however the table wants.

Any open tab can become a live shared bill. Guests pay from their own phones while the tab stays open for more rounds; the app keeps the running balance so nobody double-pays and nothing is left behind.

1. Start it. On the tab, under Let guests split this bill, choose whether to add a Restaurant customer service fee (None, Fixed amount, or Percentage of the meal subtotal with or without tax, plus its own tax rate). Press Start live shared bill.
2. Share it. Press Share QR / link. Guests scan the QR or you Copy link or text it with their consent. Rotate link invalidates the old one if a phone leaves the table.
3. Guests choose. The phone asks "How would you like to help?" with Pay for my items, Pay an amount, Pay the rest, and under Other ways to split, Split equally and Pay a percentage. Each guest adds their own tip, which never reduces the meal balance.
4. Watch it close. The staff panel lists every contribution as pending, paid or released, and the live balance due. When the balance is zero and nothing is pending, press Close shared tab. Record cash or comps as adjustments if part of the table pays another way.

Your menu, on your own site, in five lines.

Your storefront is a normal web page, so it can sit inside your existing website. Use the launch kit on the home page to generate the snippet for your slug, or copy this and change your-restaurant:

<iframe
  src="https://pos.ashik.ai/s/your-restaurant"
  title="Our restaurant menu"
  width="100%"
  height="760"
  loading="lazy"
  referrerpolicy="strict-origin-when-cross-origin"
  style="border: 0; border-radius: 16px;"
></iframe>
<p><a href="https://pos.ashik.ai/s/your-restaurant" target="_blank" rel="noopener">Open menu &amp; order in a new tab</a></p>

• Use the plain menu link. Table codes (?t=…) are for printed QR cards only; the generator refuses them.
• Keep the "open in a new tab" link under the frame. Some browsers block payment pages inside frames, and guests on phones get a better experience full-screen.
• Payment still happens at Stripe, on Stripe's own page. Embedding changes nothing about who holds card data.
• Publishing a new menu updates the embed automatically. There's nothing to redeploy on your site.

Register every screen. Run one fake ticket. Then open the doors.

Registering a station tablet

1. On the tablet itself, sign in with the login that station will use (a kitchen-role login for the pass, a runner login for the runner).
2. Open the screen it will run: Kitchen display, Bar, Hookah, Runner station, Customer board or POS counter. The link remembers where you were headed if you have to sign in first.
3. Give the device a name you'd say out loud ("Kitchen pass 1", "Main bar TV", "Pickup TV"), choose the station for kitchen devices, and press Register this device.
4. Press Enable sound and keep the screen awake. Registered devices check in every few seconds; Device status shows each one as online, stale (no check-in for 12 seconds) or offline (30 seconds). Owners and managers can Revoke a lost tablet from the same page.

The Get Started checklist

Eleven steps, in order, with a live count of how many are ready: Here's your account · Connect your service stations · Give every table its QR code · Build your first selling menu · Make the menu look like you · Review your tax rates · Connect your Stripe account · Put the right people in place · Run your first practice service · Know where the money goes · Train your team, then start selling. Each step lists what's blocking it. When all eleven are ready, press Finish setup; the app rechecks your actual configuration before marking you complete, and you'll see "Your setup checklist is complete. Review payment readiness before accepting payments."

The practice service

Once your menu is published and every required station has a device online, press Send training order in Get Started. A ticket labelled TRAINING - NO CHARGE - DO NOT SERVE appears on your real boards with a sample value and "Amount charged: $0". Have the kitchen accept it, prepare it and mark it ready; have the runner claim it, tick the ID check and complete delivery. Get Started confirms "Practice delivery verified from the real ticket history". Training tickets are excluded from every report and stat. If you need to abandon one, press Void training ticket.

What the numbers mean, and who can see them.

Sales reports

Pick Current business day, Last closed business day, or any date range. Business days run from 5:00 AM to the following 5:00 AM in your location's time zone, so a 1:00 AM ticket belongs to the night before. The page shows Payments collected (including tax and tips), Refunds, Payments after refunds, Platform fees, plus tips and tax totals and a payments-by-day chart and table. Export CSV downloads the same figures. Training orders are excluded.

Service performance

The service panel in Orders tracks closed tickets and average open-to-delivered time for the current service, by day for the last 30 days, by the runner who completed delivery, and preparation time by station once there are at least three samples. End service & clear stack archives the shift so tomorrow starts clean.

Your data

Questions about your account, data or a specific payment? Contact Ashik and a person will answer.