That ordering page
can be yours.

No. They scan the QR code and your menu opens in their phone's browser. No app store, no account, no password. The OrderLah app is the one you run the stall on.

You need a local network, because that is how phones and counter devices reach your hub. Either the shop's Wi-Fi router, or the hub tablet's own hotspot if there's no router.

You do not need a working internet line for that. The internet is only involved if you want customers ordering from outside the shop, or for reading a report from elsewhere and for updates.

Service carries on. The hub tablet is the server: it holds the menu, mints the order numbers and saves every order locally. Counter devices, the Order Board and customer phones on your own Wi-Fi keep working exactly as before.

What waits for the line: ordering from outside the shop, a card or wallet payment that has to reach a provider, and cloud reading a report from the back office. A customer standing in your shop on mobile data has to join your Wi-Fi or order at the counter. All of it picks up again when the internet does.

It depends which code is on the table and whether your line is up. The printed table code points at your own tablet, on your own network — which is what keeps ordering working on the day the internet drops. A phone on mobile data is not on that network yet, so joining the Wi-Fi and scanning again is the whole fix.

If you take orders from outside the shop, there is a second code for that public address and it goes over the internet — so it opens on mobile data, from the queue outside or from the car park. The table code carries that address with it too, so when the page finds it cannot reach your kitchen it offers the move instead of leaving somebody stuck.

With your internet down, the shop's own Wi-Fi is the only route a phone has. And the counter is the route that asks nothing of their phone at all. Browsers and devices has the long version.

Because that is honestly what is happening, and some browsers check before they allow it. Your tablet is a device on the shop's own network, and a table code asks the phone to talk to it directly rather than going out to the internet and back. A browser that wants to be sure shows a short prompt about reaching something on this network.

Tapping Allow is what loads the menu. Nothing is installed, nothing is granted beyond that one page, and no order leaves the building at that moment — it is a phone talking to a tablet a few metres away. Arriving from the printed table code, the usual case is no prompt at all.

Then that phone doesn't reach your tablet directly, and the other routes are still there. If you take orders from outside the shop, the online code goes over the internet instead and asks for no permission of that kind. Otherwise staff ring the order in at the counter.

Nothing is lost either way. A counter order and a scanned one are the same thing downstream — same order book, same numbers, same kitchen queue — and a customer who never got as far as the menu has nothing on the phone to lose.

Yes. One tablet is the hub. Other devices join it by scanning a code and take a role: counter, waiter's phone, kitchen display, customer (TV) display, self-order, or an owner's device for checking in.

The device picks its own role when it joins, so you don't have to decide in advance which code is for which tablet — hand out one code, set up whatever's in front of you.

Both, and both take one tap. Sold out removes an item from every device at once. Pause stops new orders straight away — on the ordering page and at the counter, so the till stops ringing them up too — and tells the customer clearly instead of leaving them wondering.

Yes. OrderLah generates a QR code per table alongside a Walk-in QR for counter, takeaway and walk-in orders. An order from a table QR arrives with the table on it, so the food gets to the right place.

Yes, and that's the normal case — one sticker on the table, four people scanning it. The code names the table and nothing else: no person, no phone, no basket. So it never has to be handed round, covered up between parties, or reprinted.

A bill follows the party rather than the square, too. If the table turns over during a service, the two parties' bills are kept apart and collected one at a time rather than added together — and the floor plan says out loud when a table is carrying more than one.

Yes. Every phone — in fact every browser tab — starts its own session when the code is scanned, and the basket belongs to that session. Two people at one table build two baskets and place two orders, and neither can see or change the other's.

Two details that only show up on a real table. A basket left behind by a tab somebody closed is moved to their next scan rather than copied, so nobody ends up holding two of the same order. And sending the same basket twice — after a dropped connection, say — is recognised as the same order, so a retry doesn't put two of anything in your kitchen. 🙂

Yes. Dine-in, takeaway and delivery are three switches. Turn off what you don't do, and customers only ever see the rest.

It's yours to edit. Categories, items, prices, photos, variants (roasted or steamed) and add-on groups (extra egg, no chilli). Change it at 6am without asking anybody's permission.

Taking, cropping and rotating a photo normally stays on the Hub. If you deliberately use Snap Existing Menu, the selected menu pages are sent to an AI service to read them. If you choose a look and tap Create in AI Photo Studio, the selected dish (and any stall reference photos you choose) are sent to an AI image service. The screen explains this before sending; ordinary photo editing does not use either service.

Yes — they land on the same board as everything else, so the kitchen works off one queue instead of one screen per platform. Point the tablet at the platform's order slip and it reads the items off it; anything it gets wrong you fix before it goes to the kitchen, and you can always key one in by hand.

