01738 260265 Talk to us

APP CASE STUDY · A COMMUNITY NURSERY IN PERTH

Nursery Kitchen: a menu and allergen checker for a nursery

Nursery Kitchen is a menu and allergen checker we built for a community nursery in Perth, and it is in daily use there. A cook pastes a supermarket link and the app reads the ingredients. It then checks every meal against what each child must avoid.

Book a free 20-minute callCustom software and apps

The Nursery Kitchen weekly menu, sample data: meals for each day with the allergens in each meal and a flag where a child needs something different.
The Nursery Kitchen weekly menu on a phone, sample data: Monday meals with their allergens.
Each meal shows what is in it. A red warning says a child needs a different meal. Real screens from the app. The children, dishes and products on them are made up, so none of the nursery's own records are shown.
The Nursery Kitchen serving check on a computer, sample data: each child in a room with a result for the meal and four checks to tick before serving.
The Nursery Kitchen serving check on a phone, sample data: a child with a milk allergy, the meal, the result and the checks to tick.
Each child's meal for the day, checked against what they must avoid. Real screens from the app. The children, dishes and products on them are made up, so none of the nursery's own records are shown.

At a glance

Who it is for
A nursery kitchen that cooks for children with allergies and has to check every meal.
What it is
A web app: four steps for the cook, a weekly menu, a list of children and a check before food is served.
Built on
Cloudflare, with the database in the EU. Allergens are found by fixed rules, not by AI.
Where it is today
In daily use at the nursery, behind a staff password. It has been live since 16 October 2026.
How it started
A prototype made in an AI site builder, rebuilt and moved to our hosting on 16 October 2026.

What was the nursery's problem with menus and allergens?

A nursery cook plans meals for a mix of children. Some have an allergy, and some families ask for a food to be avoided. The check has to be right every day.

What does Nursery Kitchen look like? Real screens

Each picture is a capture of the running app. Under each one is the same thing said in plain words.

  1. 01Add a product

    Paste a link, see the allergens

    The cook pastes a supermarket product link. The app reads the ingredients and allergy advice from the product page and finds the 14 regulated allergens. Contains is red and May contain is amber, each with a word and an icon. The ingredients are shown in full, with the allergen words in bold. With no link, the product can be typed in and goes through the same steps.

    In plain EnglishLike reading the label out loud and circling the allergens, without the typing.

    Sample data. This product is made up and was typed in; a pasted link fills the same boxes.

    Nursery Kitchen with sample data, step 2, Check the allergens: a made-up haddock product with Contains Wheat, Fish and Milk in red, May contain Egg and Soya in amber, and the ingredients in full with the allergen words in bold.
  2. 03Children

    Each child's list of foods to avoid

    A child is shown by a short name, a room and what they must avoid. A food that is not one of the 14 allergens can be added in words. The app also shows when the care plan was last confirmed.

    In plain EnglishThe signed care plan stays where the nursery keeps it. The app holds only what it needs to check meals.

    Sample children. The names are made up.

    Nursery Kitchen with sample data: six made-up children in three rooms, each with the foods they must avoid as red tags, one with an added food, and a care plan confirmed line.
  3. 04Serving checks

    Check each child's meal before it is served

    Every child who is in on the day is listed against the meal they will be given, with one of five results. These are Conflict, Review, Incomplete, No recorded conflict and Staff reviewed. A meal with a conflict has a button to plan a different meal. Before the checks are recorded, four things are checked on the real packs and the real child.

    In plain EnglishThe app does the matching. A person still looks at the pack and at the child.

    Sample children and meals. "No recorded conflict" never means safe, and the page says so.

    Nursery Kitchen with sample data: the serving checks for Monday 16 November, with a Conflict for a child who avoids milk, Review results for two others and buttons to plan a different meal.
  4. 05On a phone

    It works on a phone or tablet

    Text is 18 pixels or larger and buttons are at least 56 pixels tall. Nothing relies on colour alone: every tag has a word and an icon. On a phone the menu moves to a bar at the bottom.

    In plain EnglishThe cook who uses it has had no software training, so it has to be obvious.

    Sample data, on a phone.

    Nursery Kitchen on a phone, with sample data: Check the allergens, with a made-up product's Contains tags in red and May contain tags in amber.Nursery Kitchen on a phone, with sample data: a serving check for a child who avoids milk, showing a Conflict and a Plan a different meal button.

How does a product reach a child's check?

Here is what happens when a cook adds one product. Five steps.

