Canvases/CV-04

Events & Venues Canvas

From the first ticket sold to the last gate closed.

One commercial engine for congresses, museums, festivals and fairs: online checkout, box office, ticketing, access control, CRM and analytics, sharing the same orders, payments and tickets.

Modules
15
Sales channels
Online · Back office · POS
Operating modes
Event · Permanent venue
Tenancy
Multi-tenant, per-module licensing
§ 01ScopeBuilt for

An event and a museum look different, but they run on the same things: an order, a payment, a ticket, a gate. This canvas models those once and lets everything else be configuration.

  • 01

    Congresses and conferences

    Registration fees with early-bird and late-fee rules, conditional registration forms, badges from print fields, check-in with anti-passback, live statistics during the day.

  • 02

    Museums and permanent venues

    Year-round ticketing with no artificial event: day tickets and rolling passes, visitor profiling at the desk and online, end-of-shift cash reconciliation.

  • 03

    Festivals and fairs

    Multiple locations and gates, operators self-assigned by QR, real-time occupancy per hall, time-window rules for reduced tickets.

  • 04

    Online plus box office

    One catalogue, two checkouts. Order provenance is frozen at creation, so revenue is analysed by channel: gross, tax, fees, net.

  • 05

    Agencies running many clients

    One user, many tenants, switched on the fly, each with its own licence, modules and roles.

  • 06

    Connected back offices

    Rules on order and ticket events push signed webhooks to the ERP, with throttling and a delivery ledger for anything that failed.

§ 02Inside the canvasInterface schematics with illustrative data. Product screenshots will replace them.

How the platform is laid out.

This canvas is software that already runs. What you see here is the starting point we customise, not a concept to be built from zero. The figures on this page are drawings of the interface, not screenshots.

  1. 01 Configure
    • Tenant
    • Event or venue
    • Checkout
    • Offers
    • Forms
    • Ticket types
  2. 02 Sell
    • Storefront · Back office · POS
    • Server-side quote
    • Order · pending
    • Payment
    • Order · processed
  3. 03 Fulfil
    • Tickets + QR
    • Email + PDF
    • Contacts · attendees
    • Notifications
    • Statistics
  4. 04 Access
    • Checkpoint scan
    • Rule validation
    • Approved / denied + reason
    • Live occupancy
  5. 05 Report
    • Gross · tax · fee · net
    • Reconciliation
    • CSV export
    • Audit log
Interface schematic · illustrative data
End-to-end pipeline Configuration, sale, fulfilment, access and reporting share one data model. Every state change is an event.
Ticket A7K2-03 Active
Ticket type · 3-day pass
Validity
3 days from first entry
Locations
Halls 1–2
Time rule
Weekdays 09:00–13:00
Passback
Exit required before re-entry
Uses
2 of 5 remaining
Gate log

09:12Hall 1 · inApproved

11:40Hall 3 · inDenied: location not allowed

11:52Hall 1 · outApproved

11:58Hall 2 · inApproved

Interface schematic · illustrative data
Ticket rules and the gate Validity, time windows, allowed locations, remaining uses and anti-passback are properties of the ticket type, not code.
Terminal 02 · Shift closing Box office: main entrance

Opened 08:45 · Closing 18:10 · Cashier M. R.

  • 86 orders
  • 214 tickets
  • 2,115.00 card
Opening float200.00
Cash sales+ 1,340.00
Deposits+ 50.00
Withdrawals− 300.00
Expected in drawer1,290.00
Declared1,285.00
Mismatch− 5.00
Interface schematic · illustrative data
Shift reconciliation Expected versus declared cash, with mismatches flagged and every movement recorded as a transaction.
§ 03Supported today15 modules · 80 features

Everything this canvas already does.

