Skip to content

Product

Three interfaces, one service flow.

Odazivo is a hospitality service-operations platform. This is an inventory of what the product does today, organised by role, and a separate list of what is only planned.

Three roles, one requestIllustrative view · Demo data

01Guest

The table's page, without an app.

The guest gets a fast mobile page tied to the exact venue, zone and table.

  • QR or NFC entry

    Scan or tap the phone. The table is already known.

  • No installation, no account

    A plain page in the browser, no sign-in.

  • Three service requests

    Call a waiter, Bill please, I need help — the owner chooses which are enabled.

  • Honest confirmation

    Sent, accepted, completed — every status is confirmed by the server.

  • The venue's identity

    Name, logo, preset or custom colours, language, menu, links, Wi-Fi.

  • Opening hours

    The page behaves differently outside opening hours, if the venue enforces them.

Guest page · Table 12 · TerraceIllustrative view · Demo data

02Team

A request queue for a real shift.

The team app is a PWA that runs on a phone, a tablet and a desktop — built for working a shift, not for reading reports.

Request queue · team viewIllustrative view · Demo data
Floor Pulse · the tables that need attention mostIllustrative view · Demo data

  • A real-time queue

    Table, zone, request type, time created, waiting time, status, owner and urgency.

  • Filters All · New · Mine · At risk · Over time

    The counts in the filters are real counts from the queue, not decoration.

  • Accept and Complete

    Two taps. The server controls status transitions, so two people cannot accept the same request.

  • Urgency in words and time

    At risk and Over time arrive with a reason and a timer, not colour alone.

  • Floor Pulse

    A list of tables with open requests, worst first — where service pressure is building up.

  • Push notifications

    When the device allows them. If not, the queue still refreshes in real time.

03Owner and manager

Four areas, per venue and per role.

The owner is the venue's administrator. A manager has delegated, limited access. An account with several venues chooses a venue first.

Venue selection · roles per venueIllustrative view · Demo data

  1. 01Owner and manager

    Overview

    An honest operational summary: setup progress, configuration status, current requests and shortcuts. No decorative charts and no invented trends.

    • Setup progress
    • Current requests
    • Shortcuts to settings
    Overview · setup and current stateIllustrative view · Demo data

  2. 02Owner and manager

    Content

    What the guest receives on the table page: logo, venue links and the menu source — a PDF or an external link — with clear 'configured' and 'not configured' states.

    • Logo and visual assets
    • Venue links
    • Menu source: PDF or link
    Content · what the guest receivesIllustrative view · Demo data

  3. 03Owner and manager

    Design

    Preset selection, live preview, draft and published versions, discarding changes, resetting to the preset. Advanced colours with contrast validation and protection against losing unsaved changes.

    • Presets and live preview
    • Draft → publish
    • Contrast validation
    Design · preset, preview, publishIllustrative view · Demo data

  4. 04Owner and manager

    Settings

    Venue identity, languages, contact, Wi-Fi, opening hours and their enforcement, guest-action visibility, response thresholds and repeat rules. Saved per section, with protection against overwritten changes.

    • Opening hours and enforcement
    • Guest actions
    • Thresholds and request rules
    Settings · saved per sectionIllustrative view · Demo data

04Roles

Who can do what.

RolesStaffManagerOwner
Request queue, Accept, CompleteYesYesYes
Floor PulseYesYesYes
Menu on the guest pageNoYesYes
Logo, links, designNoNoYes
Venue settings and thresholdsNoNoYes
Team members and rolesNoNoYes
Access to another venueMembership onlyMembership onlyMembership only

05What is available

Available now. Planned later. Never mixed.

We sell what exists. What is on the roadmap is clearly marked and is not part of any package.

Available in the product

  • Guest page via QR/NFC, no app and no account
  • Three service requests with server confirmation
  • A real-time request queue with filters and ownership
  • Response thresholds, At risk and Over time
  • Floor Pulse — tables listed by urgency
  • Web Push notifications where the device allows them
  • Owner application: Overview, Content, Design, Settings
  • Several venues per account, roles staff / manager / owner
  • Serbian and English
  • Abuse protection and data separation per venue

On the roadmap

  • A visual floor map

    A bird's-eye view of tables with positions configured by the owner. Today's Floor Pulse is a list, not a freely editable map.

  • Supplemental ordering

    A restricted additional menu of simple items (water, bread, sauces) only after the main order has been taken — preserving the guest's first conversation with the waiter.

  • POS integration and online payments

    Not in the product. Odazivo works alongside the existing POS, without taking payment.

When something on this list ships, it moves to 'available' — not before.

See the whole flow on the example of your venue.

Book a demonstrationPricing and packages