Cellar operations software for South African wineries

Run the cellar.
The work writes the record.

Plan jobs, close them where the work happens, and keep one connected production record without entering the same event twice.

Built and running. Preparing for its first assisted vintage.

One job · one connected record

A work order to rack lot BRD-25-01 off its lees is assigned to Sam. They first move the clean wine from T02 into the empty pre-bottling tank T08. Once the physical transfer is finished, they record 5,048 litres moved and 52 litres left behind as lees. T02 is drained, T08 is updated, the event is appended to the lot history, and Alex approves the completed work order.

The day starts with attention

See what needs a winemaker before opening six screens.

The briefing says what changed and what deserves attention. A stalled ferment is raised against the rest of the active cellar, then opens into the curve that explains it.

Signal
one ferment has stopped falling
Context
healthy and stuck ferments remain side by side
Decision
open the exception, not every tank
Today Open full ↗
Fermentation board Open full ↗

One operation, end to end

A transfer does not become three versions of the truth.

A work order is planned, a cellar operator records what actually happened, and that same event updates the vessel state and the wine's history.

01

One instruction

The move is explicit

The job names the lot, source tank, destination tank and expected volume before the hose is connected.

The work order Open full ↗
02

One movement

The tank state changes

Completion places the actual 5,048 litres in T08 and records what remained behind as lees.

The tank Open full ↗
03

One permanent record

The history is already there

The same completed operation appears in the wine’s lifecycle with its vessel, person and time.

The lot Open full ↗

The three screens follow the same completed transfer in the demonstration cellar.

Planning board Open full ↗
Harvest planner Open full ↗

Plan before the pressure arrives

The fruit, the space and the work ahead belong in one plan.

Incoming loads sit against available vessel capacity. The resulting cellar work lands on the week before anyone has to reconstruct it from a whiteboard.

  1. 01
    Plan

    Fruit, tank space and the week’s jobs.

  2. 02
    Do

    Give the work to the team and close the actual result.

  3. 03
    Understand

    Read the season back from the work itself.

Why it exists

A vintage should not live in a stack of notebooks.

Cellrkit is built by Henry Thomas, a software developer in South Africa. His wife, Petroné, is a winemaker.

For years he watched her carry a season in notebooks, photographs of a whiteboard, and a spreadsheet nobody else could read, then spend the quiet months putting it all back together from memory. Cellrkit is what came out of that.

So it runs the work in a cellar and keeps the record while the work happens. It covers the production side and stops there: no accounting, no sales, no payroll. It is built by Avenera, a South African company, for South African cellars.

One wine, one story

From the weighbridge to the finished case.

The operational flows shown here contribute to one connected production record: lots and vessels, doses and supplier batches, readings, people and times. Material corrections retain the original event, and a blend keeps its parentage back to the fruit.

  1. 01Fruitgrower · block · kilos
  2. 02Winelot · vessel · analysis
  3. 03Workjob · dose · operator
  4. 04Blendparents · proportions
  5. 05Bottlechecks · product · cases
  6. 06Evidencehistory · correction · export
Parentage

The blend remembers where it came from.

Trace the finished lot backwards through every parent lot to the fruit.

Genealogy Open full ↗
Inputs

Every dose keeps its supplier batch.

Dose traceability Open full ↗
Release

Bottling waits for recorded evidence.

Release gate Open full ↗

When production records are needed, the evidence is already organised and there to export.

What it covers

Six areas, from the weighbridge through to the cases in the shed.

Harvest

Plan the picks and take the fruit in, with the grower records kept alongside.

Cellar

Lots, tanks, ferments, lab results and doses in one place.

Work

The week planned on a board, then handed out as jobs and signed off.

Packaging

Bottling runs with their pre-fill checks, and the cases that come out the other end.

Stock

What you hold and where it is, plus the purchase orders behind it.

Reports

Eleven reports read straight off the work, ready to download.

On the floor

Supported work-order tasks can travel with the cellar team.

Planning stays in the browser. The companion app gives the cellar team their supported work-order tasks on a phone, so the result can be recorded where the work happens rather than typed up from paper later.

  • Take a job off your own list, or pick up one nobody has claimed.
  • Complete supported task types with the actual result at the tank.
  • Resolve a vessel from its printed code while connected.
  • Supported job-card writes can queue without signal and sync later.

Runs on

  • Android
  • iOS
  • the same login as the browser

The field result stays with the job.

Where things stand

It has not run a real season yet.

Every screen on this site is the working product, running against Cellrkit's demonstration cellar. What it has not done is carry a real cellar through a real harvest.

The first cellars to run it will be ones we set up and support ourselves, and we are talking to those directly rather than opening it up. If you want to know how it would handle something in your own cellar, ask and we will show you.

What it costs
pricing is not settled, and it is being built to sit inside a working cellar's budget
Setting up
we do it with you: your tanks, additives, catalogues and opening volumes
Your data
the cellar's data belongs to the cellar
Getting it out
reports download as CSV, and the records stay readable

Questions

Is it an ERP for my cellar?
No. It does not do your accounting, your sales, your distribution or your payroll, and it is not trying to. It covers the production side: planning the work, carrying it out, and the evidence underneath. It sits alongside whatever you already use to run the business.
What does it cost?
Pricing is not settled yet, which is why there is no number on this site. It is being built to sit inside a working cellar's budget rather than an enterprise one, and we will agree terms with you directly before anything starts.
Can I see the working product?
The screens across this site are real, straight from the product running against our demonstration cellar. Walk a full season on the How it works page, then mail us if you would like to understand how it handles a question of your own.
Does it file anything on my behalf?
No, and it does not try to. Cellrkit keeps the production record underneath and lets you take it out: what went in, where it went, who did it. Any statutory paperwork stays yours to prepare and submit, exactly the way you do it now.
What happens when someone records something incorrectly?
Material operations are corrected or reversed through an audited path. The original event stays visible alongside the reason, the person and the time of the correction.
What devices will cellar teams use?
The planning and record side runs in a web browser, so the computers and tablets a cellar already has will do. The people working jobs on the floor use the phone app instead, on Android or iOS, which keeps going when the cellar has no signal.

Have a question we have not answered? Mail hello@cellrkit.com and just ask.