Every hive inspection produces a small piece of data — colony strength, stores, disease signs, treatments applied. On their own those notes sit in a drawer. Linked together across a season and rolled up into a ledger, they become the numbers a beekeeping business is actually run on: honey yield, treatment cost, equipment spend and net margin.
This scene shows a small apiary on the left feeding a live monthly ledger on the right. Each hive carries a status halo based on how recently it was logged; a stream of labelled honey jars carries traceable batch data from hive to account book.
UK beekeepers selling honey are expected to keep traceable batch records (lot numbers linking a jar back to the hive and inspection it came from) alongside basic bookkeeping for tax purposes. The same inspection log that catches a failing queen early is also the source data for an accurate set of business accounts.
A small 3D apiary feeds a live monthly ledger: inspection diligence keeps hive status halos green and ledger bars steady, while gaps in record-keeping show up as red surprises and untracked, greyed-out honey batches.
Hive-level inspection data (via a colour-coded halo) and season-driven nectar flow roll up into a twelve-month bar-chart ledger, with labelled honey jars carrying traceable batch data from hive to account book.
Set apiary size and record diligence, pick a season to jump the ledger's active month, and toggle batch traceability to see how missing records leave a month's figures untracked and greyed out.
UK sellers of honey are expected to keep traceable batch records linking a jar back to its hive and inspection — the same log that catches a failing queen early also underpins the business's accounts.