Omavalvonta and origin documentation for small producers and wholesalers — generated from records you already keep, instead of retyped by hand every time a professional-kitchen buyer asks for it. Paperwork stops being the reason wholesale accounts stay closed.
A professional-kitchen buyer asks for an origin document with the delivery. The producer writes it by hand in Word, or does not write it at all and loses the account. Neither outcome is about food safety competence; it is about there being no machinery between the records that exist and the document somebody wants.
We build that machinery. Deliveries, batches, temperature logs, and supplier certificates already exist somewhere — a notebook, a spreadsheet, a delivery app. We take those inputs and generate the document per delivery or per batch: a PDF or a link, carrying the batch identifiers that let the buyer trace the consignment back to a lot, with a copy retained on your side so the record exists when an authority asks for it months later.
We are software people, not food safety consultants. The content of your omavalvonta plan stays yours, or your advisor's. What we contribute is that it stops being retyped, stops going missing, and stops being the reason a wholesale account does not close.
What matters is what the generator opens. A producer who can send documentation without a phone call can serve customers that were too much trouble before — public catering, restaurant groups, wholesalers with their own audit rules. A wholesaler doing it for twenty producers is running a service, not doing admin.
Omavalvonta is the own-checks system a Finnish food business is required to operate: the records showing that temperatures, deliveries, suppliers, and hygiene practices are being monitored. The requirement is not the hard part. The hard part is that the records live in a notebook, a spreadsheet, and a delivery app, so producing a document from them takes a person an hour. We connect the records to the document.
No. We start from whatever you keep now, in whatever form it is in. Replacing a producer's working routine with a new system is the most common way these projects fail — the routine survives and the system gets abandoned. If a change genuinely pays for itself we will propose it, but the starting assumption is that your process stays and the paperwork stops being manual.
A PDF or a link, per delivery or per batch, carrying the batch identifiers that let them trace the consignment back to a lot, plus whatever supplier certificates apply. A copy stays on your side so the record exists when somebody asks for it months later.
No. We are software people. The content of your omavalvonta plan stays yours or your advisor's; what we contribute is that it stops being retyped, stops going missing, and stops being the reason a wholesale account does not close.
Scope note. We build the documentation machinery. We do not write your omavalvonta plan, and we do not certify anything — those stay with you and your food safety advisor.