Hawker stalls · Cafés · Small restaurants

Customer scan.
Customer order.
You cook.

OrderLah gives small F&B merchants a simpler way to handle QR ordering, web orders and the day-to-day running of the stall — without turning it into an IT project.

Try OrderLah See how it works ↓

No app download for customers. No PhD required for merchants.

One order, end to end

Follow the chit.

This is the whole product. An order leaves a customer's phone, lands on your tablet, and moves through the kitchen until someone eats it. Everything else on this page is a detail of these six steps.

#0088 T08
1 × Chicken Rice + Extra Chicken + No Cucumber 1 × Kopi C
NEW $6.00
  1. 01

    Scan

    A QR code on the table, or one at the counter. The camera app opens it. That is the entire customer onboarding.

  2. 02

    Order

    Your menu opens in their browser. Items, variants, add-ons, quantity, dine-in or takeaway. They tap send.

  3. 03

    Ding

    The hub rings — properly rings, not a polite buzz — and the order is on the board before the customer puts the phone down.

  4. 04

    Cook

    One tap moves it to Cooking. Every device watching the board sees the same thing at the same time.

  5. 05

    Ready

    Ready to collect. The number goes up on the display, the counter calls it, nobody hunts for a scribbled chit.

  6. 06

    Makan

    Served, settled, filed. It stays in your order history, on your tablet, whether or not the internet was ever involved.

Lunch, 12:40pm

Ordering shouldn't look like this.

  • CustomerBoss! One chicken rice!
  • YouWait ah!
  • Another customerMine takeaway!
  • KitchenWhich table?!
  • PhoneRING RING RING

Three conversations, one pair of hands, and the wok still on.

Or…

  1. SCAN
  2. ORDER
  3. DING
  4. COOK

Better lah.

You keep both hands on the food. The ordering runs itself.

How it works

Five steps. That's the whole setup.

No integration project, no cabling, no consultant. If you can print a piece of paper and charge a tablet, you can run this.

  1. Step 1

    Put up your QR

    One at the counter, one on every table, or both. OrderLah generates them for you — table numbers included, so the kitchen knows where the food goes.

    Makan Corner

    QR code linking to orderlah.app

    Scan to order 📷

    TABLE T08

  2. Step 2

    Customer scans

    The phone camera does it. The menu opens in the browser they already have. Nothing to install, no account to create, no password anybody will forget.

    QR code linking to the OrderLah interactive demo

    orderlah.app · opening menu…

  3. Step 3

    Customer orders

    Items, variants, add-ons, quantity — and dine-in or takeaway when you've turned those on. Extra chicken, no cucumber, less spicy: it all comes through in writing, so nobody mishears it.

    Chicken Rice $4.50
    Roasted Steamed

    Add-ons

    Extra Chicken+$2.00 Egg+$0.80 Extra Rice+$0.50
    Add to order$6.50
  4. Step 4

    You hear "DING!"

    The hub plays the new-order ringtone and the chit appears on the board. It is designed to be hard to miss across a hot, noisy kitchen — because a missed order is a refund and an argument.

    NEW ORDER · #0088 · T08

  5. Step 5

    Cooking → Ready → Done

    One tap per stage. The board is the single source of truth for the counter, the kitchen and the display screen at the same moment — no shouting the same order twice.

    New 1

    #0088 T08

    Cooking 1

    #0087 Takeaway

    Ready 1

    #0086 T03

Try it right here

Don't just read about it. Order something.

This is a working copy of both halves — the customer's phone on the left, your hub on the right. Nothing is sent anywhere, no real order is created, and you can restart it as many times as you like.

1 Customer's phone

Makan Corner DINE-IN · T08
Chicken Rice $4.50

Choose one

Add-ons

Kopi $1.50

Choose one

  • Nothing in the order yet.

2 Your hub

OrderLah Hub · Kitchen Board WAITING FOR ORDERS

Nothing cooking. Add something on the left and place the order. 👈

Demo only — it runs entirely in your browser and creates no real order.

The customer side

Another app?

No thanks.

Your customer is hungry, standing up, and holding a phone with 3% battery. They are not downloading anything. They scan the QR code and your menu opens in the browser that is already on the phone.

To be straight about it: OrderLah does have an app — the one you run the stall on, on your own tablet. It's the ordering side that needs nothing installed.

  • App Store
  • Play Store
  • Create account
  • Forgot password
  • Update app
  • Scan
  • Order
  • Eat

Offline-first, honestly explained

