Examples

Build an event ticket product with Melta - ticket sales, door check-in and waitlist in your own product

For clubs, organisers, studios and teams who want to sell tickets for their events without a third-party ticket shop in between. You describe events, categories and prices in plain language; Melta builds the product with checkout, PDF tickets and check-in, puts it online and runs it.

What such a product can do

A ticket product is more than a pay button next to a date: it knows dates and seats, sells in categories, sends the ticket, helps at the door and hands you the list. The concept records which of these modules yours needs.

Events with date and capacity

Every event has a date, venue, description and a fixed number of seats. Once capacity is reached, the date is sold out by itself.

Ticket categories

Early bird, regular, reduced, members: each with its own price and allotment. You change prices later by chat.

Checkout

Pick a date and category, pay by card, done. Buyers see your product as the merchant, not Melta; no contract of your own with a payment provider.

Tickets as PDF with a scannable code

The ticket goes out by email as a PDF attachment under your product's name, with the code that is read at the door.

Check-in at the door

A phone view: scan the code or search a name, mark the ticket as redeemed, see remaining seats. Door staff get a login with exactly that role.

Waitlist

When a date is sold out, interested people join the list. When seats free up, you notify them in order by email from the product.

Attendee list export

For the organiser: all purchases per date with category, payment and check-in status, inside the product and as a download for the day itself.

Melta has not built a ticket shop as an example product so far. A related example product is SOMA Yoga Zürich: a class schedule, bookings with a capacity per class, subscriptions. Date, seat and payment follow the same pattern.

How Melta builds it

Describe - You say in your own words which events you run, how many seats, which categories at which price, and who stands at the door. Melta asks at most four questions, none technical.
Read the concept - From that comes a concept in plain language. You change it by chat until it fits.
Build - When you approve, the build starts, paid from the credits of your plan. Melta builds the whole product: interface, logic, accounts, database, payments, email, legal pages, typically within 24 hours. You get an email when it is done.
Test the preview - Your private preview comes with demo data and named test logins. You buy a ticket with test data, open the PDF and redeem it at check-in. No real money moves.
Go live - Going live takes seconds, no rebuild. Melta first checks that your imprint details are complete and your payout account is connected. You choose which preview data to carry over and can roll back to the previous live version.
Change by chat - A new category, a second date, remaining seats on the start page: write it to your product's editor, watch it work, step in if needed, see the preview update live, then deploy to preview or live from the chat. Change runs are included in every plan.

What comes with it

Around the sale, Melta operates what you would otherwise organise piece by piece. Payments: one-time purchases and, for a season pass say, subscriptions; customers pay inside the product, and payouts go to the bank account you enter with your business details in Melta. Email: confirmations and tickets go out under your product's name, from no-reply@yourproduct.melta.ai or your own domain. Domain: a melta.ai subdomain, from the Growth plan your own, bought through Melta or connected. Legal pages: imprint, privacy policy and terms from your operator details, aimed at Switzerland, Germany and Austria, editable without a rebuild; general information, not legal advice. Cookieless analytics with campaigns and the funnel from visit to purchase, so you see which announcement sold tickets. The support inbox at support@yourproduct.melta.ai sorts questions automatically; replies to ticket emails land there. Plus hosting on a globally distributed network, error monitoring, spam protection for logins and forms, and layouts checked at 390 pixels wide before every release, because at the door the phone is the till.

You own what runs.

What it costs

A concept uses only a few credits; afterwards your product runs on a plan per organisation with credits every month. All numbers and how the price is made up are on the pricing page.

Common questions

Do I need my own contract with a payment provider?

No. Payment processing is part of the platform. Ticket buyers see your product as the merchant, and payouts go to the bank account you enter in Melta with your operator details before going live.

Does the ticket arrive as a PDF with a scannable code by email?

Yes. After the purchase your product emails the confirmation with the ticket as a PDF attachment, under its own name. Replies to that email land in your support inbox.

How does the door check-in work on the day?

Door staff sign in with a door role and open the check-in view on their phone: scan the code or search a name, mark the ticket as redeemed, see the remaining seats.

What happens when a date is sold out?

Then your product shows the waitlist instead of the checkout. When seats free up, you notify the people on it in order by email from the product.

Is there an example product for event tickets yet?

Not yet. The closest related example product is SOMA Yoga Zürich, with class bookings and a capacity per class.

Describe your event. Your own product sells the tickets.

A concept uses only a few credits. Checkout, PDF tickets, check-in and waitlist are built and connected once you approve it.

Get early access