EPOS, POS & booking system FAQs

An EPOS system is an electronic point-of-sale setup that records sales and helps staff run the selling process. It combines software with equipment such as a touchscreen, tablet, receipt printer or cash drawer; card acceptance requires a suitable payment service and device. For a café or leisure venue, assess the complete workflow, from taking an order or admission payment to receipts, refunds and reporting. Booking, kitchen and membership tools are additional capabilities to verify, rather than universal features.

EPOS stands for Electronic Point of Sale. It describes the electronic tools used to record a transaction where a customer buys goods or services, such as drinks, meals or activity tickets. EPOS software controls the transaction, while hardware provides the screen, printer and other physical equipment. In UK supplier terminology, an EPOS package might mean software only or a complete till bundle, so request an itemised quotation covering devices, licences, payments, installation and ongoing support.

POS means Point of Sale and can describe the place, process or system used to complete a sale. EPOS means Electronic Point of Sale, making the electronic element explicit. Suppliers often use POS and EPOS interchangeably for modern systems, so the label alone does not indicate better functionality. Compare the actual software, supported hardware and payment arrangements. For hospitality and leisure buyers, table service, kitchen routing, admissions and booking workflows matter more than which abbreviation appears in the brochure.

Staff select products or services in the EPOS software, which calculates the total using configured prices, options, discounts and tax settings. The sale is recorded against a payment method, and connected equipment can produce receipts or send orders to preparation stations. With integrated payments, the till exchanges transaction information with a compatible terminal. Cloud synchronisation can make records available centrally. Ask suppliers to demonstrate failed payments, refunds and connection outages, because these workflows vary between systems.

A typical EPOS system includes sales software, a device to run it and tools for managing products and reviewing transactions. Depending on the package, equipment may include a touchscreen till, tablet stand, receipt printer and cash drawer. A card terminal and payment processing agreement may be supplied separately. Restaurants may add kitchen printers or displays; leisure venues may need ticket scanning or booking software. Check which components, licences, installation services and replacement arrangements are actually included in the quotation.

Start with the jobs your venue must complete during its busiest period: bar sales, table orders, kitchen tickets, admission check-in or party payments. Compare usability, hardware compatibility, reporting, staff permissions and the exact offline behaviour. Ask for a demonstration using your own menu or booking scenario, including refunds. Review the total contract cost, payment processing terms, data export options and support coverage. Confirm any EPOS Bookings capability needed for your workflow before treating it as part of your purchase.

The best type depends on how your small business serves customers. A compact tablet-based setup may suit a café counter, while a busy pub may benefit from dedicated tills and handheld ordering. A soft play center should evaluate how admission sales relate to bookings and café purchases. Prioritise simple operation, dependable equipment and support during trading hours. Compare the full cost of licences, devices and payments, and avoid paying for modules your team will not use.

Cloud EPOS is useful if you want central administration, remote reporting or shared information across venues. It can reduce the need to maintain your own server, but you still need reliable devices, connectivity and an outage plan. A locally managed or hybrid setup may suit some operating requirements. Compare where data is stored, which tasks need internet access, backup and recovery arrangements, and how you retrieve records if you leave. Cloud hosting alone does not guarantee availability or security.

Some EPOS systems can continue selected tasks without internet access, but offline selling and offline card acceptance are separate capabilities. A till may record cash sales while bookings, shared stock or payment authorisation become unavailable. Certain payment providers support deferred card processing on approved devices, with limits and a risk of later declines. Ask for a written list of offline functions and a recovery demonstration. EPOS Bookings’ precise offline behaviour should be confirmed for your proposed configuration.

Yes, some platforms combine EPOS sales with bookings, while others connect separate systems through an integration. For a leisure venue, the useful question is whether reception can find a booking, handle its payment and sell extras without duplicating records. For restaurants, test how reservations connect to tables and bills. EPOS Bookings advertises sales and online booking tools, but confirm the exact modules, shared records and payment workflow in a demonstration; this does not establish that every booking scenario is supported.

Many EPOS platforms offer multi-location management, but the scope differs. Useful capabilities include consolidated sales reports, location-specific menus, central price updates and separate staff permissions. A leisure group may also need independent capacities and booking rules for each site. Check whether customer records, memberships and stock transfers work across locations, and what happens when one site loses connectivity. Request costs per location and terminal, and demonstrate your required cross-site workflows before assuming a supplier supports them.

Yes, an EPOS setup can replace a traditional cash register, adding structured product records and reporting alongside basic sales entry. You may reuse some peripherals, but compatibility needs checking. Before switching, build the menu or ticket catalog, configure tax and payment settings, and test receipts, refunds and end-of-day reconciliation. Train staff using realistic transactions before the first live shift. Choose the replacement around your workflow: a restaurant may need kitchen routing, while reception may need booking lookup alongside sales.

Begin by reviewing your existing contract, payment agreement and access to data exports. Identify which products, stock figures, customer records and outstanding bookings must move, then ask the new supplier which formats it can import. Historic reports may need to be retained separately. Configure and test the new setup before choosing a quieter changeover period, and reconcile opening balances and unsettled payments. Keep a clear fallback plan, and confirm how support will handle migration problems during live trading.

Possibly, but matching sockets or a familiar brand does not prove compatibility. Give the new provider exact model numbers, operating-system versions and connection types for tills, tablets, printers, scanners and cash drawers. Ask it to confirm support in writing and test the equipment with the proposed software. Payment terminals may be tied to a processor or agreement and need separate assessment. Compare reuse savings with remaining device life, warranty cover and the potential disruption caused by unsupported equipment.

There is no universal installation timescale. A single counter with a prepared menu is a different project from a restaurant with kitchen routing or a leisure venue migrating bookings and memberships. Timing depends on hardware delivery, data preparation, network work, payment account approval, staff training and testing. Ask the supplier for milestones and responsibilities rather than a headline estimate. Schedule the changeover outside peak service, and allow time to resolve issues before the system handles customer transactions.

EPOS software is the application that runs sales functions, such as selecting items, calculating totals, recording transactions and producing reports. It is distinct from the physical till, tablet, printer and card reader, although suppliers may bundle them together. Features can extend to tables, inventory or customer records, depending on the product and license. For UK hospitality and leisure buyers, evaluate the software against daily tasks and confirm the hardware, operating systems and payment services required to run it.

Core requirements usually include clear product buttons, configurable tax settings, receipts, payment recording, refunds and usable sales reports. Beyond that, choose features around your venue: table and kitchen workflows for restaurants, fast tabs for pubs, or booking and admission processes for leisure. Check staff permissions, data exports and what remains usable during an outage. Ask which functions are included, which require extra modules and which depend on integrations. A long feature list is less useful than a successful demonstration of your busiest workflow.

Cloud EPOS software uses a supplier-hosted service to store or manage business information and make it accessible over the internet. The selling interface may run in a browser or an installed application, and some systems keep selected functions locally. This can support remote reporting and central administration, but functionality during an outage varies. Ask where transaction data resides, how synchronisation works and how backups and exports are handled. Evaluate the service agreement alongside the till hardware and network requirements.

Yes, some EPOS applications run on supported tablets, but compatibility depends on the software, tablet model and operating-system version. A tablet can serve as a counter till or handheld order device, with a suitable stand, power supply and compatible peripherals. Check whether printing and payments require additional equipment, and test connectivity across the venue. Consumer tablets also need protection from spills and damage. Confirm the specific devices approved by your supplier before buying equipment or reusing existing tablets.

Many EPOS products track stock by reducing recorded quantities when items sell, with tools for deliveries, adjustments and stock counts. Tracking bottled drinks or merchandise is simpler than tracking ingredients used across recipes. Hospitality buyers should check portions, wastage, modifiers and supplier ordering; leisure venues may need separate retail and café stock. Online and till stock synchronisation also needs testing. Inventory accuracy depends on setup and staff processes, and recipe-level functionality should be verified rather than assumed for EPOS Bookings.

Many systems provide individual staff logins and permission levels. These can restrict actions such as refunds, discounts, price changes or access to reports, while helping identify who completed a transaction. Ask whether permissions apply consistently across tills, back-office tools and mobile devices. For venues with seasonal staff, test how accounts are added, disabled and reviewed. Shared logins reduce accountability, so favour practical individual access. Detailed audit records and manager approval workflows vary and should be checked with the supplier.

Most EPOS software provides some refund and void functions, but they serve different purposes. A void generally removes or cancels an item or transaction before completion; a refund returns money after a completed sale. Payment processors determine how card refunds are executed and settled. Test partial refunds, split payments, incorrect orders and associated stock adjustments. Ensure staff permissions and records support reconciliation. For bookings or admissions, confirm separately whether refunding a payment also cancels the booking or releases capacity.

Many EPOS applications support percentage or fixed-value discounts, while more complex promotions may require additional tools. A café might need a meal deal; a pub might need a timed offer; a leisure venue might need a membership discount. Test eligibility rules, combination limits, expiry dates and how discounts appear in reports. Check whether offers apply consistently online and at the till. Manager permissions can help control discretionary reductions, but verify each required promotion with the supplier before advertising it.

