The questions owners and managers ask.

No. The guest scans a QR code or taps the NFC tag and opens a plain page in the browser. No installation, no account, no sign-in.

Every table has its own unique link in the QR code and the NFC tag. The guest types and chooses nothing — the link already knows the venue, zone and table.

Honest confirmation from the server: the request was sent, then that a team member accepted it, and finally that it was completed. Nothing is shown just because a button was pressed.

No. The same request cannot be active twice, there is a maximum number of active requests per table, a pause before repeating and a limit within a time window. The owner can also mute a table.

Yes, if the venue enables it: a menu from a PDF or an external link. Odazivo is still not a QR menu — the menu is an addition to the table page, not its purpose.

The phones or tablets the venue already has. The app runs in the browser as a PWA on phones, tablets and desktops and needs no app-store installation.

The app keeps working. While it is open, the request queue refreshes in real time without manual reloading. Push notifications are an extra channel, not a requirement.

No. Acceptance is recorded on the server, which allows only valid status transitions. Every device sees who the owner is.

A per-table view: one row per table with open requests, ordered worst first. It shows where service pressure is building up. Today it is a list, not a freely editable floor map — the map is on the roadmap.

No. It is there so the team has a shared view of the queue and clear responsibility in a busy shift. Timing and ownership data help show where service stalls, not who is to blame.

No. Odazivo does not issue bills, take payment or enter orders. It works alongside the existing POS and organises the service around it.

Not currently. Odazivo handles service requests: call a waiter, the bill, help. Restricted supplemental ordering of simple items after the main order is on the roadmap, not in the product.

Your team, through the existing process — cash or card, as before. Odazivo only makes sure the bill request is not forgotten.

Configuring the venue, zones and tables is a matter of hours. Plates are placed in one visit, and the team is onboarded shortly before the trial shift.

One QR/NFC plate per table (part of the setup) and the devices the team already uses. No new terminals, printers or POS changes.

An additional table and plate replacement are separate, clear line items in the offer.

Yes. One account can hold memberships in several venues, with a role per venue. The user chooses a venue first and sees only the ones they can access.

A one-time setup (configuration, plates, training) and a software subscription with support. The structure is public on the Pricing page; the amount is built around your number of tables and zones.

A conversation about your service flow, a demonstration on the example of your venue, setup and plates, a trial in a real shift and a joint review. Pilot terms are agreed directly.

No. The website does not process payments. After the configuration is confirmed you receive an offer with an invoice or a secure payment link.

Yes. The guest page, the team app and the owner app work in Serbian and English.

Data is separated per venue and checked in the database, roles are enforced on the server, settings changes are audited. Details are on the Security and privacy page.

Everything described on the site as available exists in the product. The visual floor map and supplemental ordering are planned and are not part of any package. The inventory is on the Product page.