What Studio does
The capability list in full, what each one actually covers, and the things Venued deliberately does not do.
Who Studio is for
Venued Studio is the console behind venued.eu/studio. Three kinds of business use it, and an account is exactly one of them: an organiser who runs events, a venue that has a space, or a professional who gets booked to work at events. What you see is shaped by which one you are.
The rest of this page describes the organiser side, which is the largest of the three. Venue and professional accounts share the same account, team, messaging and analytics machinery, and add their own: listings, availability, booking requests and enquiries.
Events and publishing
| Capability | What it covers |
|---|---|
| Draft, unlisted, public | Three visibility tiers. A draft is private to your account; unlisted is reachable by link but not listed; public is discoverable. Publishing is gated on a verified phone number. |
| Recurring events | A series is a first-class thing rather than copies of one event, so a weekly night is edited and measured as one. |
| Private and password-gated events | An event can require a password to view. |
| Venue and professional attachment | Attach the venue and the people working the event; they appear on the public page. |
| Your own branding | Theme colour, a matched secondary, animated background style, heading font, logo and cover image, set on your profile and overridable per event. |
| AI drafting | Describe the event or upload a poster and the assistant prepares a draft for you to review. It proposes; you confirm. Anything it creates starts as a private draft. |
Ticketing
| Capability | What it covers |
|---|---|
| Four modes | Sell through Venued, take free RSVPs, point at an external ticket provider, or run no ticketing at all. |
| Tiers | Each tier has its own price, quantity, sale window and per-order minimum and maximum. Order them, group them, and hide one behind an unlock code. |
| Phased release | A later tier opens automatically when the one before it sells out. |
| Pay what you want | A tier can take any amount above a floor you set. |
| Capacity | On the tier or on the event. Sales stop at the limit rather than overselling. |
| Discount codes | Percentage or fixed amount, with redemption limits, and Studio reports what each code did — including the discount you gave away. |
| Waitlist | Collect demand past a sell-out. |
| Approval to attend | Review who gets a ticket before they get one. |
| Refunds | Full or partial, from Studio, by anyone with the finance role. |
| Transfers | A holder can pass a ticket to someone else; the old one is voided and a new one issued. You can switch transfers off per event. |
| Guest checkout | Buy without an account, and claim the order onto one later, or never. |
| Wallet passes | Apple and Google Wallet. |
| Documents | PDF tickets, invoices with sequential numbering, and a printable door list. |
| Attendee questions | Ask what you need at checkout. |
| No-show deposits | Hold a card against a free RSVP and charge only if they do not turn up. |
At the door
Every ticket carries a QR code signed with a key only our servers hold, so a screenshot of somebody else’s ticket does not scan and a hand-made code does not either.
| Capability | What it covers |
|---|---|
| Two scanners | In the browser in Studio, or in the Venued Studio phone app. |
| Works offline | The scanner downloads the ticket list before doors and keeps checking people in without signal, queueing scans locally and reconciling when it reconnects. |
| One admission per ticket | A second scan reports the ticket as already used. Re-entry is not supported: a ticket admits once. |
| Multiple devices | Pair as many as the door needs; the pairing token can be rotated. |
| Selling at the door | Take payment on the spot and issue the ticket immediately, without the buyer making an account first. |
| Card payments with no card reader | Tap to Pay on an NFC Android phone: the buyer taps their card, Apple Pay or Google Pay against the same phone running the scanner. No terminal to rent, carry or charge. Cards only — girocard’s domestic rails are not supported, though a co-badged card taps fine. |
| Door sales are visible immediately | A door sale appears in Studio, consumes capacity and counts towards takings and VAT at the moment it is taken, rather than when the buyer gets round to claiming the ticket onto an account. |
| Arrival data | Live counts as people come in, an arrival curve, and flags for tickets presented more than once. |
Money
Venued uses Stripe Connect with direct charges. In practice that means the sale happens on your own Stripe account: you are the merchant of record, the money is paid to you, and Venued never holds it. There is no Venued-controlled float between a ticket being sold and you being paid.
| Capability | What it covers |
|---|---|
| Direct payouts | Stripe pays you on your own payout schedule. Studio reads your balance and payout history; it does not sit in the path. |
| Platform fee | A flat amount per ticket, not a percentage of your revenue. Studio shows it while you are setting a price and in the breakdown on every order. |
| Processing fees | Stripe’s own fee is separate, and you choose whether it is absorbed or added at checkout. |
| Payment methods | Whatever your Stripe account supports, including cards, Apple Pay, Klarna, iDEAL and Bancontact. |
| German tax handling | VAT rates per tier, the small-business exemption propagated across your account, sequential invoice numbering, and DAC7 reporting. |
Audience and discovery
This is the part that is not a feature of the console at all, and it is the reason Studio exists inside a consumer app rather than beside one. A published event is eligible for the Venued feed immediately, matched to people by interest and proximity, with no separate marketing step.
| Capability | What it covers |
|---|---|
| Interest and proximity matching | Your event is shown to people whose interests and location fit it, rather than only to people already following you. |
| Search | Events are indexed for semantic search as soon as they are public. |
| Followers and subscribers | People can follow your organisation and be told when you announce something. |
| Public pages | Every event, organiser, venue and professional has an indexable public page with proper structured data and link previews. |
| Editorial slots | A limited number of curated featured placements. |
Analytics
Two different clocks run here, and the difference matters when you are staring at a number on the night.
| Updated | What it covers |
|---|---|
| Live | Orders, revenue, tickets sold, discount code performance, and — once doors open — arrivals, scan counts and rescan flags. |
| Overnight | Reach, impressions, who your audience turned out to be, and how a series or a repeated format performs over time. These are computed in a nightly pass, so a brand-new event shows them as pending rather than as zero. |
Team and permissions
An organisation has one owner and any number of invited members. A member holds a set of roles, so someone can be both finance and marketing without a bespoke permission level.
| Role | What it is for |
|---|---|
| Owner | The account itself. Implicit, and the only role that can invite, remove or change other members. |
| Manager | Runs the organisation day to day. |
| Editor | Creates and edits events. |
| Finance | Payouts, orders and refunds. |
| Marketing | Promotion, broadcasts and subscribers. |
| Door staff | The scanner, and nothing else. Not payouts, not analytics. |
| Viewer | Read-only. |
Messaging
| Capability | What it covers |
|---|---|
| Attendee conversations | Ticket holders can write to you and you reply from one inbox in Studio. |
| Enquiries | Requests from people who want to book you, your space or your services, in the same place. |
| Broadcasts | Announce to your subscribers, with an audience preview before you send. |
| Booking threads | A venue or professional booking carries its own conversation, beside the booking itself. |
Building on Venued
| Surface | What it covers |
|---|---|
| REST API | Scoped API keys. Create and edit events, read orders, read venues, manage webhook subscriptions. Read and write budgets are metered per minute. |
| Webhooks | An HTTPS POST when an order is confirmed or an event is published, signed so you can verify it came from us, with retries and a delivery log. |
| Embeddable card and checkout | One script tag puts a Venued event card, or the whole checkout, on your own site — inline or in an overlay — and tells your page when a purchase completes. |
| oEmbed | Venued event links unfurl in tools that support oEmbed. |
What Studio does not do
Written down deliberately, and kept accurate on purpose. If one of these lands, it moves out of this list in the same change that ships it.
| Not available | The detail |
|---|---|
| White-labelling | Your pages carry your colours and your logo, and they stay on venued.eu with Venued branding. There is no custom domain and no way to remove Venued chrome. Embedding is the supported way to put Venued inside your own site. |
| Point-of-sale integrations | No Square, Lightspeed, Toast or generic POS integration: Venued will not read or reconcile against a till you already run. Taking card payments at the door needs no POS at all — see Tap to Pay above. |
| Tap to Pay on iPhone | Contactless card acceptance at the door is Android today. The iPhone equivalent needs an entitlement from Apple that is not in place yet. |
| Multi-currency and non-German accounts | Euro, and German payout and tax rules. |
| Re-entry scanning | A ticket admits once. There is no pass-out-and-return flow. |
| Publishing through the API | The API can create and edit drafts and unlisted events. Making something public stays in Studio. |
| Money movement through the API | Orders are readable. There is no endpoint that refunds, pays out or issues a ticket. |
| Professional API keys | Organiser and venue keys exist. A professional key is refused rather than issued against endpoints that do not exist yet. |
| Seat-level reserved seating | Tiers, capacity and tables. Not a seat map. |
Common questions
Does Venued Studio handle entry control at the door?
Yes. Every ticket carries a signed QR code, and Studio includes a scanner that checks tickets in — in the browser, or in the Venued Studio phone app. The scanner downloads the ticket list in advance and keeps working without signal, queueing scans locally and reconciling when it reconnects. A ticket admits once: a second scan is reported as already used rather than waved through.
Can I embed Venued checkout on my own website?
Yes. A single script tag renders either an inline event card or a button that opens checkout in an overlay, on any site, with no framework required. The buyer completes the purchase without leaving your page, and your page is notified when they do. See the embedding guide for the snippet and its options.
Does Venued take a percentage of ticket sales?
No. The platform fee is a flat amount per ticket, not a share of your revenue, so it does not scale with what you charge. Stripe charges its own processing fee separately, and you can choose whether that is absorbed or added at checkout. Studio shows both at the moment they apply.
When and how do organisers get paid?
Directly by Stripe, on your own Stripe payout schedule. Venued uses Stripe Connect with direct charges, which means money from a ticket sale is paid into your Stripe account rather than into ours — Venued never holds your funds and is not in the payout path. Studio reads your balance and payout history so you can see it in one place.
Can I use Venued alongside my existing ticketing system?
Yes. An event can point at an external ticket provider instead of selling through Venued, in which case you still get the public event page, discovery and analytics without moving your ticketing. You can also run an event with no ticketing at all, or with free RSVP.
Does Venued integrate with a point-of-sale system such as Square or Lightspeed?
No, and for taking money at the door you do not need one. Venued sells at the door itself, and accepts contactless cards on the same Android phone that is running the scanner, so there is no terminal to integrate with, rent or carry. What there is no integration with is an existing POS you already run: Venued will not read your till or reconcile against it.
Do I need a card reader to take card payments at the door?
No. Venued supports Tap to Pay on an NFC Android phone, so the buyer taps their card, Apple Pay or Google Pay directly against the phone your staff are already holding. The sale is charged to your own Stripe account and the ticket is issued on the spot. Cards only: girocard’s domestic rails are not supported by Tap to Pay, although a co-badged card taps normally.
Does Venued Studio support multiple team members with different permissions?
Yes. You invite colleagues to your organisation and grant each of them a set of roles — manager, editor, finance, marketing, door staff or viewer — and the account owner is implicit and separate. Permissions are enforced on the server, not just hidden in the interface: door staff, for example, can run the scanner and cannot see payouts.
Is there an API?
Yes, a small REST API authenticated with a scoped API key. You can create and edit events, read orders, read venues, and subscribe to webhooks. It deliberately cannot publish an event and cannot move money: there is no refund, payout or ticket-issuing endpoint.
What does the AI assistant actually do?
It drafts. You describe what you are planning, or upload a poster, and the assistant fills in the details and suggests venues and professionals from the Venued directory. It then hands you a proposal to review. The assistant cannot create, edit, publish or book anything itself — every change is applied by you, on confirmation, and an event it drafts is always created as a private draft.
Which countries and currencies does Venued support?
Venued operates in Germany and prices in euro. Organiser payout accounts are onboarded as German Stripe accounts, and the tax handling — VAT rates, the small-business exemption, invoice numbering — is built for German requirements. Venued is not a multi-currency platform today.
Can I white-label Venued, or run it on my own domain?
No. You can brand your public pages — your own colours, background, heading font, logo and cover image, and a per-event colour override — but the pages stay on venued.eu and carry Venued branding. There is no custom domain and no removal of Venued chrome. The embeddable card and checkout are the supported way to put Venued inside your own site.