Many EPOS systems let you assign tax rates to products and calculate tax within transactions and reports. Correct UK VAT treatment still depends on your supplies and circumstances; software does not determine it automatically or guarantee compliance. Hospitality businesses may need different settings for eat-in and takeaway sales, with exceptions depending on the product. Configure rates and categories using current HMRC guidance and appropriate accounting advice, then test receipts, discounts and exports. Confirm how changes are applied and recorded across your tills.

Many systems distinguish product variations from modifiers. A variation might be a small or large coffee with its own price or stock record; a modifier might add an extra shot or change the milk. Check whether options can be compulsory, limited or priced separately, and whether they appear clearly on kitchen tickets. For leisure sales, assess adult, child and concession ticket types separately from catering options. Demonstrate your actual catalog because availability, stock behaviour and reporting differ between software products.

Yes, many EPOS products support several terminals at one venue. What matters is how they share orders, tables, stock and payment information. A pub may need multiple bars working against shared tabs, while a leisure venue may have reception and café tills with different menus and permissions. Ask about terminal licences, network requirements and how updates synchronise. Test simultaneous transactions and an offline terminal, including recovery, because a shared system does not automatically prevent every conflict or duplicate action.

Many platforms allow prices to be maintained centrally and distributed to connected tills, reducing repeated manual changes. Check whether updates apply immediately, at scheduled times or only after synchronisation. For hospitality, test location-specific menus, timed prices and how already-open orders are treated. For leisure, booking prices may be managed separately from café or retail items. Include offline devices in testing and verify staff permissions. Confirm central price management and its limits for your proposed EPOS Bookings configuration before relying on it.

Many EPOS products provide sales dashboards that update as transactions synchronise. However, ‘live’ may mean near real time, and offline devices or delayed integrations can leave figures incomplete. Ask how frequently reports refresh and whether they show gross sales, refunds, discounts, VAT and payment types clearly. Restaurants may need service-period comparisons; leisure venues may need admissions separated from café spending. Test the dashboard against completed transactions and end-of-day totals, and check whether remote access requires an additional licence.

Some systems can record advance bookings and walk-in sales together, but this requires a booking workflow or a suitable integration. A leisure reception team should be able to check availability before selling admission and distinguish arrival status from payment status. Test deposits, outstanding balances, cancellations and café extras to avoid counting revenue twice. EPOS Bookings markets connected sales and bookings, but confirm whether your chosen configuration updates capacity and reports consistently across online purchases, reception sales and booking amendments.

Cloud software generally relies on supplier-hosted services for central data and administration, while locally installed software runs key components on your own device or server. These approaches can overlap: a cloud product may have a local app, and a local till may use online services. Compare actual outage behaviour, backup responsibilities, remote access and maintenance requirements. For hospitality and leisure venues, focus on which sales, orders and bookings remain available during disruption, rather than assuming either deployment model is always more reliable.

You need a supported device to run the software and equipment suited to the way customers pay and receive service. A counter might use a touchscreen or tablet, card terminal and receipt printer, with a cash drawer if you handle cash. Restaurants may add kitchen printers, screens or handhelds; leisure reception may need scanners. Network equipment and reliable power also matter. Build the hardware list from demonstrated workflows, and confirm exact model compatibility before purchasing devices or accepting a bundled package.

An EPOS touchscreen till is a physical terminal with a touch-operated screen used to run sales software. Staff tap product buttons, enter orders and complete transactions without relying on a conventional keyboard. It may be a purpose-built all-in-one unit or a tablet mounted at the counter. The screen itself does not provide every EPOS feature: software and connected services determine functionality. Assess screen size, responsiveness, spill exposure, mounting, peripheral connections and repair arrangements for the demands of your venue.

You may be able to, provided the EPOS software supports the device, operating system and required peripherals. A computer suitable for back-office reporting is not necessarily approved for running the selling interface or integrated payments. Ask the supplier to assess exact specifications, then test printing, cash drawer operation and payment connections. Consider whether the device can withstand counter use, stay powered throughout service and receive security updates. Obtain explicit confirmation for EPOS Bookings rather than assuming any browser or tablet is supported.

The right receipt printer is one explicitly supported by your EPOS application and selling device. Thermal printers are common at counters, but connection options such as USB, Ethernet or Bluetooth vary by model and software. Check paper width, print speed, automatic cutting and any cash-drawer connection. A printer that works with a Windows computer may not work with a tablet till. Ask for an approved model list and test receipts, reconnection and reprinting before deploying it during service.

A receipt printer produces the customer’s transaction record, usually showing purchased items, totals and payment information. A kitchen printer produces preparation tickets with orders, modifiers and identifiers such as table numbers. Both may be connected to the EPOS system, but routing and ticket layouts depend on software configuration. Thermal printing is common at counters; impact printers can suit hotter kitchen environments. Check exact device suitability, ticket legibility and how amendments are communicated, rather than assuming any receipt printer will serve every kitchen station.

A kitchen display system, or KDS, presents preparation orders on a screen instead of relying solely on printed tickets. It combines display hardware with software that receives orders from supported sales channels. Depending on the product, staff can acknowledge orders, mark items complete or monitor elapsed preparation time. Restaurants should test routing between stations, amendments, modifiers and canceled items. Leisure cafés may need simpler queue handling. EPOS Bookings advertises kitchen display tools, but specific functions and supported equipment require confirmation.

A KDS can help teams view queues, update order status and monitor preparation times, while printers provide physical tickets that some kitchens prefer. Neither is automatically better for every venue. Compare ticket volume, station layout, staff habits and how changes or cancellations are handled. Screens need suitable mounting, power and dependable connectivity; printers need paper and maintenance. A mixed setup may suit some kitchens. Test a busy service scenario and agree a fallback process before replacing an established preparation workflow.

A self-service POS kiosk is a customer-facing device that runs software for tasks such as browsing a menu, selecting items and completing a purchase. It may combine a touchscreen, payment terminal and printer, but functionality depends on the application. Ordering kiosks differ from check-in kiosks, which validate an existing booking or admission. For hospitality and leisure buyers, assess accessibility, queue space, menu clarity and staff assistance. Confirm how orders reach preparation teams and how failed transactions or unavailable items are handled.

Yes, kiosks designed for ordering and payment can let customers choose products and pay using a supported payment device. They need an appropriate software licence, catalog and connection to the venue’s fulfilment workflow. Test modifiers, sold-out items, receipts, failed payments and refund procedures. A kiosk intended for booking check-in may not support food ordering or payment. EPOS Bookings lists self-service kiosk software, but the available ordering, payment and admission functions should be demonstrated for the specific equipment and modules proposed.

If you accept cash, a secure drawer is usually practical for storing notes, coins and change, although an EPOS application does not inherently require one. A cashless counter may have no need for it. Some drawers open through a compatible receipt printer, while others use a direct connection or manual key. Check compatibility and who can trigger drawer opening. Hospitality and leisure venues should also define float, cash-counting and reconciliation procedures, since a drawer alone does not provide cash control.

Yes, many EPOS products support barcode scanners for quickly identifying retail items, but compatibility depends on the scanner model, connection and selling device. Products need correctly assigned barcodes in the catalog. A leisure venue selling merchandise may benefit from scanning, while a café may mainly use touchscreen buttons. Scanning booking QR codes is a separate workflow and may need different software or scanner capabilities. Confirm support for the codes and tasks you actually use, including mobile-screen scanning where required.

Compatible card terminals can integrate with an EPOS till so the sale amount is sent automatically and the payment result returns to the software. The connection may use a local network, Bluetooth or a cloud service, depending on the solution. A physical cable is not always involved. Check the exact terminal, processor and software integration, including refunds and connectivity requirements. EPOS Bookings advertises integrated payments, but supported providers, devices and contractual terms must be verified for your proposed installation.

Yes, supported handheld devices can let staff enter table orders and send them to kitchen or bar stations without returning to a fixed till. Some setups also support payment on the device or through a paired terminal, but ordering and payment are separate capabilities. Test Wi-Fi coverage, battery life, table identification, modifiers and order amendments. For a pub or restaurant, consider how devices work alongside existing tills. Confirm supported handheld models and licences before assuming EPOS Bookings provides your preferred tableside workflow.

There is no fixed terminal count for a venue of a given size. Estimate simultaneous demand at your busiest points: bar service, café orders, reception check-in and customer payments. Separate bottlenecks caused by selling from those caused by fulfillment or admission checks. A handheld or customer kiosk may relieve some pressure, but it needs its own workflow assessment. Test staffing and transaction scenarios, and compare additional licences and equipment costs against the benefit of faster service and useful backup capacity.

The response depends on which device fails and what alternatives your setup supports. Another authorized till may continue sales, while a failed printer may require rerouting tickets or a manual order process. A broken payment terminal can need a separately approved replacement or alternative payment method. Agree support contacts, replacement times and access to spare devices before purchase. Keep a tested fallback procedure for sales and admissions, and reconcile any manual records afterwards. Confirm whether repairs, loan equipment and call-outs are included.

