TOMASAKI: an online ordering system for a restaurant with delivery

The client and the task

TOMASAKI runs as one kitchen with two brands: sushi and poke on one side, sweet and savoury bubble waffles on the other.

Before the system, orders went through a delivery platform. Customers already knew the place and trusted it, but every order carried the middleman's commission, and the customer could not see where their food was.

The goal, as written in the brief: customers order directly from TOMASAKI and trust the process enough to come back. With real photos, real prices, a live order status and an honest delivery time.

• Two menus, one order The customer orders sushi and waffles together, with one cart and one delivery.
• The kitchen sees the order at once Without anyone retyping it from one place to another.
• The team runs it on its own The menu, prices, promotions and opening hours change without a developer.

What the online ordering system for a restaurant includes

We built a working web application, not a brochure. It has three faces: a site for customers, a board for the kitchen and an admin panel for the owners.

• A site with two menus More than 160 items with real photos of the dishes, in Bulgarian and English. Bulgarian is the default language.
• One cart and choices on dishes Sushi and waffles go into one order. Where a dish needs a choice, such as which sushi comes in the bento set, the site asks instead of guessing.
• Delivery or pick-up The customer chooses when ordering. For pick-up no address is asked for and there is no delivery fee.
• Payment Cash or card on delivery, and since October 2026 also card online via myPOS. The card is entered on the myPOS page, not on the site.
• Live status After ordering, the customer follows on their own page whether the order has been accepted, when it has left and when it has been delivered, without reloading.
• Notifications on the phone If the customer allows them, they get a notification when the order is accepted, when it leaves and when the driver is at the door.

How it works day to day

Here is the path of one order, from the tap on the button to the customer's door.

• In the kitchen A new order appears live on the board, with a sound. The team accepts it and chooses how many minutes it will take. The customer sees that time too.
• The ticket On acceptance, the ticket printer in the kitchen prints a ticket in Bulgarian. It serves both the cook and the driver: it has the dishes, the chosen options, the address and the phone number. If a ticket fails to print, the board shows it and offers to print it again.
• Countdown Every order being cooked carries a clock with the minutes left. As time runs out it changes colour, and when an order is late it shows by how much.
• Declining If an order cannot be fulfilled, the team declines it before accepting it, and the customer sees that they should call. With online payment, declining refunds the money to the card.
• Online payment An order paid online reaches the kitchen only after myPOS confirms the payment. The board and the ticket say it is paid, so the driver does not collect the money a second time.
• Buttons for a difficult night With one tap the team pauses delivery and keeps pick-up only, turns off card payment or closes ordering. The site opens and closes by itself according to the opening hours.
• The mobile app The restaurant also has its own mobile app, built by another developer. We are connecting it to the system: its orders will land on the same board and ticket printer, and the status will flow back to the app. The link is built and being tested.

The admin panel: the owners run it themselves

Everything that changes often is in the team's hands. No emails to a developer and no waiting.

• Menu and photos Adding and removing dishes, changing prices and photos, marking a dish as sold out.
• Promotions Discounts and bundle offers such as "take three, pay for two". The price is worked out on the server, so the menu, the cart and the ticket always show the same total.
• Allergens A table with one dish per row and one allergen per column, one tap per answer. Allergens are declared for every dish, and a new dish stays flagged until someone answers for it.
• Opening hours and minimum order The hours and the minimum amount for delivery change in the settings.
• Messages and reviews Customers write to the restaurant from the site, and after delivery they leave a star rating. Everything arrives in one place in the panel.
• Statistics and history Orders, revenue, best-selling dishes and order history with an Excel download.

What changed for the owners

We do not publish order or revenue figures. They belong to the client, and we do not show results we cannot prove. Here is what changed in the work.

Direct orders do not pass through a middleman taking a commission on every order. The system is paid for with the build and monthly maintenance, which do not depend on the number of orders.

The kitchen sees every order at once, the ticket prints by itself on acceptance, and the driver leaves with everything needed on one slip.

Orders, history and customer messages stay in the restaurant's own system, not with a middleman.

What comes next

The system grows with the restaurant. We are discussing a module for cake orders that will use the same online payment.

The text message when the driver arrives is built and will be switched on when the restaurant chooses a provider. Until then, customers get a notification on their phone through the browser.

Maintenance is monthly: we fix faults in the delivered scope, and new features are quoted separately.

• An ordering system for your venue What it includes and how the work runs.
• Own system or platform How to choose and when it is worth it.
• What drives the price What goes into the scope of a system like this.
• All projects Websites, systems and AI assistants we have built.