Food traceability software, built in Ireland.
Forward and backward batch trace, in seconds.

When the FSAI calls or a retailer raises a complaint, you have hours, not weeks. Keystone is Irish-built traceability software for batch-based food production, every dispatch line tied to its batch, every batch tied to its supplier deliveries, every change immutably logged.

• Live with Cashel Farmhouse Cheesemakers (Tipperary), a multi-award-winning farmhouse dairy with international distribution
• Pilots scoped to go live in 30 days · Standard licence from €790/month
• Hosted in EU / Ireland (AWS eu-west-1, Dublin)
• Supports FSAI, HACCP and BRCGS traceability workflows

Excel and paper traceability stop working at the worst possible moment.

In our experience working with Irish food producers, the typical setup is an accounts package and a stack of spreadsheets. It works, right up until the FSAI calls, a retailer triggers a withdrawal, or a BRCGS audit lands a mock-recall test. Then suddenly: who supplied that milk on the 14th? Which batches did it touch? Which customers got those batches? Which retailer branches received those pallets? In Excel, that's a fortnight of work and a knot in your stomach. In Keystone, it's under 30 seconds.

Two clicks. Full chain. PDF in your hand.

We don't sell you US software with a euro sign.

Keystone is built in Ireland, for Irish food producers, by a founder who's spent 15+ years inside Irish operations. We understand AccountsIQ, we know what BRCGS actually asks for in §5.4, we've sat through SFPA inspections. The system speaks the same language your QA manager does, because we wrote it with one.

From question to signed PDF, step by step.

A retailer technical manager emails at 09:12: 'complaint on SKU 47712, best-before 14 June, which batch, and where else did it go?' In Keystone: the retailer code resolves to your internal product through the customer SKU mapping; the best-before resolves to batch B-1042; one click renders the full chain, the three milk deliveries that fed Wednesday's silo run, the make-day record with its QC checks, all eleven dispatches the batch entered, every customer and depot with quantities per line. Export as a signed PDF, attach, reply by 09:15. The same lookup that took the QA manager half a day in spreadsheets is now shorter than the kettle boiling, and identical whether it's a retailer, the FSAI, or a BRCGS vertical audit asking.

One system of record for three layers of obligation.

30 days from scoping call to first traced dispatch.

Implementation is founder-led and fixed-fee: day 1 scoping, week 1 data shape (products, customers, suppliers, codes), week 2 dispatch templates and label formats, week 3 the full backward trace working on your imported history, week 4 first live dispatch through the system. Twelve months of historical data is included in the standard implementation, so your first audit after go-live doesn't straddle two systems. If you want to understand what the auditor will actually ask before you buy anything, start with our free guides on running a mock recall and the BRCGS traceability requirements, no email gate.

Questions buyers actually ask.