Integrated EPOS payments connect the sales software with a supported payment service and terminal. The till sends the amount to be collected, and the payment result returns to the transaction record, reducing manual re-entry and helping reconciliation. This differs from recording ‘card’ after using an unrelated terminal. Check how the integration handles failed attempts, refunds, split bills and connection loss. Compare processing fees and contract terms alongside convenience. Integration does not remove the need to check settlement reports and investigate discrepancies.

With an integrated terminal, the EPOS system sends the amount and receives the payment outcome through a supported connection. With a standalone terminal, staff normally enter the amount themselves and then record the payment in the till. Standalone equipment can offer flexibility, but manual entry creates more opportunities for mismatched totals. Integrated setups can simplify reconciliation but may restrict processor or hardware choices. Compare contracts, connectivity and refund workflows, and test how either approach behaves when the till or terminal becomes unavailable.

A POS setup can accept contactless payments when it includes a compatible reader or supported phone-based payment service and an active processing account. The till software alone does not read a contactless card. Acceptance rules, transaction limits and requests for additional verification depend on the payment method and provider. For busy counters, check speed, reader placement and how successful payments are recorded. Confirm the proposed equipment and processor, and do not assume normal contactless functionality remains available during an internet outage.

Many modern payment readers support Apple Pay and Google Pay alongside contactless cards, subject to the processor and device configuration. Customers typically present an eligible phone or watch to the reader; the POS software then records the sale through its supported payment workflow. Online wallet acceptance is a separate capability that needs its own checkout integration. Ask your supplier to demonstrate the methods you want in person and online, and verify refunds and reporting. EPOS Bookings’ exact wallet support should be confirmed for your chosen payment setup.

Yes, an online booking system can collect advance payment when connected to a supported payment gateway or checkout service. Full payment, deposits and later balance collection are distinct workflows, so check each one you need. Test whether a failed or abandoned payment releases reserved capacity and whether successful payment triggers the correct booking confirmation. For UK leisure and hospitality venues, make cancellation and refund terms clear before checkout. Confirm EPOS Bookings’ supported payment arrangements and booking-payment behaviour rather than assuming every option is included.

Many booking and EPOS platforms can take a deposit or full prepayment when a customer reserves. EPOS Bookings publicly describes deposits and prepayments within its online payments offering. Confirm whether deposits can be fixed amounts or percentages, how they appear on the final bill, and what happens after cancellation. For example, a restaurant taking £10 per person should be able to identify that deposit clearly when the table later settles its remaining balance.

Online booking systems commonly support full payment at checkout, which suits ticketed activities, parties and fixed-price events. EPOS Bookings states that customers can pay in advance and that payments can link to bookings or activities. Ask how payment status appears at check-in and in reports. For example, a prepaid soft play session should be clearly marked as paid so reception can admit the family without accidentally charging them again.

A well-integrated booking and POS workflow should make a deposit visible and allow it to be accounted for when the customer settles the remaining balance. The exact EPOS Bookings workflow should be demonstrated for your configuration rather than assumed. Ask for a booking-to-checkout example. If a party costs £300 with a £75 deposit, staff should be able to identify the £225 balance without checking a separate spreadsheet or calculating it manually.

Refund capability is common in payment-enabled EPOS systems, but the route, permissions and timing depend on the software and payment provider. EPOS Bookings publicly lists refund and cancellation handling, including refunds or credits. Confirm whether staff can refund the original payment, whether partial refunds are supported, and what audit trail remains. For example, you may need to refund one canceled child from a larger family booking rather than reverse the whole transaction.

Some booking and payment systems support partial refunds, but this should not be assumed for every configuration or payment provider. Ask EPOS Bookings to demonstrate the exact process and whether the remaining booking stays valid. This matters for groups. If eight trampoline places were prepaid and one guest drops out, you may want to refund one place while keeping the other seven attendees, their session and associated booking details intact.

The commercial rule comes from your cancellation and deposit policy; software should help you apply that rule consistently. EPOS Bookings advertises deposits plus refund or credit handling, but confirm how cancellation windows, retained deposits and credits are configured. Decide your policy before setup and display it during booking. For example, you might allow a refund before a stated deadline but retain a deposit for a late cancellation, subject to your published terms.

Integrated systems can link a payment to the reservation, activity or order that generated it, reducing manual matching. EPOS Bookings states that payments can link automatically to reservations, activities or orders. Ask how this appears in daily reporting and how exceptions are handled. A useful test is creating an online booking, taking an additional payment on site, then checking that staff can identify both transactions against the same visit without duplicating revenue.

EPOS reports usually show recorded sales and payment methods, while your payment provider and bank show processed transactions and settlements. Reconciliation means comparing those records and investigating differences such as refunds, fees, timing or failed payments. Do not assume one report covers every layer. Ask which EPOS Bookings reconciliation reports are available. A sensible routine is comparing POS card totals with provider totals, then matching settlements when they reach the bank.

Payment-provider compatibility should be confirmed for your exact account, terminals and required payment flows. EPOS Bookings promotes integrated payments and customization, but that does not establish compatibility with every processor or device. Provide your provider name, terminal models, online payment requirements and contract constraints. Ask for written confirmation or a demonstration. This avoids discovering later that countertop payments work but online deposits, refunds or another important workflow require a different arrangement.

Most business EPOS systems provide sales reporting, but export formats and direct accounting integrations vary. EPOS Bookings describes reporting within its EPOS offering; confirm exactly what can be exported and whether an accounting package connection is available for your setup. Ask for a sample export before purchase. Your accountant may need gross sales, VAT breakdowns, refunds, tips and payment types, while settlement fees may still need separate records from the payment provider.

For most restaurants, prioritise fast order entry, table management, kitchen routing, payments and clear end-of-day reporting. Reservations and online ordering may also matter. EPOS Bookings publicly offers restaurant table management, online reservations, kitchen display or printer workflows and QR table ordering. Build your shortlist around your real service journey. For example, a full-service restaurant should test moving tables, amending orders and sending items to the kitchen during a realistic busy-service demonstration.

They can be when booking and POS components are properly connected. EPOS Bookings states that its restaurant solution combines reservations with table management, ordering and payments. Confirm how a reservation becomes an occupied table and whether booking details remain visible to authorized staff. Ask for a demonstration using your floor plan. Staff should be able to find a 7:30 booking, seat the party at an appropriate table and open the order without unnecessary re-entry.

Online reservation tools let customers choose available times without phoning, and EPOS Bookings publicly lists online reservations for restaurants and cafés. Confirm how availability rules, party-size limits, booking intervals and closed periods are configured. A useful test is Friday evening: if you only want certain party sizes at 7:00, the online choices should reflect those rules rather than exposing every table and potentially creating an impractical seating plan.

A connected reservation and table-management system can reduce double-booking by maintaining a shared view of availability. EPOS Bookings states that its restaurant reservations sync with table management to prevent double-booking. Still test manual bookings, walk-ins, table combinations and edits. For example, ask what happens when two four-person tables are combined for a party of eight and whether those tables immediately stop appearing as separately available for the same service period.

Table-management software often provides a visual floor plan so staff can open orders and see table status. EPOS Bookings specifically describes custom table layouts and managing orders by tapping a table. Confirm who can edit the layout and whether temporary changes are easy during service. If tables 10 and 11 are combined for a large booking, staff should understand how the system represents that arrangement without losing track of the bill or availability.

Hospitality POS systems commonly route orders to kitchen printers or kitchen display screens. EPOS Bookings lists both KDS and kitchen printer workflows for restaurants, cafés, pubs and takeout businesses. Confirm whether items can route by preparation area, such as bar, hot kitchen or dessert station. During a demo, place a mixed order and check where each item appears. The practical goal is fewer verbal handoffs and less re-keying during a busy service.

A kitchen display system, or KDS, shows incoming orders on screens rather than relying only on printed tickets. It can help teams track what is waiting, being prepared or completed, although workflows vary. EPOS Bookings offers KDS functionality. Choose based on your kitchen: a small café may prefer a printer, while a busy restaurant or takeaway may benefit from screens. Ask to test order changes, cancellations and multiple preparation stations before deciding.

QR ordering can let guests scan at their table, view a menu, order and potentially pay on their phone. EPOS Bookings publicly offers QR code table ordering and says restaurant orders can link to the POS and kitchen. Confirm how table identity, menu availability, service charges and payment work in your setup. For example, test whether an order from table 14 reaches the correct preparation point and appears clearly alongside orders entered by staff.

Hospitality EPOS software can support both counter and table workflows, but the exact way tabs, tables and payment states are managed varies. EPOS Bookings offers table management, KDS and QR ordering for pubs and bars. Ask the supplier to demonstrate your service mix rather than assuming a restaurant workflow fits. For example, test a customer who orders drinks at the bar, later orders food at a table and needs the transaction to remain easy to identify.

Open tabs and split bills are common hospitality requirements, but their exact availability and rules should be confirmed for the proposed EPOS Bookings configuration. Ask to see how staff identify a tab, add later orders, split by item or amount, and close it securely. Use a realistic demo: four guests share food, buy separate rounds and then want two payments. If that workflow takes too many steps, it may slow service during busy periods.

