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.

• 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

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.

What prepared-food producers need on day one.

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.

Questions buyers actually ask.