Skip to content
Articles on Web Development

Online ticketing for a museum: what you really need

Selling museum tickets is not like selling a T-shirt. There are time slots, capacity limits and checks at the entrance. Here are the features you can't do without and the ones worth considering.

· 4 min read

In this article

Want to talk it through for your business?

Message us on WhatsApp (opens in a new window) or by email
In this article

    In short: Online ticketing for a museum needs time slots with capacity limits, ticket types (full price, concession, complimentary, groups, schools), tickets with a signed QR code, entrance checks from a phone or tablet, confirmation and reminder emails, and a way to handle changes and refunds. Only the necessary data is collected and payments go through a certified payment provider.

    A museum doesn't sell a product that gets shipped: it sells entry at a set time to a space with limited capacity. An online ticketing system designed for a shop can't handle that. Specific features are needed. And the staff at the entrance must be able to use them without lengthy training.

    The essential features

    Time slots with capacity

    Each slot has a maximum number of visitors. When it is full, it disappears from the options. This avoids queues and keeps within the safety limits of the rooms. Capacity can vary by day and by route (guided tour, temporary exhibition).

    Ticket types

    Full price, concession, complimentary, family, group and school. Each with its own price and rules. For concessions that depend on eligibility (age, student status), the check happens at the entrance and the rule must be explained before purchase.

    Tickets with a QR code

    After payment, the visitor receives the ticket with a QR code. The code must be signed so that it can't be forged. A code that anyone could make up offers no protection. Each ticket is valid once.

    Entrance checks

    Whoever is on the door scans the code with a phone or tablet and sees straight away whether it is valid. A ticket that has already been used is rejected. This is the part that has to work every time: test it on a slow connection and in poor light before opening.

    Confirmation and reminder emails

    A clear confirmation with the date, time, ticket type and directions. A reminder the day before reduces the number of visitors who forget to come.

    Changes and refunds

    Changing the date or time of a ticket and handling refunds according to the museum's rules. The fewer requests that reach the office, the better.

    Features to consider

    • Multiple languages for purchasing and for emails.
    • Season tickets and memberships for repeat visitors.
    • Selling other products such as catalogues, special tours or add-on services.
    • Group and school bookings with dedicated handling.
    • Connection to the on-site ticket office so that there is a single capacity count.
    • Reporting: visitors by day, slot and ticket type, and takings.

    Privacy and payments

    Ask only for the data you need: name and email are often enough. Payments are handled by a certified provider and the site does not store card details (see online payments). The privacy notice must explain how long the data is kept.

    How the work is organised

    1. Rules. Opening hours, capacities, ticket types, concessions and refund policies, written down.
    2. Building the ticketing system and testing it with real cases (a group, a concession, a ticket already used).
    3. Short training for the door staff, with a one-page guide.
    4. Gradual launch with a share of the tickets, then everything.
    5. Reviewing the data after the first few weeks to adjust capacities and times.

    Further reading: custom-built platforms and communities · online payments · privacy for an online shop

    Frequently asked questions

    What does an online ticketing system for museums need?

    Time slots with a maximum capacity, ticket types with their own rules, a QR code that can't be forged, entrance checks, confirmation and reminder emails, handling of changes and refunds, and reports.

    Why does the QR code need to be signed?

    A code that anyone could make up offers no protection against forgery. A signed code lets staff at the entrance verify that the ticket is genuine and reject a second use.

    What data is collected from visitors?

    Only what is needed, often just name and email. The privacy notice must explain how long the data is kept, and payments go through a certified provider.

    Let's talk

    Need to sell tickets online for your museum or cultural site?

    We work out the rules, capacities and entrance checks together with you.

    Related service: Custom platforms and communities