Many café EPOS systems distinguish service types while keeping orders in one interface. EPOS Bookings states that its café solution can manage dine-in and takeaway activity alongside table management and kitchen tools. Confirm how receipts, kitchen tickets and order labels differ. During a demo, enter one table order and one takeaway order for similar items. Staff should be able to tell them apart immediately at preparation and handover, without relying on memory.

Stock control is a common EPOS capability, but detail varies from finished-item counts to ingredient-level recipes. EPOS Bookings says its café system can track ingredients such as coffee, milk and pastries and lists inventory management. Ask how recipes, wastage, deliveries and stock adjustments work. For example, selling one latte might ideally reduce coffee and milk quantities, but verify that your chosen configuration supports the level of ingredient tracking you expect.

Sales reporting can help identify best-selling items and trading patterns when transactions are consistently recorded. EPOS Bookings describes reporting for café sales and popular items, and reporting is part of its wider EPOS proposition. Ask what date, product, category and location filters are available. A practical use is comparing weekday breakfast sales with weekend afternoons, then using that evidence to adjust preparation levels, staffing or menu placement rather than relying on memory.

A connected takeaway setup can bring several order channels into one operational queue, reducing duplicate entry. EPOS Bookings states that phone, online and walk-in orders can be managed together and promotes online ordering connections. Confirm exactly which online channels you use and whether each has a supported integration. If your website and a delivery marketplace are important, ask for both workflows to be demonstrated so staff are not forced to retype one channel manually.

EPOS Bookings says its takeaway offering can connect with a business’s own website or third-party delivery platforms, but that does not establish support for every platform. List the marketplaces you use or plan to use and ask for written compatibility confirmation. Also check menu syncing, order acceptance and status updates. The key decision is whether orders enter your kitchen workflow automatically or still require staff to copy them from a separate tablet.

Takeaway EPOS systems can route accepted orders to kitchen printers or a KDS, and EPOS Bookings publicly describes both options. Confirm what triggers printing, whether different items route to different stations and how duplicate tickets are prevented. Test an online order and a phone order during the demo. Both should be clearly labelled and reach the right preparation point, so kitchen staff can work from one dependable queue rather than checking multiple screens.

Meal deals, item modifiers and extras are important for many takeout businesses, but the exact promotion and menu-building tools should be confirmed rather than assumed. Ask EPOS Bookings to build one of your real orders during the demo: for example, a pizza meal with size choice, crust option, toppings, drink and paid extra. Check both the customer-facing price and kitchen instructions. If complex orders are awkward to enter, errors can outweigh other benefits.

Hospitality systems often provide amendment and void workflows, but controls differ because kitchens need a clear record of changes. EPOS Bookings offers connected ordering and kitchen tools; ask specifically how post-send changes work. Test a realistic case: a guest changes a side after the order reaches the kitchen. The important question is whether the kitchen receives an unmistakable update and whether the till keeps an audit trail rather than silently replacing the original instruction.

It can if the chosen modules and configuration support each service channel. EPOS Bookings markets POS, table management, QR ordering, online bookings and takeaway ordering across hospitality, but confirm how the pieces work together for your venue. Map your customer journeys first. A café-bar might need morning counter orders, lunchtime tables and evening QR ordering. Ask the demo to cover all three journeys and show how sales and kitchen work remain clearly separated.

Use your busiest real workflows rather than accepting a generic feature tour. Ask to create a reservation, seat it, enter and amend an order, route items to kitchen, take payment, refund something and run an end-of-day report. For takeaway, add phone and online orders too. EPOS Bookings publicly offers many of these modules, but configuration matters. Bring a sample menu and awkward scenarios; the key test is whether ordinary staff can complete them efficiently.

A soft play system should usually handle timed sessions, capacity, family bookings, payments and fast arrival checks, with party and café workflows often important too. EPOS Bookings publicly lists activity slot scheduling, family and group bookings, online payments, capacity control, digital waivers, QR or kiosk check-in and café or retail integration. Start with your busiest Saturday journey. Test a parent booking three children, paying online, completing required details and checking in without reception re-entering information.

Family booking tools can allow one customer to reserve places for multiple children in a single transaction. EPOS Bookings specifically advertises family and group bookings for soft play, with one payment. Confirm what information can be collected for each child and how pricing varies by age or session if needed. Test one adult booking three children of different ages, then check whether reception sees the party together while still having the individual details your venue requires.

Capacity control is central to session-based venues. EPOS Bookings states that soft play operators can set timed sessions and manage visitor numbers. Confirm whether capacity can vary by session, activity area or attendee type, and how walk-ins affect remaining availability. For example, you might allow 60 children on a standard session but fewer during a toddler event. The system should reflect the limits you configure so online bookings stop when the relevant capacity is reached.

EPOS Bookings publicly states that parents can pre-book soft play sessions and pay in advance. Confirm the checkout information you can collect, the payment journey and what the customer receives after purchase. Then test arrival from the staff side. For example, a parent who has already paid for two children should be easy to find at reception, with the booking clearly showing its payment status so the queue keeps moving and staff do not accidentally charge twice.

Party bookings often need more than a standard admission slot: capacity, room or table allocation, deposits, food, extras and a remaining balance may all matter. EPOS Bookings advertises family and group bookings and broader customization; confirm the exact party workflow you need. Ask the supplier to model one of your packages. For example, test a 15-child party with a deposit, optional food upgrades and a final headcount deadline, then see what staff receive on the day.

EPOS Bookings specifically promotes café and retail integration for soft play, including snacks, drinks and merchandise through the EPOS system. Confirm how admissions, café sales and retail items appear in reporting and whether separate preparation or stock workflows are available where needed. For example, test a family buying entry online, then ordering lunch and grip socks on site. Staff should be able to process each sale clearly without confusing admission revenue with food or retail sales.

Self check-in can move routine arrival steps away from the reception desk, especially when guests have already booked and paid. EPOS Bookings advertises QR-code and kiosk check-in for soft play. Confirm what customers must complete before entry and what happens when a booking cannot be found. A useful test is a busy Saturday arrival wave: compare how prepaid families, walk-ins and customers with incomplete details are handled so exceptions do not simply create a second queue.

EPOS Bookings publicly offers digital waiver management for trampoline parks and describes collecting consent with booking-related workflows. That does not by itself determine what wording, retention period or legal process your venue requires. Confirm how waivers are presented, stored, searched and checked at arrival, and obtain appropriate legal advice on your waiver content. Operationally, test whether a customer can book a jump session, complete the required waiver and arrive with staff able to verify completion quickly.

Family venues often need to know which participant has a completed waiver, not merely whether the booking holder signed something. EPOS Bookings advertises family-friendly digital waivers, age restrictions and expiry tracking, but confirm the exact participant-linking workflow for your setup. Test a parent booking three children where only two waivers are complete. Reception should be able to identify the outstanding requirement clearly, rather than opening several records or relying on a paper checklist.

Timed capacity control helps trampoline parks avoid selling more places than a session or activity area is configured to accept. EPOS Bookings lists activity slot scheduling and capacity or session management for trampoline parks. Confirm whether limits can differ by session, zone, ticket type or day, and how walk-ins consume availability. For example, if a quieter toddler session has a lower limit than an evening open-jump session, the booking system should apply the appropriate configured capacity to each.

EPOS Bookings advertises an online booking widget for trampoline sessions, parties and products. Confirm how party packages differ from ordinary jump sessions, especially where rooms, food, deposits, extras or minimum numbers are involved. Ask for both journeys in a demo. For example, a standard one-hour jump may need only a time and attendee count, while a birthday party may also need a party room, food choices and a balance due later.

An integrated venue POS can sell admissions alongside café and retail products, and EPOS Bookings publicly promotes POS use for entry fees, cafés and retail sales at activity venues. Confirm how products are categorised, stocked and reported in your configuration. For example, test a customer buying a jump ticket, mandatory grip socks and a drink. You should be able to see whether staff can complete the transaction efficiently and whether each item reaches the correct stock or preparation workflow.

Many attraction systems can combine admission with optional products or upgrades, but the exact bundling and pricing rules vary. EPOS Bookings describes POS, online bookings and product sales for amusement and leisure settings; confirm the specific package builder you need. Test a real transaction such as two admissions plus an activity upgrade and food voucher. The important decision is whether customers can buy the combination cleanly and whether staff can recognize each entitlement at the relevant point of service.

Self-service kiosks can reduce routine counter transactions by letting guests purchase tickets or check in, depending on configuration. EPOS Bookings publicly lists self-serve kiosks and automated check-ins or ticket purchases for leisure and amusement settings. Confirm which journeys your proposed kiosk supports, what hardware is required and how exceptions reach staff. For example, test a prepaid booking, a same-day ticket purchase and a customer who needs help, rather than judging the kiosk only on its simplest screen.

