Every Held feature

This is every feature, by area — for when you need to know exactly how something works. The shorter guide, in the order you’ll use things, is the Basic view.

€0

for you — no subscription, no commission

€1.25

per person, paid by the guest

Next morning

the deposit lands in your Stripe

Account type

• Bar — one venue open regularly (bar, club, lounge), with a calendar that extends itself.
• Agency — multi-day festivals and one-day events on fixed dates; can sell tickets and clone an edition.

Signup and approval

• Sign up at /register: name, type, your name, email and password.
• Approval: until we approve you, you can log in but nothing can be published or changed. You get a “signup received” email, then “your account is active”.

First-venue guide

• Setup wizard (bar or festival/event): basics, opening schedule, deposit and drink mode, menu, look, floor plan — step by step, with back and forward.
• Festival or event, free or ticketed — agencies choose in the wizard and add ticket types right away.

Payouts and company details

• Company info: legal name, OIB (checksum validated), address, and premises type, address and code (used in the price-list file name).
• Stripe Connect Express: connect the payout account on Stripe’s own page; see the status of identity, card payments and payouts.
• Dashboard reminder while Stripe or company details are missing — it disappears once everything is ready.

Several venues

• Venue/festival switcher at the top of the sidebar — dashboard, Days, Reservations, Tonight and Tickets show the one you pick.

Bar

• The calendar extends itself — always open 90 days ahead (you can change the number).
• Weekly schedule: closed or opening hours for each weekday.
• Seatings: e.g. 19:00 and 22:00 — the same table sells once per seating.
• A closed night takes no bookings; if it already has some, use “Cancel this night”.
• An event on a night: name and description (HR/EN), times, image — a poster on the calendar and the night’s page.

Festival and event

• Fixed dates — every day has its own page, bookings, programme and, if you like, its own floor plan.
• Scheduled go-live — guests see nothing until then, while you can test a booking from the admin.
• Status: upcoming, then active, then past (archived); reopen; delete only without confirmed bookings.
• Next edition in one step (Clone…): a new first day (we suggest the same weekdays a year later) and the name with the new year. Copies the floor plan, tables, page, programmes, rules, table terms, welcome perk and tickets (with a new QR key and sale dates moved along). Bookings and sold tickets start at zero; the copy stays hidden until you activate it.

Extras for every festival/venue

• Table terms (HR/EN): minimum spend, dress code… — shown to the guest before paying.
• Welcome perk (HR/EN): e.g. “welcome shot” — shown in the booking summary.
• Accent colour — a thin line on your page.

The editor

• Tables: round or rectangular, label (VIP-1), capacity (sets party size and fee), section (Terrace…), size, rotation.
• Room elements: bar, stage, DJ, entrance, stands, walls, custom shapes, room boundaries.
• Tools: multi-select, group, align, distribute, lock, hide, layers with search, undo/redo, zoom, pan, snap to grid.
• Background: upload a drawing of the room and trace it.
• Booked tables are locked — they can’t be moved while they have a booking.

More than one space

• Floors: ground floor, terrace, upstairs — each with its own plan.
• Per-day layout: give one day a different arrangement (copy of the main one, revert to it).
• Saved spaces: store a plan and apply it to another festival.
• Export the plan as a PNG and as a sheet in the Excel export.

• Organizer page (/o/your-name): all your festivals and events; a bar with one venue goes straight to its calendar.
• Festival/venue page: hero, programme, about, food and drinks, gallery, location and hours, reserve band — all edited in Croatian and English.
• Calendar: month view — programme nights as posters, regular nights, closed days, an “up next” strip.
• Day page: cover, description, live floor plan, table terms, seating picker, tickets (paid events).
• Croatian and English on every page, switching language without losing your place.
• Share images (Instagram, WhatsApp, Facebook) generated for every page.

1. Night and seating, then a table on the live plan: free, taken (hatched), being booked by someone else (yellow, can’t be picked), selected. It shows how many tables are left.
2. The chosen table is held for 15 minutes for that guest only; everyone else sees it within seconds.
3. Drinks (depending on mode): deposit only — no such step; deposit + bottle selection — the guest picks bottles or “not sure yet”. Bottles are paid on site.
4. Details: name, email and confirm email (can’t be pasted), phone, notes. R1 receipts aren’t available online yet.
5. Review: what’s included, welcome perk, deposit and fee as separate lines, cancellation terms, legal notice.
6. Card payment (Stripe, 3D Secure) → confirmation page and an email with the fiscal receipt and a calendar file.

• One table — one booking per day and seating, guaranteed even when two people pay at once.
• A payment arriving after the hold expired, or after you cancelled the night, is refunded automatically.
• The guest sees the booking from the email link (with their email) and can cancel it there.

