🌟 Option for seating charts/assigned seating.

[mnfctrdinitaly]

Is your feature request related to a problem? Please describe. No. This is not a bug or problem, just a missing feature.

Describe the solution you'd like Perhaps a venue admin panel that allows for the generating of a seating chart and then the ability to assign that chart to an event.

Describe alternatives you've considered Not sure how else to achieve this.

Additional context This feature helps with pre-sales as patrons can select their seats and are incentivized to buy ahead of time.

[daveearley]

Thanks for the suggestion @mnfctrdinitaly! Seating selection is on the long term roadmap.

[Riredus]

I want to support this feature request. A seating chart would be an outstanding feature in comparison to most other tools.

[daveearley]

@Riredus and everyone interested,

I'm starting research into this and would love to hear about your use cases. A few questions:

• How many floors or levels does your venue typically have?
• Do you sell tickets for multiple ticket types in a single event?
• How detailed or complex are your seating layouts? Do you have unique design requirements such as irregular shapes, zones, or accessibility needs?
• Would you prefer to upload existing floor plans (e.g., PDF, image) or create them directly within the app?

Also, if you know of existing implementations that would be good to reference, open-source tools, or any other relevant information, please share!

Thanks in advance!

[Riredus]

Hi Dave,

great to hear that. My usecase is a small non-profit club that does three events with ~100 guests each.

We have each seat is priced the same with discount options for students and free entry for some people.

I have attached a picture of our current floor plan.

I would probably prefer to create the floorplan in the app. I assume it would be easier to integrate instead of overlaying an image with the UI. With ~100 seats that is not a big effort in comparison to bigger venues so other opinions might differ.

I have not seen good open source implementations yet. The picture i have attached is from a tool called ticketleo.

The free version we are currently using has huge problems with misleading ad buttons which caused problems for a lot of elderly guests.

Thanks again for your work, enjoy the coffee and feel free to reach out if you need someone for testing.

Best regards Tobias

Dave Earley @.***> schrieb am Mo., 9. Dez. 2024, 23:55:

@Riredus https://github.com/Riredus and everyone interested,

I'm starting research into this and would love to hear about your use cases. A few questions:

• How many floors or levels does your venue typically have?
• Do you sell tickets for multiple ticket types in a single event?
• How detailed or complex are your seating layouts? Do you have unique design requirements such as irregular shapes, zones, or accessibility needs?
• Would you prefer to upload existing floor plans (e.g., PDF, image) or create them directly within the app?

Also, if you know of existing implementations that would be good to reference, open-source tools, or any other relevant information, please share!

Thanks in advance!

— Reply to this email directly, view it on GitHub https://github.com/HiEventsDev/Hi.Events/issues/39#issuecomment-2529710671, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMOVYBXAHLLGDST2KZ2USN32EYNW3AVCNFSM6AAAAABJLJTCA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRZG4YTANRXGE . You are receiving this because you were mentioned.Message ID: @.***>

[velocity23]

+1 on this. In response to your questions:

1. For the events I do, usually just one, but I rarely see venues with more than 3 floors. That said, often these are "flattened" in seatmaps because it's less confusing for users (ie. the upper levels are just shown as if there were behind the ground level, with some text to indicate that).
2. Not often, I would say. But most implementations I see require the customer to select the quantity of tickets first, and then pick seats to correspond with that.
3. Almost always to some extent. Theatres especially can have weird gimmicks like gaps for the sound desk, strange layouts for boxes, etc. Accessible seating and restricted view also has to be indicated in some form.
4. No need for uploading PDF floorplans imo, but it would be cool to be able to export them and/or save them separately to events so they can be reused.

The best implementation I've seen in my research has been Humanitix. It's a really good mix of not having to drag-and-drop every single seat, but still being able to make irregular shapes.

[meilechwieder]

I think ticket tailor did a pretty good job with implementing seating charts

https://help.tickettailor.com/en/articles/4096543-how-to-create-a-seating-chart

[daveearley]

@meilechwieder

Ticket Tailor’s implementation is fantastic, but unfortunately, a seating tool of that caliber is far beyond what’s feasible for Hi.Events given our current resources.

Any seating implementation we introduce will be very simple initially. However, over time, I’d love to see it evolve into a more powerful tool, especially since there are currently no open-source solutions in this space.

[meilechwieder]

Hi, was this added to the roadmap? If yes, is there a rough eta?

[daveearley]

Hi, was this added to the roadmap? If yes, is there a rough eta?

There is no timeline for this, unfortunately. It's a massive undertaking and other features are taking priority.

[meilechwieder]

Hi Dave,

I actually believe that at a basic level, this is fairly simple to implement:

1. in the ticket setup wizard, we have a checkbox for "Assigned Seating"
2. we have 2 inputs, a) number of rows of seats b) number of columns
3. we display a map of boxes based on the number of rows and columns
4. we allow the user to select which ones are not sold/reserved/unavailable
5. at checkout, we show the attendees the map, allow them to click to select, as well as showing green boxes for the available ones and red for reserved/sold
6. in db, this should be a simple table of columnXrow (for ex. "A10") and a status of the seat, plus a relationship to which ticket/order it belongs.
7. in ticket pdf we print the column/row

On Sun, May 25, 2025 at 12:07 PM Dave Earley @.***> wrote:

