Where stands.

A1 · Multiple locations and rooms

Admins can add and deactivate rooms for each location, assign rooms to occurrences, and view room names in event details. The system rejects room overlaps.

A2 · Shared calendar

The admin calendar shows all locations and can be filtered by location and type. The public calendar, also inside the website widget, can be filtered by location once there is more than one. On phones the page fits the screen and the week and month grids scroll sideways inside their own box.

A3 · Opening hours and exceptions

Regular opening hours per weekday plus exceptions for holidays or special days. The app and website show whether the venue is open today.

A4 · Places and rooms without double booking

Places with rooms are maintained in the admin. Overlapping reservations of the same room are rejected.

B1 · Events and event series

Single events and recurring series with place, room, category, images and description. Publishing makes them visible in the app and on the website without a developer.

B2 · One-day workshops

A workshop is an event with a single date, a participant limit and paid booking. There is no separate workshop type. For price tiers see D5.

B3 · Multi-day workshops

One booking covers every session of the workshop, and guests are checked in at each session. Check-in for these tickets needs an internet connection.

B4 · Events

A workshop and a party can be sold together as a combo. The workshop booking is checked in at each workshop session.

B5 · Parties

Parties are sold online with a guest limit and a secure QR ticket per booking. For price tiers see D5.

B6 · Festival or congress edition per year

Each edition gets its own public page with line-up, FAQ, info and a timetable by day and room. Editions are published and unpublished in the admin.

B7 · Contributors and exhibitions

Profiles for artists, speakers or exhibitors with their own types and links, shown on the event pages.

B8 · Artist portal

Artists propose events through their own portal. The team accepts or declines each proposal in the admin.

B9 · Giveaways

Guests enter a giveaway in the app. The team draws winners in the admin and exports the list.

B10 · Follow events, contributors and categories

Guests follow an event, a contributor or a category and get a push message when something new appears.

C1 · QR tickets and offline check-in

Every booking has a secure QR ticket. Staff scan per day and event, also offline; scans sync later.

C2 · Wallet passes

Tickets can be added to Apple Wallet and Google Wallet.

C3 · Free registrations (RSVP)

Free events take registrations with a guest limit. The team sees the guest list and checks guests in.

C4 · Participant limits

Each event has a participant limit, and group bookings count every person.

C5 · Automatic waitlist

Waitlist per event in signup order. A freed place goes to the next person automatically, who is notified, until the booking deadline.

C6 · Booking deadlines

Set per event how many minutes before the start bookings close. Later bookings are refused.

C7 · Cancellation deadlines

Set per event until when a cancellation is refunded. A later cancellation before the event frees the place but keeps the payment, pass units and membership credits.

C8 · Door roles

Own roles with rights per area, for example check-in only for the team at the door.

D1 · Guest checkout without an account

Guests book events and festival passes on your website with only their email address, online payment included. They get an email with a link to view their booking and ticket QR code and to cancel under the usual rules. If the address already belongs to a customer, the booking lands in that account. Memberships and value cards still need a login.

D2 · Tickets with price tiers

Prices can change by date (early bird) or after a number of tickets sold, for events, festival slots, passes, multi-visit passes and combos. Unpaid or cancelled orders free their ticket again.

D3 · Cancellation with refund/credit

Cancellations are refunded to the payment method or as a voucher, and pass units come back.

D4 · Discount codes

Percent and fixed-amount codes work for events, festival tickets, shop, multi-visit passes and combos. Codes can be limited to product types, dates and number of uses.

D5 · Vouchers

Value and product vouchers pay online for events, festival tickets, shop, multi-visit passes and combos. A used balance comes back when the order is cancelled.

D6 · Bring a friend / referral

Each user gets one referral code per organization. A new customer can claim one code, and both users receive a voucher after the referee’s first paid purchase.

D7 · Combo tickets

Several events can be bundled into one combo price. One payment creates all bookings, and cancelling the combo cancels them all and refunds the rest.

D8 · Single tickets at events

Each festival slot can have its own price tiers and ticket quotas. Otherwise the event price applies.

D9 · One cart, one payment

Passes, tickets and products go into one cart and are paid in one Stripe checkout, promo codes included.