• Dashboard: active festivals, bookings today and this week, deposits collected.
• Tonight (bars): the live board — floor plan with bookings, by seating, drinks or “not decided”, floors, the next nights; refreshes itself.
• Days: every day with its fill; an open day shows tables, seats, occupancy, collected, figures per seating and floor, the booking list, exports, event editing, closing and “Cancel this night”.
• Booking list: filters (date, status, payment type), search (name, email, reference), export everything or one date.
• Booking detail: guest, seating, table, floor, Deposit (yours) / Held fee / Total paid, drinks, payment, fiscal receipt; resend confirmation, re-fiscalize, calendar file, cancel.
• Phone and walk-in bookings without payment — the guest gets an email confirmation.
• Excel export: a row per booking with guest, table, seating, drinks, deposit and fee, totals and a floor-plan sheet. Every export is logged.
• Capacity alerts by email when a day passes your thresholds and guest reminders before their date (in Settings).

• Several menus, one default; categories and items (name and description HR/EN, price, available yes/no).
• Drink mode per venue/festival: deposit only, or deposit + bottle selection.

Setup

• Paid entry (agencies): switching it on creates the scanner link and the QR key; it can’t be switched off after the first ticket sells.
• Ticket types: day ticket or festival pass, GA or VIP, name HR/EN, price, quota.
• Sale phases: each type has a sale window (from–to) and a quota; a phase ends at its date or when it sells out. Next phase sets up the following phase in one click.
• Enable/disable in one click — a disabled type disappears from the page, sold tickets stay valid.
• Capacity per day and the ticket type included with a table.

What the guest sees

• Every phase in order: finished ones crossed out, the current one on sale (with “until …”), the next with its start date. After buying: an email with QR codes and a PDF pass, and a ticket wallet link.

Selling and overview

• Tickets in the sidebar: follows the picked festival; whole festival or one day; fill per day; ticket-type editing; sold tickets.
• Sold tickets: total sold, orders, revenue, % checked in; a row per order (buyer, email, reference, source: online / with a table / at the door), tickets by type and day, check-in status, amount. Search by name, email, reference or ticket code; filters; resend tickets; Excel.

Door scanner

• No app, no login — a link in the phone’s browser; can be added to the home screen.
• Works without signal after one sync; scans are sent when the signal returns.
• Counter: how many are in and how many are still coming; day picker; torch; manual code entry.
• Full-screen verdicts: “Let them in” (green), “Already in” (hatched), “Wrong day / Not valid / Unknown code” (red).
• Conflicts: the same code on two phones is recorded and shown under Tickets.
• New scanner link and new QR key in one click (the old link stops at once).

Cancelling

• Cancel a day (that day’s tickets and tables refunded; passes pro-rata, in full or as credit) or the whole event (every ticket at face value, the fee isn’t refunded).

• Fee: €1.25 per person (per seat at the table) or per ticket — paid by the guest.
• Transfer every morning at 4:00: deposits for nights that have passed reach your Stripe (Friday → Saturday morning), once Stripe has confirmed the guest’s payment (a last-minute booking: up to 3 working days). Paid events the same: each festival day the next morning; festival passes after the last day.
• Bank payout: bars every Friday (last week, complete, before the weekend); festivals and events straight away: Held starts the payout the same morning as the transfer, so the money arrives the first business day after the event.
• Held pays Stripe’s fees — you get the full deposit.
• The deposit at your till: the guest has already paid it — on the night, take it off their bill as a voucher at the till, so the same amount isn’t charged and taxed twice.
• A deposit from a guest who cancels or doesn’t show is yours and transfers as normal.
• Overview in Payouts: every transfer (date, amount, number of bookings, e-invoice) and every bank payout.
• Until Stripe is connected, the money waits and moves the first morning after you connect.

Guest cancels or doesn’t show

nothing is refunded — you keep the deposit

You cancel — “The guest”

when the guest asks you: nothing is refunded

You cancel — “We are”

the guest gets the deposit back, with a storno receipt and your reason by email

“Cancel this night”

every guest gets the deposit back, the night closes

Held’s fee

never refunded

Refunds come from money not yet transferred to you — possible until the morning after that night (for paid events, until the day is released). After that the system refuses.

• Fiscal receipt for the guest issued automatically after payment (JIR, ZKI, QR check code), R2, noting it was sold on your behalf. You need no certificate or till of your own.
• Storno receipt on every refund.
• Receipts in the admin: every issued receipt with its PDF.
• e-Invoice with every bank payout: a statement of Held’s fees on the bookings in that payout, delivered to your e-Račun inbox through FINA — for your bookkeeping. Needs your OIB and legal name in company info.

• To the guest: booking confirmation (fiscal receipt, calendar, cover photo), reminder, cancellation (and your reason with the refund amount), tickets with QR codes, ticket refunds.
• To you: signup received, account approved, capacity alerts.
• All in the language the guest booked in, with your name as the heading.

• Analytics: visitors, page views, sources (Instagram, Google…), UTM campaigns, bookings from visits; 7, 30 or 90 days. Counted only with the guest’s consent.
• Meta Ads: connect your ad account and follow your campaigns.
• Page editors: your organizer page and each festival page in two languages, with images and a gallery.

• Your data is yours alone — no one else can see or open it.
• Guest data is anonymised automatically 3 years after the event; receipts are kept 11 years as the law requires. Held never uses it for marketing.
• Cards are handled by Stripe — Held never sees a card number.
• Prices and fees on a booking are frozen — later menu changes never alter past bookings.
• Cookies: essential ones without consent, analytics and maps only after agreement.