Wi-Fi having a bad day?

Your stall shouldn't.

Most ordering systems are a website with your menu on it: the shop is a thin client, and when the line drops, so does lunch. OrderLah is built the other way round — your tablet is the server. It holds the menu, mints the order numbers and stores every order on the device itself.

Everything working
  • Customer, anywhere
  • Internet (optional)
  • Your hub tablet

Ordering from outside the shop is an extra you switch on. The hub dials out to a relay itself — no VPN, no router settings, nothing for you to keep alive.

Internet down
  • Internet — gone
  • Your hub tablet
  • Counter, kitchen & customer phones on the shop's own Wi-Fi

The QR at the table still opens the menu, the counter still sends orders, the kitchen board still moves, and the takings are still recorded. Only ordering from outside the shop waits for the line to come back.

Because "sorry, system down" shouldn't be part of the menu.

Merchant controls

Your stall. Your rules.

The things you actually need mid-service are one tap away, not four menus deep. Try them — these are live.

Chicken finished?

Mark it sold out and it stops being orderable everywhere at once — counter, table QR, every device. Put it back the same way.

Crispy Chicken Wings $5.00

Kitchen drowning?

Pause ordering, catch up, switch it back on. Customers see a clear message instead of sending orders you can't cook.

Accepting orders

Even wok hei needs a break.

Service modes

Turn dine-in, takeaway and delivery on or off as you like. Only serving takeaway after 8pm? Switch the rest off.

🍽️ Dine-in 🥡 Takeaway 🛵 Delivery

Off means off. No surprise orders.

Tables

Number your tables, print a QR for each, and every order arrives knowing where it's going. Free-text table names work too, if your "tables" are really "the two stools by the fan".

One QR per table. The kitchen never asks "which table?" again.

The kitchen board

The screen your kitchen actually looks at.

Big numbers, big lanes, readable from the wok. Every card carries how long it has been waiting — and turns red when it has been waiting too long, before the customer has to come and ask.

HUB RUNNING · 3 DEVICES

New 1

  • #0088 T08 00:42

    Chicken Rice ×2+ Extra Chicken
    Kopi C ×1

Cooking 1

  • #0087 Takeaway 03:18

    Mee Goreng ×1+ Extra spicy

Ready 1

  • #0086 T03 05:01

    Laksa ×2

The sound only plays when you press the button — browsers don't allow audio before that, and neither would we.

Reality check

Built for actual stalls.

Not designed in a meeting room.

18 orders land at once
Can. They queue on the board in order, each with its own number and timer. Nothing overwrites anything.
Wi-Fi drops out mid-lunch
Still running. The hub is on your counter, not in a data centre. Devices on the shop's own network carry on.
Chicken sold out
One tap. Off the menu everywhere, instantly. Back on just as fast when the next batch is ready.
Uncle pressed the wrong thing
Back. Big buttons, an obvious way out of every screen, and nothing important happens without a confirm.
"Need to download app or not?"
Nope. Say that once and the customer is already ordering.
Tablet screen keeps sleeping
Handled. The hub keeps the screen awake and asks to stay plugged in, so it is never quietly asleep during a rush.

The setup

One device runs the show.

Pick your best tablet and make it the hub. It keeps the menu, the orders and the takings. Everything else — the counter phone, the kitchen screen, the TV on the wall — joins it by scanning a QR code.

Customer scans your QR Their own phone, no app
OrderLah Hub Your tablet · the menu, the orders, the data
  • Counter Take orders, take payment
  • Kitchen display The board, at the pass
  • Customer display Now ready: #0086
  • Owner's phone Check in without standing there

They all talk over your own network — the shop's Wi-Fi router, or the hub tablet's hotspot if there isn't one. That is why a broken internet line doesn't stop service.

Pairing is a QR scan. The hub shows a code, the new device reads it, done. No IP addresses to type, no router settings to change.

Printers, if you want them. Pair a kitchen printer and test it from the hub. Plenty of stalls run on the screen alone.

Real screens

This is the actual app.

Not a concept, not a redraw — these are screenshots taken from OrderLah running. Swipe or scroll through them.

← scroll for more →

What's in it

Everything a small stall needs. Nothing it doesn't.

No modules to buy, no enterprise tier holding the useful parts hostage. This is the list — if something isn't on it, OrderLah doesn't claim it.

Taking orders

