Keystone
by CloudVoro
Batch traceability

Batch traceability without the spreadsheet acrobatics.
Full upstream + downstream chain in under 30 seconds.

Every batch carries its full chain inside Keystone — supplier deliveries upstream, dispatches and customer branches downstream. Two clicks, signed PDF, done. No more Vlookup chains, no more 'which version of the Excel was current that week.'

  • Forward trace: batch → dispatch → customer → retailer branch (incl. private-label re-codes)
  • Backward trace: dispatch line → batch → supplier delivery → raw-material lot
  • Mock-recall in 90 seconds (BRCGS Issue 9 compatible)
  • Immutable audit log — every change, signed, who/when/why
How it works

Every batch is a node in a chain. We hold the chain.

When a batch is created in Keystone, every input — supplier delivery, raw-material lot, QC record, transformation step — is recorded as an upstream link. When that batch is dispatched, every customer and retailer branch it reaches is recorded as a downstream link. The chain is cryptographically signed at every write, so neither side can be tampered with after the fact.

What you can answer

The questions auditors actually ask.

Where did this batch end up?
Forward chain: every dispatch line, every customer, every retailer branch, every private-label code.
What went into this dispatch?
Backward chain: every batch, every supplier delivery, every QC test along the way.
Which batches share a supplier delivery?
Cross-trace: pick any supplier delivery and see every batch that used it — typical recall trigger.
Who changed the spec mid-run?
Audit log: every spec change with user, timestamp and reason — immutable.
FAQ

Questions buyers actually ask.

How is Keystone different from a generic ERP?
A generic ERP treats batches as inventory line items. Keystone treats them as nodes in a directed chain with cryptographic signing — built for traceability first, accounting second.
What about variable-weight production (e.g. cheese wheels)?
Native support. Each unit can carry its own weight, with case-level and pallet-level rollups that reconcile against your dispatch totals.
Can I trace by customer SKU code, not just mine?
Yes — bidirectional mapping is built in. Search by your code or by the retailer's private-label code.
How far back does the audit log go?
Forever. Nothing is ever truly deleted in Keystone — soft-deletes with restore, hard-deletes blocked.

Ready to see if Keystone fits your floor?

20-minute discovery call. No sales pitch. Written scope within 48 hours if we fit — referral to someone better if we don't.

Talk to us
Compliance & trust

How we keep your
data and your audits safe.

We are honest about what's certified and what's in progress. Anything marked "in progress" reflects active work towards a recognised standard — never marketing decoration. Privacy queries go to privacy@cloudvoro.com. Sub-processor list at /legal/sub-processors. Full security posture at /site/security.

Live
Hosted in EU / Ireland
Customer data resides on AWS Ireland (eu-west-1) — never leaves the EU.
Live
GDPR · Privacy Contact named
Internal Data Protection Lead handles subject access requests. Owner is ADPO Ireland member.
In progress
NIS2 · building toward readiness
Tenant isolation, audit trails and MFA support customers in NIS2 scope. CloudVoro itself is below the size threshold; not yet certified.
In progress
ISO 27001 · alignment
We map our controls to Annex A but hold no third-party certificate. Formal certification on the 2026 roadmap.
In progress
Cyber Essentials · planned
UK Cyber Essentials assessment is on our roadmap. We will name the assessing body (IASME) and a confirmed date here once scoped.
Live
Encryption · at rest & in transit
TLS 1.3 in transit, industry-standard symmetric ciphers at rest, KMS-managed keys.