Running a Small On-Site Shop or Café Without a Dedicated EPOS Team
Plenty of family-run parks have some form of on-site retail — a small shop for essentials and holiday treats, a café serving breakfast and light lunches, sometimes both. For a large operator, running that side of the business comes with a dedicated retail or hospitality team, proper stock systems, and someone whose whole job is keeping the till side running smoothly. For a family park, it's usually one more thing layered onto a team that's already covering reception, bookings, and everything else — which means the EPOS system itself needs to be simple enough to run without dedicated expertise, while still being properly capable underneath.
The real requirements of a small on-site till
A small park shop or café doesn't need the complexity of a large retail chain's point-of-sale system, but it does need the fundamentals done properly: a clear product grid that a seasonal staff member can learn in minutes, an accurate running basket, correct VAT handling without anyone needing to understand VAT rules to operate the till day-to-day, and a proper receipt for every transaction. Anything more complicated than that becomes a training burden a small, often seasonal team simply doesn't have time to absorb.
Why VAT handling matters more than it seems
It's easy to underestimate how much a small mistake in VAT breakdown can cost over a season, particularly for a site selling a mix of standard-rated and zero-rated goods — a shop selling both branded merchandise and basic groceries, for instance, needs the till to apply the correct rate automatically rather than relying on whoever's on shift to remember which category each product falls into. Getting this wrong consistently, even in small ways, becomes a real accounting headache at quarter-end, and correcting it retroactively is far more time-consuming than getting it right automatically at the point of sale.
Voids, corrections, and the trust that comes with a clean process
Mistakes happen at any till — a wrong item rung up, a customer changing their mind, a genuine error in a busy queue. Having a proper, clean void process, rather than an awkward manual workaround, matters both for the practical correction and for the paper trail it leaves behind. A void that's properly recorded, rather than silently adjusted, is the difference between a system that can be trusted for accurate daily reporting and one where small unexplained discrepancies quietly accumulate over a season.
The daily journal as an early-warning system
Beyond the individual transaction, a proper daily journal — a clear summary of the day's takings, broken down by category and payment method — is genuinely useful for more than just bookkeeping. Reviewed regularly, it becomes an early-warning system for stock discrepancies, unusually quiet days worth investigating, or a product category performing better or worse than expected, all visible without anyone needing to manually reconcile a till roll against a stock sheet.
Stock management that fits a small operation
For a small on-site shop, stock management doesn't need to be elaborate, but it does need to exist in some genuine form — knowing what's low, what needs reordering, and what's been sitting unsold for months taking up shelf space. A simple, easily editable stock list attached directly to the same system used for sales removes the need for a separate spreadsheet that inevitably drifts out of sync with what's actually on the shelf.
Why connecting EPOS to the rest of the park matters
The real advantage of EPOS being part of the same platform as bookings and reporting, rather than a standalone till system with no connection to anything else, is that daily takings feed directly into the park's overall financial picture without a separate manual entry step each evening. For a small team already stretched at the end of a long day, not having to separately type the till total into an accounts package is a genuinely meaningful reduction in end-of-day admin, repeated every single day the shop or café is open.
Keeping it simple on purpose
The right measure of a good small-park EPOS system isn't how many advanced features it has — it's how quickly a new seasonal staff member can be trusted to run it confidently on their own, and how little day-to-day attention it needs from an owner who already has a dozen other things competing for that same attention. Simplicity, deliberately built in rather than left out through lack of ambition, is exactly what makes an on-site shop or café a genuine asset for a family park rather than one more system quietly demanding more time than it gives back.
Training a new starter in minutes, not hours
For a role that's often filled by seasonal or part-time staff with limited prior retail experience, the actual usability of the till interface matters enormously in practice, even if it rarely features in a feature comparison list. A product grid that's visually clear, with items grouped sensibly and priced correctly without manual entry, means a new starter can be shown the basics once and left to serve customers confidently within the hour — rather than needing a supervisor standing nearby for the first several shifts, which for a small team is time that's genuinely difficult to spare.
What happens when the shop is unexpectedly busy
A quiet café can be run comfortably even with a slightly clunky system, because there's time to work around any friction. The real test comes on a genuinely busy day — a wet bank holiday when every guest on-site decides to visit the shop within the same hour — and it's exactly then that a slow or confusing till becomes a real, visible problem: a queue building, a frustrated customer, a staff member under pressure making more mistakes than usual. A system built to be fast and simple under normal conditions is what actually holds up when conditions stop being normal.
The end-of-season reconciliation this quietly avoids
Poor
EPOS habits built up gradually across a season — inconsistent voids, stock not
properly tracked, takings not cleanly reconciled day to day — tend to surface
all at once at season's end, when someone finally sits down to make sense of
the whole year's figures. A system that gets the daily basics right
consistently avoids that unpleasant end-of-season reckoning entirely, because
each day's figures were already correct and properly recorded at the time,
rather than needing painful reconstruction months later from incomplete
records.
A small profit centre worth taking seriously
It's
easy for a small on-site shop or café to be treated as an afterthought compared
to the core business of pitch and booking revenue, but for many family parks
it's a genuinely meaningful contributor to overall income, particularly on wet
days when guests are looking for something to do without leaving the site.
Giving that part of the business a properly working, easy-to-run system is a
small investment of attention that tends to pay for itself many times over
across a season, simply by making sure nothing about the till itself gets in
the way of a sale that would otherwise have happened easily.
Born in Colwyn Bay North Wales, Steve's introduction IT & Computers was at secondary school in 1974. That first year, Machine Code was hand written onto gridded paper and sent to Connah's Quay Technical College where is was copied to punch card and then entered into a mainframe computer. The results printed out were sent back for the following week! Yes Steve was around before the Internet and was coding the hard way.
Steve left School in 1976, or as he prefers to say, “I ran
away from home and joined a flying circus” - joining the Royal Air Force to
work as an Electronics Engineer on analogue and digital RADAR and
communications equipment. His last 5 years in the RAF he worked in an Automatic
Test Equipment (ATE) department on the System Management Team and also writing
models for Microchips. It was a good job that he had kept up with computers
which had become rather a passion by the time he started in ATE. After 8 specialist
programming courses for ATE Programming and a Cluster Start Course for System
Administration, Steve was one of the most flexible people in the department.
During that time the main Mainframe we replaced in a £3.9
million upgrade reducing the run time of the biggest ATE program from just
under 2 weeks to the time it took for a finger to come off a depressed return
key!
Leaving the RAF after 18 years’ service, Steve worked for a
Charity (Apex Leicester Project) before returning to electronics at Sonatest in
Milton Keynes which after 3 or 4 years led to a Job at Telematica; the then
development arm of Trafficmaster PLC (Tm). Eventually brought in-house at Tm he
worked moved into the IT Support Team of 5 people looking after 300 users in
the UK as well as sites in Italy, Germany and Benelux countries – 24x7 cover. His
last project moving email from a Linux Box to Microsoft Exchange for the 300
users in the company each of whom typically had 5 email addresses.
In 2006 Steve left to start his own company back in North
Wales, Computer Technical Solutions Ltd (CTS) was an MSP and became an MSSP
following another of Steve's passions Cybersecurity. Whist working full time
running CTS, Steve completed a Masters Degree in Computer Science with
Cybersecurity at Wrexham University.
Officially semi-retiring in 2025, by May 2026 that
overactive mind started thinking about all of the software he had seen not just
for MSSPs but also for his clients that was either extremely expensive or that
didn't exist with a complete answer to the needs of the SME.
By August 2026 Angstep Ltd was formed and two significant pieces of software had been created. Netmon the Network Monitoring Software and the second release Parkcore aimed at Caravan/Lodge Holiday Parks, now in the final development stages and under Beta Release. Determined, focused and loving life… And so, it begins!
