Skip to main content
Syrve is a cloud POS. Once connected, storekit imports your menu from a Syrve external menu, sends online orders to your Syrve terminal group as they come in, keeps out-of-stock items off sale by mirroring Syrve’s stop list, and progresses order statuses automatically as the kitchen works through them. This section is split into focused guides. Start with Connecting Syrve, then set up the areas you need.

Connecting Syrve

Enter your API Login, pick your organization, and enable the integration

Menu Sync

Import your Syrve external menu and keep stock in sync with the stop list

Orders & Payments

How orders reach the till, payment and order-type mapping, and status updates

Stock & Availability

The stop-list mirror — after every sync and live over webhooks

Dine-in: Table Orders

At-table orders open a tab on the POS

Orders Failing: Till Asleep

The most common failure — wake the sleeping terminal group

Troubleshooting

Fix connection, menu, stock, and order problems

​
How the Connection Works

Syrve connects with a single API Login — the API credential for your Syrve organization, issued by Syrve (or your Syrve reseller). You enter it once for your account, then per store you pick the Syrve Organization, the External Menu to import, and the Terminal Group orders should land on. storekit loads your Syrve order types, payment types, discounts, tips types, and cancel causes so you can map them.
The Syrve integration is only available to accounts that have it enabled. If you don’t see Syrve in your Integrations list, contact storekit support to have it turned on.

​
How Orders Flow to Syrve

Orders are sent to Syrve as soon as they’re placed — the order shows as syncing until the till confirms it, and is only marked Accepted once Syrve has the order. If the till rejects it (or never confirms), the order is marked failed in storekit with the reason — the customer’s order still completes, so it’s never lost. The most common cause is a sleeping terminal group.

​
Supported Features