Guide · Buying advice
How to choose food traceability software
, a buyer's guide for producers who hate buying software.
We sell traceability software, so read this with that declared. It is still written to be useful if you buy from someone else: when spreadsheets genuinely stop being enough, the questions that expose weak systems in a demo, what the pricing models actually cost, and the implementation red flags that turn 30-day projects into 12-month ones.
12 min read Updated 2026-07-08By the CloudVoro team
In this guide
01When spreadsheets genuinely stop being enough02Twelve questions that expose weak systems in a demo03Pricing models, decoded04Implementation red flags05An honest note on fit, including oursWhen spreadsheets genuinely stop being enough
Spreadsheets are not a traceability failure, thousands of certified producers run on them. They fail on predictable triggers, and buying software before one of these is usually premature:
A retailer contract lands
Own-label supply brings customer codes, twice-yearly recall exercises, hours-not-days response expectations and technical audits. This is the single most common trigger.
The 4-hour test keeps failing
If the annual traceability exercise repeatedly overruns or the mass balance never closes, the corrective action eventually has to name the tooling.
One person is the system
When the trace only works with a specific human present, every holiday is a compliance gap. Auditors now test for this.
Volume outgrows re-keying
Each manual transcription (production book → dispatch sheet → invoice) is an error site; past a few hundred dispatch lines a month the errors compound.
Multi-site or export
Cross-site transfers and export documentation multiply the reconciliation work non-linearly.
Twelve questions that expose weak systems in a demo
- 1Trace this batch backward, while I watchNot a slide. A live trace from a dispatch line to supplier lots. Time it. If a demo can't do it fast, production won't.
- 2Now forward, from a raw-material lotBoth directions matter; some systems are strong one way only.
- 3How do intermediates work?Silos, brines, rework, work-in-progress. If the answer is "custom fields", internal traceability will be your job, not the system's.
- 4Show me a mass balanceProduced vs dispatched vs stock vs waste for one lot. Systems that can't compute this leave the worst half of the annual test manual.
- 5How do customer SKU codes map?Private label demands bidirectional mapping with effective dates. "You can put it in the description field" is a no.
- 6What does the auditor artifact look like?The output that lands in front of BRCGS or the FSAI, a signed, timestamped chain report, should be one click, and you should like how it looks.
- 7Is the audit trail immutable?Who changed what, when, and can history be silently edited? Editable history is a credibility problem in front of any auditor.
- 8What happens offline?Production floors have dead corners and outages. Ask what happens to a QC check entered when the Wi-Fi drops.
- 9Where is the data, and how do I leave?Hosting region (GDPR), backup cadence, and, critically, the exit: can you export everything in a usable format without a fight?
- 10What integrations are real?"Integrates with Sage" spans a spectrum from tested API sync to "we export CSV". Ask for a customer running the exact integration you need.
- 11Who actually implements?Named humans, their food experience, and days on your floor, or a partner network and a ticket queue?
- 12Show me year-1 and year-3 total costLicence + implementation + integrations + training + per-user growth. Get it written. The gap between headline and total is the industry's worst habit.
Pricing models, decoded
| Model | Typical shape | Where it bites |
|---|---|---|
| Per-user / month | €30–€90 per user | Food ops means tablets on floors and seasonal staff, user counts balloon; people share logins, which destroys your audit trail |
| Modular licensing | Base + paid modules | The demo showed the full suite; traceability, QC and labels each cost extra. Price the modules you actually saw |
| Flat per-site | Fixed monthly, all modules | Simplest to budget (Keystone uses this: €790/mo single site); check the definition of "site" and any fair-use limits |
| Custom-quoted enterprise | POA | Fine at scale; for a 15-person producer the sales cycle alone costs more than a year of the alternatives |
Whatever the model, the number that matters is the year-1 total (licence + implementation + integration + training) and the year-3 total at your projected headcount. Implementation quotes deserve equal scrutiny: fixed-fee with a written scope beats day-rate with a hopeful estimate, every time.
Implementation red flags
"Go-live in 12–18 months"
For a single-site producer, traceability + dispatch + QC is a 30–90 day project when scoped honestly. Year-long plans signal a system that needs consultants to operate.
No historical data migration
Starting from zero means your first year of audits straddles two systems. Insist on at least 12 months of history imported.
Training as a priced afterthought
If the vendor expects your QA manager to train the floor from PDFs, adoption will be your problem alone.
No reference customer your size
A system proven at 400 employees can be wrong at 15. Ask to call a customer within 2× your headcount.
Demo data only
A vendor confident in their system will run a pilot on your real production data. (This is why we structure pilots that way, 30 days, real data, half-refundable.)
An honest note on fit, including ours
No system is right for everyone. Full ERPs (SAP, Dynamics, CSB) make sense above roughly 150–200 employees with dedicated IT; generic manufacturing tools (MRPeasy and similar) are cheaper if you don't need food-specific structures like COAs, catch weights and retailer dispatch formats; strong documentation platforms (FoodDocs and similar) solve HACCP paperwork but are not batch traceability engines. Keystone sits deliberately in the middle: batch-based food producers, typically 5–100 staff, supplying retail or foodservice, who need traceability + dispatch + QC + labels without an ERP project. If that is not your shape, one of the categories above will serve you better, and if it is, our pricing and pilot terms are public.
Key takeaways
- Buy on triggers (retailer contract, failed 4-hour tests, key-person risk), not on fear.
- Demand live traces, mass balance and customer-code mapping in the demo, timed, on realistic data.
- Compare year-1 and year-3 totals at your projected headcount, in writing, never the headline price.
- Insist on historical data migration and a reference customer near your size.
- A pilot on your real production data is the strongest de-risking tool a vendor can offer.
Free 5-part email course
Get audit-ready in five short emails.
The 18-point checklist PDF, the 30-second traceability test, what BRCGS auditors actually flag, and how Cashel Blue got audit-ready, one email every few days. No spam, one-click unsubscribe.
GDPR-friendly: we store your email for this course only. Unsubscribe link in every email.
Frequently asked questions
How much does food traceability software cost?
Headline prices range from ~€50/user/month for generic tools to five-figure enterprise licences. The honest comparison is year-1 total: licence + implementation + integrations + training. For reference, Keystone is €790/month flat per site with implementation from €4,950 fixed-fee, but compare totals, not headlines.
How long does implementation take?
For a single-site producer, an honestly-scoped traceability + dispatch + QC implementation is 30–90 days including data migration and training. Multi-site, heavy integrations or ERP-class systems run longer. Treat 12-month plans for a small site as a red flag.
Do small food producers need traceability software at all?
Not always, spreadsheets can pass audits. The genuine triggers are an own-label retail contract, repeated failure of the 4-hour traceability test, dependence on one person, or transcription volume that breeds errors. Before a trigger, disciplined spreadsheets are a legitimate answer.
What should I see in a demo before shortlisting?
A live backward trace from a dispatch line, a live forward trace from a raw-material lot, a mass balance for one batch, customer SKU-code mapping, and the exact PDF an auditor would receive, all timed, all on realistic data, none of it slides.
Cloud or on-premise for food traceability?
Cloud is now the default for SMEs: no server maintenance, automatic backups, updates included. The questions that matter are hosting region (EU for GDPR comfort), backup and restore evidence, offline behaviour on the floor, and a contractual data-export path if you leave.
See this done in software, on real production data.
Keystone runs the full chain, supplier delivery → batch → dispatch → customer, in under 30 seconds. 20-minute discovery call, no sales pitch.