Multi-activity venues often need separate calendars, durations and capacity rules for different attractions. EPOS Bookings states that leisure venues can manage multiple activities and schedule lane times, pool sessions or classes. Confirm how many calendars your proposed package includes and how shared resources are handled. For example, a center offering bowling, climbing and classes should test overlapping bookings and resource limits, ensuring a customer cannot reserve a time that depends on equipment or space already committed elsewhere.

Memberships may involve recurring payments, passes, visit entitlements and renewal rules. EPOS Bookings publicly says its leisure offering supports recurring payments, passes and membership tools. Confirm the exact billing provider, retry process, cancellation workflow and membership rules for your configuration rather than assuming they match your current scheme. For example, ask how a monthly member is recognized when booking a class and what staff see if the member’s payment or entitlement is not current.

Operational reporting can help venues understand demand patterns and decide when to adjust staffing, session schedules or promotions. EPOS Bookings publicly describes reporting on peak times, popular activities and customer trends for leisure venues. Ask which filters, exports and date comparisons are available in your proposed setup. For example, compare Saturday morning soft play attendance with weekday afternoons, or identify which activity sessions regularly fill first, then use that evidence when reviewing future timetables.

A useful venue system should let staff account for walk-ins without losing sight of capacity already committed to online customers. EPOS Bookings advertises POS, booking and capacity tools, but confirm exactly how walk-ins are added to sessions in your configuration. Test a session with 40 places where 35 are already booked online and a family of four arrives without booking. Staff should be able to admit them while leaving an accurate remaining capacity rather than maintaining a separate count.

Check the operational workflow separately from the legal adequacy of the waiver. EPOS Bookings advertises digital waivers, age restrictions, expiry tracking and related check-in tools, but software availability does not establish that a particular waiver meets your legal or insurance requirements. Ask how signatures, participant links, timestamps, expiry and retrieval work, then review your wording and retention approach with appropriate advisers or insurers. A good demo should include an incomplete waiver and show exactly how staff spot it before admission.

Ask the supplier to run your busiest customer journey from start to finish: online booking, family or group details, payment, waiver where required, capacity reduction, arrival, check-in, café or retail purchase, refund and reporting. EPOS Bookings publicly offers many of these components, but your configuration matters. Bring a real party package and an awkward exception, such as one missing waiver or a partial cancellation. The demo should prove how staff handle normal visits and problems without parallel spreadsheets.

Start with the work your team needs to complete: sell the right places, collect payment, prepare arrivals and handle changes. Bring a busy-day timetable to your demonstration, including groups and walk-ins. Ask to follow one booking from checkout to reception, then amend it. Compare the proposed configuration against these tasks and obtain a written list of included features, equipment and ongoing charges before choosing a system.

Yes. EPOS Bookings lists guest checkout for activity bookings. Decide whether occasional visitors should use that route and how staff will locate their reservations later. Test the information collected at checkout, the reference customers receive and the process for correcting an email address. Keep membership journeys separate when evaluating the setup, rather than making every first-time visitor follow the same registration process. See the EPOS Bookings page.

EPOS Bookings supports family and group bookings. For your demonstration, supply a realistic mix of children, accompanying adults and non-participating visitors. Ask how that group appears to reception and how its places are allocated. Confirm any rules for participant ages, supervision ratios and group limits individually. Supporting a group booking does not establish that every combination of ticket dependencies or eligibility checks is already configured. See the EPOS Bookings page.

Define admission categories around your venue’s actual entry rules, including visitors who enter without participating. Specify age boundaries, required accompanying adults and which categories consume capacity. Ask the supplier to demonstrate the combinations you intend to sell, including free places. Confirm whether dependencies and quantity limits can be enforced in your proposed setup, then check that reception receives enough information to resolve an incorrect selection.

EPOS Bookings offers both reservation and activity-booking workflows, but they allocate different resources. A restaurant booking reserves table time, while an activity booking allocates session places. Map those requirements separately during evaluation. If customers need a play session and a café table together, request a demonstration of that combined journey and confirm its scope before advertising it as a single reservation. See the EPOS Bookings page.

Yes. EPOS Bookings describes deposit and full-payment options for activity bookings. Decide which approach applies to each booking type and document when any balance becomes due. Ask to demonstrate a deposit booking, a changed headcount and final settlement. Confirm the payment setup and balance-collection process rather than assuming automatic collection or a particular payment provider is included in your proposed solution. See the EPOS Bookings page.

Start with the admission limits established for your operation, then decide how those translate into bookable places. Account for parties, accompanying visitors and any areas sharing the same space. EPOS Bookings supports capacity around activity slots. Ask how your particular ticket categories affect availability and test a nearly full session. The configured sales limit needs to reflect your venue’s operational requirements. See the EPOS Bookings page.

Evaluate both sales routes against the same session using a realistic last-place scenario. Ask which availability staff see when making an on-site sale and what happens if another customer completes checkout simultaneously. Confirm how reserved group allocations and manual adjustments are handled. Obtain an agreed workflow for exceptions and demonstrate the behaviour in the proposed EPOS Bookings setup before relying on it during peak admissions.

A basket hold should be treated as a configuration question to confirm. Ask whether places are reserved before payment, when a hold starts and how it expires. Test abandoned checkout, failed payment and two customers requesting the last place. If a timer is offered, check the wording customers see. Your reception team also needs to understand whether apparently unavailable places are sold or temporarily held.

Confirm waiting-list functionality with EPOS Bookings rather than assuming it accompanies capacity controls. Describe whether you need automatic notifications, a staff-managed queue or a limited acceptance period for released places. Ask what happens after a cancellation and how the next customer pays. If the agreed setup uses manual follow-up, assign responsibility and publish clear expectations so customers do not mistake a waiting-list request for a confirmed booking.

Yes. EPOS Bookings describes website reservations and telephone bookings recorded by staff. Build a standard reception script covering location, time, guest details and the applicable payment terms. During the demonstration, enter a telephone reservation and inspect how it appears in the appointment calendar. Confirm staff access and the process for correcting mistakes so both channels produce information colleagues can use consistently. See the EPOS Bookings page.

EPOS Bookings describes multi-location reservation functionality. List each site’s services, durations and operating rules before evaluating the setup. Ask how staff identify the booked location, which records they can access and how a customer-facing confirmation names the site. Confirm any requirement to transfer a reservation between locations separately, particularly where payment handling, availability or equipment differs between branches. See the EPOS Bookings page.

Write the policy first: notice periods, eligible booking types, permitted outcomes and who can approve exceptions. Then ask EPOS Bookings to demonstrate how those rules are represented in your proposed workflow. Check the customer instructions and staff actions for cancellations before and after the deadline. Confirm automation, permissions and recordkeeping individually so your published policy matches what the configured system and team actually do.

Do not assume cancellation automatically refunds a payment. Ask EPOS Bookings to confirm the refund workflow for your payment setup, including approval requirements and how a partial refund is recorded. Test a canceled admission, a deposit and an additional item on the same booking. Staff should know when availability is released and how to communicate the payment outcome without promising an unverified processing time.

Set an amendment deadline and define how staff check replacement availability before confirming a move. Ask to demonstrate the change with paid tickets, a deposit and a different session price. Confirm whether the customer receives revised information and which reference remains valid. Include a reception step to review the new slot and any wristband allocation, so an accepted amendment is reflected throughout the visit.

Specify how your venue treats reduced numbers, substitutions and additions, then demonstrate each case. Ask whether changes affect capacity, the booking total and any minimum group commitment. Confirm who can authorise a refund or additional charge and what reception sees afterward. Keep party-package rules distinct from ordinary admission tickets so staff can apply the appropriate policy without cancelling an entire group unnecessarily.

Include the venue location, date, start and finish times, booked quantities, payment position and reference. Add concise arrival instructions, any required waiver step and the route for amendments. Review the message on a phone using a realistic family or restaurant reservation. Ask which fields and templates your proposed setup allows staff to edit, then check that an amended booking produces clear, current information.

Yes. Confirmations and reminders are described on EPOS Bookings’ reservation page. Agree the communication channels, delivery timing and wording for your configuration. Request examples for a new reservation and a changed time, and clarify how staff handle an incorrect address or missing message. Do not advertise SMS, specific reminder schedules or delivery reporting until those details have been confirmed for your solution. See the EPOS Bookings page.

Create a lookup procedure that checks the booking and payment outcome before anyone repeats the sale. Record the customer’s details, selected session, transaction time and available reference. Ask the supplier to demonstrate a failed or interrupted checkout and explain what staff can inspect. Specify escalation and customer communication steps, including how to distinguish a completed reservation from a payment attempt awaiting clarification.

EPOS Bookings’ activity-booking page describes booking cut-offs as part of timetable configuration. Decide how much preparation time each activity needs and whether staff can accept later arrivals through a separate process. Test availability immediately before and after the agreed cut-off. Confirm how exceptions are authorized and communicated so customers are not sold a session your team cannot realistically prepare or admit. See the EPOS Bookings page.

Compare the complete admission journey: ticket selection, payment, arrival verification, exceptions and any on-site sale. Bring examples of date-based entry and timed tickets if you offer both. Ask how different admission categories affect availability and what staff see when a ticket is amended. Assess reporting and hardware requirements separately, then confirm the exact scope of the proposed solution against your busiest reception period.

