Prepared food · Ready meals
Production software for prepared food manufacturers. Every component lot, in every meal, to every customer.
A ready meal is traceability's stress test: one finished SKU can contain a cooked protein, a sauce made Tuesday, blanched veg from two suppliers and a garnish, each with its own lot, allergens and shelf life. When any single component is questioned, you must name every meal batch it entered and every customer those batches reached. Keystone was built for exactly this shape of problem.
Home › Prepared Food Manufacturing Software
Proof points
In one glance.
- Multi-component recipes: every batch records the actual component lots consumed
- Sub-assembly support: sauces and cooked components are batches too, chained into finished meals
- Allergen-led recall readiness, the most common trigger in prepared food
- Retailer dispatch formats and own-label code mapping built in
The component problem
Sub-assemblies are where spreadsheets tap out.
Prepared food is production inside production: the sauce is a batch, the cooked rice is a batch, and the finished meal consumes both. Spreadsheet systems flatten this into one row per meal and lose the component lineage, which is precisely what an allergen alert or a supplier recall interrogates. Keystone chains batches into batches to any depth: the tikka sauce batch knows its spice and cream lots; the meal batch knows the sauce batch; the trace from a supplier's cream recall to the affected meal SKUs on a retailer's shelf is one click, with quantities.
Built for the sector
What prepared-food producers need on day one.
- Allergen evidence per batch — Each batch carries its recipe version and actual component lots, the evidence base behind every declaration, and the instant affected-list when a component is questioned. Undeclared allergens are the most common recall trigger in this category.
- Cook / process records — QC checks (cook temps, cooling curves, metal detection) attach to the batch they belong to, so the vertical audit arrives pre-assembled.
- Short shelf life planning — Date logic flows from components to finished meals; the planner surfaces what must dispatch first.
- Retailer own-label reality — Multiple retailer codes per meal, per-retailer dispatch formats, and code-level trace when the retailer quotes their SKU, built in, not bolted on.
Gotowość do audytu
BRCGS-shaped evidence from live records.
Prepared-food suppliers to the multiples live under BRCGS and retailer technical audits with twice-yearly recall exercises. Keystone computes the chain and the mass balance from the same records production creates daily, so the timed traceability test, component forward or meal backward, completes in minutes and the write-up is the only manual work. Built with an Irish farmhouse producer as founding partner; the multi-component batch model is the same one prepared food runs on.
FAQs
Frequently asked.
How deep can component chains go?
Any depth, component batches into sub-assembly batches into finished batches. Both trace directions survive the whole tree, with quantities at every level.
A supplier recalled an ingredient, what does the trace look like?
Pick the affected supplier lot; Keystone lists every sub-assembly and meal batch that consumed it (directly or through components), every dispatch, every customer, with quantities, in seconds, exportable as a signed PDF.
Can QC records attach to batches?
Yes, cook temperatures, cooling checks, metal detection and any custom checks record against the batch, so trace reports carry the QC history with them.
Do you support multiple own-label retailers on one meal?
Yes, one internal SKU can carry any number of retailer codes with effective dates. Trace works from either side of the mapping.
Ile czasu zajmuje uruchomienie?
Pilots scoped to go live in 30 days. €790/month flat licence, implementation from €4,950 fixed-fee including 12 months of history.