# One platform instead of five separate tools — and now your website too

  [Home](https://mijnevent.nl/en) / [Blog](https://mijnevent.nl/en/blog) / One platform instead of five separate tools — and now your website too   modules website organisers 

# One platform instead of five separate tools — and now your website too

 A ticket shop here, a web shop there, the membership list in a spreadsheet and a website built by yet another agency. What that collection really costs you, and what changes once it is one system with one Mollie connection.

 [Jasper Koers](https://mijnevent.nl/en/author/jasper-koers) · 29 August 2026 · 9 min read 

  ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/een-platform-in-plaats-van-vijf-losse-tools.webp)  Photo: [Margo Evardson](https://unsplash.com/@stadinstudio?utm_source=MijnEvent&utm_medium=referral) / [Unsplash](https://unsplash.com/?utm_source=MijnEvent&utm_medium=referral)     In short

- Separate tools do not just cost you five subscriptions, but also five exports, five processor agreements and five suppliers pointing at each other when something breaks.
- MijnEvent runs sixteen product lines — from rentals and parking to memberships, merchandise, food trucks and anonymous visitor feedback — on the same account, the same subdomain and the same Mollie connection.
- Every module charges a flat amount per transaction instead of a percentage: €0.50 per paid ticket, €0.75 per parking reservation, €0.35 per food truck order. Free tickets are always fee-free.
- The Website module is new: you have your site built or renewed — from €450 one-off plus €49 per month — with your ticketing, rentals and memberships built straight in.
- The real advantage is in what only works when it is one system: one scanner at the gate, one visitor database, one financial overview and one processor for your GDPR records.

  Almost no organisation deliberately chooses five separate systems. It just grows that way.

First came the website, built by a local agency. Then ticket sales, because that agency could not do those. The year after, a web shop for the club shirts, because the ticketing system did not know what a product was. The membership list was already in a spreadsheet and stayed there. And since last year there has been a separate till app at the bar, because the drink tokens ran out.

Five systems, five login screens, five invoices. And above all: five files with the same people in them, none of which know about the others.

# What separate tools really cost

The subscriptions are the least of it. What it actually costs appears on no invoice at all:

**Exports.** You want to know who is coming. That means a CSV from the ticketing system, a list from the web shop, the member list from the spreadsheet, and then deduplicating by hand. Every event, all over again.

**Volunteers.** At the entrance someone stands with a phone for the tickets, a printed member list for the members and a second sheet for whoever booked parking space 12. Three checks, three chances of error, one queue that stops moving.

**Your GDPR records.** Every tool that processes personal data needs a processor agreement and a line in your record of processing activities. With five tools that is five agreements, five retention periods and five parties where a subject access request can land.

**The blame question.** When the link between your site and your ticket shop stops working, the agency points at the ticketing system and the ticketing system points at the agency. You are in the middle, and your event is in three weeks.

**Percentages that stack.** Most separate tools charge a percentage: of the ticket price, of the web shop revenue, of the bar takings. That is precisely the model that runs harder the better you do.

# What now fits on a single account

MijnEvent started out as a ticketing platform, but that has not been what it is for a while. Here is what now runs on the same account, the same subdomain and the same Mollie connection:

ModuleWhat forPriceTicket salesThe basics: events, ticket types, capacity, waiting list€0.50 per paid ticket, or €0.25 with the Organiser plan[Rentals & reservations](/en/modules/rentals)Boats, bikes, courts, rooms, equipment€5.00 per booking, or €0.50 with the year licence[Reserved seating](/en/modules/reserved-seating)Floor plans for theatres and cinemasFree — no cost per seat[Memberships & season passes](/en/modules/memberships)Dues, automatic renewal, membership card in the walletYear licence €99 + €0.25 per collection[Merchandise & web shop](/en/modules/merchandise)Shirts, club gear, local products, collected at your event€0.50 per order[Food trucks & mobile catering](/en/modules/food-trucks)Ordering at the stall or the bar, a till screen per outlet€0.35 per order[Parking & camping pitches](/en/modules/parking)Sell pitches in advance, scan on number plate€0.75 per reservation[Courses & workshops](/en/modules/courses)Series with one enrollment and one pass€0.50 per enrollment[Donations & fundraising](/en/modules/fundraising)A donation page and a donation field in the checkout0% fee on donations[Event feedback](/en/modules/attendee-feedback)Anonymous feedback, only to the people who actually came€10 per round, the first one free[Attendee details](/en/modules/attendee-details)Dietary needs, size, company name — asked after the purchase€50 per event, the first one free[Attendee mailings](/en/modules/attendee-mailings)Mail exactly the right group, without export listsFree around your event[Safety & permit](/en/modules/safety-permit)Live view of your inflow, evidence for the councilFree — included[Newsletter integration](/en/modules/newsletter-integration)Opt-in at checkout, straight into your own serviceFree — included[Local vouchers & city cards](/en/modules/city-cards)Local vouchers that keep the money in town€499 per year + €0.35 per card[Website](/en/modules/website)Have your site built or renewed, with your modules in itFrom €450 one-off + €49 per monthTwo things are still being built: [cashless consumptions](/en/modules/cashless) — topping up a balance and paying at the bar with your phone — and [Minty](/en/modules/minty), the AI assistant. They are listed here because we name them as they are, not because you can switch them on tomorrow.

Everything that is available shares the same foundation: a flat amount per transaction instead of a percentage, and money that lands directly in your own Mollie account rather than with us first. Free tickets, free bookings, deposits and donations are always fee-free.

# New: your website is part of it now

The last missing piece was the place your visitors arrive: your own website.

With the [Website module](/en/modules/website) you have it built or renewed — custom-made, with a content management system you operate yourself, on your own domain and in your own branding. Your MijnEvent modules run inside it directly: a visitor buys a ticket without leaving your site, a member books a court in the same place, a student enrols without going anywhere else.

Build costPer monthWith an upfront investmentfrom €450€49Without an upfront investmentnone€119 (min. 36 months)The monthly amount covers hosting, security updates, monitoring and support, and is invoiced per calendar year. Design and build are done by Coding Agency, the studio that also made MijnEvent; the integration, the wallet passes and the on-site check-in come from MijnEvent. One point of contact, one invoice.

Already have a site that is dated? Renewing it is almost always wiser than starting over — provided all your old web addresses are properly redirected, because that is what your search visibility hangs on. The full story is on the [website development page](/en/website-development).

And if you only want ticket sales on your existing site, you do not need anything built: [one line of code places the widget](/en/blog/connect-ticketing-to-your-website), checkout included.

# Four organisations, four combinations

The nice thing about modules is that almost nobody uses the same set.

**A museum** sells admission tickets with time slots, rents out the hall for corporate drinks, sells catalogues and museum cards in the web shop, and collects annual dues from the Friends of the museum. Four product lines, one visitor database, one financial overview. The [website](/en/website-for-museums) shows the calendar and the exhibitions, with ticket sales built into it.

**A club** does it the other way round: the basis is membership administration with automatic collection and a membership card in the wallet, and on top of that a few events a year where members get in free and outsiders pay. The bar committee sells club clothing through the same web shop. The [club website](/en/website-for-clubs) shows the fixture list next to the sign-up form.

**A festival** stacks the highest: tickets, camper pitches and camping fields, food trucks with their own tills, merchandise, and a safety dashboard that runs on the scans you are doing anyway. At the gate you scan [everything with one app](/en/blog/check-in-and-qr-scanning) — ticket, camper pitch, membership card. Afterwards, the feedback module sends one anonymous question to the people who were actually there.

**A theatre or music venue** sells numbered seats on a floor plan, sells season passes and gift cards, and rents the hall to third parties. The [theatre audience](/en/website-for-theatres) sees one programme page, not three systems.

# What only works when it is one system

This is the part you do not rebuild with integrations.

**One scanner at the gate.** The steward scans a QR code and the app works out what it is by itself: a ticket, a parking permit, a membership card or a course pass. No second device, no second app, no printed list beside it.

**One visitor database.** Someone who bought a ticket, became a member and ordered a shirt is one person in your overview — not three rows in three systems. That is the difference between a mailing that is right and a mailing that arrives three times.

**One financial overview.** Ticket revenue, rentals, web shop and catering in one report, with one VAT record underneath and one Mollie account everything arrives in.

**One processor.** One processor agreement, one retention period, one place where a GDPR request comes in and gets handled. At your board's next privacy question that saves more time than you would think.

**One cost model.** Flat amounts per transaction, no percentage that grows with your revenue. What that saves over a season is worked out in [the second bill](/en/blog/payment-costs-ticket-sales-the-second-bill).

# When separate tools do make sense

Fair is fair. If you run one small event a year and nothing else, a free ticket shop next to your existing site is perfectly fine — a platform would be solving a problem you do not have.

And if you have a website that works well, you do not need to replace it to sell online. The widget simply goes on it.

The tipping point is where you need your second system. Not because one platform is inherently better, but because the second tool introduces the export work, the second processor agreement and the second queue at the entrance. And the third doubles that again.

# How to start

You do not have to move anything all at once. You start with ticket sales and add what you need each season — most organisations take two to three years before their set is complete.

Modules are activated per organisation, so there is always a short conversation first about what fits. The same goes for the website: one conversation about which pages, which modules and whether an existing site comes along, and out of that comes a fixed price before anything is built.

What will not happen: sitting there at the end of the season deduplicating four exports to work out who actually showed up.

   Frequently asked questions

## Frequently asked questions

## What does 'modular' mean at MijnEvent exactly?

  You start with ticket sales and switch on the product lines you need: rentals, parking, merchandise, memberships, courses, food trucks, donations, feedback or a website. Every module runs on the same account, the same subdomain and the same Mollie connection, and appears in the same dashboard. You only pay for what you use.

## Can I use a single module without selling tickets?

  Yes. A marina that only rents out boats, a club that only collects membership fees or a municipality that only issues a local voucher use the module without ever selling a ticket. Ticket sales are the platform's starting point, not a requirement.

## What does it cost to use several modules?

  There is no platform subscription and no setup cost. You pay a flat amount per transaction: €0.50 per paid ticket (€0.25 with the Organiser plan of €14.95 per event), €0.75 per parking reservation, €0.50 per web shop order, €0.35 per food truck order. Donations carry a 0% fee. Two modules have an optional year licence that lowers the per-use rate.

## Is the website really part of it, or is that a separate agency?

  Design and build are done by Coding Agency, the studio behind MijnEvent. The link with your ticket sales, the wallet passes and the on-site check-in come from MijnEvent. You have one point of contact and one invoice, and the site runs your modules directly.

## Do I have to move everything at once?

  No, and that is usually unwise anyway. Most organisations start with ticket sales and add a module each season: members first, then parking, then the web shop. Modules are activated per organisation, so there is always a conversation first.

  [    Back to blog ](https://mijnevent.nl/en/blog) 

  MijnEvent

## Read more

 [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/gdpr-visitor-data-events.webp) gdpr 

 Jasper Koers · 26 August 2026 · 8 min read

## GDPR for event organisers: handling visitor data properly

You collect names, e-mail addresses and payment details. That comes with obligations — here are the ones that matter, in plain language.

 ](https://mijnevent.nl/en/blog/gdpr-visitor-data-events) [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/verloting-bingo-op-je-evenement-wat-mag.webp) legislation 

 MijnEvent · 24 August 2026 · 11 min read

## Raffles and bingo at your event: when Dutch gambling law kicks in

A tombola at the parade, a bingo night at the community hall, raffle tickets sold alongside your entry tickets — it all looks harmless, but the Dutch Gambling Act is unambiguous. What is allowed without a licence, what you apply for at the town hall, and where gambling tax comes in.

 ](https://mijnevent.nl/en/blog/raffles-and-bingo-at-your-event-dutch-rules) [ ![](https://regify-mijnevent.s3.eu-central-1.amazonaws.com/blog/covers/what-does-a-ticketing-platform-cost.webp) pricing 

 MijnEvent · 24 August 2026 · 5 min read

## What does a ticketing platform cost?

Commissions, service fees, payment costs and subscriptions: how to work out what selling tickets really costs you — with worked examples for 100 and 500 tickets.

 ](https://mijnevent.nl/en/blog/what-does-a-ticketing-platform-cost) 

   MijnEvent

## Ready to get started?

Create a free account and sell your first tickets today.

 [Start free](https://mijnevent.nl/registreer) [Pricing](https://mijnevent.nl/en/pricing)