Skip to main content
All CollectionsIntegrating seats.io
When to use Not For Sale
When to use Not For Sale
Pablo Neirotti avatar
Written by Pablo Neirotti
Updated over a week ago

When to use Not For Sale

Not For Sale is meant to be used when you either want to:

  • A. block out seats that you won't sell as they are not part of your inventory

  • B. gradually open up parts of a venue for sale over time

When *not* to use Not For Sale

Any time you are trying to block only a few specific seats at a time, or "reserve" them temporarily. You will hit the daily usage limit by using Not For Sale incorrectly. In these cases you should either:

Ways to manage it

You can manage the For Sale configuration of an event via either:

Usage limit

Objects Not For Sale are not billed, however there is a limit to how many times you can use this feature. You can only make 10 changes (on which some seats become Not For Sale) per event, per day.

This can be better explained with an example:

  • You mark 100 seats as Not For Sale, and commit changes. This consumes 1 save.

  • You mark 20 seats as For Sale (which were previously marked Not For Sale), and commit changes. This does not consume a save.

  • You mark another set of 20 seats For Sale, and other different 50 seats as Not For Sale. This consumes 1 save.

  • During this example, 2 saves were consumed out of the 10 available.

Due to these limitations, we advice to stick to using For Sale only for the intended use cases, and use the offered alternatives when your flow does not fit the purpose of For Sale.

Did this answer your question?