Case study10 min readUpdated 7 Aug 2026

A Bangkok mid-to-high-end restaurant goes digital, part 1: it lacks ordering, kitchen, and customer systems — so why can't it just buy them all at once

This Bangkok mid-to-high-end restaurant genuinely lacks everything: orders by hand, kitchen by shouted call-outs, customers by memory. But the systems on the market are either too complex, too expensive once subscriptions add up over years, or sold without any design for digitalization and marketing. Digitalization is the end goal — but it has to be built in steps.

This series follows a Bangkok mid-to-high-end restaurant, step by step, into digital. The story comes from our real implementation experience in food and beverage — if you run a place that cares about experience and is sensitive to looking cheap, you should see your own kitchen in every chapter. Each chapter explains: what was built, what was deliberately not built, and what evidence earned the right to move on.

The restaurant lacks everything

This is a mid-to-high-end restaurant in Bangkok, about forty seats, focused on refined Thai cuisine and café food. The average ticket is not low; the customers are local middle class, business entertaining, and some tourists. The owner knows exactly what his place looks like today:

  • Orders by hand. Servers jot the dishes on paper. Wrong items, missed items, illegible handwriting — that’s daily life.
  • Kitchen by call-outs and clipped paper. Orders reach the kitchen by shouting or clipping a paper slip at the pass. Whether the kitchen got the order, and which table goes first, is entirely the chef’s call.
  • Customers by memory. Repeat customers are recognized by face; the conversation is carried by memory. The dish a guest loves, the table they sat at last time, whether they have kids — it all lives in servers’ heads, and it disappears when staff change.

The paper menu also ages, gets dirty, and costs reprints or hand-scratch-outs to change prices — for a mid-to-high-end restaurant that lives on experience and positioning, that hurts even more than it would for a street-side shop.

But the off-the-shelf systems can’t be bought either

The owner isn’t someone who never looked at the ordering, kitchen, or membership systems on the market. After looking, he reached three conclusions — and each one makes “just buy a suite” fall apart:

  • Too complex. Full systems are designed for large chains and multi-branch operations: multi-store inventory, head-office reports, cross-branch permissions. He has one restaurant; eighty percent of the features are unused, yet he still has to learn, configure, and maintain them.
  • Subscriptions don’t add up over years. The monthly fee looks cheap, but multiply by three or five years and it covers a part-time employee or a full menu and photography refresh. Restaurant profit is earned table by table; money spent on a standing subscription must be thought through.
  • They sell software, not a build-out. The vendor hands over the software and that’s the end of it. Nobody tells him what to do first, how to verify each step, how to get the chef and servers to actually use it, or how to pair it with marketing to bring guests in.

The owner’s conclusion: digitalization is the end goal, but it has to be built in steps. Not because he doesn’t need these capabilities now — he badly does — but because the buy-it-all-at-once path is expensive, doesn’t fit his workflow, and nobody has designed how to make it land.

Building in steps is not a downgraded goal

Building in steps does not mean:

  • believing the restaurant doesn’t need full capabilities today;
  • splitting systems apart for the sake of selling more;
  • keeping inefficient manual work forever;
  • replacing ordering and kitchen systems with a website.

It means:

  • keeping the full direction, but building one step that can land and be verified;
  • changing a limited scope at a time, so the chef and servers can absorb it;
  • using real operations to test which step truly has value and which is just “it feels like it should”;
  • letting each phase’s data and experience become the input of the next phase.

The route this series walks has an order that comes from one simple judgment: put the menu online first (the foundation of everything), then market to draw guests in (make people willing to come), then do website ordering to the kitchen (make orders lighter), then build customer profiles and membership (make guests feel remembered and willing to return). Every step has to stand up to market verification and scrutiny.

The first step: start with menu digitalization

Before approving any next step, the owner agreed to watch one thing first: get the menu right.

The menu is the foundation of all digitalization — without a trustworthy, unified, maintainable online menu, everything after it (website ordering, kitchen orders, online display) is built on air. Part 2 is about why menu digitalization is the first step, and how it solves the paper-menu problems of aging, dirtying, and reprinting on price changes.


Boundary matters: menu digitalization and online information display, Google Maps listing, website building, and basic forms belong to a normal website project. The website-ordering-to-kitchen, customer-profile, membership-stored-value, and social-media-operations systems in this series are separate projects with their own scope — they are not part of a standard website package.