CASE STUDY · MK Adisyon

Managing restaurant operations in one flow, from order to payment

MK Adisyon is a two-surface product that keeps the restaurant team on one shared record, from the first table order through kitchen preparation to closing the bill: a working web system and a mobile application in closed testing.

Sector
RESTAURANTS & CAFÉS
What we built
Business systems · Mobile app
Status
Live demo
MK Adisyon web cashier screen with sample order and payment data
MK Adisyon responsive web waiter screen with sample table data

Whose problem?

Restaurants and cafés coordinating ordering, preparation, service and payment at the same time. Information entered by a waiter needs to reach the kitchen, cashier and management without being entered again.

  • Service teams following room and table status
  • Kitchens managing waiting, preparing and ready orders
  • Cashiers handling split or partial payments
  • Managers overseeing products, tables, shifts and operations

What was the problem?

Restaurant operations move between teams working at different speeds. When order details, table changes and payment status do not live in one record, delays, duplicate entry and misunderstandings become more likely.

  • Different teams seeing different table and order states
  • Product options, notes and service rounds reaching the kitchen incompletely
  • Ready orders not reaching the service team at the right time
  • Per-person or per-item bill splitting slowing down checkout

How did we approach it?

We designed task-focused views for each role while keeping every role connected to the same check. A table opened by a waiter, kitchen preparation and cashier payment steps therefore stay in one continuous flow.

  • Task-focused screens for waiter, kitchen, cashier and management roles
  • One order record followed from the table through payment closure
  • Explicit state changes such as preparing, ready and served
  • Layouts suited to the task on phone and desktop screens

A real web system and a mobile application in closed testing

MK Adisyon has two real product surfaces. The operational features below are verified in the working web system. A separate mobile application has been developed and is in closed testing; this study attributes only verified scope to it.

MK Adisyon web cashier screen with sample order and payment data

The working web system brings table, ordering, kitchen, service, cashier and management flows together in role-based views.

  • Areas and tables, table opening and guest count
  • Products, options, notes, service rounds and kitchen dispatch
  • Waiting, preparing, ready and served order flow
  • Moving and merging tables, and splitting a bill
  • Amount-, person- or item-based splits and partial payments
  • Shifts, products, tables, expenses, finance and activity logs

MK Adisyon's second developed product surface is its mobile application. It is in closed testing; this study does not extend its feature scope beyond the verified welcome screen.

  • A real, developed MK Adisyon product surface
  • Currently in closed testing
  • A verified application address separate from the web system

The resulting system

Records in the web screens are sample data. The phone-framed waiter view is the responsive web interface; the separate mobile app screen is labelled explicitly. “Mavi Adisyon” in the web interface is existing rebrand debt; the public product name is MK Adisyon.

Modules verified in the web system

Rooms and tables

Areas and tables are tracked by state; opening a table starts with its guest count.

Waiter order flow

Products are added with options, notes and service rounds, then sent to the kitchen.

Kitchen display

Orders move through waiting, preparing and ready states, and readiness is sent back to service.

Table operations

Open tables can be moved or merged, and their items can be split into another bill.

Cashier and payment

Bills can be split by amount, person or item; partial payments and different methods are recorded.

Shift and cash movements

Shift opening, cash in and out, and cash counts remain in the same operational record.

Management

Products, tables, kitchen, waiter, cashier, expenses, finance and activity are followed from management views.

Where is it today?

Facing a similar problem?

If you want to bring ordering, kitchen and payment work onto one shared record, let’s review how your restaurant operates today.