Function

Combi-tickets

One ticket valid in multiple houses. Out of the box within a single instance, across separate instances or third-party providers via the entry add-on.

One ticket, several houses

A combi-ticket grants admission to several houses with one sale and one barcode. Holders redeem it in any order; each participating house scans on its own. From the visitor view a single product, from the house view a shared pass.

Within a single instance, go~mus supports this out of the box. Across instance or provider borders, the logic runs through the go~mus + entry add-on, which dispatches the barcode pool between the connected systems.

In a network: several houses, one instance

For networks whose houses share a single go~mus instance, the combi-ticket is a pure configuration matter. You define which houses participate and which ticket types the combi-ticket covers. Sale, admission and reporting run through the standard paths, no additional add-on required.

Useful for foundations with several locations, network tenants and house families that maintain their tickets together anyway.

Across instances and providers

For a pass that spans multiple separate go~mus instances or other point-of-sale and ticketing providers, the entry add-on takes care of the dispatch. The barcode is registered in the entry pool and shared with the participating systems. Each house scans with its own setup, results flow back. No foreign backoffice data leaves its instance.

Other point-of-sale and ticketing providers hook in via the entry API. This way, a combi-ticket can also be redeemed by houses that do not run go~mus.

Example: MuseumsPass Berlin

The MuseumsPass Berlin is sold by one participating house and grants admission at every participating house. Most houses run go~mus, a few use other point-of-sale or ticketing systems. Through the entry integration, the pass distributes its admission rights to all participating houses, regardless of the local stack. Visitor view: one pass, many houses. Operational view: clean settlement between houses.

Sale, admission, settlement

The combi-ticket is sold at the POS or in the online shop of the issuing house. Admission is scanned by all participating houses with their usual setup. Settlement between the houses follows agreed distribution rules, for example by admission frequency or a fixed share per pass. Reports show, per pass, which house redeemed a sub-ticket when.

Bundles within your own house

Family tickets, multi-day passes and other bundles within the same instance are not combi-tickets but wrapper tickets. More on wrapper tickets.

Get to know go~mus

Schedule a personal presentation. We will help you integrate go~mus into your workflow and support you in connecting your existing infrastructure.

Get in touch