How to choose venue management software for a UK attraction, leisure centre or events venue comes down to one decision before any feature list: whether every guest moment lands on one record in one platform, or on several systems that finance reconciles by hand. This guide is for the owner, general manager, operations or finance lead, or council leisure officer who has to make that call and defend it. It gives you a map of your venue’s day, a requirements checklist, a three-year cost template, compliance questions and a scoring template.
The one decision that matters more than any feature
A venue that sells tickets, passes and on-site food, drink, merchandise and lockers can run them as one platform with one record per guest, or as a ticketing system, a membership database, a bar ePOS and a locker contract, each reporting in its own format. The second route looks cheaper on the first invoice. The cost arrives later: a pass holder who is a stranger to the bar till, a refund keyed into two systems, and a marketing list that never agrees with the finance report. The first route puts more weight on one vendor, so the checklist, trial and reference calls below test whether that vendor can carry it.
In Britain, “venue management software” usually means function-room and event-space booking: weddings, conferences, the banqueting diary. If you take admissions and payments from the public, you are shopping for attraction management software, or for councils and trusts, leisure management software. A search for a venue management system in the UK returns both kinds, so check that a demo begins at the gate rather than the diary. See what attraction management software is and how it differs from booking software.
Map your venue’s day before you read a brochure
Write down what a guest does from deciding to visit to coming back a year later. Each handover between capabilities is where a separate system drops the record.
| Guest moment | What happens | Capability it needs | What to check in the demo |
|---|---|---|---|
| Buy | A family books a slot, two annual passes and a locker | Ticketing, timed entry, memberships, checkout | One basket, one payment, delivery to a mobile wallet |
| Arrive | The car park is full; pass holders want a fast lane | Timed entry, capacity caps, member entitlements | Capacity visible to the gate team in real time |
| Enter | Passes scanned from a wallet, a printout or a wristband | Ticket scanning | Scan speed, duplicate detection, what the operator sees |
| Pay | Lunch at a kiosk, drinks at the bar, a toy from the shop | Card machines, kiosks, ePOS, kitchen display | Whether each sale lands on the ticket’s guest record |
| Store | Bags and coats go into a locker | Smart lockers, unattended payments | Hire in seconds by card or the booking’s QR code |
| Drink | An adult orders a beer and looks under 25 | Age verification, licensing conditions | What the bar team sees, and what the check does not do |
| Renew | The pass renews a year later; a lapsed member is reminded | Memberships, renewal reminders, lifecycle emails | Renewal without chasing; a report finance trusts |
If a vendor can show four of these seven rows, you know what the other systems will be and what reconciliation will cost.
The requirements checklist
Take this table into every demo. The middle column is the shape of a good answer, not a script. Where VenueOra publishes an answer we say so; otherwise ask the vendor.
| Area | What to ask | What a good answer looks like | Why it matters |
|---|---|---|---|
| Sell: ticketing | Can we set up ticket types, bundles and price rules ourselves, with live capacity? | Admin creates products unaided; capacity counts down across every channel | VenueOra ticketing enforces real-time capacity |
| Sell: timed entry | How are time slots, session lengths and capacity caps set? | Slot templates by day type, caps per slot, a written late-arrival policy | See timed entry, capacity and time slots |
| Sell: scanning | What does the gate scan, on what devices, and what does the operator see? | QR codes on phones or scanners, RFID where wristbands are used, a used ticket rejected on screen | Ask the vendor how scanning behaves when connectivity drops |
| Sell: memberships and passes | Do plans renew on the same record as tickets, and how are due and lapsed members chased? | Annual and monthly plans, renewal reminders and lifecycle emails, member-only tickets and member pricing | See season pass and annual pass software |
| Sell: payments | Do online and in-person payments share one record, and what are the fees? | One order record for tickets, kiosk and terminal payments; fees in writing | VenueOra publishes its Free and Venue plans; card processing is quoted with your plan |
| Serve: card machines | Who supplies, installs and supports the terminals, and how fast is settlement? | A named supplier, next-day settlement, contactless and chip and PIN, Tap to Pay on phones | Know who to ring when a terminal fails |
| Serve: kiosks | Can guests order and pay unaided, with orders reaching the kitchen and guest record? | Kiosks on the same menu, stock and ledger as the tills | Queues shorten only if orders avoid re-keying |
| Serve: ePOS and kitchen display | Is the till the same system as the ticketing, or an integration? | One menu, one price list, one report; kitchen display fed by tills and kiosks | An integration is maintained on every upgrade |
| Serve: lockers | Who funds, installs, powers and maintains the lockers, and how do guests pay? | A service, not a purchase: the vendor funds and runs the lockers for a revenue share; guests hire by card or QR | See what lockers as a service includes |
| Protect: age checks | What does the check read, return, and not do? | Documents accepted, results and limits listed plainly; image retention in days | A vendor who says a check proves an ID is genuine is overclaiming |
| Protect: card data | Where does card data flow, who is the acquirer, and which self-assessment will we complete? | Card data goes to a PCI DSS Level 1 acquirer, never to venue hardware or vendor code; your acquirer confirms the questionnaire | The obligations remain yours whoever you buy from |
| Protect: personal data | Who is controller and who is processor, where is data stored, what is deleted when? | A signed data processing agreement, UK storage stated, retention periods in writing | The terms come from UK GDPR Article 28, not vendor preference |
| Protect: licensing | How does the system support our premises licence conditions, and what is left to staff? | Logs, prompts and checks that support a policy; the licence stays the venue’s | No software holds your licence for you |
| Build: API | Is there a documented API, and what can we read and write through it? | Public documentation, sandbox keys, versioning and rate limits | An undocumented API is a sales promise, not a capability |
| Build: webhooks | Can the system push sale, scan, refund and renewal events as they happen, signed? | Signed webhooks with retries | How your CRM and finance system learn what happened without polling |
| Build: data export | Can we export every guest, order and payment record, in a standard format, at any time, free? | Yes, self-service, documented formats, including on exit | Your data has to leave with you |
| Run: reporting | Which reports exist, and can finance reconcile takings to the bank from them? | Sales, attendance and revenue in real time; settlement reports that match payouts | A report finance cannot reconcile is a report nobody uses |
| Run: support hours | When is support open, and what is the response target on a trading Saturday? | Hours that cover your trading pattern, UK-based, response targets in the contract | Weekday-only support is the wrong shape for a weekend venue |
| Run: onboarding | Who sets up products, imports pass holders and configures hardware, and how long? | A named lead, a dated plan, a data import tested before go-live | Go live in your off-season, not your peak |
| Run: training | How are seasonal staff trained, and what help exists at 9am on a Saturday? | Role-based guides, short videos, a sandbox, a help line open when you trade | Seasonal turnover makes training an annual cost |
Commercial models, and how to compare cost over three years
Vendors price in five main ways and most contracts mix two or three; a three-year view puts them on one page.
Subscription. A fixed monthly or annual fee per site, per till or per user. Predictable; check what counts as a site and whether seasonal closure pauses the fee.
Per-ticket or per-transaction fee. A pence amount, a percentage, or both, on each sale; ask whether a refunded ticket refunds the fee.
Revenue share. The vendor takes a share of a revenue line instead of a fee; uncommon in admissions, usual in lockers. LockVault, our smart-locker service, installs and runs lockers at no upfront cost and no operating cost to the venue, and the venue receives a share of gross rental revenue, with the final split agreed after a site survey. Revenue figures are estimates from footfall and typical conversion. The final split and forecast come from a site survey. See how locker revenue share works and revenue share versus buying lockers.
Hardware purchase versus service. Tills, scanners, kiosks and card machines can be bought, hired or bundled. A purchase is a capital line and a maintenance rota; a service is an operating line with the vendor carrying repairs and updates. For lockers, ask who insures the hardware and who answers when a door jams.
Implementation and services. Onboarding, data migration, training and integration, charged once or per day: the fees most often missing from the first quote.
Fill in the template for each vendor with the same volumes.
| Cost line | Year 1 | Year 2 | Year 3 | Three-year total | Notes |
|---|---|---|---|---|---|
| Software subscription | Per site, till or user | ||||
| Per-ticket and per-transaction fees | Volume multiplied by fee | ||||
| Card acquiring fees | Blended or interchange-plus | ||||
| Hardware purchase or hire | Tills, scanners, kiosks, terminals | ||||
| Installation and onboarding | Set-up, data import, install | ||||
| Training | Initial, plus each season’s starters | ||||
| Support and maintenance | Included hours; out of hours; repairs | ||||
| Integration and development | API work, accounting, CRM | ||||
| Internal reconciliation time | Hours a week at hourly cost | ||||
| Revenue share paid or received | Negative when the venue receives a share | ||||
| Exit costs | Data export, early termination, hardware return | ||||
| Total |
Internal reconciliation time is the cost of separate systems and belongs in the comparison even though no vendor invoices it; a vendor who charges for a data export at the end is charging you to leave.
Compliance questions to ask every vendor
Every system on your shortlist touches card data and personal data, and if you serve alcohol, age checks. No vendor can make you compliant with anything; a good one reduces your scope and answers plainly.
Card data and PCI scope. The PCI Security Standards Council states that PCI DSS applies to any entity that stores, processes or transmits cardholder data, and that outsourcing payment processing reduces a merchant’s scope but does not remove its responsibility to protect account data. Validation levels are set by the payment brands and your acquirer, not the Council, and the questionnaire follows the card data flow: SAQ A, for example, covers card-not-present merchants who have fully outsourced processing and is not applicable to face-to-face channels. Ask each vendor to draw that flow for online, gate, bar, kiosk and locker payments and to name the acquirer. On VenueOra, card payments run through a PCI DSS Level 1 acquiring partner and card data never touches your tills, kiosks or lockers. See PCI DSS for venues and attractions, compliance and security and data.
Controller and processor roles. The ICO describes the controller as the body that determines the purposes and means of processing personal data, and the processor as the body that processes it on the controller’s behalf and instructions. The venue is normally the controller of ticketing and membership data and the vendor a processor, and UK GDPR Article 28(3) sets the terms their contract has to contain, from documented instructions and sub-processors to deletion or return of data at the end. Ask for the vendor’s data processing agreement first; ours is the VenueOra data processing agreement. Door ID scanning is covered in who is the data controller when a nightclub scans ID.
Retention. The ICO’s storage limitation principle sets no fixed period: personal data may be kept only as long as its purpose needs, and the organisation is expected to set, document and review retention periods. Ask the default retention for each data type and whether you can change it. VenueGo, a verification platform designed for venues, deletes images after 30 days unless a review is open.
UK storage. Ask where data is processed and stored, and whether that can change without notice. VenueOra ticketing and membership data is UK-based; VenueGo processing runs in London with data stored in the UK.
Age-check limits. As of October 2026, the Licensing Act 2003 (Mandatory Licensing Conditions) (Amendment) Order 2014 requires the premises licence holder in England and Wales to ensure that an age verification policy is adopted for alcohol sales, under which anyone who appears under 18, or under a higher age the policy sets, produces identification bearing a photograph, date of birth and either a holographic mark or an ultraviolet feature. A digital check sits inside that policy and does not replace it; digital proof of age for alcohol sales covers what venues can accept and from when. Ask each vendor what its check reads, returns and does not do, then compare with ours. VenueGo reads the document in the camera. It does not look up DVLA, the passport office, or any other government database, and it does not read a passport chip. A clear result is not proof a document is genuine. It does not replace a premises licence, a challenge at the bar, or legal advice.
Procurement for councils and leisure trusts, in brief
Council leisure services buy under the Procurement Act 2023, which sets the route by contract value. As of October 2026, the threshold for goods and services bought by sub-central contracting authorities, which include local authorities, is £207,720 including VAT for procurements begun on or after 1 January 2026; for central government authorities it is £135,018. Smaller contracts still carry notice duties: an authority other than central government publishes a below-threshold tender notice and a contract details notice on the central digital platform for contracts over £30,000 including VAT, and Find a Tender is where public sector buyers publish those notices.
For cloud software, G-Cloud 15 (RM1557.15) is the usual framework route; it runs from 6 August 2026 with lots for software as a service and cloud support, and buyers may award without competition for straightforward, low-value needs or run a competitive selection for complex ones. Whether a leisure trust counts as a contracting authority depends on how it is constituted and funded. Our guide to how councils and leisure trusts buy software covers thresholds, frameworks and the questions procurement teams ask; the leisure centres and trusts page shows how the platform fits a trust’s day.
A scoring template, and how to run a reference call
Score every shortlisted vendor on the same weighted criteria, agreed before the first demo. Score 1 to 5 against the good-answer column, multiply by the weight and divide by five for a weighted score out of 100. Adjust the weights to your venue.
| Criterion | Weight (%) | Score (1 to 5) | Weighted score |
|---|---|---|---|
| One guest record across buy, enter, pay, store, drink and renew | 15 | ||
| Ticketing, timed entry and scanning | 10 | ||
| Memberships, passes and renewals | 10 | ||
| On-site payments: tills, kiosks, card machines and lockers | 10 | ||
| Card data and personal data handling | 10 | ||
| Age checks and support for licensing conditions | 5 | ||
| API, webhooks and data export | 10 | ||
| Reporting that finance will reconcile | 5 | ||
| Three-year cost from the template above | 15 | ||
| Support hours, onboarding and training | 10 | ||
| Total | 100 | out of 100 |
Then run a reference call for each vendor still standing. Ask for a venue of your type and size that went live in the last two years, and speak to the operations manager rather than the owner who signed. Ask what the first busy Saturday was like, what broke, how fast support answered, whether the first invoice matched the quote, and what they would do differently. Finish with the question that tells you most: whether they have exported their data, and what happened.
Red flags, and how to run a trial
- The demo starts in the back office or the banqueting diary, not at the gate and the till.
- Pricing comes only after a call and is never put in writing.
- The vendor says the product makes you “PCI compliant” or “GDPR compliant”, or that an age check proves a document is genuine.
- Tickets, passes and on-site sales sit in separate databases joined by a nightly export.
- Data export is a paid service, or is not in the contract.
- Support closes at 5pm on Friday and you trade until 10pm on Saturday.
- Every reference venue is in another sector.
- The contract renews automatically with a long notice period, or hardware is locked to the software.
A trial should prove something specific, on a real trading day, with real staff. Choose one weekend. Set up three pass types, one timed-entry product with a capacity cap, one bar menu and, if in scope, one locker bank. Run the gate on the vendor’s scanning with the devices you would buy. On the Monday, ask finance to reconcile the takings to the settlement report without the vendor’s help. Process one refund, one lapsed renewal and one membership application, and check each shows on the guest record. Agree before the trial how the data will be exported at the end, then do it.
What VenueOra does here
The VenueOra platform sells tickets, passes and payments from one record per guest, so the moments in the table above land in one place. Ticketing with real-time capacity, timed entry as sessions with capacity and buffer time, QR check-in that rejects a used ticket, memberships and passes with renewal reminders and online, kiosk and terminal payments on one order record are the Sell rows of the checklist. Smart lockers on revenue share, self-ordering kiosks and ePOS and kitchen display supplied with Posso, our hardware and installation partner, are the Serve rows; age verification on the guest’s phone and integrations and API cover Protect and Build. The pricing page carries both platform plans, Free at £1.50 per ticket sold and Venue at £150 a month and 80p per ticket sold, plus VenueGo plans from £0 for 25 checks; bespoke pricing and locker proposals start with a request. See a day at theme parks, leisure centres and trusts and festivals.
This page describes how VenueOra’s products handle card data, personal data and age checks. It is not legal advice. Your premises licence conditions and your own data protection assessment take precedence.
Sources
- PPN 023: 2026 Threshold Amounts, GOV.UK
- Procurement Act 2023 guidance: Thresholds, GOV.UK
- Procurement Act 2023 guidance: Below-Threshold Contracts, GOV.UK
- Find a Tender, GOV.UK
- RM1557.15 G-Cloud 15, GCA
- Does PCI DSS apply to merchants who outsource all payment processing operations, PCI SSC
- PCI DSS v4.0 Self-Assessment Questionnaire A, PCI SSC
- What are controllers and processors, ICO
- What needs to be included in the contract, ICO
- Principle (e): Storage limitation, ICO
- The Licensing Act 2003 (Mandatory Licensing Conditions) (Amendment) Order 2014, legislation.gov.uk