Kitchen Software That Works Without Wi-Fi
Every piece of kitchen software demos beautifully on an office desk. The test that matters is different: a cellar prep room with one bar of signal, a market stall in a field, a van halfway to a wedding venue. Here is what "works offline" actually means for a modern web app, what a cook genuinely needs available with no connection, and how FoodCore handles it — including the data it deliberately does not put on your device.
Why kitchens have terrible signal
It is not bad luck. Commercial kitchens are close to the worst radio environment a small business will ever operate in, and for structural reasons.
Thick walls and steel. Kitchens live in the older, heavier parts of buildings — brick, concrete, sometimes a listed façade you cannot drill through for a repeater. Stainless steel surfaces, walk-in fridges and extraction ducting all reflect and absorb the frequencies mobile phones use. A router two rooms away in the front of house can look fine on paper and be useless at the bench.
Cellars and basements. A great many UK prep kitchens are below ground. Mobile signal underground is close to nonexistent, and Wi-Fi has to travel through a floor to reach you.
Freezer and cold rooms. A walk-in freezer is, electrically speaking, a metal box. Signal does not go in. If your stock count happens in there, it happens offline.
Market stalls and outside catering. A farmers' market in a rural car park, a village hall, a marquee in a field, a food van at a festival with forty thousand other people saturating the same cell — these are the conditions where you most need your recipes and labels, and they are precisely the conditions where you are least likely to have a connection.
Wet hands and one shared tablet. Even where signal exists, the practical reality is a single device, propped somewhere it will not get splashed, being used by whoever is on shift. Anything that requires a fresh login and a page load every time it is picked up will be abandoned within a fortnight.
What "offline" actually means for software
The word gets used loosely. There are three genuinely different things, and the difference determines what happens when the signal drops.
A plain website fetches every page from a server. No connection, no page — this is the majority of "cloud" tools, and it is why so many kitchens end up printing recipes out.
An installable web app uses a service worker: a small piece of code the browser keeps after your first visit, which can serve the application's files from the device instead of the network. Add it to the home screen and it behaves like an app — its own icon, its own window, no address bar — while still updating itself without an app store.
A native app is downloaded and installed. It is not automatically better offline; a native app that fetches everything from a server on launch is exactly as useless in a cellar as a website. The offline behaviour comes from what the app stores locally, not from how it was distributed.
What you actually need offline in a kitchen
Not everything needs to be available with no signal, and pretending otherwise leads to storing far more on a shared device than is wise. Sorted honestly, the list is short.
See how FoodCore works in a real kitchen →
How FoodCore works with no signal
FoodCore works with no signal after one online visit. Two mechanisms do the work.
A service worker caches the app itself. The first time you open FoodCore on a device with a connection, the browser installs a service worker that keeps the application's own files locally. After that, opening FoodCore does not require the network to get the interface on screen — it loads from the device, which also makes it noticeably faster on a tired old tablet.
An IndexedDB read-through cache holds your working data. IndexedDB is the browser's structured local database. FoodCore uses it as a read-through cache for recipes, ingredients and label templates: when you view a record with a connection, it is served from the network and written to the local cache; when you view it again without a connection, it is served from the cache. Over ordinary use the device quietly accumulates the things you actually work with, which is a better outcome than asking you to pick a "download for offline" list you will forget to update.
It is installable to a phone or tablet home screen. Add FoodCore to the home screen and it opens in its own window with its own icon. In a kitchen this is worth more than it sounds: no address bar to lose, no risk of someone closing the tab, and instant launch because the app shell is already on the device.
What is deliberately not cached — and why that is a feature
This is the part most vendors would leave out of a marketing page, and it is the part worth reading carefully.
Customer data is deliberately excluded from the device cache. Customers, orders, receipts, rota and scanned receipts are never stored on the device. That is a design decision, not an unfinished feature.
The reasoning is straightforward. Browser storage cannot be meaningfully protected on a shared kitchen tablet. There is no way to encrypt IndexedDB against someone who can unlock the device, because whatever key would decrypt it has to be available to the app on that same device. A tablet that five people use, that lives on a shelf by the pass, that has a passcode everybody knows — that is not a place to put a database of customers' names, addresses, phone numbers and dietary requirements. So FoodCore does not put one there.
For a bakery or caterer, that is the right side of the trade to be on. Losing a tablet with your recipes on it is a bad day and a commercial annoyance. Losing a tablet holding the personal and dietary data of several hundred customers is a different category of problem entirely, with reporting obligations attached. Keeping the two apart by design means the worse outcome simply cannot happen through a mislaid device.
Logging out clears the cache
Logging out of FoodCore clears the cached data from that device. On a shared tablet this matters: when a member of staff finishes a shift and logs out, the recipes and templates they were working with do not stay behind for whoever picks the device up next.
The flip side is worth planning around. If you log out at the end of every shift on the tablet you rely on at a market, you will arrive with an empty cache and no signal to refill it. On a dedicated device, the better pattern is usually to stay logged in and control access with the device passcode plus role-based permissions inside the app — see our guide to kitchen staff permissions and access control for how to set those up sensibly.
Preparing for a market day or an outside event
Because the cache is read-through, preparation is simply a matter of opening things while you still have a connection. Ten minutes the night before is enough.
- Install the app to the home screen on the device you are taking, if you have not already.
- Open every recipe you are producing while on good Wi-Fi. Viewing a record is what puts it in the cache.
- Open the ingredients those recipes use, so allergen data is available if someone asks you at the stall.
- Open the label templates you will print from, and print what you can in advance.
- Do not log out before you leave — that would clear everything you just cached.
- Test it in aeroplane mode before you pack the van. Thirty seconds now, versus finding out in a field.
- Take a paper backup of anything you are legally required to have to hand, and a pen for orders taken on the day. Signal-free order taking is still a notebook job — deliberately.
If you are setting up a van or stall from scratch, our guides to starting a food van in the UK and starting a market stall cover the wider operational setup around this.
The honest limits
Offline support is a cache, not a second copy of the system. Three limits are worth stating plainly. First, you need one online visit on each device before anything works offline — a brand-new tablet in a cellar will get you nowhere. Second, you can only read offline what you have already opened on that device; a recipe you have never viewed is not there. Third, anything involving customers, orders, payments or the rota needs a connection, by design, for the reasons above.
Within those limits, the thing a cook needs at the bench — the recipe, the method, the allergens, the label — is on the device and stays on the device.
Explore everything FoodCore does →
Kitchen software offline: frequently asked questions
Does FoodCore work without an internet connection?
Yes, after one online visit. The first time you open FoodCore on a device while connected, a service worker installs and caches the application itself, and a read-through cache in IndexedDB stores the data you have viewed. From that point the app opens and runs with no signal at all: you can browse recipes, ingredients and label templates that have been cached. What you cannot do offline is anything that needs the server — syncing new changes to other devices, pulling data you have never opened on that device, or working with the parts of the product that are deliberately not cached.
What exactly is cached on my device?
Three things: the application shell itself, cached by the service worker, plus recipes, ingredients and label templates, held in an IndexedDB read-through cache. Those are the things a cook needs in their hands while the oven is on. Everything else is fetched live from the server when you have a connection, and is not written to the device.
Why are customer orders not available offline?
Because customer data is deliberately excluded from the device cache. Customers, orders, receipts, rota and scanned receipts are never stored on the device. Browser storage cannot be meaningfully protected on a shared kitchen tablet — anyone who can unlock the device can reach it, and there is no realistic way to encrypt it against that. Rather than pretend otherwise, personal data is kept off the device entirely. It is a deliberate trade: slightly less offline capability, considerably less risk to the people whose names, addresses and dietary information you hold.
Can I install FoodCore on a phone or tablet?
Yes. FoodCore is installable to a phone or tablet home screen, so it opens in its own window with its own icon rather than as a browser tab. This matters in a kitchen for practical reasons as much as anything: no address bar to lose, no accidental tab switching with wet hands, and the app opens instantly because it is already cached. Installing is done from the browser's own share or menu button — there is no app store download involved.
What happens to the cached data when I log out?
Logging out clears the cached data from that device. This matters most on a shared tablet: if a member of staff finishes a shift and logs out, the recipes and templates they were working with are not left sitting on the device for whoever picks it up next. The practical consequence is that the next person to log in will need a connection once to repopulate the cache, so on a device you rely on offline it is usually better to stay logged in and rely on your own device passcode and staff permissions instead.
What if a kitchen tablet is lost or stolen?
A lost or stolen tablet exposes recipes and label templates. Those are commercially sensitive — your formulations and your method are genuinely valuable — but no customer's name, address, phone number or dietary information is on the device, because that data is never cached there. That is the whole point of the split. The commercial exposure is real and worth taking seriously, but it is a business problem rather than a personal data breach affecting your customers.
How should I prepare for a market day with no signal?
Open the app on the device you are taking, while you still have a good connection, and view the things you will need: the recipes you are producing, the ingredients they use, and the label templates you will print from. The cache is read-through, so opening a record is what puts it on the device. Then install the app to the home screen if you have not already, charge the device fully, take a printed backup of anything legally required, and expect to write down anything new — orders taken on the day — to enter when you are back in signal.
Try it in your own kitchen — 7-day free trial →
Further resources
FoodCore is kitchen management software built for small UK food businesses. We handle recipe costing, Natasha's Law labels, allergen matrices and order tracking.
Start free trial →