Offline in the cellar: what a real cloud has to manage

The cellar has no Wi-Fi. The vineyard has dead spots. And the walk-in customers turn up in the yard exactly when the line is down. Anyone choosing business software should therefore look closely at what “cloud” is supposed to mean — the word covers three very different architectures.

Architecture 1: installed locally

The classic program on the office computer. It runs without internet — that is its real advantage, and it is often underrated.

The price: it runs only there. Whoever enters something in the cellar writes it down and retypes it later. Whoever needs information while out and about phones the office. Updates and backups are your business — until the day the machine will not start and the last backup is three weeks old.

Architecture 2: runs only in the browser

What is usually called “cloud” today: an application running on a server and operated through a browser. Reachable everywhere, always up to date, nothing to install, backed up centrally.

The catch fits in one sentence: without a connection nothing works at all. Not “limited” — nothing. No entry, no delivery note, no invoice, no information. In a cellar with no signal the application is not slow, it is gone.

Anyone hoping to solve that with a mobile repeater is only moving the problem. A cellar behind a metre of stone is not a reception problem you can amplify away.

Architecture 3: runs locally, synchronises centrally

The third variant installs itself on the device — phone, tablet, computer — and keeps its own working copy of the data there. It is operated locally, saves locally, and as soon as there is a connection again, device and server reconcile.

To the user that looks like a cloud: the same data everywhere, no updates, nothing to install in the classic sense. Only without the dependence on the line at the moment of entry.

The practical case everything turns on

Saturday morning, three customers in the yard, one of them wants six cases and an invoice. At that moment the internet goes down.

• Installed locally: works — provided you are in the office and not in the yard.
• Browser only: you write by hand and retype it on Monday. The till is locked, the delivery note is handwritten, and the stock figure is wrong until you catch up.
• Synchronising: you write the delivery note and the invoice as always. The device remembers everything. When the connection comes back, it is up there — without anyone having given it a thought.

The question to ask when choosing

Not: “Is it cloud?” But:

What happens if I switch off the connection right now — can I still write an invoice and make a cellar entry?

There are only two answers to that question, and both are informative.

What synchronisation has to manage

Being able to work offline is not enough on its own — what matters is what happens when things are brought back together. Two points decide it:

• Conflicts have to be detected, not overwritten. If two devices have made entries on the same vessel, the later one must not simply win.
• Document numbers must not be duplicated. Two invoices written offline with the same number are a problem you only notice at an inspection.

Anyone looking at an offline-capable solution should ask exactly these two questions. They separate a thought-through synchronisation from a buffer.

Why this counts for more in viticulture than elsewhere

In most industries the connection is where the work is. Not at a wine estate. The work happens in the cellar, in the row, in the yard, in the cold store — in precisely those places where reception is the exception. Software that only works at a desk moves the work back to the desk.

And with that you are back where you started: the evening appointment with the pile of notes.