Concerts

In the backend, you arrange rows, seats and seat types via a built-in generator. Seat types support freely definable distinctions like „love seat" or „accessible". Several seating plans per house are possible, e.g. main hall, small hall or foyer seating, depending on the event type. Template seating plans can be duplicated so you do not start from scratch for a special seating layout.

Per seating plan, you define seat categories (e.g. VIP, standard, balcony) with their own prices per event. Wheelchair places are a dedicated seat type and visualised clearly. Prices interact with the pricing rules, so they combine with membership discounts, target audiences or reseller pricing.

Press allocation in the first row? Sponsor seats for an opening? You block seats manually with a reason that stays traceable in the backoffice. In the online shop, a guest selection holds seats via a token for a short reservation window; afterwards they return to the pool. Sponsor reservations can be created with longer validity and closed manually.

Online shop and backend share the same seating plan with visual seat selection; real-time availability is synchronous across all channels. Resellers sell via ExperienceBank or the direct API from their own quota.

Seating-plan sales at POS 2.0 are in preparation. For houses that want to sell seats at the front desk as well, the seating-plan integration follows step by step.

As soon as the first tickets on a seating plan are sold, the plan is structurally locked. Changes to rows or seats are then blocked because they would create inconsistencies retroactively. New events on top of the same seating remain possible. Duplicating the seating plan as a template and adapting it for another tour is the clean path to leave the productive plan untouched.

If the generator is not enough, you upload an SVG file of your seating layout. go~mus reads the parameters automatically and makes the layout usable in the sales frontend and the backoffice. For complex seating, we adjust the SVG together on request.