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 sees the restaurant's floor plan and clicks the table they want, picks a date, time and party size, and only genuinely available slots 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, the system pushes it to the till immediately — staff see it on the terminal, attached to the exact table, with no retyping. 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 — when the POS starts rejecting requests, Stolio notices, backs off automatically and retries with growing intervals. It never floods a third-party API.
• Reservations never wait for the POS — the most important principle: a guest always completes their booking, even if the POS is entirely offline. Synchronization catches up the moment the POS returns. A third-party outage must never stop reservations.
• Signed internal communication — the system's components talk to each other via cryptographically verified requests, so synchronization can't be triggered by anyone unauthorized.

The outcome of the July incident: guests noticed nothing, bookings kept flowing, and the sync healed itself once the API recovered.

What Javor gets out of it

• Dozens of online reservations per month from its own website — 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 — tables pair automatically. And without a POS, everything else (the table-picker widget, the mobile app with push notifications, guest CRM) works on its own, from 499 CZK per month with no commissions. Try it free for 14 days.