Stop an item versus deleting it

Stop takes an item off sale and keeps it. In the app, guests see it greyed as "Not on sale" and cannot add it; on the Menu code's page it is not shown at all. Everything already sold on it stays exactly as it was. Resume and it is back. Run out of a keg, Stop the beer. In the app it is Stop selling in the item's menu, and Resume selling to bring it back; on the dashboard it is the Stop button on the row.

App
Drawing of the app's Menu screen with an item's menu open, Stop selling marked 1
Web
Drawing of the dashboard's Menu page, with the Stop button on an item's row marked 1
1. Stop selling in the app, Stop on the dashboard.

Delete removes the item, and only works while nothing has sold on it. In the app, Delete leaves the item's menu once there is a sale. Once there is a sale, the item is history that other records point at, and the service refuses to delete it: see why can't I delete this tier.

So the habit is: Delete for a mistake you caught straight away, Stop for everything else.

AppMy Events › the event › Menu › the item's menu › Stop sellingWebYour Events › the event › Menu › the item's row › Stop

Didn’t find it?

You reach people who know the industry, not a queue. Tell us the event name and what you were trying to do.