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, 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.
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.
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.
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.Stock Flows One Way
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.
Next Steps
Menu Sync
How the menu itself is imported
Troubleshooting
Stock isn’t updating? Start here