Deadline control in HoReCa isn't some abstract idea of "discipline" — it's a concrete list of dates, and every one of them can turn into a problem: a cook's health permit, a conformity certificate on a batch of raw ingredients, the shelf life of a prep item, a lease with automatic renewal, insurance on your equipment. While there are only a few such dates, the manager keeps them in their head. Once there are many — and in a working cafe, bakery or small production facility there are exactly that many — one is bound to slip through. And you find out at the worst possible moment: during an inspection, during a stock count, or once the batch has already gone into production.
In this article we'll look at how HORUVIA — an AI operator for a business that lives in its inbox and documents — closes this gap: a deadline engine with alerts at 60, 30 and 7 days, OCR of paper certificates so dates land in the system without manual entry, and a HoReCa preset that sets up the right deadline types right at onboarding.
Why an expired document hurts the most
A cafe or small producer rarely has one dedicated person responsible "for deadlines." Health permits are handled by the manager or the employee themselves, certificates by whoever received the delivery, contracts by the owner. Each document lives with its own "owner," and there's usually no single register of dates: some in a spreadsheet, some in a folder of scans, some in a stack of papers by the register.
The trouble is that an expired document gives you no advance warning. A valid health permit and an expired one look identical — the only difference is a single date on the stamp. A conformity certificate sits quietly in the folder long after its validity has run out. You usually learn about it not from the document itself, but from an inspector — or when a partner asks for a current copy and there isn't one.
Employee health permits: deadline control without a spreadsheet taped to the fridge
Health permits are the most telling example. Almost everywhere, permit tracking works the same way: a spreadsheet or a printout on the wall, with dates entered by hand when the employee was hired. From there the list ages: people come and go, someone renewed their permit and didn't mention it, someone's date was mistyped from the start. Over time no one trusts the list anymore — and rightly so.
In HORUVIA it works differently. A health permit is a deadline type in the deadline engine: each employee has a record with an expiry date and an owner. When 60 days remain, the system sends the first alert to Telegram; at 30 days, a second; at 7, a third, and more insistent. Renewing a permit two months out is a calm, planned task; finding out it's expired on the day of an inspection is an entirely different scenario.
What matters is that you don't type the date in by hand: a scan or photo of the permit is read by OCR, the system pulls the dates and offers a ready-made record — the person just confirms. More on this below.
The deadline engine: alerts at 60, 30 and 7 days
The deadline engine is the core of deadline control in HORUVIA. The logic is simple: any document or obligation with a date becomes a "deadline" object — with a type, a date, a linked document and an owner. From there the system counts down on its own and sends alerts in a cascade: at 60 days (time to plan), at 30 (time to act) and at 7 (last window).
The deadline types that matter for a cafe, bakery or production facility:
- employee health permits;
- conformity certificates and declarations — on your products and on incoming raw materials;
- expiry dates on ingredient batches and prep items;
- contracts — lease, supply, equipment servicing (on auto-renewal and "vanishing" dates we have a separate breakdown);
- insurance and scheduled equipment maintenance.
Alerts arrive in Telegram — where the manager already spends their day, not in a separate interface you have to remember to open. The 60/30/7 cascade fixes the main flaw of "day-before" reminders: the day before a permit expires it's already too late — you have to pull the employee off the shift.
Tracking expiry dates: batch, date, owner
With expiry dates the logic is the same, but with one honest caveat. Expiry tracking in HORUVIA is not a warehouse system with scales and stock levels: it doesn't count how many kilos of flour sit on the shelf. It watches dates. A batch of ingredients arrives — and with it the delivery note and the certificate; the batch's expiry date and the certificate's validity date are logged as deadlines, and the same alert cascade runs on them.
For a small producer this closes a classic pain point: a batch is bought with a margin to spare, sits there, and you remember its expiry is near by the smell rather than the calendar. An alert at 30 days gives you time to use the batch in production or adjust the next order; an alert at 7 lets you decide deliberately, not after the fact.
If your stock is already managed in an accounting or inventory system, HORUVIA doesn't compete with it: there's a basic exchange with 1C, and the system's role is to be a layer of date control and notifications on top of your existing records, not a replacement for them.
OCR of scans: permits and certificates without manual entry
The weak spot of any deadline register is data entry. If every date has to be retyped by hand from the certificate into the spreadsheet, the register dies fast: there's no time for it, and manual entry adds typos — we wrote about the cost of such errors in our article on OCR and manual-entry errors.
That's why in HORUVIA paper documents enter the system through OCR. A scan or photo of a health permit, certificate or contract is read, the system pulls the dates and details out of the document and offers a ready-made deadline record. The person checks and confirms — a matter of seconds, not manual entry.
For documents that pile up on your computer there's a desktop agent: point it at a folder, and everything dropped into it is automatically sent to the server and picked up for processing. Scan a stack of certificates at once — and they're in the system, without forwarding them one by one.
Where deadline control in HoReCa begins: a preset at onboarding
Setup from scratch is the second reason attempts to "start a register" stall out. To get the system running you need to define the deadline types, the owners and the notification channels — and that's exactly the stage where things usually grind to a halt.
In HORUVIA there are onboarding presets by segment for this, and HoReCa is one of them. The preset immediately creates the right deadline types: health permits, certificates, expiry dates, lease and supply contracts, insurance. What's left isn't designing the system but filling it: run the scans through OCR and assign owners. For what a sensible plan for the first week of rollout looks like, see our article on automation in a week.
Cafe purchasing automation: inbox, invoices, order recommendations
Deadline control is part of a bigger picture. Cafes and producers live in correspondence with suppliers, and cafe purchasing automation in HORUVIA starts right there in the inbox: the system sorts incoming email by supplier and type — invoices, price lists, offers, claims — and keeps a memory on each supplier: documents, prices, history.
From this come concrete mechanics:
- an invoice arrives — HORUVIA prepares a payment draft; only deterministic code handles money, with no model "creativity," and a human always approves the payment;
- an offer with a deadline arrives — an alert in Telegram, so the discount doesn't burn out unread;
- an email to a supplier goes unanswered for more than six hours — a reminder;
- an order recommendation is calculated from seasonality, ABC analysis and current stock — a prompt on how much of what to order, not ordering blind.
Purchasing and document tasks live on a kanban task board, and the overall picture sits in the Company Pulse. These mechanics are proven on HORUVIA's flagship case — importing heavy-truck spare parts in Kazakhstan, with real inboxes from dozens of brands; the HoReCa preset carries that same foundation over to the kitchen and the production floor.
What HORUVIA doesn't do
For clarity — the boundaries. HORUVIA doesn't replace your register, inventory software or HACCP logs, doesn't do your bookkeeping and doesn't pay on its own: any movement of money is prepared by deterministic code and confirmed by a human. The system's job is narrower and more concrete — to make sure not a single date, from a health permit to a certificate, slips through unnoticed, and that supplier email doesn't demand manual sorting every morning.
If you want to see how this looks on your own documents, request a demo on the home page: we'll take your real permits and certificates and show how they turn into deadlines with alerts. You can estimate the payoff in hours and money in the calculator, and short answers to common questions are collected in the FAQ.