daveearley left a comment (HiEventsDev/Hi.Events#39) https://github.com/HiEventsDev/Hi.Events/issues/39#issuecomment-2907917103

Hi, was this added to the roadmap? If yes, is there a rough eta?

There is no timeline for this, unfortunately. It's a massive undertaking and other features are taking priority.

— Reply to this email directly, view it on GitHub https://github.com/HiEventsDev/Hi.Events/issues/39#issuecomment-2907917103, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOS7IR2QREFHKEUGABLZGZ33AHTFXAVCNFSM6AAAAABJLJTCA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMBXHEYTOMJQGM . You are receiving this because you were mentioned.Message ID: @.***>

[meilechwieder]

Hi Dave,

At a basic level, I think implementing assigned seating is relatively straightforward. Here's how it could work:

In the ticket setup wizard, we include a checkbox labeled "Assigned Seating." 2.

If checked, two input fields appear:

  *Number of rows*
  -

  *Number of columns*
  3.

Based on those inputs, we generate a grid (seating map) with labeled boxes (e.g., A1, A2, B1, etc.). 4.

The organizer can then click on individual seats to mark them as unavailable, reserved, or not for sale. 5.

During checkout, attendees see the seating map:

  *Green* seats = available
  -

  *Red* seats = sold/reserved
  -

  They can click to choose their seat.
  6.

In the database, each seat is stored with:

  A label (e.g., "A10")
  -

  A *status* (available, reserved, sold)
  -

  A reference to the related *ticket or order*.
  7.

On the final ticket (PDF), we display the selected seat (e.g., "A10") so attendees know exactly where they're sitting.

On Sun, Jun 1, 2025 at 2:34 AM Meilech Wieder @.***> wrote:

Hi Dave,

I actually believe that at a basic level, this is fairly simple to implement:

1. in the ticket setup wizard, we have a checkbox for "Assigned Seating"
2. we have 2 inputs, a) number of rows of seats b) number of columns
3. we display a map of boxes based on the number of rows and columns
4. we allow the user to select which ones are not sold/reserved/unavailable
5. at checkout, we show the attendees the map, allow them to click to select, as well as showing green boxes for the available ones and red for reserved/sold
6. in db, this should be a simple table of columnXrow (for ex. "A10") and a status of the seat, plus a relationship to which ticket/order it belongs.
7. in ticket pdf we print the column/row

On Sun, May 25, 2025 at 12:07 PM Dave Earley @.***> wrote:

daveearley left a comment (HiEventsDev/Hi.Events#39) https://github.com/HiEventsDev/Hi.Events/issues/39#issuecomment-2907917103

Hi, was this added to the roadmap? If yes, is there a rough eta?

There is no timeline for this, unfortunately. It's a massive undertaking and other features are taking priority.

— Reply to this email directly, view it on GitHub https://github.com/HiEventsDev/Hi.Events/issues/39#issuecomment-2907917103, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOS7IR2QREFHKEUGABLZGZ33AHTFXAVCNFSM6AAAAABJLJTCA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMBXHEYTOMJQGM . You are receiving this because you were mentioned.Message ID: @.***>

[cgonIT]

@Riredus and everyone interested,

I'm starting research into this and would love to hear about your use cases. A few questions:

• How many floors or levels does your venue typically have?
• Do you sell tickets for multiple ticket types in a single event?
• How detailed or complex are your seating layouts? Do you have unique design requirements such as irregular shapes, zones, or accessibility needs?
• Would you prefer to upload existing floor plans (e.g., PDF, image) or create them directly within the app?

Also, if you know of existing implementations that would be good to reference, open-source tools, or any other relevant information, please share!

Thanks in advance!

Hi @daveearley , answering your questions with my needs:

• How many floors or levels does your venue typically have? I only manage outdoor events, like small campings or similar. Camper-Van events. So only one floor.

• Do you sell tickets for multiple ticket types in a single event? Usually we offer 2 types: plot with electricity, and plot without electricity.

• How detailed or complex are your seating layouts? Do you have unique design requirements such as irregular shapes, zones, or accessibility needs? You can imagine, like a parking area or camping plots structure. Most of the plots have similar size so no problem on this.

• Would you prefer to upload existing floor plans (e.g., PDF, image) or create them directly within the app? In my case it doesn't matter, but create them directly and the option to save as "template" for future events would be nice.

[3zero2]

Can I chime in with my use case please?

How many floors or levels does your venue typically have? Usually two floors, stall and balcony. Sometimes 3 floors.

Do you sell tickets for multiple ticket types in a single event? Yes, usually each seat can be assigned to a pricing point. So when creating an event you also enter the price points that will be used (say Gold, Silver and Bronze) and then each ticket is assigned to one of these price points.

How detailed or complex are your seating layouts? Do you have unique design requirements such as irregular shapes, zones, or accessibility needs? Not usually. Theatres are usually kind of box shaped with seats inside.

Would you prefer to upload existing floor plans (e.g., PDF, image) or create them directly within the app? Don't mind creating within the app if that is simpler to implement. What is crucial is that a background image can be added, so as to show where the stage, exits, entrances and different sections are located.

[rkkoszewski]

What about using the same seats format as in Pretix? The https://seats.pretix.eu/ tool generates a JSON file that describes the seating setup. Pretix itself is also open source and can be found here: https://github.com/pretix/pretix/