Yes. EPOS Bookings describes advance ticket bookings and relevant on-site ticket sales through EPOS. Demonstrate both routes for the same admission period and check how staff work with current availability. Include a customer adding an extra visitor at reception. Agree ticket presentation, payment equipment and the staff process before launch rather than treating the online checkout and counter sale as unrelated workflows. See the EPOS Bookings page.

EPOS Bookings supports QR scanning within a staff-led admissions process. Use the demonstration to check how a scan locates the relevant booking and what reception must verify before entry. Include the ticket formats customers will actually present. Agree an assisted lookup route for unsuccessful scans and ensure that a successful scan does not cause staff to skip other required admission checks. See the EPOS Bookings page.

Give staff a short sequence: check the current ticket, improve screen readability and try the approved scanner position. If that fails, use the agreed booking lookup route instead of selling a replacement ticket immediately. Ask EPOS Bookings which details staff can search and how the assisted admission is recorded. Test poor screen brightness and an outdated ticket during setup to expose practical reception problems.

Confirm the accepted formats and code behaviour for your specific ticket setup. Test a phone display and printed ticket with the proposed scanner, including normal reception lighting. Ask whether screenshots remain valid after a booking change and whether any codes refresh. Publish instructions that match the demonstrated behaviour, and provide an assisted route for customers who cannot present the approved ticket format on arrival.

Define whether staff admit individual guests, smaller subgroups or the entire booking at once. Demonstrate staggered arrivals and ask how remaining attendees are identified without duplicating admission. Agree how the organiser shares booking details and what later arrivals need to present. Confirm the recordkeeping available in the proposed setup, so reception can distinguish a located group reservation from the number of people actually admitted.

Ask EPOS Bookings to demonstrate the validation rules for your proposed ticket journey, including a second scan and a copied code. Specify whether tickets are named, transferable or valid for multiple entries. Confirm what warning staff see and who can override it. Publish a policy consistent with the configured checks rather than assuming that the presence of a QR code alone prevents ticket sharing.

Decide whether re-entry is permitted and how staff verify that a returning visitor still has valid admission. Demonstrate the proposed exit and return process, including a previously scanned ticket. Confirm whether it requires software recording, a physical pass or another agreed method. Make the original session finish clear, and keep re-entry permission separate from any purchase of additional play time or another session.

EPOS Bookings describes touchscreen kiosks with optional compatible payment terminals, printers and QR scanners. Choose components around the task: selling a ticket requires a different journey from locating a prepaid booking. Request an itemised configuration showing the included equipment and connections. Test peripheral reach and output positions in your reception layout before ordering, and identify who replenishes printer consumables where printing is required. See the EPOS Bookings page.

Kiosk options can support check-in depending on the venue setup, according to EPOS Bookings’ soft play page. Ask to demonstrate your actual booking type, its QR presentation and the result shown after identification. Confirm whether staff must still issue wristbands or verify a waiver. Position the kiosk within an arrival process that clearly directs customers to their next step. See the EPOS Bookings page.

Run a realistic ticket purchase from the first screen to the completed admission instruction. Include mixed ticket categories, a nearly full session and payment failure. Ask which functions belong to the configured software and which depend on optional hardware. Observe whether customers can find payment and receipt points easily. Confirm assistance arrangements and the equipment included in the quotation before committing to the installation.

Define how staff verify the transaction before retrying payment or issuing another ticket. Ask the supplier to explain the records available after interruption and the recovery procedure for your hardware. A printing failure may leave a valid sale that still needs an admission document. Give reception a clear escalation route, and test how customers are directed to staff when the kiosk cannot complete its normal journey.

Map which activities and participants require a waiver under your venue’s policy, then ask to demonstrate the relevant check at reception. EPOS Bookings describes waiver checks as part of suitable admissions journeys. Confirm how staff identify missing or outdated information and what happens before entry is authorized. Define a practical exception process rather than assuming that a ticket scan proves every consent requirement is complete. See the EPOS Bookings page.

A ticket scan records an admissions action, but EPOS Bookings explicitly distinguishes that from live occupancy. Departures, re-entry and staggered groups need additional consideration. If occupancy is a buying requirement, specify the entry and exit information you need and ask how it will be captured. Confirm any gate, turnstile or specialist access-control scope separately before treating a displayed admissions total as current building occupancy. See the EPOS Bookings page.

Keep an assisted reception route for customers who cannot use the touchscreen or present a scannable ticket. Review approach space, screen reach, communication needs and access to staff when planning the installation. Confirm the lookup process available in your proposed software and train colleagues to use it. Test the complete assisted journey alongside self-service, including how the customer receives session instructions and any required wristband.

Yes. EPOS Bookings describes timed soft play bookings and capacity management. Bring your actual session timetable, admission categories and party allocations to a demonstration. Ask how places are offered for each slot and what reception sees when customers arrive. Review the proposed setup against busy school-holiday operations, including changeovers, rather than judging it solely by whether customers can select a time online. See the EPOS Bookings page.

Measure the time customers need for the activity and the work staff complete between groups. Include collecting belongings, departures and your preparation routine when designing the timetable. Test the proposed schedule during representative busy periods before publishing it. Ask how the software represents session durations and breaks, and avoid selling back-to-back places when the operational process needs a gap to prepare the next admission.

Define the admission cut-off, any required briefing and whether the original finish time still applies. Ask the supplier to demonstrate what reception sees for a late customer and how an approved move is recorded. Make the rule clear at checkout and in arrival instructions. If staff offer a different slot, verify capacity and any payment adjustment before issuing its session information or wristband.

Present the exact overlap pattern to EPOS Bookings and ask to see it across booking availability, reception and session management. Check how your capacity requirements apply when two groups share space. Decide how staff identify each group and where early arrivals wait. Confirm the behaviour of the proposed schedule rather than assuming that separate slots automatically account for every shared area or equipment constraint.

Set a policy for additional time, including availability, payment and whether customers must leave during changeover. Ask to demonstrate an extra session purchase and any amendment to the original allocation. Reception should communicate the new finish clearly and review the wristband color where needed. Confirm that the proposed workflow reflects actual capacity and preparation time, rather than letting staff extend visits informally without checking the next group.

EPOS Bookings assigns colors to activity slots so reception can issue matching physical wristbands after checking the booking. The band provides a visual reference for the customer’s timing group. Evaluate it using your daily schedule and the colors staff keep at reception. Agree who checks the allocation and explains the finish time, then practise the handover between reception and activity-floor staff. See the EPOS Bookings page.

The published feature describes physical wristbands used as a visual color reference, and states that it does not automatically track the wearer’s location. Do not treat that feature as evidence of RFID, gate opening or electronic child tracking. If those functions matter to your purchase, specify them separately and request a confirmed technical proposal covering equipment, compatibility and the intended workflow. See the EPOS Bookings page.

Use distinct colors for groups whose different finish times would otherwise be difficult to recognize. Keep a clear schedule available to reception and floor staff, and check that the bands stocked match the planned allocation. Avoid reusing a color while it could confuse active groups. Trial the arrangement during a busy overlap and confirm how software color settings fit your intended timetable before introducing it.

Create a reception procedure that verifies the booking before replacing a lost band or changing its color. For customers unable to wear a band, agree an alternative way for staff to identify the session without assuming one approach suits every visitor. Document who approves exceptions and how floor staff are informed. Confirm any software records needed for that workflow with EPOS Bookings during configuration.

Yes. EPOS Bookings describes configured announcements before a session finishes and at its end, including messages addressed to wristband color groups. Agree the timetable and customer wording during setup, then demonstrate a complete session sequence. Confirm the onsite audio arrangement separately. Staff still need to manage departures and prepare the space, so include the announcement feature within your normal changeover routine. See the EPOS Bookings page.

Observe several changeovers and identify when families need to start gathering children and belongings. Use that evidence to choose an advance reminder and a clear finishing message. Make each announcement identify the relevant group and give a useful next action. Test the schedule during busy periods, then adjust it if families consistently leave late or start preparing unnecessarily early because the message is unclear.

EPOS Bookings says audio hardware and speaker requirements need confirmation for each venue. Provide details of your current equipment, coverage areas and desired message route. Ask for a proposed arrangement that identifies any additional hardware or installation work. Test intelligibility with normal venue noise and music, then agree how staff deliver a live reminder if the scheduled audio cannot be heard. See the EPOS Bookings page.

EPOS Bookings lets venues plan suitable wording around session timing and the relevant color group. Prepare short messages that identify the customers concerned and explain the next action. In your demonstration, ask how wording is configured and who can update it. Confirm any requirements for different languages, voices or separate audio zones individually rather than assuming these options follow from scheduled playback. See the EPOS Bookings page.

Use several ways to communicate the finish: booking information, reception explanations, visible session details and personal reminders where needed. Plan an agreed approach for customers requiring communication support. Check whether messages are intelligible in seating and activity areas during service. Assign staff to support the finishing group, because an announcement playing successfully does not establish that every customer has heard or understood it.

