In brief
We completed a practical project focused on digitizing HACCP journals and production reporting for a food industry company. We do not disclose the client’s name, but the engineering contour can be described publicly: mobile data entry, QR points, roles, reporting and operation under unstable internet conditions.
For us, this was not just a one-off development project. It became the basis for oneHACCP — ACG’s own product idea for production control and HACCP journals. The goal is to connect executable templates, version control, mobile work on site and reproducible reports for internal control and inspections.
The problem: paper, spreadsheets and scattered versions
Production control is not only about recording a fact. It is also important to know which form was active on a particular day, who filled it in, where the control point was located, whether deviations occurred and whether the report can later be reproduced using the same rules.
When part of the process lives on paper, part in Excel, part in PDF forms and part in messages, operational risk appears. Inspection preparation becomes a manual search for evidence, and template updates become a separate burden for administrators and employees.
What we built into the solution
The core scenario was intentionally simple: an employee approaches a control point, scans a QR code, opens the right journal on a phone, enters the data and continues working. If the connection is unstable, the system should preserve the workflow and synchronize later.
Administrators need a different layer: roles, journal lists, period reports, data preparation for inspections, clear exports and control over which templates are being used. That is why we looked not at a single input form, but at the full responsibility contour.
From project to product
The project showed that this task is broader than one company. A methodologist or auditor needs to define a template; the production site needs to execute it every day; management needs reporting; and inspectors need a reproducible result.
That is why oneHACCP is being designed as a product contour rather than a set of isolated forms. In the target model, template versions, an action log, deviations, role-based access, PDF reports and mobile work without permanent connectivity all matter.
Why this reflects the ACG approach
For us, the HACCP project is a good example of engineering, product and operations meeting in one task. A polished interface is not enough: the system has to account for the real production environment, employee workload, reporting requirements and future support.
This matches the way ACG prefers to work: we build digital solutions not around technology for its own sake, but around reproducible working processes that can be supported, evolved and audited.