> ## Documentation Index
> Fetch the complete documentation index at: https://storekit.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Syrve Stock & Availability

> Mirror Syrve's stop list into storekit after every menu sync and live over webhooks, so out-of-stock items come off sale as the kitchen 86s them.

Syrve's **stop list** — the till's out-of-stock list — is the source of truth for what's off sale. storekit mirrors it onto the online menu so customers can't order what the kitchen has run out of.

## When the Stop List Is Read

* **After every menu sync.** A fresh import says nothing about what the kitchen has 86'd, so storekit reads the stop list for your **Terminal Group** as the last step of every **Sync menu** run (manual or scheduled).
* **Live, over webhooks.** With [webhooks enabled](/docs/guides/integrations/pos/syrve/connect#set-up-webhooks), Syrve signals every stop-list change and storekit re-reads it immediately — an item 86'd on the till comes off sale online without waiting for a sync.

<Warning>
  Without webhooks the stop list is only re-read on menu sync, so items 86'd mid-service stay orderable online. [Set up webhooks](/docs/guides/integrations/pos/syrve/connect#set-up-webhooks) if stock accuracy matters to you.
</Warning>

## How Stop-List Entries Are Applied

Syrve keeps items on the stop list in two states, and the **remaining count is the signal**, not the membership:

* **No stock remaining (or none tracked)** — the item is out of stock: storekit snoozes it, for items and modifier options alike.
* **A positive remaining count** — the kitchen still has some: the item **stays on sale**. storekit doesn't mirror the count itself — availability online is on/off.

An item comes back on sale when it drops off the stop list (or gets stock again). An item the stop list never mentions keeps whatever availability you've set on it in storekit.

<Info>
  If your Syrve organization runs several terminal groups and they disagree about an item, the stricter answer wins — storekit can't choose which till an order routes to, so an item any group has run out of goes off sale.
</Info>

## Where Syrve Snoozes Show Up

Items snoozed from the stop list appear in **Reports** → **Item Snooze** alongside manual snoozes, attributed to Syrve — so you can see what the POS is taking off sale and when. They also fire the item out-of-stock webhook if you use [API webhooks](/docs/guides/integrations/api-webhooks).

## Stock Flows One Way

<Info>
  Syrve decides what's off sale. Snoozing or unsnoozing an item in storekit never changes the stop list in Syrve — manage the stop list on the till, as you normally would.
</Info>

## Next Steps

<CardGroup cols={2}>
  <Card title="Menu Sync" icon="utensils" href="/docs/guides/integrations/pos/syrve/menu-sync">
    How the menu itself is imported
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/docs/guides/integrations/pos/syrve/troubleshooting">
    Stock isn't updating? Start here
  </Card>
</CardGroup>


## Related topics

- [Syrve Menu Sync](/docs/guides/integrations/pos/syrve/menu-sync.md)
- [Deliverect Stock & Availability](/docs/guides/integrations/pos/deliverect/stock-and-availability.md)
- [Stream Stock & Availability](/docs/guides/integrations/pos/stream/stock-and-availability.md)
- [Lightspeed Stock & Availability](/docs/guides/integrations/pos/lightspeed/stock-and-availability.md)
- [Toast Menu Sync](/docs/guides/integrations/pos/toast/menu-sync.md)