QR ordering
Counter code, table codes, or both. Customers order themselves.
Browser ordering
Nothing for the customer to install, sign up for, or update.
Counter ordering
Your staff take orders on a phone or tablet, same order book.
Variants & add-ons
Extra egg? No chilli? Kopi C instead of Kopi? Handled, in writing.
Dine-in · Takeaway · Delivery
Turn each one on or off whenever you like.
Tables
Numbered tables or your own names, printed as their own QR codes.

Running service

Order queue
New → Cooking → Ready → Done, with a timer on every card.
Audio alert
The hub rings on a new order, because nobody refreshes a screen every seven seconds.
Sold out
One switch takes an item off every device at once.
Pause ordering
Stop new orders while you catch up. Turn it back on when ready.
Kitchen & customer displays
A screen at the pass, a screen on the wall calling numbers.
Printers
Pair and test a kitchen printer — optional, plenty run screen-only.
Payment recording
Cash, PayNow, card terminal, comps, partial payments and refunds, kept as an auditable history. Show your own payment QR on screen.
Reports
Sales, order history and completed orders you can look back through.

Keeping it yours

Offline-first hub
Your tablet is the server. Service doesn't wait for the internet.
Encrypted on the device
The local order store is encrypted at rest with a per-install key.
Backup & restore
Daily automatic backups, checksum-verified, restorable when a tablet dies.
Staff PIN & permissions
Everyone signs in as themselves; you decide who can do what.
Multiple devices
Counter, kitchen, display and owner devices pair to the hub by scanning a code.
Five languages
English, 中文, Bahasa Melayu, မြန်မာ and Tiếng Việt — switchable in settings, because your kitchen is not monolingual.
Ordering from outside
Optional. Switch it on and the hub dials out itself — no VPN, no router setup. Off by default.
Your choice of hosting
Run everything on the tablet, on your own server, or on OrderLah Cloud. The tablet setup is what most stalls use.

Pricing

Simple pricing. Coming soon.

OrderLah is being prepared for a first group of merchants, so there is no price list to show you yet — and we would rather say that than invent one. What we can do now is set it up with you and get your feedback into the product while it still changes easily.

  • We look at how your stall actually runs before touching anything.
  • You get the setup that fits — QR only, counter only, or the lot.
  • What you tell us changes the app. That's the point of a pilot.

Tell us about your stall and we'll show you the relevant setup. One conversation, at a time that isn't your lunch rush.

Join the pilot

Takes about a minute. Fields marked are required.

What are you interested in?

We use what you send here to contact you about the pilot, and nothing else. Privacy.

Straight answers

Questions people actually ask.

Does my customer need to install OrderLah?

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.

Do I need Wi-Fi?

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 things like cloud backups and updates.

What happens if my internet goes down?

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 kitchen board and customer phones on your own Wi-Fi keep working exactly as before.

What stops is ordering from outside the shop, which needs the line. It picks up again when the internet does.

Can I use more than one device?

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

Can I mark food sold out, or pause ordering?

Both, and both take one tap. Sold out removes an item from every device at once. Pause stops new customer orders while you catch up, and tells the customer clearly instead of leaving them wondering.

Can customers order from the table?

Yes. OrderLah generates a QR code per table alongside a general one for the counter or a poster. An order from a table QR arrives with the table on it, so the food gets to the right place.

Can I use it for takeaway only?

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

Can I set up my own menu?

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.

Where is my data stored?

In the usual hawker setup: on your hub tablet, in a local database that is encrypted at rest. Orders, menu, staff and takings live there. No order reaches OrderLah — not summarised, not counted, not anonymised.

If you'd rather have a server, two other arrangements exist: run your own, or use OrderLah Cloud. The difference between them is written out field by field in the project's data-ownership document ↗, not buried in a licence.

Does OrderLah process payments?

No, and it's important to be clear about that. OrderLah records how a bill was settled — cash, PayNow, card terminal, comp, partial payment, 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.

What does it run on?

An Android tablet as the hub — 8 to 11 inches is the sweet spot, and the screens are laid out for exactly that. Counter and owner devices can be Android or iOS phones and tablets. Customers just need a phone with a browser.

How much is it?

Not settled yet, so there's nothing honest to quote. OrderLah is at the pilot stage — tell us about your stall and we'll talk about it properly rather than putting a made-up number on a website.

Enough talking.

Want to see how this would work in your stall? Have a play with the demo first — it costs you two minutes and no phone call.

Try the Demo Join the Pilot

Tell us about your stall and we'll show you the relevant setup. That's the whole process.

QR code linking to orderlah.app

orderlah.app

Less software.
More makan.