Where do I find it?
What does it mean?
This article explains how to create and set up a seating charts in Seats.io.
What should I do?
Log in to your Seats.io account and select ‘New seating chart'.
Please note: If you don’t have a login, contact our IT department to create your access.
We have to select 'Simple' and start from scratch for the highest accuracy, as the reference chart feature doesn’t work fine at the moment of writing this document.
Create rows: Use the multiple Row tool to build your layout (e.g., 21 rows of 19 seats).
Define sections: Select your seat blocks and assign labels such as "Side Section - Odds" or "Side Section - Evens".
Labeling: Ensure every seat has a section, row number, and seat number.
Currently, we support only simple seating charts, but we will support other types in the future.
Using the tools on the right menu bar, we can create the seating chart. You can do it category by category: first the central seats, then the lateral seats, followed by the box seats, and so on.
After creating each block, adjust the spacing and style on the right side.
After creating all the blocks, you will have your seating chart. To create box or second-floor seats, create a separate block in the main plan; it will be treated as a different section.
Each seat on the map must include a section, row number, and seat number.
To define seating information, select each section and name it. First, assign the section label.
Repeat the process for each section:
Side section - Odds
Side section - Evens
Label each section's rows by selecting the section and editing the row labeling on the right. We use numeric rows starting at 1.
Repeat the process for each section. Then, all rows should be numbered.
Next, label the seats by selecting the rows or the entire section and adding the seat labels.
Once finished, your seating chart will look like this:
On the top right, we see errors and missing parts. This seating chart lacks categories, so the next step is to create them.
We will import categories from Palisis, but we need at least one category in Seats.io to create the connection. Therefore, we must create a test or dummy category in Seats.io.
Categories and focal points
Before connecting to Palisis, your chart must be "Error Free" in Seats.io:
Create a dummy category: You must have at least one category (e.g., "Dummy Category") assigned to all seats to allow the initial sync between Seats.io and Palisis.
To create a dummy category, go to the top right, select Manage, and create a new category. Name it anything; we will use ‘dummy category’.
Now we assign all seats to the new category by selecting each seat block and assigning the newly created category.
We repeat this for each block of seats:
If you check the right side menu, you will see one yellow point, indicating something is pending. We need to add the focal point.
Set a focal point: Use the Focal point tool (usually placed on the stage or front of the vehicle). This determines the "Best Available" logic, where seats closer to the point are considered the best.
Visual aids: Use the Image tool to upload a floor plan or stage icon to help users orient themselves.
Use the settings on the right to adjust the image and place it correctly.
Creating a dummy event
Before the Palisis system can "see" your chart, you must create a test event within the Seats.io dashboard. This acts as a placeholder that mimics a real departure.
-
Create the event: Close the chart designer and navigate to the main Events setup area.
-
Naming: The system will assign a random code, but you should rename it to something recognisable, such as "Dummy event". Ensure the event key contains only alphanumeric characters and dashes (no spaces or special symbols).
Publishing: Go to the "All Seating Charts" page. Your chart must show a Green "Published" status.
If you see "Unpublished Changes," you must click Publish for the connection to work.
You can also publish changes from the seating chart edition page:
After publishing, it will look like this:
Creating channels in Seats.io (optional)
Beyond standard seat selection, you can use the Channels feature in Seats.io to manage specific inventory distribution.
Use Case: Blocking Capacity for Partners
This is particularly useful if you have a contract with a specific partner (e.g., a corporate group, a VIP agency, or a school) and you want to "reserve" or block a specific set of seats exclusively for their use. By setting up a channel:
Those seats are removed from general sale on your Webshop, Box Office and devices.
You can also use this to block rows for internal use (e.g., keeping the front row empty for operational reasons).
How to configure it:
In the Seats.io designer, select the Events and channel. Then select the seats you wish to restrict.
On the left-hand menu, assign them to a specific Channel.
-
You can define specific "Channel Keys" that allow your partners to access their dedicated inventory.
Good to know
One seating chart, one Palisis account
To ensure your bookings sync correctly, each Palisis account requires its own unique seating chart. Using the same seating chart across multiple accounts can cause technical conflicts. If you manage more than one account, please create a dedicated seating chart for each one rather than reusing an existing layout.
Why this matters:
Prevent overbooking: Reusing a chart can lead to synchronization errors.
Accurate reporting: Unique charts ensure that availability is tracked correctly for each specific account.
Mandatory publishing of changes
Any modification made within the Seats.io designer (such as renaming a row, moving a focal point, or changing a seat category) is not live until it is published. You must click the 'Publish' button in Seats.io before these updates will be reflected in your Palisis Box Office, Webshop, or mobile devices.
Auto-Sync for categories: Linking or unlinking Palisis categories triggers an automatic publish. No manual action is needed to update your category mapping.
Template and event matching
Every departure in Palisis requires a corresponding "Event" in Seats.io to act as a template. The first time you link a departure, you may encounter the "Default template not Found" alert.
-
The solution: Simply copy the exact template name provided in the Palisis alert, navigate to your Seats.io dashboard, and rename your event to match that string exactly. This establishes the link between the two systems.