go~mus + shop

The four routes are not mutually exclusive, they complement each other. They all run on the same go~mus back office, so you can use them in parallel and go deeper any time:

• A standalone shop for your main sales, plus the bundle on a campaign or exhibition landing page.
• Web components on your main pages, with newsletters and third-party pages linking into the shop.
• The bundle for your visitors, the API for resellers, platforms and your own apps.
• The API as the foundation: the same data the shop, bundle and web components show, you can also fetch directly.

You do not have to commit once and for all. Start turn-key and go deeper later, or combine from the start whatever fits your venue.

Across all four routes you sell the full range of products you configure in the go~mus back office:

• Day tickets for entry on the selected day
• Time-slot tickets with a slot picker, e.g. for high-traffic special exhibitions
• Individual offers with date and quota: public guided tours, workshops, readings, concerts without a seating plan, talks, family and school-class formats
• Group offers where availability results from size, duration and time windows rather than fixed dates
• Group requests right in the shop: from go~mus 5.0 group requests can be placed directly in the shop too, for example when the preferred date is sold out
• Events with a seating plan: seat-accurate sales for concerts and seated rooms
• Annual passes and season tickets, with personalisation afterwards (photo upload, name fields)
• Gift vouchers as value products your visitors can give as a present
• Donation campaigns with campaign picker and a free amount, a flow of its own without a ticket

All four routes are multilingual, with URL-based locales like /de/ and /en/ in the standalone shop, a language choice that follows the page for the bundle and web components, and multi-locale parameters in the API. German and English are the default, additional languages such as French, Italian, Dutch or Luxembourgish can be added on demand. Translations live in the go~mus back office and the sales surface delivers them automatically.

Visitors check out either as a guest or with an account. The standalone shop and web components ship a full self-service area:

• Registration with email confirmation, login, password reset
• Profile maintenance (name, address, phone, password change)
• Order history with detail view and invoice IDs
• Status per order (paid, pending, failed)

The embedded bundle deliberately sells as a guest only, without an account. That keeps the integration lean. If you need accounts, the standalone shop or the web component route is the way to go.

Integration with selected payment service providers or processing through our own embedded payment, go~pay. Live in production: Adyen for credit cards and other payment methods. You choose the methods and the styling of the checkout.

Discount codes redeem in the basket and are configured in the go~mus + promotions add-on. Gift vouchers your visitors buy redeem in the same place.

Hotels, tourism partners and event organisers book your tickets, events and group offers via a dedicated B2B path. Billing per order or via consolidated invoice.

Several houses under one umbrella? A single go~mus back office serves multiple museums or multiple brand-separated shop frontends. Each brand keeps its own domain, its own branding and its own languages while data flows together centrally.

The standalone shop is statically pre-rendered. In practice: every page sits as ready HTML on the server and ships without wait. Lighthouse performance on static pages reaches top scores in our live shops, time-to-first-byte is short, search engines index without JavaScript rendering.

Accessibility applies to the delivered interfaces: standalone shop, bundle and web components. We align with BITV 2.0 and WCAG 2.1 Level AA, test with Lighthouse, axe DevTools and manual keyboard walkthroughs. For your own content (images without alt text, embedded third-party widgets) your contribution stays needed.

What is the go~mus shop?

The go~mus shop is online ticket sales for museums and cultural institutions. You bring the same sales onto your website in four ways: a turn-key shop on your domain, an embedded bundle, individual web components, or the REST API directly. All four run on the same go~mus back office.

What is a bundle in go~mus?

A bundle is a pre-built JavaScript file you embed into your existing website with a single script tag. It shows the calendar, cart and checkout as an overlay, sidebar or inline, without changing your CMS. Not to be confused with wrapper tickets: those are a ticket type (one main ticket that groups several sub-tickets), not an integration route.

Is withdrawal included in the bundle?

Yes. Since 19 June 2026 many online shops need a withdrawal button, and the bundle ships it: withdrawal is a standalone step in the booking, no cart. There is nothing extra to embed.

What are web components?

Web components are individual booking building blocks as HTML elements (<go-*>) that you place freely in your own CMS and style entirely with your CSS. More control than the bundle, meant for custom frontends.

What is the go~mus API?

The go~mus API is a REST API (v4) that delivers all booking data directly: availability, tickets, events, guided tours and orders. The route with the most control, for custom frontends, platforms and resellers.