OrderLah is not plugged into those platforms and doesn't speak to them. Reading a slip you already have is not the same as an integration, and we won't call it one.

Yes. Set your tax rate and registration number, add a service charge if you take one, and choose whether the payable total rounds to the nearest 5 cents. Receipts can be printed, shared, or scanned off the screen by the customer.

At the end of the day there's a closing screen: what came in since the last close, split by cash, PayNow, card and the rest. Snapshot it and the next day starts from zero.

In the usual Hub setup, the order book, menu, staff and takings are stored in an encrypted local database on your Hub. Local orders do not need to leave the shop. If you enable public ordering, relay traffic passes temporarily through OrderLah to reach the Hub; the relay is not another copy of your order book. Report summaries you request in the merchant portal also pass through OrderLah.

Account, licence and security records are stored by OrderLah, and online-payment records are retained when you use an integrated provider. An outlet deliberately using OrderLah-hosted operation stores its order book with OrderLah instead. With self-hosting, the order book stays in the database you operate. The privacy policy gives the full data-by-data explanation.

An update replaces the software, not your shop. Your menu, your settings, your staff and their permissions, your order book, the devices you've paired and your licence all carry across. That is the rule the whole update path is built around rather than a habit: your records are on your tablet, so an update that behaved like a fresh install would be the end of them.

Before an update, OrderLah takes a recovery point — an ordinary backup of what is there, checked before it's called a protection, and listed as Before update in the same restore list you already use. It's kept apart from your daily backups so it can't overwrite one, and restoring it is your decision: nothing rolls your shop back on its own while you're open.

No, and it's important to be clear about that. OrderLah records how a bill was settled — cash, PayNow, card terminal, refund — as a history you can audit later, and it can show your own PayNow, DuitNow or Touch 'n Go QR on screen for the customer to scan.

The money itself moves through the arrangements you already have with your bank or wallet provider. OrderLah never sits in the middle, and takes no cut.

Orders are unaffected. Nothing in the order path calls a payment provider, so customers scan and order exactly as before and the kitchen carries on.

Cash is unaffected too, and a wallet QR image you uploaded yourself still shows on screen — nothing has to be reached to put a picture up. What can't happen is a payment the provider has to start: the customer is asked to try again rather than told it failed.

The part worth knowing is what gets written down. A call that times out is recorded as unestablished, never as failed, because the provider may have acted before the answer was lost — so the bill stays settleable and a confirmation that turns up late still lands. An order's status and how the bill was settled are kept apart, and whether an unpaid or pending order reaches the kitchen at all is your setting, not ours.

An Android tablet as the hub, running Android 7.0 or newer. The counter grid is solved from the width it is actually given, so a bigger screen is more dishes at the same comfortable size rather than a supported-device list to check yourself against. Customers just need a phone with a browser.

No, and there's no OrderLah box to buy. We don't sell tablets, printers or terminals, and there is no OrderLah terminal you need in order to make any of this work.

What you need is one Android tablet to be the hub, and whatever else you already have can join it over the shop's own network — a counter tablet, a kitchen screen, a waiter's phone, a screen on the wall. A thermal printer if you print tickets, bought from whoever you like. One licence covers the outlet rather than the tablet, so the devices paired to your own hub are unlimited.

Create your account on the web, put OrderLah on an Android tablet, and activate — the five steps are here. Nobody has to approve you and there is no waiting list. The one thing worth knowing before you press anything: your 14 days start when you activate on the tablet, not when you sign up, so a tablet that turns up next week costs you none of them.

One licence per outlet. Choose a term plan or Permanent Offline; the pricing page shows it live in your own currency — read from the same price list checkout charges from, so it cannot go stale. Before that, every new outlet gets 14 days of the whole product with no card, and nothing to cancel at the end of it.

Every new outlet gets 14 days of the whole product — the counter, the Order Board, QR ordering, the closing report, the lot. No card, nothing to cancel, and nobody between you and it.

The clock starts when you activate on your tablet, not when you sign up, so creating the account and getting a tablet don't have to happen on the same day. 🎉 The tablet tells you the fourteen days have started, and the days left sit on your home screen and on the licence screen after that. The five steps to get there are here.

If you do nothing, it simply stops being a trial. We don't charge you for having tried it, there's nothing to cancel, and no card was ever taken to charge.

To carry on you buy a licence for the outlet — one licence, one shop, every device paired to your own hub. The pricing page shows the figure live in your own currency, read from the same price list checkout charges from.

Either way your shop stays where it always was. The menu, the settings and the order book are on your own tablet, and nothing there is deleted because a trial ended.