The inventory below is what ships before we change a line. It is a floor, not a ceiling: the features your company needs are defined in the audit and built on top.

  1. M-01

    Platform and governance

    Multi-tenant foundations, licensing and access control.

    • Every domain record scoped by tenant
    • Per-tenant licence, seats and activatable modules
    • Role-based access: 25 resources × 10 actions, with a permission matrix editor
    • Audit log on every mutation
    • Notes, typed labels (single and bulk), saved table views
    • Hot tenant switching for users working across organisations
  2. M-02

    Events

    The event as a first-class object, from draft to archive.

    • Lifecycle: draft → published → postponed / cancelled / archived
    • In-person, online and hybrid formats
    • Event profile: branding, contacts, accessibility, catering
    • Early-bird and late-fee rules with windows, channels, stacking and preview
    • Attendees: batch processing from orders, labels, CSV export
    • Live page: occupancy per location, last-hour flow
    • Public event landing by slug
  3. M-03

    Venues and locations

    Sell on a place, not only on a date.

    • Permanent-venue mode: no artificial event required
    • Locations with capacity, groups and checkpoints
    • Location maps with typed pins for gates, stands and services
    • Operators self-assign to a checkpoint by scanning a QR
    • Dedicated venue workspace
  4. M-04

    Catalogue

    Products, add-ons, stock and tax.

    • Products with SKU, price, stock and image variants
    • Reusable add-ons and add-on groups with min/max and price override
    • Tax rates per tenant, inclusive or exclusive, with overrides per product and offer
    • Pessimistic stock locking: no overselling
    • Deep clone of a checkout configuration
  5. M-05

    Checkout

    A configurable point of sale, online or in store.

    • Branding, texts, terms and language per checkout
    • Offers with ordering, price override and single-quantity purchase
    • Stripe payment account and offline bank transfer
    • Public link and QR
    • Per-checkout statistics
  6. M-06

    Form engine

    Structured data collection, versioned and reusable.

    • Immutable published versions: historic data stays readable
    • Drag-and-drop builder with live preview
    • Conditional visibility, also evaluated server-side
    • Mappings to contacts, orders, ticket print lines and profiling
    • One renderer shared by admin, storefront and POS
  7. M-07

    Orders

    Three channels, one authoritative quote.

    • Created from storefront, back office or POS
    • Event or venue provenance frozen at creation
    • Prices always recalculated server-side
    • State machine with requires-attention on balance mismatch
    • Cancel with used-ticket protection and stock return
    • Mark as paid, single and bulk; CSV export with dynamic columns
  8. M-08

    Payments

    Stripe as the source of truth, fees included.

    • Stripe Connect per tenant with OAuth onboarding
    • Signed, de-duplicated webhooks
    • Provider fee and net retrieved per transaction
    • Four collection paths: online, free, bank transfer, POS
    • Summary by gross, tax, fee and net
  9. M-09

    Ticketing

    Typed tickets, issued once.

    • Idempotent issuance on processed orders
    • Fixed or rolling validity (for example three days from first entry)
    • Day and time rules, allowed locations, maximum uses
    • Bundles, anti-passback and optional auto check-in
    • Locally generated QR; A4 and 80 mm thermal PDF
    • One email per order; signed print URLs
  10. M-10

    Check-in

    A complete decision at every gate.

    • Checks expiry, remaining uses, validity, time rules, location and passback
    • Every denied attempt stored with a typed reason
    • Checkpoint derived from the operator, never from the payload
    • Real-time occupancy and cross-location statistics
    • Bundles recorded as one aggregated entry
  11. M-11

    POS

    The box office, with a cash drawer that adds up.

    • Terminals with server-verified PIN
    • Shift opening and closing with reconciliation
    • Expected versus declared, mismatch flagged
    • Deposits and withdrawals as recorded movements
    • Preferred products per terminal; thermal printing
    • Unreconciled transactions always visible
  12. M-12

    Contacts and CRM

    A CRM fed by the sale itself.

    • Dynamic attributes with PII classification
    • 360° view: orders, tickets, check-ins, notes
    • Duplicate detection with merge preview
    • Automatic creation from orders, enriching without overwriting
    • CSV export
  13. M-13

    Profiling

    Know your visitors without writing code.

    • Tenant-defined typed dimensions
    • Fed directly by form mappings
    • Statistics by checkout, location, POS, checkpoint and period
    • Sensitive dimensions excluded from reports by default
  14. M-14

    Notifications and automations

    An event bus you can build on.

    • Transactional outbox with idempotent handlers
    • Rules: conditions → email, signed webhook or in-app
    • Liquid templates per tenant
    • Throttling windows against bursts
    • Delivery ledger with retry and manual resend
  15. M-15

    Tenant administration

    Everything an operator needs to run their own house.

    • Members, invitations and role editor
    • Logo, language, currency and timezone
    • Payment accounts and tax rates
    • Scheduled jobs with manual run
    • Audit log viewer
Then, in the audit

We add what only your company needs.

Our AI-first team maps your processes, finds what the canvas does not cover yet, and builds it as new modules, configured and delivered together with the rest.

  • Custom+ Accreditation workflow
  • Custom+ Sponsor portal
  • Custom+ Your module
§ 04Agents on this canvasOrdered data in · reliable work out

Structured enough for agents to be trusted.

Agents fail on ambiguity. A canvas removes it: typed data, explicit rules and a record of everything that happened, connected to the rest of your company.

  • Every state change is an event

    Orders, payments, tickets, check-ins and shift closings are published on a transactional event bus. An agent subscribes to what matters and acts on it.

  • Rules decide, agents explain

    The gate says no with a typed reason. An agent can turn that into an answer for the visitor, or a pattern for the operations manager.

  • Reporting without the spreadsheet

    Gross, tax, fees and net are already separated by channel and location, ready to be read, compared and summarised.

CV-04: Events & Venues

Put this canvas to work in your company.