Connection
”Syrve” isn’t in my Integrations list
The integration isn’t enabled for your account. Contact support to have it turned on.”We could not reach Syrve’s API with the configured API key”
The saved API Login doesn’t work — it’s mistyped, revoked, or not yet issued for API access. Re-enter it under Syrve API Settings (use the pencil icon to replace it). storekit validates the credential against Syrve before saving, so a value that saves successfully is one that works.I can’t save the settings
An Organization must be selected before the settings can be saved — the page prompts you to select one.Menu Sync
The Sync menu button is disabled
- An External Menu must be selected.
- The store must have an active storekit menu.
The External Menu dropdown is empty
External menus are created in Syrve Office. Set one up there (and make sure your Organization is the right one), then reopen the page.Items show £0
Syrve returned no price for those items — a known gap in some Syrve external menus. Fix the prices in Syrve Office and run Sync menu again. Setting the price in storekit isn’t a durable fix: the next sync replaces it with what Syrve returns.Items or modifiers are missing
Only content visible in the Syrve external menu imports — items, sizes, and modifier groups hidden in Syrve are skipped, as are modifier groups with no visible options. Check the external menu in Syrve Office and re-sync.An item that’s in stock shows as sold out (or vice versa)
Availability follows Syrve’s stop list for your Terminal Group — see Stock & Availability for the exact rules (including why a stop-listed item with stock remaining stays on sale). Webhooks deliver stop-list changes live; without them, the list is only re-read on menu sync — run Sync menu to force a reconcile, and set up webhooks so it stays current.Orders
Orders are failing to reach the till
A failed order is marked failed in storekit with the Syrve error on the order; the customer’s order still completes. Common causes:- The terminal group is asleep — the error mentions a timeout. This is the most common failure and has its own guide: wake the till, and note that Syrve rejects a re-send of a timed-out order as a duplicate — ring it in manually.
- No order type for the fulfillment method — set Delivery Order Type, Pickup Order Type, or Table Order Type under Syrve Order Complications, then open the order and use Resend order to POS.
- The integration is only partly configured — the Organization and Terminal Group must both be set; fix and resend.
- An item can’t be matched on the POS — the menu on the till has changed since the last import. Run Sync menu, then resend.
The payment isn’t on the Syrve order
Set Cash Payment Type and Card Payment Type under Syrve Order Complications. Orders placed while one is missing are sent without a payment — staff have to close those on the till.The service charge on the check doesn’t match the order
The selected Service Charge is a percent-based charge in Syrve, which recalculates its own percent on the POS and ignores the amount storekit sends. Use a flexible-sum charge from Syrve Office instead. Remember the delivery fee is folded into the same charge, so on delivery orders the combined figure is expected.Order statuses aren’t updating in storekit
Status updates arrive by webhook. Check Syrve Webhooks on the Syrve Settings page — if the panel says Webhooks not configured, click Setup webhooks. If you’ve changed Organization, save and set webhooks up again.Syrve says the order was cancelled, but it’s still live in storekit
That’s deliberate: a ticket voided on the till does not cancel a paid storekit order behind your back. storekit flags the order; cancel (and refund) it in storekit if that’s what should happen.A cancelled storekit order is still on the till
- Cancellation only reaches Syrve for pickup and delivery orders — at-table tabs must be voided on the till.
- A Cancel Cause must be selected under Syrve Order Complications; Syrve rejects cancellations without one.