Parkcore Blogging Site

Every Report Built Into Parkcore, and the Decision Each One Is Built to Answer

Status: Most of what's below is live today; a couple of newer additions are still finishing rollout, flagged where relevant. (14/10/2026)

Quick answer:

Parkcore's Reports section covers occupancy and revenue, full payment history for any pitch or owner, gas and electricity meter readings, card takings across every payment channel, till sales reconciled against stock, and stock and purchasing data — all drawn from the same underlying records rather than separate exports. Together they answer the handful of questions that actually determine whether a park is being run well: are we full, are we getting paid, what did we sell, and what's left on the shelf.

There's an old test for whether a business actually knows how it's doing: ask the person in charge a simple question — how did last month go? — and watch what happens next. If the answer takes thirty seconds and a screen, the business has reporting. If it takes an afternoon, a spreadsheet and a phone call to accounts, it has data, scattered, which is a different and far less useful thing. Most holiday parks have plenty of data. Not all of them have reporting.

A report, done properly, isn't a pile of numbers. It's a specific question, answered reliably, by someone who didn't have to go hunting for the answer. "Are we full this weekend?" is a question. A twelve-tab spreadsheet is not an answer to it, however carefully it's kept. Parkcore's Reports section exists because a park manager asks the same handful of questions over and over, all season, and each one deserves its own clear answer rather than a general-purpose export everyone has to interpret by hand.

Overview and occupancy: are we full, and will we be

The Overview report is the first thing most managers actually look at — a live read on arrivals, departures and occupied units right now, the same data that drives the main dashboard. It answers the most basic operational question there is: is the park full, and if not, where are the gaps? Because it's built from the same booking records as everything else, a guest checked in at reception shows up as occupied immediately, not after some overnight batch job catches up. The report exports to CSV for anyone who wants to work with the numbers directly.

Alongside it sits revenue reporting — Average Daily Rate and Revenue Per Available Pitch, the two figures that separate "we're busy" from "we're profitable." A park running at 90% occupancy on deeply discounted pitches can earn less than one running at 70% at a sensible rate, and ADR and RevPAU make that visible instead of felt. Occupancy answers whether the park is full. Revenue answers whether being full is actually worth it.

Payment History: has this pitch, or this owner, actually paid

Reception and accounts spend a disproportionate amount of time on one question: has this been paid? Parkcore's Payment History report answers it two ways. Pick a pitch, and see every booking that unit has ever had — dates, status, what was taken, what's outstanding — without scoping to a date range, because the point is the complete picture. Pick an owner instead, and see their full invoice history the same way: invoiced, paid, still owing.

The value shows up in exactly the moment it's needed — a guest on the phone insisting they've already paid, an owner querying a balance — when the answer should take seconds, not a search through a filing cabinet or a separate accounts package. Both views export to CSV and print to a branded PDF.

Meter readings have everything recorded

Meter Readings: what did this pitch actually use

For parks that bill owners or long-stay guests for gas and electricity, meter reading history used to live wherever someone happened to write it down — a notebook, a spreadsheet, memory. Parkcore's Meter Readings report has three parts: recording a new reading against a pitch, utility and register (including the day/night split for Economy 7 meters); a per-pitch usage report over any date range, showing opening and closing readings and the consumption between them; and an all-time park-wide summary across every pitch and utility. A meter replacement is handled sensibly — if the serial number changes between readings, the report flags it rather than reporting a nonsense or negative figure. Both views export to CSV and print to PDF.

This answers a question that's easy to ignore until it costs real money: is utility usage in line with what's being billed, and is any one pitch drifting from its normal pattern in a way worth a closer look.

Card Takings and Till Sales & Stock: does the money agree with the goods

Wherever card payments happen — reception, the shop, the bar, or an owner settling a site fee at the desk — Parkcore's Card Takings report shows exactly what was taken, when, and through which channel, because every payment flows through the same recorded system rather than a separate machine with its own disconnected log. Till Sales reporting shows what was actually sold, item by item, tied to the same transactions, and Stock reporting shows how those sales moved what's on the shelf.

