Dyresto
A restaurant transaction system built under a tight delivery constraint — role-based workflows spanning menus, tables, cart, ordering, cashier operations, transactions, and reporting.
- Stack
- Laravel · MySQL · PHP
- Category
- Business Applications · Restaurant
What shipped
- Role-based flows for administrator, waiter, and cashier responsibilities, plus a customer-facing role.
- Menu and table management with cart and order flow handing off to cashier transactions.
- Transaction history and print/reporting workflows.
Dyresto is a restaurant cashier application built with Laravel 6.2 during a pre-UKK (competency-exam) challenge — a delivery-constrained build that forced the system to stay focused on the transaction loop: menu, order, cashier, receipt.
What it does
Restaurant information, food categories, and a menu anchor the product side; tables and a cart feed into orders. Roles split the work — administrator, waiter/cashier, and a customer-facing path — and completed orders land in transactions and a transaction history, with print and reporting workflows for the close of service.
Engineering notes
- Roles map the restaurant floor. Order-taking, cashiering, and administration are distinct responsibilities in the data model.
- Cart to transaction, end to end. The order flow passes through the cart and ends at a recorded, reportable transaction.
- A tight constraint kept the scope honest. Built as a timed challenge, the system demonstrates the transaction core without invented extras.
Place in the story
Alongside Dyposten, the 2019–2020 period is the early transactional-systems chapter: menus, tables, cart, roles, and printed output — the building blocks of every transactional product that followed.