Test a representative day with overlapping groups, timetable changes and a missed message. Confirm the right group is addressed at the intended time and that staff know the live-announcement fallback. Observe actual departures and readiness for the next admission, rather than checking playback alone. Agree who reviews the daily schedule and audio setup, then record any unresolved configuration or hardware requirements before relying on the process.

EPOS Bookings describes membership schemes linked to customer profiles, with relevant booking and EPOS processes available around the member journey. See the EPOS Bookings page. Start by defining eligibility, benefits and the visits your membership covers. Ask for a demonstration showing enrolment, a member booking, arrival and a café purchase. Confirm which parts are included in your chosen plan and whether your particular benefit rules need additional configuration.

A membership gives customers a defined relationship with your venue, such as eligibility for agreed access or benefits. A loyalty scheme rewards qualifying purchases or visits under your rules. EPOS Bookings distinguishes these approaches on its membership software page: the EPOS Bookings page. Decide whether your priority is predictable membership income, repeat visits or additional spending. Ask the supplier to demonstrate the relevant rules, especially if members also earn loyalty rewards.

Define who belongs to the family membership, how many children it covers and whether adults can change between visits. Ask EPOS Bookings to demonstrate your proposed household structure rather than assuming a customer profile supports every family arrangement. Check whether each child needs a separate record, how reception identifies eligible visitors and what happens when a child reaches an age limit. Confirm pricing rules and any restrictions before advertising the membership.

Ask EPOS Bookings to confirm the payment method and renewal workflow available for your specific membership package. Membership management alone does not establish that automated collections, retry rules or customer cancellation tools are included. Request an example covering the first payment, renewal notice, failed collection and final cancellation. Clarify payment provider charges, authorization requirements and how staff see an unpaid membership before deciding whether to admit the customer.

Agree the practical rules before setup: when benefits stop, whether a pause extends expiry and who can approve exceptions. Ask the supplier to show how those states appear to reception staff and how future bookings are affected. EPOS Bookings buyers should confirm whether expiry checks, pauses and cancellation changes are supported in their proposed configuration. Include a member who booked before expiry but arrives afterwards in the demonstration to expose ambiguous rules.

EPOS Bookings lists loyalty schemes on its soft play page: the EPOS Bookings page. The public description does not establish every possible points, stamp or reward mechanism. Bring a simple example, such as a reward after qualifying visits, and ask the team to demonstrate earning and redemption. Confirm eligible purchases, expiry, refund treatment and whether customers must identify themselves before payment. Publish only the reward rules your agreed setup can actually apply.

Ask for a demonstration using the same customer across an online booking and an on-site sale. Establish which activities qualify, how the customer is identified and when the reward balance updates. Do not assume that online and till rewards share a balance merely because both sales channels are available. For EPOS Bookings, confirm the supported earning channels, redemption locations and any synchronisation delay in writing before promoting a combined loyalty offer.

Your scheme should explain whether a refund reverses earned rewards and what happens if the customer has already redeemed them. Ask the supplier to demonstrate a full refund, a partial refund and a return after redemption. Confirm whether adjustments happen automatically or require authorized staff action. EPOS Bookings buyers should verify the behaviour for their chosen scheme, including how adjustments are recorded, so staff can resolve disputes without inventing a policy at the till.

The EPOS Bookings membership page describes members showing a QR code on their phone for staff to scan on arrival: the EPOS Bookings page. Ask the team to demonstrate the screen staff see after scanning and the checks still required for your venue. Confirm compatible scanning equipment, how a member retrieves their code and the alternative process when their phone is unavailable. Include any required booking or waiver checks in reception training.

A QR reference for identifying a member does not by itself establish automatic gate access. Tell EPOS Bookings the gate manufacturer, controller model and required admission rules, then request written compatibility confirmation. Ask who installs and supports the connection and how access behaves during network failures. Demonstrate expired memberships, repeated scans and emergency procedures before relying on automated entry. Keep a staffed fallback process appropriate to the venue and its equipment.

Prepare a reception fallback that verifies the customer without exposing another person’s details. Ask EPOS Bookings to show the available member lookup process and explain which staff permissions it needs. Decide what information is sufficient to identify the member, how exceptions are recorded and when a supervisor should intervene. Avoid promising admission based only on a stated name. Test poor mobile reception, a flat battery and a customer who cannot access their account.

The soft play page confirms guest checkout for customers who do not want to create an account: the EPOS Bookings page. Guest checkout can still require the information needed to fulfil a booking. Ask to see the exact fields, confirmation message and arrival reference in your proposed setup. Check how customers request changes and whether membership benefits require identification through a separate process. Keep account creation and optional marketing choices clear to the customer.

Confirm this workflow with EPOS Bookings before promising it to customers. Ask whether staff can associate an existing guest booking with a verified profile and how duplicate records are avoided. The demonstration should cover a customer using a different email address, an existing membership and an earlier guest payment. Establish whether booking history, waivers or loyalty eligibility transfer, and who can approve the change, rather than assuming all records merge automatically.

Collect information that serves a clear booking, membership or service purpose. A name and contact details may be enough for some journeys; family activities can require additional participant information. Decide why each field is needed and explain its use in your privacy information. Ask EPOS Bookings which fields are configurable, who can view them and how corrections are made. Avoid using free-text notes to collect unnecessary sensitive information about customers or children.

Ask the supplier for an import template, supported fields and a safe way to preview the result before importing your full database. Confirm how duplicates are detected and whether merging preserves bookings, membership history and marketing preferences. For EPOS Bookings, these migration details should be demonstrated for your actual source data. Start with a small authorized sample, resolve inconsistent email addresses and retain a protected backup so mistakes can be corrected.

Compatibility depends on the named product, version and workflow you need. EPOS Bookings advises reviewing specific third-party ordering platforms on the EPOS Bookings page. Prepare a list of your accounting, website, payment and ordering services, then ask which connections are supported today. Confirm what data moves, its direction, update frequency and additional charges. Request a working demonstration and identify who supports each connection before replacing a process that already works.

Ask EPOS Bookings to confirm compatibility with your exact accounting product and subscription before assuming a connection exists. A sales export and an automated accounting integration provide different levels of service. Specify whether you need daily totals, individual invoices, payment fees, VAT breakdowns or refunds. Have your accountant review a sample output and confirm reconciliation steps. Obtain written details of setup costs, ongoing connector charges and responsibility for failed transfers.

Ask EPOS Bookings to show how a customer would move from your current website into the booking journey. Confirm whether the supported approach is a link, embedded component or another arrangement, and who implements it. Test mobile usability, session selection, payment and confirmation using your branding. Clarify domain requirements, accessibility considerations and any website maintenance costs. An online booking service does not automatically mean every website platform supports the same installation method.

EPOS Bookings describes online collection ordering, including menu choices, order identification, collection timing and a configured payment journey. See the EPOS Bookings page. Ask for a demonstration using your menu and opening hours. Confirm how collection slots, sold-out items and special requests are handled, and what the customer receives after payment. Check the staff handover process as carefully as the ordering screen so meals reach the correct customer.

Do not assume these marketplaces are connected because an EPOS system offers online ordering. Ask EPOS Bookings to confirm each named service, your region and the required workflow. Its ordering page calls for platform-specific compatibility review: the EPOS Bookings page. Check menu updates, order acceptance, cancellations and payment reporting separately. Clarify whether a third-party connector is involved, what it costs and which supplier investigates missing or duplicated orders.

EPOS Bookings describes online collection, QR table ordering and staff-led table service within configured restaurant workflows: the EPOS Bookings page. Relevant orders can use a kitchen display or printer route. Ask to see each channel with your actual preparation stations, table references and collection details. Confirm item routing, timing and how amendments reach the kitchen. Test a cancellation after preparation starts, because changing payment status may require a separate operational response.

Confirm stock synchronisation as a separate requirement, including the exact online shop platform. Ask which system holds the master stock record, how quickly changes transfer and how returns or canceled orders affect availability. Demonstrate two customers trying to buy the last item through different channels. For EPOS Bookings, obtain written confirmation of the supported connection and failure handling. Inventory functionality alone does not establish synchronisation with an external shop.

Ask EPOS Bookings for current API documentation and access terms before planning development. A willingness to discuss customization does not establish a public, self-service API. Confirm authentication, available endpoints, permitted data, rate limits and whether a test environment exists. Describe the business workflow you need rather than requesting generic access. Obtain written details of developer support, version changes, security responsibilities and any charges before commissioning code that depends on the service.

Request confirmation of event notifications or webhooks for the specific events you need, such as a new booking, cancellation or payment change. Ask about retries, duplicate delivery, event ordering and how missed updates are recovered. If EPOS Bookings cannot provide that mechanism, discuss supported alternatives and their expected delay. Your developer should test failure recovery and use stable record identifiers so repeated messages do not create duplicate bookings or transactions.

Agree responsibility before launch, especially when the EPOS supplier, website agency and connector provider are different businesses. Identify the first support contact, what evidence they need and who can restore service. Ask how failed transfers are detected and replayed, and whether temporary manual entry will create duplicates later. For EPOS Bookings, request support boundaries and any integration maintenance charges in the quotation, alongside a practical fallback for your busiest trading periods.