The point of reporting all three together is that they can't quietly disagree. In a typical setup with a separate EPOS till and a separate card machine, "does the till agree with the bank?" means pulling two reports and checking them against each other by hand when something looks off. Because Parkcore's three reports are views of the same underlying transactions, agreement is the default rather than something a manager has to verify every week. Both print cleanly for an end-of-day handover, with printing kept to admin, manager and superadmin roles, since a printed financial report is a physical document that can leave the building.

Stock, movements and purchasing: what's here, what happened to it, and what to order next

Beyond the till, Parkcore keeps a full stock list — every item, its supplier, its price, its current level, flagged clearly when it's low or out — exportable and printable for a stock take or a supplier conversation. Every change to that stock is logged individually in a movement history: a sale, a delivery, a correction, damage, waste, each with its own reason and timestamp, rather than a single running total that can't explain how it got there. Click into any item for its full history; click into any supplier for what they've delivered.

Built on top of that history, reorder suggestions calculate what each item actually needs, based on real sales velocity and each supplier's lead time, grouped by supplier so a purchase order can be raised directly from the suggestion. This piece is newer and still finishing rollout, but the stock list and movement history underneath it are already live and already answering the question that matters most at the till: do we actually know what we have.

How this compares to reporting bolted on after the fact

Plenty of park software can produce a report. Fewer can guarantee two reports about the same event will actually agree, because fewer are built so the event is only ever recorded once. A separate EPOS system, card machine and booking platform can each report accurately on their own slice of the business and still leave a manager reconciling the gaps between them every week. Parkcore's reports draw on one shared set of records, not three systems each approximating the same reality — the difference between a report you read and one you have to double-check.

Key takeaways

  • Parkcore's Reports section covers occupancy, revenue (ADR/RevPAU), payment history by pitch or owner, meter readings, card takings, till sales and stock, and stock movements and purchasing.
  • Each report answers a specific, recurring operational question rather than producing a general-purpose export to interpret by hand.
  • Because every report draws from the same underlying transaction records, figures that should agree — like till sales and card takings — do, by default, without manual reconciliation.
  • Payment History and Meter Readings both export to CSV and print to branded PDF; Card Takings and Till Sales & Stock print with access limited to admin, manager and superadmin roles.
  • Reorder suggestions and purchasing reporting are the newest additions and still completing rollout; the stock list and movement history beneath them are already live.

Frequently asked questions

Occupancy and revenue reporting, Payment History (by pitch or owner), Meter Readings, Card Takings, Till Sales & Stock, and stock movement and purchasing reporting — all reached from the same Reports section.

Yes. Payment History and Meter Readings export to CSV and print to a branded PDF. Card Takings and Till Sales & Stock print cleanly for end-of-day handovers, with access limited to admin, manager and superadmin roles.

Because both are built from the same underlying transactions rather than two systems each keeping their own record. Agreement is the default, not something needing manual checking.

Most of it — Overview, revenue, Payment History, Meter Readings, Card Takings and Till Sales & Stock are all live. Reorder suggestions and purchasing reporting are newer and still completing rollout.

Parks that want one place to answer "are we full," "have we been paid," and "does the till agree with the stock" can see how Parkcore's reports draw all three answers from the same connected data.

Steve Richards headshot

Bio for Stephen Richards: 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!

Steve left School in 1976 joining the Royal Air Force to work on RADAR and communications equipment. His last 5 years involved working 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.

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 with his last project moving email from a Linux Box to Microsoft Echange 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 was an MSP and moved to become an MSSP following another of Steve's passions Cybersecurity. Officially 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 two significant pieces of software have been created. Netmon the Network Monitoring Software and the second release Parkcore aimed at Caravan/Lodge Holiday Parks..... And so it begins!