The operations layer between your factory floor and your accounts system.
Sales orders, batch traceability, dispatch, retailer EDI, COAs, mock recalls, one system for dairy, bakery, meat, prepared-food and food-wholesale producers.
Founding partner
Cashel Blue, 40+ SKUs, 9 export markets
hello@cloudvoro.com keystone.cloudvoro.com
Keystone·BY CLOUDVORO
Sales brochure · 2 / 16
01 · The operational reality
Running a small food business is a paper factory bolted onto a food factory.
Somewhere between the ten-litre milk churn and the retailer’s dock, a founder’s week disappears. It gets spent chasing kill sheets, hand-typing dispatch notes, matching customer purchase orders against internal SKU codes, printing COAs at four in the afternoon, and remembering which spreadsheet holds this month’s allergen list.
The accounts package handles the invoice. The factory handles the making. Everything in between, the operational middle, runs on Excel, WhatsApp, sticky notes and one person’s memory.
Most food businesses aren’t drowning in bad software. They’re drowning in the absence of the right software.
Friday afternoon
A retailer emails: “which batches went into last week’s Tesco delivery?” You open three spreadsheets.
Sunday night
Someone types tomorrow’s dispatch notes by hand because the accounts package prints them wrong.
The quiet fear
If there was a recall on Tuesday, who would find the affected batches by Wednesday morning? Honestly?
The audit before the audit
Two weeks of evenings spent making sure the paper trail agrees with the paper trail.
The operations layer for European food manufacturers · keystone.cloudvoro.comhello@cloudvoro.com
Keystone·BY CLOUDVORO
Sales brochure · 3 / 16
02 · Why generic software fails here
Food manufacturing has eight quiet realities that generic ERPs never handle well.
Odoo, Business Central, Sage, NetSuite, every one of them can invoice a wholesaler. None of them, out of the box, can hold the operational shape of a real food business without a five-figure customisation project. Here are the eight edges the big vendors round off:
01
Every retailer wants their own SKU code
Tesco calls it FBWHL14. You call it CB-200. The dispatch note has to match the retailer’s. Get it wrong and it’s rejected at the door.
02
Nothing weighs what the recipe says
A 1.4 kg wheel is really 1.36 kg to 1.44 kg. Case counts round. Invoices need catch-weight totals, not nominal ones.
03
Recalls aren’t a report, they’re a countdown
From “which batches?” to “which customers received them?” you have four hours, not four days. And they always ask on a Friday.
04
Batch corrections happen
You mis-labelled a batch on Tuesday. Fixing it in October cannot break the audit trail from July. Most systems just overwrite.
05
Co-packing is a first-class case
Same cheese, three retailer wrappers. Same batch, three private-label variants. Traceability has to survive that.
06
Ingredient lots matter, not just batches
When the flour supplier issues a lot recall at 5pm, you need to know which finished batches used which flour drums, in minutes.
07
Audit logs must be tamper-evident
BRCGS §5.4 and FSAI don’t want you to say “we didn’t change it”. They want proof you couldn’t have.
08
Documents are the product too
A dispatch note with the wrong pallet count is a rejected delivery. A COA missing a signature is a rejected pallet. Templates matter.
The operations layer for European food manufacturers · keystone.cloudvoro.comhello@cloudvoro.com
Keystone·BY CLOUDVORO
Sales brochure · 4 / 16
03 · What Keystone actually is
One operational spine. Four straight lines from milk to money.
We didn’t design Keystone as a set of modules. We designed it as a spine, four stages every food manufacturer goes through, and made sure every screen, every audit log, every document falls onto that spine in the same place.
01
Inwards
•Suppliers
•Milk intake
•Silos
•Ingredient lots
•Packaging lots
•Goods-in records
02
Production
•Make days
•Cheese / product batches
•Recipe as-built
•QC & release
•Batch corrections
03
Outwards
•Sales orders
•Weekly planner
•Dispatches
•Retailer SKU maps
•Catch-weight rounding
•Pallet labels · COAs · EDI
04
Traceability
•Backward trace
•Forward trace
•Mock recall report
•Customer draft comms
•Tamper-evident audit log
Design principle
Every event on the floor writes to one chain. A milk delivery on Monday, a make day on Tuesday, a dispatch on Friday, a customer complaint in October, all reachable from the same trace query, in seconds, on any device.
The operations layer for European food manufacturers · keystone.cloudvoro.comhello@cloudvoro.com
Keystone·BY CLOUDVORO
Sales brochure · 5 / 16
Stage 01 · Inwards
Every drum, sheet and litre tagged the moment it crosses your dock.
No goods enter the factory without a supplier lot, a date and an accept/reject decision. When the flour supplier issues a recall six weeks later, the lot number tells you which finished batches used it, before you even lift the phone.
The operations layer for European food manufacturers · keystone.cloudvoro.comhello@cloudvoro.com
Keystone·BY CLOUDVORO
Sales brochure · 6 / 16
Stage 02 · Production
One make day that becomes the whole audit trail.
The make sheet the supervisor already fills in, but tied at line-level to the milk intake, the ingredient lots, the packaging lots and the batches it produces. Recipe is captured as-built, not as-planned.
MD-2026-00074
Tipperary Blue · 10 Feb 2026 · Sup. M. Kowalska
RELEASED
Milk used
Silo 2MI-2026-000742,480 L
Ingredients used
SaltMA4001-26A00724.2 kg
RennetRN-26B1121.6 L
CulturesFS-26A044620 g
Packaging used
WaxWAX-2602-L117.4 kg
FoilFOIL-2602-R8480 sh
Output batches
CB-2026-014Tipperary Blue 200g480 units
CB-2026-015Tipperary Blue 1.4kg48 wheels
What’s actually happening
1Milk, ingredients, packaging, output batches, four sections, one sheet, one save.
2Supplier-lot auto-suggest so the supervisor never re-types the same lot twice.
3Output batches inherit the full upstream chain automatically, no manual linking.
4Batch corrections don’t rewrite history; they add a signed amendment.
The operations layer for European food manufacturers · keystone.cloudvoro.comhello@cloudvoro.com
Keystone·BY CLOUDVORO
Sales brochure · 7 / 16
Stage 03 · Outwards
A dispatch note that speaks the retailer’s language, not yours.
Every retailer wants their code, their template, their pallet-label format, their COA structure. Keystone stores it all against your customer record and reprints it in their language every time, down to the catch-weight totals on the invoice.
DSP-2026-00312
Tesco Ireland Distribution · PO 4416782
DISPATCHED
Your code
Our SKU
Cases
Catch-wt
TES-FBWHL14-742
CB-1400-STD
12
16.83 kg
TES-FBWDG20-315
CB-200-STD
48
9.72 kg
TES-FBSLC10-908
CB-100-SLC
24
2.46 kg
Documents generated:
· Dispatch note (Tesco template)
· Pallet label × 3 (SSCC + retailer barcodes)
· COA per batch (12 sheets)
· EDI DESADV / ASN, queued
What’s actually happening
1Customer → SKU mapping means the dispatch note prints in the retailer’s code system automatically.
2Catch-weight rounding: nominal kg gets scaled up/down to actual weighed kg, per case, per pallet.
3Retailer-specific templates: dispatch note, pallet label, COA all follow the customer’s spec.
4EDI DESADV / ASN queued and sent automatically when the retailer is on integration.
The operations layer for European food manufacturers · keystone.cloudvoro.comhello@cloudvoro.com
Keystone·BY CLOUDVORO
Sales brochure · 8 / 16
Stage 04 · Traceability
A mock recall that finishes before the kettle boils.
Start from any point, a supplier lot, a milk intake, a make day, a finished batch, a dispatch, a customer PO, and Keystone builds the full report in seconds. Affected batches, downstream customers, draft comms, printable PDF response pack.
Mock recall report
Starting point: Salt lot MA4001-26A007
Make days
3
Batches
11
Dispatches
18
Customers
9
Units
5,940
Downstream customers
Tesco Ireland Distribution3 disp.1,842 units
Sheridan’s Cheesemongers2 disp.384 units
La Rousse Foods2 disp.620 units
Avoca Handweavers1 disp.204 units
+ 5 others10 disp.2,890 units
Generated in 4.2 seconds. Customer draft communications ready. Export as PDF response pack.
What’s actually happening
1One-click from any starting point. Ingredient lot, milk intake, make day, batch, dispatch, customer.
2Affected customers with dispatch counts and unit totals, ready to hand to your quality lead.
3Customer draft communications generated per affected dispatch. Copy, print, export, never sent automatically.
4Signed PDF response pack: cover, summary, batches, dispatches, notes, status history, drafts. Ready for the auditor.
The operations layer for European food manufacturers · keystone.cloudvoro.comhello@cloudvoro.com
Keystone·BY CLOUDVORO
Sales brochure · 9 / 16
04 · The eight operational moves
Eight things Keystone does that generic ERPs simply don’t.
Not features. Moves. Small operational decisions that make the difference between software that fits a food business and software a food business fits itself around.
01
Customer-SKU mapping
Every retailer’s code is stored against your internal SKU. Dispatch notes print in their language, automatically.
02
Catch-weight case rounding
Nominal 1.4 kg × 12 = 16.8 kg. Actual weighed total = 16.83 kg. That’s what goes on the invoice.
03
Blind-spot recall sweep
Traceability that starts from an ingredient lot, not just a finished batch. Nothing hides upstream.
04
Tamper-evident audit chain
Every event cryptographically chained. You cannot rewrite yesterday without leaving a signed break in the log.
05
Mock recall in one click
Any starting point → full downstream + customer draft comms + PDF response pack. Under a minute.
06
Batch corrections without history loss
Re-label a batch six months later. The old record is preserved, the correction is signed, the trace still runs.
07
Co-branding as first-class
Same product, different customer wrappers, private-label variants, all traceable in the same batch chain.
08
Ingredient-lot forward trace
Supplier issues a recall on flour lot #X? You have the affected finished batches on screen before you finish the coffee.
The pattern. Every one of these exists because a real food manufacturer, not a product manager in an office, asked for it. That’s what “purpose-built” actually looks like in practice.
The operations layer for European food manufacturers · keystone.cloudvoro.comhello@cloudvoro.com
Keystone·BY CLOUDVORO
Sales brochure · 10 / 16
05 · A day in the life
What a Friday actually looks like once Keystone is running.
The founder
06:45Coffee. Opens Order Pipeline on the phone. Sees next week’s make plan already sequenced against retailer POs.
09:20Retailer emails asking about a delivery from three weeks ago. Types the dispatch number. Full trace on screen in eight seconds.
14:00Reviews the week’s catch-weight variance vs nominal, sees a batch trending high, flags it for the make team.
16:40Signs off Monday’s dispatch pack. Goes home.
The production supervisor
07:00Make day opens on the tablet in the make room. Milk intake auto-linked to today’s silo.
10:30Adds an ingredient lot to a batch as it happens. No paper, no re-typing at 5pm.
13:15Closes the make day. Two output batches created with full lineage back to supplier lot, nothing to reconcile later.
15:00QC dashboard shows batches ready for release. One tap, released.
The office
08:30Overnight EDI POs from three retailers already parsed into sales orders on the pipeline.
11:00Prints tomorrow’s dispatch pack, retailer-specific notes, pallet labels, COAs, in one go.
14:20Customer asks “which batch did we send you in Aug?”. Copy-paste dispatch number, screen shot, sent.
17:00Sync to Sage runs. Invoices are ready before the accountant asks.
The measure of good operational software isn’t how impressive its dashboards are. It’s how many hours it hands back to the founder every week.
The operations layer for European food manufacturers · keystone.cloudvoro.comhello@cloudvoro.com
Keystone·BY CLOUDVORO
Sales brochure · 11 / 16
06 · Compliance & security
Honest about what’s live, honest about what’s in progress.
Food software vendors love to list every acronym in the compliance dictionary. We list only what we can prove today, and mark the rest as in progress. Because when a retailer’s auditor asks, that’s the answer that matters.
✓ Live today
MFA on every login
TOTP + WebAuthn / passkeys enforced for admin accounts.
GDPR posture
DPO named. PII encrypted at rest with dedicated tenant keys. DSAR + erasure endpoints wired.
AES-256 at rest, TLS 1.3 in transit
AWS KMS-managed keys. Per-tenant database isolation, no shared schema.
Tamper-evident audit log
Every mutation cryptographically chained. Signed exports for auditors.
EU-only hosting by default
AWS eu-west-1 (Dublin). Or deploy inside your own AWS account with our IaC.
Daily encrypted backups
Point-in-time restore, 30 days retained. Restore drills every quarter.
· In progress
ISO/IEC 27001:2022 alignment
Controls mapped, evidence gathered, formal certification on the 2026 roadmap.
Cyber Essentials (IASME scope)
Scoped, documentation drafted, assessment booked.
NIS2 readiness
Designed-for from day one; formal attestation follows Ireland’s national transposition.
BRCGS §5.4 traceability alignment
Product supports the workflows; individual customer facilities carry their own certifications.
Penetration test cadence
Annual third-party; results shared under NDA on request.
SOC 2 Type II
Backlog, will start when three customers ask.
Why this matters
Retailer audits ask two questions: “can you trace it?” and “can you prove no one changed the trace?”. Keystone answers both by design, not by policy.
The operations layer for European food manufacturers · keystone.cloudvoro.comhello@cloudvoro.com
Keystone·BY CLOUDVORO
Sales brochure · 12 / 16
07 · Founding partner
Cashel Blue. Where every design decision was tested.
Ireland’s original farmhouse blue cheese, three generations of the Grubb family, exporting to nine markets, forty-plus internal SKUs, private-label lines with Tesco Finest and M&S Made Without. If Keystone couldn’t run their week, it couldn’t run anyone’s.
40+
internal SKUs, retail + foodservice + gift
9
export markets: UK, FR, BNL, DK, DE, US, CA, ME, AU
12
private-label variants across the retailer mix
400+
customer-mapped SKU codes maintained daily
“It doesn’t feel like software we bought. It feels like software we would have built if we’d had the ten years and the developer team. Everything is where it should be, and the traceability just works.”
Sarah Furno · Managing Director, Cashel Blue Farmhouse Cheese
Recall drill
From “which flour lot?” to “which retailer, which dispatch, which pallet?”, under a minute. On a Sunday. On the phone.
Retailer audit
BRCGS auditor asked for the trace on a random batch. Cashel Blue opened Keystone, exported the signed PDF pack. Auditor closed the section.
Friday afternoon
Order Pipeline replaced three spreadsheets, one WhatsApp thread, and a paper diary. The office got Friday afternoons back.
The operations layer for European food manufacturers · keystone.cloudvoro.comhello@cloudvoro.com
Keystone·BY CLOUDVORO
Sales brochure · 13 / 16
08 · What onboarding actually looks like
Live in weeks, not quarters. Because software vendors that need six months are building you, not configuring software.
Week 0
Discovery on your floor
Two days on-site. We map your suppliers, your customers, your dispatch templates, your retailer codes. We watch a make day. We watch a Friday. We watch a dispatch. Then we write a fixed-fee scope in plain English, no billable hours, no “discovery phase” that never ends.
Week 1
Data lift
Your customers, products, retailer SKU mappings, dispatch templates, pallet-label formats, all migrated from spreadsheets into a live tenant. You review, we correct, we lock. Sandbox is up by Friday.
Week 2– 3
Templates & training
Branded dispatch note, pallet label, COA templates configured for every customer that needs their own. One day of on-site training with the whole operational team. Not a webinar, sat next to them at their screens.
Week 4
Go-live & three-day hand-holding
First three days of live production, we sit on the phone with your office. First live dispatch pack goes out under our supervision. First recall drill runs by day five.
Month 2– 3
Post-go-live hand-holding
Direct line to the build team, you talk to whoever wrote the code, not a support tier. Any tweak needed in the first thirty days is bundled into implementation. No side invoices.
The honest bit
Complex retailer EDI (Tesco / Aldi / Lidl / M&S), multi-site consolidation, or twelve months of historical data all extend the timeline. We’ll tell you before you sign, not three weeks in.
The operations layer for European food manufacturers · keystone.cloudvoro.comhello@cloudvoro.com
Keystone·BY CLOUDVORO
Sales brochure · 14 / 16
09 · What it costs
Two lines on the invoice. Recurring for “run”. One-off for “fit”.
We deliberately separate what it costs to run Keystone (a monthly licence) from what it costs to fit Keystone to your operation (a one-off implementation project). Nobody gets locked into a two-year contract because the vendor is amortising setup cost in the recurring fee.
Recurring, monthly
The licence
One flat price per site. Every module unlocked, no “Pro tier” games, no per-user creep. Multi-site operations move to a capacity dimension when they run more than one site. Annual billing available at a straight discount. Cancel anytime, data exported as CSV within 48 hours.
One-off, fixed-fee
Implementation
Bounded, quoted in writing before you commit. Discovery, data lift, templates, training, and thirty days of hand-holding, all in the number. Complex retailer EDI, historical data imports, custom modules and accounts-package integrations are quoted separately so you only pay for what you actually use.
Better than a free trial
The 30-day pilot programme.
A real, scaled-down implementation with your data on our screens for thirty days. If you continue, it credits to full implementation. If you walk away within fourteen days of the pilot ending, half is refundable, and your data exports as CSVs, no penalty.
Full published pricing lives at keystone.cloudvoro.com/site/pricing. Every number is bounded, in writing, and quoted before you commit.
The operations layer for European food manufacturers · keystone.cloudvoro.comhello@cloudvoro.com
Keystone·BY CLOUDVORO
Sales brochure · 15 / 16
10 · Fit
Who Keystone is for , and who it isn’t.
We’d rather lose a sale than force-fit a customer. Below is what we look for. If you don’t recognise your business here, we’ll happily point you elsewhere.
✓You supply retailers, foodservice or wholesale, with proper traceability requirements.
✓You’re between 5 and 50 people, typically €1M to €20M turnover.
✓You’re family-run or founder-run, and someone in the building still touches product every week.
✓You want the audit log, dispatch quality and recall drills of a mid-market operator without the mid-market ERP price tag.
✓You’d rather talk to the developer than a sales tier.
× Better served elsewhere if…
×You’re a plant of 500+ people needing a full MES and PLC integration on the make line.
×You’re a €100M+ business with a shared-services IT team looking at SAP or Business Central.
×You need heavyweight demand planning, S&OP or multi-echelon inventory optimisation.
×You don’t make anything, you distribute other people’s finished product.
×Your operation is fine on paper and you have no compliance or growth pressure to change.
The honest test
Book a twenty-minute call. We ask five questions about your operation. At the end of it, we’ll tell you honestly whether Keystone is the right fit, or which of our competitors we’d recommend instead. No pitch, no chase sequence.
The operations layer for European food manufacturers · keystone.cloudvoro.comhello@cloudvoro.com
Keystone·BY CLOUDVORO
Sales brochure · 16 / 16
11 · How to start
Twenty minutes and a piece of paper.
We don’t do free trials of production software, they’re theatre. Here’s how a real conversation with us goes:
1
A twenty-minute call
On video. We ask about your operation, your retailers, your worst Friday. You ask us anything. No slides, no salesperson.
2
A one-page scope
Within 48 hours. Fixed fee for implementation, plain-English list of what’s in and what isn’t. Yours to keep, whether we work together or not.
3
Then you decide
A 30-day pilot with your real data, or straight to a full implementation. Either way, we start with the discovery visit on your floor.
Get in touch
Direct line
+353 85 181 0310
You’ll talk to the person who wrote the code.
Email
hello@cloudvoro.com
Reply within a working day, usually within the hour.
Book online
keystone.cloudvoro.com/site/contact
Pick a 20-minute slot. Video call. No SDR funnel.
Keystone by CloudVoro · The operations layer for European food manufacturers.