Salix · Case study · 2026
The record book
that listens.
NutriCent is food safety compliance for New Zealand kitchens. A cook says a chiller temperature out loud, and it becomes a timestamped record against a registered Food Control Plan.
Built by Salix. Live at nutricent.co.nz.
Chapter one
Every day, in writing.
A registered Food Control Plan does not ask a kitchen to be clean. It asks the kitchen to prove it was clean, in writing, every day: opening and closing checks, temperatures, cooking, cooling, cleaning, and the corrective action taken when a number comes back wrong.
NutriCent is built around the MPI Simply Safe and Suitable template, which is the plan most New Zealand food businesses actually work to. At the end of it sits a council verifier who reads the records, not the kitchen.
The hygiene is rarely the part that fails. The paperwork is.
Chapter two
Who holds the probe.
The person holding the probe is often not the person who wrote the plan.
So the record keeping speaks seven languages, not just the marketing site. Every voice flow has a manual twin, in all seven, because the person on shift at four in the afternoon should not need the plan author’s first language to write a temperature down.
- English
- te reo Māori
- Chinese
- Hindi
- Korean
- Thai
- Vietnamese
Chapter three
Where signal dies.
Cool rooms and back docks are where signal dies and records get skipped.
A compliance app that needs a connection has a hole in it exactly where the food is. Entries save on the device and sync when the connection returns, so the record exists before the signal does.
That is an unglamorous requirement, and it is the one that decides whether the log has gaps in it at audit.
Chapter four
Take a reading.
NutriCent’s flow is three moves. Say it, hear it back, confirm. Hands stay on the food.
Demonstration. Nothing leaves this page, and nothing is stored.
- Say it or type it. A cook says the reading, or types it.
- It reads back. The app repeats the value and waits.
- Confirm. It becomes a timestamped, attributed record.
“Main chiller is 3.8 degrees.”
Every flow above has a manual twin in NutriCent itself, in all seven languages. This one does too, for the same reason.
Chapter five
A flag that explains itself.
Every flagged record names three things: the rule that flagged it, the MPI card the rule derives from, and a suggested corrective action. NutriCent’s stated reason is the giveaway that somebody had used the alternative: instead of a red tick with no explanation
.
- Allergens
- A site matrix of present, may contain, not present or unknown, with versioned manager verification.
- Traceability
- One step back, site handling, one step forward. Lots, batches and complaints.
- Calibration
- Thermometers checked by ice slurry, boiling water or a reference thermometer, against an equipment register.
- Labels
- ZPL, TSPL and ESC/POS over browser print, Web Serial, WebUSB or Web Bluetooth, laid out for the printer’s dpi.
- Shelf life
- Advisory only. A manager confirms it before anything is labelled, and it is never a compliance decision on its own.
- Languages
- 7 for the records themselves, not just the interface.
NutriCent. Voice first food safety records for New Zealand kitchens, built around the MPI Simply Safe and Suitable template. Two surfaces: an admin dashboard and a kitchen staff app. Offline first, seven languages, verifier ready exports as PDF and CSV.
Designed and built by Salix in Auckland. Live at nutricent.co.nz. Every fact on this page is published by NutriCent itself.
If you have a problem shaped like this one, start a project.