Menu export is messy
We clean duplicates and naming before building, and you sign off the draft.
We do the migration work, largely automated from your Toast data: menu, modifiers, prices, employees, sales history and guests. Typically days, not weeks.
Updated 2026-11-19
In Toast Web you can generate read-only Standard API credentials (Integrations, then API access; available on RMS Essentials and higher). With those credentials and your Toast exports we pull the data above automatically, so nobody retypes the menu. Read-only means nothing changes in your Toast account.
Some things need manual review. Recipes and inventory are not in Toast POS data, so we rebuild them with you if you want recipe costing. Gift card balances and loyalty points depend on what Toast lets you export. Card-on-file tokens cannot be moved, so guests who saved a card will need to enter it again.
| When | What happens |
|---|---|
| Day 0 | Discovery call: your current system, contract dates, menu size, hardware, delivery channels. |
| Days 1 to 3 | We pull your menu, modifiers and prices through the read-only API and review the draft with you. |
| Days 3 to 4 | Hardware, network and payment processor set up and tested. |
| Days 4 to 5 | Staff training, then a parallel run on a quiet day. |
| Cutover | The new system becomes the register. The old one stays read-only. |
| First week | We watch tickets, card settlement and printing, and fix what shows up. |
Typically days, not weeks. We do not promise a fixed number of hours: hardware lead times, your contract notice dates and the manual review items above set the real date. Confirmed on your demo.
We clean duplicates and naming before building, and you sign off the draft.
We start on compatible devices you already own, or stage the menu first.
We test a live payment before cutover and compare the first batches.
Training is in English and Russian, and the parallel day is a rehearsal.
We help you plan the cutover around notice and billing dates; the contract itself is yours to read.
Native (official Syrve connector), Via Deliverect, Via SmartyPOS (our build/API) or On request. We list which applies to you before you commit.
Keep your old system active until the new one has handled real service. That is the rollback plan: if something breaks on a Friday night, the old register is still there. Cancel only after a few clean days.
The parallel day is not a formality. We take real orders on the new system while the old one stays on, so staff see the whole path from order to ticket to card settlement.
Pizzerias, cafes, bars and full-service restaurants that want clear costs and an open API.
Anyone who has read their agreement and wants a plan for the exit.
Setup, training and support in Russian or English.
Central menu and reports across locations; scope is agreed on the demo.
Typically days, not weeks. We confirm the date on your demo, because hardware and contract dates matter.
Read-only Standard API credentials that you generate in Toast Web (Integrations, then API access, available on RMS Essentials and higher), plus your Toast exports. Read-only means we cannot change anything in your Toast account.
Recipes and inventory are not in Toast POS data. Gift card balances and loyalty points depend on Toast export options. Card-on-file tokens cannot be moved. We list these items with you before cutover.
No. We build the system while you operate, rehearse on a quiet day and cut over at a time you choose.
From Toast, the guest list comes from the Guestbook export, with the consent and marketing opt-ins you hold. We handle the import.
Syrve through SmartyPOS is $59, $99 or $129 per month depending on the plan. Card processing is separate and quoted on the demo. Migration scope is agreed on the call.
Not necessarily. Syrve runs on iPad, Android and Windows. Use compatible hardware you own or buy through us.
Keep the old system active during the overlap. Nothing is cancelled until you are satisfied.
Eight steps, in order. Most of the work is reading paperwork and asking questions in writing before you set a cutover date.
Read moreWhy restaurants switch, what the switch involves, and what to check before you sign anything new.
Read moreSoftware is priced per month. Card processing is separate: we do not tie you to a processor, and we quote the rate on the demo.
Read morePrice, processing, contracts and API access side by side. Each cell carries a source and the month we checked it.
Read more45 minutes, no pressure. We open Syrve around your concept, show what is live, and say plainly whether it is a fit.
Read moreA 45-minute call. We open Syrve with your concept in mind, show what is live today, and tell you straight whether it fits.