A direct-order page that keeps the whole price of the dish

Independent restaurants and cafes that already have demand: a busy LINE chat, regulars who order the same thing, a queue at lunch. Built for the shop that wants the apps to be one channel, not the landlord of the business. Commission rates have historically run far above what survives a food margin, and the current discounted rates are scheme rates, not the structural norm.

The build gives the shop one thing the platforms never will: a sales channel it owns end to end.

• A bilingual menu site with a real URL per dish, structured so search and answer engines can quote it
• Order flow with PromptPay QR at checkout; the order only enters the kitchen once payment clears
• Pickup and delivery-radius rules the owner sets, so the shop never promises what it cannot deliver
• A kitchen queue screen: new orders slide in, one tap moves them from cooking to ready
• Order status pushed to the customer's LINE: received, cooking, ready to collect
• A customer list with consent, owned by the shop, for repeat-order broadcasts

• The full codebase in the restaurant's own repository
• Hosting, domain, LINE OA, and PromptPay wiring set up in the shop's name
• A plain-language runbook: change a price, mark a dish sold out, pause delivery on a flooded soi
• A recorded handover call the owner can rewatch instead of re-asking

1. Map

   A short first week

   I sit at the counter for one service and trace a real order through the apps, the chat, and the kitchen, to find where margin and customers leak.

   A one-page scope: the order flow, the payment rule, and what we deliberately leave to the apps.

2. Shape

   Inside the same fortnight

   I design the menu and checkout around a hungry customer on a phone, and the queue screen around a cook with wet hands.

   Clickable screens the owner approves before any backend is built.

3. Make

   The build weeks

   I build the menu, the payment, and the kitchen queue as one tested path: paid order in, ticket out, status to LINE.

   A working order placed with a real PromptPay charge, showing up on a real kitchen screen.

4. Prove

   A focused week

   We run one real service day through the system in parallel with the old way and watch where staff or customers hesitate.

   A short list of fixes from real service, all closed before launch.

5. Hand-off

   The final days

   I move every account into the shop's name and walk the owner through prices, sold-out days, and the daily summary.

   The keys: code, hosting, accounts, and a runbook in plain Thai and English.

• Quoted per project after a short scope call. You see the full number before any money moves.
• Payment is phased against the build: a deposit to start, a milestone at a working paid order, the balance at hand-off.
• Fixed scope, fixed price, and no percentage of any order, ever. That is the point.

• The shop has, or will open, a PromptPay-capable account and a LINE OA in its own name.
• The menu is reasonably stable; daily specials fit, a full rebuild of the menu every week does not.
• One owner-approver for decisions during the build.

• No rider fleet and no logistics; the shop delivers with its own people or keeps the apps for far orders.
• No POS replacement; this is the direct channel, not the cash drawer.
• No loyalty points engine in the first scope; the customer list comes first, mechanics can come later.

The kitchen screen is the product, not the website

A pretty menu site that prints orders into the old chat changes nothing. The decision that matters is making the paid order itself the source of truth: it enters the kitchen queue the moment money clears, and every status the customer sees comes from that queue. The shop stops transcribing orders, and the apps become optional instead of structural.

• Every dish gets a real, fast page with menu structured data, so 'best khao soi near me' can land on the shop's own ordering page, not a platform listing.
• Bilingual page structure so Thai and English searches both find the menu, and answer engines can quote it with the shop's name attached.

The result

Built so that every direct order keeps its full price, every regular becomes a name the shop can reach again, and the apps go back to being one channel among several. The margin that used to leave with the commission stays in the till.

What it proves

That an ordering channel earns its keep when it changes who owns the customer, not when it adds another screen. Own the order, own the name, and the platform fee becomes a choice.