E1 · Credit-based membership

Credit plans use the number of credits set for each event, per person. Fixed plans cover their linked events.

E2 · Credit allowance per period

Paid invoices refill credits once per billing period. A stored period marker prevents duplicate refills.

E3 · Notice periods

Cancellation schedules against the notice period and billing boundary.

E4 · Minimum terms

Cancellation cannot take effect before the minimum term ends.

E5 · Automatic renewal

Stripe renews active subscriptions by default. Non-renewing plans schedule an end date.

E6 · Freeze / pause periods

Members can pause and resume Stripe payment collection.

E7 · Upgrades / downgrades

Changing a plan updates the recurring Stripe price with proration.

E8 · Automatic dunning

Failed invoices mark memberships past due and trigger notifications.

Retry settings depend on each connected Stripe account.

F1 · Flea market stall requests

Create a market with date, area layout and number of stalls. Exhibitors request a stall in the app, the team confirms or declines, and requests wait on a waitlist when all stalls are taken.

F2 · Room rental inquiries

Guests send a rental request with preferred date and occasion. It lands with the team as a trackable case.

F3 · Stamp cards

A loyalty program for regulars in the app. A check-in adds a stamp automatically, staff can also stamp and redeem the reward by scanning a QR code.

F4 · Value cards

Prepaid value cards are sold in the app. Staff redeem the balance on site by scanning the card.

G1 · Customer profile

Customers can add or remove a profile photo and update a mobile phone number. Both are included in the personal data export.

G2 · Tags with bulk tagging

Create your own customer tags such as “regular” or “wedding couple”. Select participants in the list and add or remove a tag for all of them in one step, then filter the list by tag.

G3 · Reduced rates

Students and other reduced-rate customers upload a proof, and the reduced price only applies once an admin approves it. Until then the regular price applies. Value cards can require the same approved proof for their reduced price.

G4 · Communication

Email, push and in-app announcements.

No SMS or WhatsApp.

G5 · Newsletter integration

Connect your Brevo or Mailchimp list. Customers and members who agreed to marketing mail are added every hour. Anyone who withdraws consent or deletes their account is removed again.

G6 · Invoices

When invoicing is enabled, settled Stripe payments, including membership renewals, can receive numbered PDF invoices. A generic issuing API accepts source type, settlement reference, recipient and line snapshots. Payment refunds receive credit notes. Small businesses can issue invoices without VAT, and customers and admins can download PDFs.

Membership refunds do not create credit notes. PDF labels support German and English, while line descriptions stay in the module's language.

G7 · Participant master data

The venue keeps full records for every participant: name, contact details, address, birth date, matriculation or student number, customer card number, account holder and a stored IBAN that is only readable as its last four digits.

G8 · Shared inbox with tickets

Connected mailboxes turn incoming email into support tickets with status and assignee, so requests do not get lost.

G9 · Live notifications for the team

New tickets, bookings, stall requests and proposals appear in the admin without a reload. The menu shows badges with the number of open items.

G10 · Branding and app menu

Colors, logo and the app menu are set per venue in the admin.

G11 · Audit log

Admin changes are recorded with who did what and when.

H1 · Credit card

Cards are a Stripe Checkout default.

H2 · PayPal

Ready once PayPal is switched on in your Stripe account.

H3 · SEPA direct debit

Ready once SEPA direct debit is switched on in your Stripe account, for one-off payments and memberships. Late payment success or failure is handled.

H4 · Google Pay

Ready once Google Pay is switched on in your Stripe account.

H5 · Apple Pay

Ready once Apple Pay is switched on in your Stripe account.

H6 · One-off and recurring payments

One-off payments and recurring membership payments run through your connected Stripe account. Recurring SEPA and automatic payment retries are settings in your Stripe account.

I1 · Automated emails with customizable triggers

You create your own automatic emails: a welcome mail for new participants, a thank-you after payment or a birthday greeting. Each has its own delay and German and English text with placeholders such as the first name. Birthday mails only go to customers who agreed to marketing. Built-in reminders keep working.

I2 · Reactivation of inactive customers

