Sold out in your POS.
Gone from Laayo.
The Laayo API for restaurant billing software. Store hours, sold out items and orders, kept in sync both ways.
Flip Chicken momo.
Everything a restaurant changes, from one screen.
Open, closed or busy
Store hours and busy time follow the POS. Busy adds prep time instead of turning customers away.
Sold out and back
Up to 500 items in one call, with an optional time it comes back.
Orders straight to the KOT
Laayo orders arrive with your own item IDs, add-ons and notes. No retyping.
Accepted, preparing, ready
The kitchen’s taps move the customer’s live tracking and tell the rider when to come in.
Menu changes, approved
New dishes and price changes go to the owner in the Laayo vendor app first.
Payouts per order
Each payout lists every order with its commission, so the books match without a spreadsheet.
Linking takes one code.
The owner taps Connect in Billing software, in the Laayo vendor app, and reads you a 6 digit code. You type it into your settings screen. That's the whole setup, and the owner can unlink at any time.
You never see a store that didn't give you its code.
Three calls cover most of it.
Orders come to you as webhooks. Desktop POS with no public address can poll for events instead.
PUT /v1/stores/27/status
{ "state": "busy", "extra_prep_minutes": 15 }
200
{ "data": { "state": "busy", "customers_see": "35-50 min" } }Built so nothing breaks at dinner time.
Signed requests
Every call carries an HMAC signature and a timestamp. Replays are refused.
Retries for 24 hours
If your server is down, webhooks wait and try again. Nothing is dropped.
Quiet POS, open store
If we stop hearing from you for 10 minutes, the store stays open and the owner is told.
The owner can take over
When your POS is down, the owner can switch to Laayo’s own toggles for an hour.
Customer data kept small
You get what the kitchen needs. Customer phone numbers are masked.
Every change logged
Who changed what, from which key, and when. You and the restaurant can both see it.
Your console.
Every linked restaurant, every webhook and every request, in one quiet list.
From sandbox to live.
- 1Get test keys
A test restaurant is ready in a minute.
- 2Build
A settings screen and one webhook handler.
- 3Pass the checklist
Six checks run against your sandbox.
- 4Pilot one restaurant
We watch the first week with you.
- 5Live for everyone
Listed in the vendor app as ready to connect.
Questions from POS teams
What does it cost?
Nothing. Laayo covers the integration because restaurants on it handle orders faster.
How long does it take?
Most of the work is one settings screen and one webhook handler. The sandbox checklist tells you when you’re done.
Our POS runs on Windows with no public address.
That's fine. Send calls from any machine with internet, and poll GET /v1/events for new orders instead of taking webhooks.
Who can see the restaurant’s data?
Only the POS the owner linked, and only that store. Customer phone numbers are masked.
Can we change prices from the POS?
You can send them. The owner approves price and name changes in the Laayo vendor app before customers see them.
What if our server goes down?
Webhooks retry for 24 hours. The store stays open on Laayo, the owner is told, and they can use Laayo’s toggles until you’re back.