Syrve + Online Ordering From a Restaurant Website: How to Connect It, Step by Step (2026)

Short version: a restaurant on Syrve doesn't have to choose between "convenient in the POS" and "a channel of its own with no commission." Orders from a restaurant's own website can drop straight into Syrve POS — exactly like orders from Pyszne.pl or Glovo, just without the 25–35% commission. The menu is maintained in one place — iikoOffice — and the website updates itself. Below: how the connection works, how to set it up, and its honest limitations.

What Syrve is, and why it's familiar to anyone who's worked with iiko

Syrve is an international cloud POS system for food service that, according to partner Mico (2025), serves more than 8,000 restaurants worldwide and entered the Polish market through a network of local partners — Knajpa Pro, Mico, and others. Technically, Syrve is a fork of iiko: the back office is called iikoOffice, and the logic for menus, inventory, and reports mirrors what iiko users already know.

For restaurateurs who relocated to Poland from Ukraine or Belarus, that's an important detail: if you ran a venue on iiko for years, you won't need to learn Syrve from scratch — which means your team won't need retraining either. The one thing missing from Syrve's box is a website of its own for guests to order from. That's the piece the ordering-platform integration covers.

How the "own website → Syrve" connection works

The setup has four parts. First, the external menu: in iikoOffice you publish an external menu (dishes, prices, modifiers), and the website pulls it in automatically — create a dish in iikoOffice, and it appears on the website within about 15 minutes. Second, orders: a guest places an order on the website, and it appears automatically in Syrve POS, just like an order from an aggregator, with no manual transfer and no phoning things in. Third, statuses: the kitchen changes the status in the POS, and the guest gets an SMS and sees progress in the website's tracker. Fourth, stop lists: sync runs both ways, and an item pulled in Syrve instantly disappears from sale on the website.

A bonus for management: Syrve's reports show website orders as a separate channel — making it easy to compare the revenue from your own channel against aggregators and dine-in.

Connecting it, step by step

Step 1. Check your version. The integration works with cloud-based Syrve Cloud. If you're still on a local install, or you're only just moving over from iiko, that question gets sorted out with a Syrve partner before the website gets connected.

Step 2. Prepare an external menu in iikoOffice. Put together what should be sold online: dishes, prices, modifiers. The online menu doesn't have to mirror the full dine-in menu — drop items that don't travel well.

Step 3. Connect an ordering platform with Syrve support. In Gustano, the platform's team handles the connection as part of onboarding: you link the accounts, and the platform syncs the menu.

Step 4. Add the marketing layer. On top of the data coming from Syrve, the website gets photos, sales-oriented descriptions, tags ("Spicy," "Vegan"), and menu translations into Polish, Ukrainian, English, and Russian — AI translation runs with one click and can be edited by hand.

Step 5. Place a test order. Check the whole chain: the order shows up in the POS, statuses move in both directions, the guest's SMS goes out, and the stop list works.

Step 6. Turn on payments and launch. BLIK, Apple Pay / Google Pay, cards, and Przelewy24 — money lands directly in the restaurant's account through Stripe, the payment processor takes its ~1.5–2.5%, and there's no platform commission.

The honest limitations of Syrve mode

The integration is a division of roles, and that has consequences worth knowing up front. The menu is only editable in iikoOffice: the website side handles the marketing layer (descriptions, translations, tags, photos), but not ingredients or prices. AI menu import from photos or a PDF isn't available in Syrve mode — the menu's source is Syrve itself. Stop-list scheduling isn't available, and neither is the "free gift item" mechanic in promotions. And one more thing: the platform's loyalty program runs in parallel with Syrve — there's no iikoCard5 integration, and points live on the website side.

If any of these limits are a dealbreaker, the honest answer is that Syrve mode isn't for you; for every other scenario, the split of "Syrve handles operations, the website handles the storefront and marketing" works as intended.

What this looks like in practice

Friday, rush hour. An item runs out — you pull it in Syrve, and it's instantly flagged unavailable on the website: not a single order for something that's gone. A guest places an order — it's already in the POS, the kitchen is working, and the phone stays quiet. The guest gets an SMS, "Your order is being prepared," in their own language. On Monday, you open the Syrve report and see your own website's channel as a separate line — how many orders shifted from aggregators straight to you.

By our estimate, Syrve runs at a notable share of Polish delivery-focused restaurants — and for them, a website that drops orders straight into the POS is the shortest path to a commission-free channel: operationally it's no different from an aggregator, except the money and the customers stay with the restaurant.

What it costs

Gustano is a Polish SaaS platform for delivery restaurants — a branded online ordering website with zero commission, BLIK and card payments, a loyalty program, delivery zones, and Syrve POS integration. From 250 zł net/month.

Syrve mode is a +50 zł/month option on top of the Standard plan. That's 300 zł net a month in total for a site in 4 languages, payments landing directly in your account, SMS statuses, loyalty, delivery zones, and orders that drop into your own Syrve on their own. The first customers are onboarding manually right now and get two months free.

Reviewed 13.07.2026. For details on how Syrve works, check with the system's official partners in Poland.