You set up a win-back mail for customers who have not booked for a while, for example 30 or 90 days. Each customer gets it once per quiet period, and a new booking starts the count again. It only goes to customers who agreed to marketing.

I3 · Funnel tracking

Guests book right inside the website widget. Each step reaches your own Google Tag Manager as an event: calendar viewed, event viewed, booking started, sent to payment, and booking done for free events. Your site’s cookie banner stays in charge, and no personal data is sent.

Payment runs in a new tab, so a paid booking’s completion does not reach your Tag Manager (Meta still gets it, see I7). Our own booking pages load no tracking tags.

I4 · Cross-domain tracking and UTM

Campaign links (UTM source, medium and campaign) are saved with every web booking and appear in the booking export. The website widget passes your page’s campaign on, and its events land in your own analytics, so the visit stays on one domain. Festival pass orders do not keep the campaign yet.

I5 · Ad tracking

Connect your Meta pixel in the admin. Paid bookings made in the website widget are reported to Meta as purchases with their amount, straight from our server, so the payment tab no longer gets in the way. This only happens when your own pixel already ran on your site, so your cookie banner stays in charge. No email or IP address is sent.

No Google Ads conversions yet. Bookings made outside the widget and festival pass orders are not reported.

J1 · Event calendar in WordPress

A website widget embeds the public calendar into any page, including a WordPress Custom HTML block. Paste two lines; the calendar grows with its content, and guests book right inside it. Only payment opens in a new tab.

J2 · Individual workshops in WordPress

The same widget embeds a single event or workshop page, or one of its dates.

J3 · Voucher sales on the website

Guests buy gift vouchers on your website without an account, also inside the website widget. The voucher arrives by email with its QR code and remaining balance, and staff redeem it at the counter.

J4 · SEO, AEO, GEO

Every event page tells search engines and AI answers its dates, place, prices, performers and organizer, the calendar describes this week's dates, and every performer page describes the person, without running JavaScript. A sitemap lists the calendar, every public event, and each venue domain's robots.txt points search engines to it while keeping the admin and API out of the index. Limits: the calendar describes only the current week; later dates appear on the event pages.

J5 · Multilingual

Booking pages, the guest checkout, the calendar, emails and invoice PDFs follow the visitor's language in German or English, and the app and invoice PDFs also come in Spanish. Invoice line texts stay as issued.

K1 · Full REST API

The app already uses an interface for other software.

Most admin features are not yet open to other software.

K2 · Webhooks

Stripe payment updates arrive automatically.

Other tools cannot subscribe to updates yet.

L1 · Booking and subscription management

The app for iOS and Android supports bookings, tickets, wallet passes, payments and venue branding. Members can browse plans, subscribe through Stripe, check membership status, cancel under the plan terms and download invoices.

N1 · Booking export

One export of all bookings in a date range: event bookings, registrations and festival passes in a single list, as an Excel file or CSV. Each row shows the booking date, offering, name, e-mail, persons, status, price and payment status. The export contains only areas the admin may see, and every export gets an audit entry.

N2 · Reports for the tax advisor

A revenue and VAT report per month or year, split by tax rate with totals, as a spreadsheet. A DATEV booking batch (SKR 03 or SKR 04) for direct import by the tax advisor. Credit notes count negative, and every export gets an audit entry.

O1 · Merchandise sales

Own shop with products, variants, stock, online payment and QR pickup. For print-on-demand merch, the organization adds its Spreadshop or another merch store link on the brand page. The app shop and the website then link to it. The merch store prints, ships and takes payment. Orders placed there do not appear in MiVenti's orders, invoices or reports.

P1 · Full migration from third party

No third party import yet. Customers come first, then active subscriptions, which need a migration path into the existing subscription plans (E). Remaining balances move to multi-visit passes. Vouchers move to shop vouchers. SEPA mandates: not checked, depends on whether third party can hand them over to Stripe.

P2 · Exit strategy

Admins download every record of the venue as one ZIP archive with a spreadsheet file per table: events, bookings, passes, subscriptions, vouchers, orders, invoices and all linked customer accounts. Passwords, keys and tokens stay out, and every export is logged. Each customer can also export their own data.