ObjednámSi.sk

An online ordering system for restaurants

My own product · web + administration

ObjednámSi.sk — restaurant customer website with daily specials, menu categories and an empty basket

Overview

My own restaurant system: menus with allergens and sides, daily specials, delivery or collection, order statuses with notifications, coupons, reviews and statistics. One system for customers and restaurant administration.

My role
Product, design and full-stack development
Team
My own product
Client / company
ObjednámSi.sk
Platforms
Customer website · Web administration
Status
Live

Scope

  • Product design and feature scope
  • Customer website and ordering flow
  • Restaurant administration
  • Order status notifications
  • Statistics and customer overview

01 /Context

ObjednámSi.sk is my own ordering system for restaurants. It provides an online menu, a customer ordering website and administration for menus, delivery, coupons and statistics.

The customer and operational sides work as one system, also prepared for a mobile app.

02 /Problem

Restaurants differ in details that determine usability: daily specials at one set price or a separate price for each dish, sides and sauces as individual items, delivery to different places at different prices, and collection. When a system cannot handle one of these cases, the business has to work around it.

Customers also need to know what is happening with their order at every stage: accepted, awaiting delivery, fulfilled or cancelled.

03 /My role and responsibilities

This is my own product. The feature scope, data model, customer interface, administration and system operation are my responsibility.

04 /Constraints and risks

  • One system for many businesses. Every feature needs to be configurable in administration rather than custom-coded for each business.
  • Administration users are restaurant staff, not technicians. Onboarding a new business includes setting up the menu and training; after that the system needs to work without developer intervention.
  • Both the customer and the restaurant need a clear view of the order’s status from acceptance to completion.

05 /Key decisions

  1. 01

    A menu as a data model

    A dish has a name, price, weight or size, allergens and variants. Sides, sauces, salads and drinks are separate lists linked to the dish and offered when it is added to the basket.

  2. 02

    Daily menus in every form

    Daily specials sit within the menu alongside categories, variants, allergens and dish extras.

  3. 03

    Order statuses with notifications

    Notifications and a status overview accompany an order from acceptance through preparation to delivery or collection.

  4. 04

    Data for the next decision

    Coupons, reviews, statistics and the customer overview are available directly in administration.

06 /Architecture

The system has three layers: a customer website, restaurant administration and a shared backend with a database of menu items, orders, customers and coupons. The server sends order status notifications; statistics and the customer overview use the same data as the kitchen.

07 /UX

Customers see categories with images and icons, dish variants and allergens, and suggested sides when adding items to the basket. Delivery or collection is part of the order flow, not a hidden setting. Administration follows the operation’s logic: menu, delivery, orders, coupons and statistics.

08 /Technology

Web, Administration, Notifications

09 /Outcome

ObjednámSi.sk connects customer orders with restaurant administration, from menus and delivery to coupons, reviews and statistics.

Gallery