Case Study: How Restaurant Javor in Šumava Connected Online Reservations Directly to Its POS

2026-07-25 · Case Study

Restaurant Javor sits in Železná Ruda, a mountain town in Šumava — Italian and Mediterranean cuisine, fresh pasta, a grill, open Thursday to Monday. A typical resort-town restaurant: quiet midweek, then weekend and holiday surges where every table counts and nobody has a hand free to answer the phone.

Since June 2026, Javor runs on the Stolio Pro+API plan with a live connection to its Syrve POS. This case study describes how the integration actually works — including the technical details that usually stay under the hood.

What the guest sees: booking with a specific table

On restaurantjavor.cz, the Stolio widget invites guests to "pick your own table." No anonymous form — the guest picks a date, time and party size, then chooses the exact table they want from the tables actually free at that moment, and only genuinely available times are offered. It works around the clock: on a Tuesday, when Javor is closed and no one answers the phone, a guest can still book Saturday dinner.

Under the hood: the reservation reaches the POS in seconds

Javor has 23 tables in Stolio, each paired 1:1 with a table in the Syrve POS. When a new reservation arrives, Stolio checks that the till is online and pushes the booking to it within seconds — staff see it on the terminal, attached to the exact table, with no retyping. If the till is off, the booking waits in Stolio and is delivered when it is back. No duplicate reservation book, no paper next to the register. At the same moment, staff phones get a push notification from the Stolio mobile app: new booking, name, party size, time.

Defence mechanisms: what happens when the POS stops responding

This is the part we are proudest of — and it was tested for real in July 2026, when the POS API temporarily started rejecting login requests. An integration with any third-party system is only as reliable as its failure handling. Stolio builds in several layers of protection:

• Smart authentication — the system caches its POS login token and renews it only when needed, never hammering the POS API with unnecessary requests.
• A circuit breaker — if Syrve blocks the login, Stolio pauses every call for six hours (then checks only once a day if the block continues) instead of retrying, and it never sends a booking Syrve would certainly refuse. It never floods a third-party API.
• No booking is lost — if the till is offline, the guest still completes the booking and Stolio delivers it as soon as the till returns. If Stolio cannot check Syrve's live table availability at all, online booking for that time pauses and guests see the restaurant's phone number: a short pause beats a double-booked table.
• Authenticated internal communication — the database and the sync service talk using a shared secret kept in an encrypted vault, so synchronization can't be triggered by anyone unauthorized.

The outcome of the July incident: Stolio backed off instead of hammering the POS, and the sync caught up by itself once the API recovered.

What Javor gets out of it

• Online bookings from its own website every month since June 2026 (24 in July, at the summer peak) — with zero per-cover commission to anyone.
• Bookings arrive even outside opening hours, when the phone used to ring into the void.
• Staff see reservations where they already work: at the till and on their phones.
• Guests pick their favourite tables — and come back: repeat guests are tracked automatically.

Does this fit your restaurant?

If you run a Syrve POS, connecting Stolio is a single setup step — paste your Syrve API key and the tables pair automatically. Without a POS, the booking widget, the mobile app and the guest list with visit history work on their own, from 499 CZK per month with no commissions; guest table choice comes with the Syrve connection on Pro + API, and push notifications start with Plus. Try it free for 14 days.