Parkcore Blogging Site

Every Stock Change, Explained: Why an Audit Trail Beats a Running Total
Parkcore logs every single change to stock — a sale, a void, a refund, a delivery, damage, waste, a stock count, a correction — as its own dated, reasoned entry, not just an adjustment to a running total. Click any stock item and see its full history: not just what the current count is, but exactly how it got there, one movement at a time.

Status: Available now.

Quick answer:

Parkcore logs every single change to stock — a sale, a void, a refund, a delivery, damage, waste, a stock count, a correction — as its own dated, reasoned entry, not just an adjustment to a running total. Click any stock item and see its full history: not just what the current count is, but exactly how it got there, one movement at a time.


Accountants have a saying worth borrowing: a number without a reason attached to it isn't a fact, it's a claim. A bank balance that simply says "£4,200" tells you almost nothing useful compared to a statement showing every deposit and withdrawal that added up to it — and the moment something looks wrong, it's the statement, not the balance, that actually lets you find out why. Stock levels in most retail systems are handled the first way: a single number that goes up or down, with no record of why, overwritten silently every time something changes.

What a running total quietly hides

Picture a stock count that shows 40 units of something on Monday and 31 on Friday. A simple running-total system tells you that and nothing more. It doesn't tell you whether nine were sold, whether two were voided after a till error, whether one was given away as a refund, whether three arrived damaged and were written off, or whether someone did a physical count and corrected an error from weeks earlier. All of those produce the exact same final number, and all of them mean something completely different for the business — one's healthy sales, one's a till process worth tightening up, one's a delivery worth raising with a supplier, one's shrinkage worth investigating.


A running total answers "how much is left." It can't answer "why," and "why" is usually the more useful question.

What Parkcore actually records

Every stock change in Parkcore is logged as its own entry, with an explicit reason: opening stock, a sale, a void, a refund, a delivery received, damaged stock, waste, a physical count, a manual correction, an edit, or other. Nothing adjusts the stock figure silently — every single change to how much of something exists is a dated record explaining what happened and why, tied to the item it affects.


This is hooked directly into the till itself: a sale reduces stock automatically the moment it's rung through, a void or refund reverses it the same way, and nothing requires a separate manual step to keep the stock figure honest. Click into any individual item and see its full history — every movement, in order, building up to today's figure — or look at deliveries specifically, each one tied to the order it came from where applicable. One further protection worth knowing about: stock can't be pushed below zero by any of this. If the numbers would imply negative stock, Parkcore logs what actually happened rather than quietly accepting an impossible figure.

Stock NEVER goes Below Zero

Why "it never goes below zero, and nothing adjusts silently" matters

Both of those sound like small technical details. In practice, they're what makes a stock figure genuinely trustworthy rather than something a manager has learned to mentally discount. A system that can drift to a negative number, or that allows a figure to be edited without a trace of who changed it or why, is a system where "the stock count says 12" is treated as a rough guess rather than a fact — and once staff stop trusting the number, they stop using it, and a feature built to save time ends up ignored instead.

How this compares to most retail and park software

Most EPOS systems, including the ones bundled into other park management platforms, track a current stock figure and little else — a number that moves when a sale happens, with adjustments typically made by simply overwriting it. Genuine movement-level history, with an explicit, structured reason for every change, is the kind of feature usually reserved for dedicated retail inventory systems costing far more and built for entirely different businesses — not something a holiday park's shop or bar would normally expect, let alone get built into the same platform as its bookings and guest data.


The practical consequence of not having this is familiar to anyone who's tried to investigate a stock discrepancy using a system that only keeps a running total: there's nothing to investigate. The number is what it is, and working out why it's wrong means reconstructing events from memory, till receipts, and guesswork. With a full movement log, the investigation is just reading — every change is already there, dated and explained.

What this unlocks beyond "knowing what happened"

A proper movement log isn't only useful after something's gone wrong. It's also what makes Parkcore's reorder suggestions genuinely reliable, since they're calculated from real sales velocity drawn directly from logged sale movements, not from a running total that might include unexplained drift. It's what lets waste and damage be tracked as their own visible category, rather than disappearing into an unexplained gap between what should be on the shelf and what actually is. And it's what makes a stock count — the physical, walk-the-shelves kind every shop does periodically — genuinely useful: the correction it produces is recorded as its own entry, not a silent overwrite that erases the question of how far off the previous figure had drifted.

The conversation this changes

The conversation this changes

There's a specific recurring conversation in any business that sells physical stock: "didn't we have more of these?" In a park without movement-level history, that question tends to end in a shrug — a vague sense that something doesn't add up, with no real way to confirm it, investigate it, or learn from it. In a park with it, the same question has an actual answer within a minute: a quick look at the item's history shows exactly when stock moved, by how much, and why, whether that's a delivery that was booked in short, a run of legitimate sales, or a pattern of waste worth addressing directly with whoever's responsible for that part of the shop. Turning a shrug into a specific, actionable answer is a small-sounding change that, over a season, adds up to real money — both in waste caught early and in staff time no longer spent debating a number nobody can actually verify.

Key takeaways

- Every stock change in Parkcore is logged as its own dated entry with an explicit reason, not folded silently into a running total.

- Sales, voids, and refunds update stock automatically from the till; deliveries, damage, waste, counts, and corrections are logged just as explicitly.

- Stock can never be pushed below zero — an impossible figure is never silently accepted.

- Movement-level history is rare in park and EPOS software generally, typically found only in dedicated inventory systems built for much larger retail operations.

- The full movement log underpins reliable reorder suggestions and makes investigating any discrepancy a matter of reading the record, not reconstructing it from memory.

Frequently asked questions

Both — every change is logged as its own entry with an explicit reason (sale, void, refund, delivery, damage, waste, count, correction), building up to the current figure rather than replacing it silently.

No — stock can never be reduced below zero; any discrepancy that would imply a negative figure is logged rather than silently accepted.

Automatically. A sale, void, or refund at the till updates stock immediately as part of the transaction, with no separate manual step required.

Because a total alone can't explain a discrepancy — movement history lets anyone see exactly what happened and when, turning an investigation into a quick read instead of a guessing exercise.

Parks wanting stock levels they can actually trust and explain can find full movement history on every item inside Stock & Suppliers in Parkcore today.

Leave a Reply

Your email address will not be published. Required fields are marked *

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!