The Seats.io designer allows you to indicate which seats belong to the same category. A category gives seats a color and a price tag (which you set at rendering time). All seats belonging to a category have the same color and price. That goes for all the events that are linked to a chart.

But what if the categorisation differs from event to event? What if in Monday's session seats A-1 and A-2 are in the same category, but on Tuesday they aren't? You'd still want to use the same chart, because the seat positions and labels are exactly the same - only their categories are different.

To do so, you can override the categories you assigned through the chart designer on a per-event basis. Or more specifically: on a per-rendering basis.

Two renderer parameters make this happen: categories and objectCategories. categories allows you to pass in an array of categories, which replaces the categories of the chart. objectCategories lets you assign those custom categories to objects (seats, booths, etc.). E.g.:

categories: [
    { key: 'cat1', label: 'Some category', color: 'red' },
    { key: 'cat2', label: 'Another category', color: 'blue' }
],
objectCategories: {
    'A-1': 'cat1',
    'A-2': 'cat1',
    'A-3': 'cat2'
}

Make sure to include all objects in  objectCategories . Otherwise the ticket buyer won't see the ticket price when hovering that object. If you prefer a safety net, disable the objectWithoutCategorySelectable flag.

Did this answer your question?