It is Tuesday at 11 a.m. You receive a notification from the food safety authority: listeria has been detected in a specific batch of grated cheese distributed in your region. Your chain has 30 locations spread across the Mediterranean coast. The question you need to answer in the next few minutes is clear: which locations received that batch, in which dishes was it used, and is any remaining stock in cold storage? The clock is ticking.
The scenario nobody wants to face
Food alerts are not hypothetical. In 2025 alone, AESAN (the Spanish Food Safety Agency) published over 300 notifications through the European RASFF system. From microbiological contaminations to undeclared allergens, the reasons vary, but the common denominator is always the same: you must act fast.
When you operate a single restaurant, traceability is relatively straightforward. The head chef knows what was purchased, from whom and when. But when you manage a chain of 20, 30 or 50 locations, the complexity multiplies exponentially. Each location receives goods from different suppliers, on different days, with different batches. The same product may arrive in different batches at different locations. The simple question — where is that batch? — becomes a logistical problem of considerable dimensions.
The reality: days instead of minutes
In most HORECA chains, the process of tracing a batch during a food alert remains essentially manual. Delivery notes are filed on paper, in folders or filing cabinets at each location. Some groups scan and store them in shared folders, but without indexing or structured search.
During an alert, the usual protocol is as follows: the operations director or quality manager calls each location manager, one by one. They ask them to search their filing cabinets for the affected supplier's delivery notes from recent weeks. The manager stops whatever they are doing during service, rummages through papers, locates (or not) the delivery note, tries to read the batch number printed in tiny font and communicates the result by phone or WhatsApp.
In chains with 30 locations, this process can take between two and four days. Two days during which a potentially dangerous product may remain in the cold chain, be incorporated into preparations or even served to diners. The health risk is evident. The reputational risk, incalculable.
What European regulations require
Regulation (EC) 178/2002 establishes the food traceability principle known as "one step back, one step forward": every operator in the food chain must be able to identify who supplied a product and to whom it was delivered. For a restaurant chain, this means being able to link every ingredient received with its supplier, batch, reception date and the location that received it.
Non-compliance is serious. Penalties for severe food traceability deficiencies can reach 600,000 euros under Spanish food safety law. But beyond the fine, what truly destroys value is media exposure. A chain that takes days to respond to a food alert projects an image of lost control that consumers do not forget.
Common gaps in traceability
Non-digitized delivery notes
The first broken link is almost always the delivery note. If the supplier's document stays on paper, the batch number, expiry date and delivered quantity do not enter any searchable system. They exist, but they are trapped in a physical filing cabinet at each location.
Unregistered batch numbers
Even when the delivery note is digitized, many systems only capture product, quantity and price. The batch number, which is precisely the critical data during an alert, is omitted because it is not part of the usual purchasing flow. It is a quality data point, not an accounting one, and that is why it gets neglected.
No link between reception, storage and production
The third gap is the deepest. Even if the batch is recorded at reception, there is rarely a digital connection between that batch and what happens next: which cold room it was stored in, which preparations it was used in, when it was depleted. Without that link, traceability is partial: you know a batch entered, but you cannot confirm whether it has already been used up.
How Controliza enables instant traceability
Controliza's Trazoon module transforms goods reception into an automatic traceability capture point. Every time a location receives a delivery, simply photographing the delivery note is enough. The AI-powered OCR technology extracts not only product, quantity and price data, but also the batch numbers and expiry dates printed on the document.
Automatic batch capture from delivery notes
Controliza's intelligent recognition identifies and structures delivery note data, including batch fields that other systems ignore. It requires no manual intervention or specific training for reception staff. Capture occurs in seconds, in the very act of receiving goods.
Automatic batch-location-date linking
Each captured batch is automatically linked to the location that received it, the supplier that provided it and the exact reception date. This triple link is the foundation of all subsequent traceability queries. Controliza's Purchasing system maintains a centralized, searchable record of all active batches across the entire chain.
Batch search in seconds
During a food alert, the quality manager enters the affected batch number into Controliza's search engine. In a matter of seconds, the system returns the complete list of locations that received that batch, reception dates, delivered quantities and current stock status. No phone calls, no filing cabinets, no uncertainty.
Compliance reports for audits
Controliza generates structured traceability reports that comply with Regulation 178/2002 requirements and are directly presentable to auditors and health inspections. Documentation that previously required weeks of manual compilation is produced automatically.
Could you respond to a food alert today in less than one hour?
Controliza's Trazoon module automatically captures batches from every delivery note and links them to each location in your chain. Combined with the Purchasing module, you get complete traceability with no additional operational effort. Request a personalized demo and see how it works with your real data.
Prevention, not just reaction
Batch traceability is not only for managing crises. The same data that allows tracing a batch during a food alert feeds a continuous prevention system. Controliza uses batch and expiry information to generate proactive alerts that prevent problems before they occur.
Expiry alerts and expired stock
The system monitors expiry dates of all registered batches across all locations. When a product approaches its expiry date, Controliza generates an alert to the location manager to prioritize its use or remove it. This reduces the risk of serving expired product and minimizes waste from expiration.
Automatic FIFO compliance
By knowing the batch and reception date of each product at each location, Controliza can verify whether the FIFO (First In, First Out) principle is being respected in storage. If a location is consuming a more recent batch while still having stock from an earlier batch, the system detects and flags it. It is a control layer that simply does not exist in the manual process.
From batch alert to immediate action
Speed matters, but so does execution. Once you identify the affected batch, you still need to block stock, stop recipes that use it and verify traceability across open delivery notes and current inventory.
With Trazoon, Controliza connects supplier batches, delivery notes and stock movements in one shared system. That lets your team isolate risk in minutes, protect food safety and avoid unnecessary waste from withdrawing unaffected products.
Measurable impact
HORECA chains that have implemented digitized traceability with Controliza report quantifiable improvements in the first months of operation:
Data measured in active Controliza clients.
Beyond the operational figures, the most significant value is the one that cannot be measured directly: the peace of mind of knowing that during any food alert, your chain can respond in minutes with exact data, not in days with approximations.