Prepare your product list, prices, tax settings, booking rules, staff roles and existing equipment details. Map a normal sale and the exceptions staff regularly handle, such as refunds or booking changes. Ask the supplier to confirm network requirements, installation responsibilities and the go-live timetable. EPOS Bookings buyers should agree what setup work is included in the quote and arrange time for staff to practise with the configured system before serving customers.

Compatibility depends on device models, operating systems, connection types and supported drivers. Give EPOS Bookings the exact equipment list rather than relying on a generic description such as USB printer. Ask which items are approved, which need replacement and who supports reused equipment. Test a complete transaction, printed receipt and scan before ordering. Include device age, warranty status and replacement costs when comparing reuse with a new hardware package.

Ask for a demonstration of the exact failure scenario instead of assuming offline operation. Sales, card authorization, online bookings and kitchen routing may behave differently when connectivity is lost. EPOS Bookings should confirm which functions remain available, what data is stored locally and how synchronisation resumes. Test reconnection for duplicate transactions and stock changes. Agree a fallback reception and payment procedure that staff can follow during a busy service.

Plan the cutover around the data you genuinely need: upcoming bookings, active memberships, product records and historical reports. Ask both suppliers about export formats, migration scope and access after cancellation. Reconcile a sample before importing everything, and keep protected copies of essential records. With EPOS Bookings, confirm migration responsibilities and timing in advance. Choose a manageable go-live window and document how staff handle transactions or bookings created during the changeover.

Bring specific questions, such as which sessions sell out, which products perform well and how refunds affect takings. Ask for reports using a representative trading day, including cash, card, online payments and discounts. EPOS Bookings buyers should confirm available filters, reporting periods and exports rather than assuming every metric is included. Check whether reports show gross sales, net sales or payments received, because those figures answer different business questions.

Reports can support reconciliation when their definitions match your accounting process. Ask the supplier to show a sale, deposit, partial refund and mixed payment, then trace each through the reports. Confirm how VAT categories and rounding are configured with your accountant. For EPOS Bookings, request a sample export and an explanation of settlement reporting. Do not assume till totals equal bank receipts, as processing fees and settlement timing can create differences.

Ask how locations are represented, whether reports combine them and how staff are restricted to the sites they manage. Compare like-for-like periods and confirm whether local pricing or different opening hours affect the figures. EPOS Bookings buyers should verify the proposed multi-location package, reporting access and additional charges. Request a demonstration using two locations with different products or activities so shared catalogs and site-specific reporting are clear before rollout.

Define roles around real responsibilities: reception, café service, supervisors and administrators. Ask EPOS Bookings to demonstrate permissions for refunds, discounts, exports and customer details in your chosen setup. Check whether restrictions apply consistently across tills and remote access. Give each employee an individual account where supported, and remove access promptly when they leave. Review who can override a restriction and whether that action leaves a record managers can investigate.

Treat remote access and audit history as separate requirements. Ask EPOS Bookings which devices and reports are supported remotely, how accounts are protected and whether additional authentication is available. Request an example showing a changed booking or refunded sale, including the staff identity, time and reason recorded. Confirm retention and export options for that history. A cloud dashboard alone does not establish a complete audit trail or every security control you need.

No software purchase guarantees your business complies with UK data protection law. You need appropriate purposes, privacy information, access controls and documented responsibilities for handling customer data. Where a supplier processes personal data on your behalf, review the required processor contract; see the ICO guidance. Ask EPOS Bookings for contractual and security information relevant to your setup. Assess your own booking, membership and marketing practices rather than treating a vendor statement as a compliance certificate.

Ask EPOS Bookings for the hosting locations, subprocessors and support access arrangements that apply to your contracted service. Confirm whether personal data is transferred internationally and what safeguards apply where required. Review encryption, backups, access logging and incident notification responsibilities with the supplier. Request the relevant data processing terms rather than relying only on a website privacy notice. Include information about children or waivers in your assessment where your venue collects it.

Create a process for locating customer records, assessing rights requests and separating information still needed for another lawful purpose. Ask EPOS Bookings to demonstrate available correction, export and deletion tools, including related booking records. Keep marketing choices separate from operational messages and review the applicable UK GDPR and PECR rules. The ICO explains planning considerations at the ICO guidance. Confirm retention settings and supplier assistance before promising customers that every record can be immediately erased.

The useful comparison is the complete package for your business, including software, equipment, payment processing and implementation. EPOS Bookings publishes industry-specific pricing and recommends confirming the full quotation: the EPOS Bookings page. Specify your locations, tills, users and required modules so quotes are comparable. Ask which charges recur, whether VAT is included and what changes after an introductory offer. Avoid treating a software subscription as the total cost of a working venue setup.

Ask for separate lines covering hardware, installation, training, migration, payment fees, integrations and ongoing support. Check charges for extra users, locations, replacement devices and services billed by another provider. Establish whether taxes are included and when annual price changes can occur. EPOS Bookings buyers should have required modules and any custom work named in the written quote, so a low headline subscription does not obscure the cost of the configuration they need.

Compare the total payable over the same period, including any discount, setup costs and features required. Annual billing may reduce the subscription amount but can tie up cash and change refund or cancellation options. Ask EPOS Bookings to confirm the current annual total and when payment is collected. Check whether the agreement renews automatically and whether changing plans affects unused payments. Choose the arrangement that fits your cash flow and expected business stability.

Use realistic journeys rather than only exploring menus. Test a booking, payment, arrival, café sale, amendment, refund and end-of-day reconciliation with the staff who will operate the system. Record issues and ask the supplier to explain whether they need configuration, training or development. For EPOS Bookings, confirm the trial’s included modules, equipment and support before starting. Agree clear acceptance criteria so the trial answers your purchasing questions within the available time.

Cancellation rights depend on the agreement you accept, including minimum term, notice period, renewal rules and any separate finance or payment contracts. Ask for those documents before signing. With EPOS Bookings, confirm how cancellation is submitted, when billing stops and whether prepaid amounts are refundable. Establish how to export your data and how long access remains available. Do not assume monthly invoicing means there is no longer contractual commitment.

Ask how plan changes take effect, whether charges are prorated and whether annual commitments restrict downgrades. Check what happens if a lower plan supports fewer users, activities or locations than you currently use. EPOS Bookings should confirm the rules for your selected industry and billing arrangement. Before upgrading, identify the specific limit or feature you need; before downgrading, export relevant information and agree how existing bookings and staff access will be handled.

Request a training schedule covering the roles that will use the system, including supervisors responsible for refunds and reporting. Ask whether training is live, recorded or provided through written guides, and whether new starters incur additional charges. EPOS Bookings buyers should confirm the training included in their package and the cost of further sessions. Use your own bookings, menu and exception scenarios so employees practise the tasks they will perform at work.

Match support coverage to the periods when an outage would disrupt your venue most. Ask about contact channels, response targets, urgent escalation and responsibility for hardware or payment faults. Confirm what is included and whether enhanced cover costs extra. For EPOS Bookings, obtain the agreed service hours in writing rather than interpreting a contact page as a support guarantee. Keep essential account references and a practical fallback procedure available to supervisors.

Compare the limits against your actual staffing and activities. As checked on 1 October 2026, the soft play pricing cards list Basic at £69 monthly, Standard at £89 and Premium at £130: the EPOS Bookings page. Basic lists three users and three activity calendars; Standard lists six of each; Premium lists unlimited users and calendars. These are industry-specific software prices. Confirm VAT, equipment, required modules and the complete written quote before enrolling.

The current soft play page describes a trial lasting one calendar month, with email verification and account approval required: the EPOS Bookings page. It also says Direct Debit setup and billing dates are explained during registration. Confirm the exact start and end dates, included features and any equipment arrangements before activating it. Ask when paid billing begins and how to decline continuation, so your team can test the proposed setup with clear expectations.

Do not assume the software subscription includes physical equipment. EPOS Bookings separates software plan comparisons from the wider setup and asks buyers to confirm hardware and other costs: the EPOS Bookings page. Request an itemised equipment schedule showing terminals, printers, scanners, kitchen displays and any kiosk you need. Confirm ownership or rental terms, installation, warranty and replacements. If reusing equipment, ask for compatibility approval before accepting a package based on that saving.

EPOS Bookings says suitable software improvements can be provided without an additional charge when requirements and scope are discussed and agreed: the EPOS Bookings page. This is conditional, so request written confirmation for your own requirement. Describe the workflow, external equipment or service and acceptance criteria. Agree delivery timing, testing and ongoing support, and clarify any hardware or third-party charges before relying on a proposed change for launch.

You can reach EPOS Bookings through the contact page or by calling 0203 727 7212: the EPOS Bookings page. For technical support, confirm the hours and channels included in your plan, especially if your venue trades at weekends or in the evening. Ask how urgent trading problems are escalated and who handles hardware, payment or integration faults. Keep the agreed support details available to supervisors so they know whom to contact when service is interrupted.