General Pest Control Software
Recurring service agreements, Branch 2 certification enforcement, and first-class commercial account infrastructure — built for pest operators running residential and commercial routes.
Key capabilities
Built for commercial accounts
Residential pest jobs and commercial pest jobs are different animals. Residential customers want the job done and a confirmation email. Commercial accounts — restaurants, warehouses, food processors, hotels — need standardized inspection records that cover specific areas of the facility, device-by-device monitoring history, and documentation they can produce for a health inspector without a day's notice.
Bug HQ has dedicated infrastructure for both. Commercial pest logs are a separate record type from standard pest jobs. Each log captures which areas of the facility were inspected — the predefined list covers Reception, Kitchen/Break Room, Restrooms, Storage, Loading Dock, Office Areas, Production Floor, Dining Area, and Bar Area — plus whether pest activity was found, structured findings with pest type, location, severity, and action taken (stored as jsonb for flexibility), recommendations, and next service date. This is the documentation format that health department audits and third-party food safety audits actually ask for.
Monitoring device tracking gives each physical station its own record in the monitoring_devices table — six device types supported: rodent bait, glue board, pheromone trap, fly light, bird spike, and other. Each device has a device number, location description, installed date, last serviced date, and current activity status. Every service visit creates a device_activity_logs row: was activity found, what pest type, what action was taken.
In the field, the tech scans the device's QR code using the Bug HQ field app scanner. The app reads the path — /scan/d/[device-id] — identifies the entity as a device, logs the scan with the tech's identity and timestamp, and surfaces the device record. The tech logs what they found and what they did. That entry is immediately part of the device's service history — permanently tied to the device and the commercial account.
When a commercial account comes up for renewal, the office can pull device-by-device service history for any property without calling a single technician. The record is already there.
How it works
Create the Job and Assign a Qualified Tech
From the office or field app, create a new pest job in three steps: select the customer and property, choose the service type and pest types (multi-select across 11 options), set the schedule and price, then assign a tech from the Branch 2-certified dropdown. If the job is recurring, select the frequency and Bug HQ creates the service agreement in the same action. The job appears on the schedule with the assigned tech.
Tech Works the Job — Findings, Chemicals, Photos, Signature
In the field app, the tech logs findings per location and severity, selects chemicals from the product library, captures photos (with GPS stamp if location permission is granted), and collects the customer's signature. For commercial stops, the commercial pest log captures area-by-area inspection results — Reception, Kitchen, Loading Dock, and others — and any monitoring devices are scanned via QR code to log activity. All data ties to the job record.
Invoice Generated, Review Sent, Agreement Tracked
After marking the job complete, an invoice can be created directly from the job record. A review request is automatically queued and sent when the schedule fires. If the job is recurring, the pest_service_agreements record updates with the next service date. The office dashboard shows month-over-month job count, revenue, active agreements, and customer rating — updated as each job closes.
Who uses this feature
The dashboard shows today's jobs, in-progress count, overdue jobs, month revenue vs last month, active agreements, completion rate, and customer rating — all on one screen. Agreements track next service date so nothing falls through. Review requests send without manual follow-up.
Commercial pest logs and monitoring device records give you the documentation trail to walk into any renewal conversation — or any health department visit — with a complete service history per facility area and per device. No calling techs, no paper chase.
Branch 2 certification is enforced at the job assignment level — the dropdown only shows qualified techs. Chemical logs, pest findings, and treatment records are captured per job. Every compliance input is already in the system when you need to produce it.
What this looks like in your day
A restaurant group you service at three locations is up for renewal. The account manager calls and wants a summary of the last six months before they sign. You open Bug HQ, pull up the first location, and go to commercial pest logs: 24 monthly visits, each one showing areas inspected, activity found per area, findings with severity, action taken. Then you open bait stations: 8 devices — 4 rodent bait, 2 glue boards, 2 fly lights — each with its full activity log going back to the install date. Location 2 had a mid-year spike in the Loading Dock that your tech caught and treated in two visits. It's all documented: date, pest type, severity, action taken. You pull the device-by-device history right from the account record and share it with the buyer before the call ends. The renewal closes. You didn't open a spreadsheet or call a technician.
Frequently asked questions
When you create a pest job with the recurring toggle on and select a frequency, Bug HQ calls /api/pest-jobs/create which inserts the pest_job record and then — in the same request — inserts a pest_service_agreements record with status 'active', the selected frequency, price_per_service, and next_service_date set to the first job date. The agreement number is generated automatically (SA- prefix). You don't create the agreement separately — marking a job recurring is the trigger.
Standard pest jobs track the job-level outcome: service type, pest types found, chemicals used, and completion notes. Commercial pest logs are a separate record type designed for the structured area-by-area format that commercial accounts require — they track which specific areas were inspected (Reception, Kitchen, Loading Dock, etc.), whether pest activity was found per area, structured findings with pest type, location, severity, and action taken, plus a next service date. Both records can exist for the same property. Commercial logs are accessed at /office/pest-control/commercial-logs.
Yes. The monitoring_devices table stores each device independently — a single property can have rodent bait stations, glue boards, pheromone traps, fly lights, and bird spikes all tracked separately with their own device number, location description, installed date, last serviced date, and activity status. Each device has its own activity log so you can see the full service history per station, not just per property.
Bug HQ generates QR codes with paths in the format /scan/d/[device-id]. When a field tech scans the code in the Bug HQ field app, the scanner at /field/scan parses the URL, identifies the entity type as 'device', logs the scan to the scan_logs table with company_id, scanned_by, scan_type, entity_type, and entity_id, then surfaces the device record. The scan is timestamped and associated with the technician who scanned it.
The new pest job form filters the technician list to only show users whose branch_certs array contains 'Branch 2' or 'branch2', plus any user with the admin role. Techs without Branch 2 certification don't appear in the dropdown. This prevents assigning a WDO-only inspector (Branch 3) to a general pest job that requires a different license category.
Related features
Build a predictable, documentable pest control operation
Free 14-day trial. Credit card required — cancel free anytime before trial ends. Setup in under an hour.
Get Started →