Diagram of one product: a supermarket product link goes to the Worker, a reader service returns the page text, and the Worker finds the allergens with fixed rules and saves them in the EU database. The Worker updates the menu and the list of children, and the child check gives one result per child on a tablet, a phone and a printout.
  1. 01 of 05

    The cook pastes a product link

    Only the web address of the public product page is sent anywhere. No child, no account and no basket.

    In plain EnglishA link goes out. Nothing about a child does.

  2. 02 of 05

    The page is read

    A reader service returns the text of the product page, from a copy up to an hour old. The app keeps the ingredients and the allergy advice. If the page cannot be read, nothing is saved and the cook is told.

    In plain EnglishA failed read changes nothing.

  3. 03 of 05

    Fixed rules find the allergens

    Plain, tested rules look for the 14 regulated allergens, with wheat, rye, barley and oats under cereals and each tree nut by name. A missing warning is shown as not known, never as free from.

    In plain EnglishThe same label gives the same answer every time.

  4. 04 of 05

    The product goes onto meals

    The cook picks the meals it is used in. The menu updates at once: each meal's allergens change, and so does the number of children who need a different meal.

    In plain EnglishChange it once and every meal follows.

  5. 05 of 05

    The check meets each child

    For each child who is in that day, the app compares their meal, or the different meal planned for them, with what they must avoid. A person records the check after looking at the real packs.

    In plain EnglishThe software matches. A person decides.

What is it built with?

One platform, Cloudflare, and a few well-known tools. Each part has one job.

How did we make the big choices?

Six decisions shaped it. Each one had a real alternative. This is the record of what we weighed.

01 Decision

Should an AI read the labels?

A wrong answer here could harm a child.

  • ChosenFixed, tested rules

    The same label gives the same answer every time, and each rule has a test. The result is advice for staff, never a safety certificate.

  • RejectedAn AI model reads each label

    It could cope with odd wording. It could also miss an allergen or invent one, and we could not test every answer it might give.

02 Decision

How should "may contain" and "not known" be shown?

A label can say yes, maybe, or nothing at all.

  • ChosenSeparate states, and unknown never reads as safe

    Contains is a conflict. May contain needs a person to review it and stops the check being recorded. Missing information stays marked as not known.

  • RejectedOne list of allergens

    Simpler to look at, but it hides the difference between what is in the food and what might be.

03 Decision

Who decides if a child can have a "may contain" meal?

That is a question for the child's care plan, not for software.

  • ChosenStaff, with a written reason, for that child and that meal

    A person confirms the care plan and the pack, and writes why. The decision is tied to that child, meal, recipe and product, and any change cancels it. It can never override a definite conflict.

  • RejectedThe software decides from the label

    A keyword match cannot know what a care plan allows.

04 Decision

Where does the product information come from?

We found no public data feed from the supermarket the nursery uses.

  • ChosenRead the public product page, and let staff type a product in

    One pasted link replaces the copying. When a page cannot be read, nothing is saved and typing always works. The supermarket's terms and the reader's reliability still need checking.

  • RejectedAn unofficial route to the supermarket's data

    Not something to build a nursery's routine on.

05 Decision

How simple should the screens be?

The cook has had no software training.

  • ChosenFour steps, large text and plain words

    Paste, check, choose, done. Words like "workspace" and "evidence" were taken out, and the rest sits under a button called More.

  • RejectedEverything on view at once

    Our first version had eight equal places to start. Nothing said where to begin.

06 Decision

Build a tool, or buy one?

Nursery and catering tools already exist, and a free recipe tool is published by Food Standards Scotland.

  • ChosenA small tool for this nursery's own routine

    We compared existing tools first. What we could add was open evidence for each product, a different meal for an individual child and honest not known states.

  • Not chosenA ready-made nursery system

    It may suit the nursery better in the end. From public pages we could not confirm that one covers each child's different meals and shows where each label came from. We did not check prices.

What does it not do?

Nursery Kitchen is advice for staff. These are the things it cannot do.

What has it done so far?

Only things we can show. We have not measured time saved, and we will not quote a number until we can show where it comes from.

What is still to do

These are the open items we know of, from our last read of the app's notes on 15 November 2026.

Nursery Kitchen: common questions

What is Nursery Kitchen?

It is a web app that checks a nursery's menu against the foods each child must avoid. Staff add products from supermarket pages, put them on meals and see which children need a different meal.

Is it in use at the nursery?

Yes. It is in daily use in the nursery's kitchen, behind a staff sign-in, and has been live since 16 October 2026. The screens on this page use made-up children and dishes, not the nursery's records.

Does it use AI to find allergens?

No. Fixed rules find the 14 regulated allergens in the ingredients and allergy advice, and a person checks the result against the pack.

Can a nursery rely on it?

Not on its own. It is advice for staff, a missing warning is shown as not known, and every delivery, pack and child still needs a person's check. It is in daily use at one nursery, and that does not change this.

Where is the data kept?

In a database on Cloudflare in the EU, behind a staff sign-in. Pasting a link sends only the web address of a public product page to a reader service.

Could another nursery use it?

Not as it stands. It is built around one nursery's routine. We can talk about a version for yours, and about what would need to be agreed first.

Could a school or care home use the same idea?

The idea is the same: match a menu to a list of foods each person must avoid. The data, access and checks would need agreeing for each setting.

Need a tool for a routine like this?

Book a free 20-minute call. We will tell you what could be built, what has to be agreed first, and if a tool you can buy would suit you better.

Book a free 20-minute callCustom software and apps

Facts checked on 15 November 2026 against the app's own design notes, rollout notes and tests. Daily use is as our team reports it, not something we have measured. The children, dishes and products on every screen are made up. We have left the nursery's name out of this page.