The app captures. Bio-Pest keeps.
Bio-Pest is a pest-management system built on Odoo 19, and Pestanova is its field half. They are one product and one purchase. The app cannot run without it: a technician signs in to their own company's Bio-Pest server, and that is where every record goes.
The site
The site, as the system sees it
A client site is a hierarchy four levels deep. Upload the floor plan and draw the sub-zones onto it. Traps sit on that plan as pins, each with an auto-generated QR code that is unique across the database and printable eight to an A4 sheet.
- Site
- Building
- Floor
- Room
A site’s status is the worst status anywhere below it. If one trap in one room goes critical, the site reads critical, and it does that on its own.
Thresholds
Thresholds you scope, and evidence that overrides them
You set the catch count at which a trap turns amber and the count at which it turns red, and you scope the rule as tightly as you like — this trap type, at this client, in this zone, for this pest category. Leave a field blank and it applies to everything.
Direct evidence overrides a quiet count. Droppings, gnawing, a live sighting, nesting or smear marks raise a trap to at least Warning even when nothing has been caught, because a rodent that eats the bait and walks away is not a clear trap.
Escalation
When something is found
- A high-risk species posts a red alert to the site's thread and schedules a task on the account manager for the same day.
- A high-severity sighting flags the zone.
- A finding marked for corrective action opens a CAPA ticket by itself, pre-filled and assigned.
The corrective-action trail, in four stages
Unassigned
Root cause analysis
Action implementation
Verification and closure
Root cause and action taken are separate fields, because an auditor asks for both and “dealt with it” answers neither.
Seeing it
The heat map, and the history behind it
The heat map, and the time machine
The floor plan with every trap on it, coloured by status, glowing in proportion to how much has been found. Step the date back and the map replays as it stood on each inspection — which is how you show an auditor that the problem in bay four has been shrinking for three months.
Reporting
Five built-in analysis screens. Eradication time is analysed as a cohort: findings grouped by the date they were found against the date they were controlled.
The five analysis screens
- Activity
- CAPA performance
- Chemical usage
- Inspection coverage
- Species risk matrix
Requirements
What it needs
Odoo 19 Enterprise. Field Service is a hard dependency, and so is the cohort view used in reporting, so Bio-Pest cannot run on Odoo Community.
Tell us about your sites
How many technicians you have, and what your clients are audited against. We will tell you plainly whether the suite fits.
Talk to us