Bait station scanning for pest control routes

B2BMobile1 monthReact NativeSupabasePDF generation

The idea

Food plants and warehouses have to prove to their own third-party auditors (AIB, SQF) that every rodent station gets checked on every service, station by station, with dates and findings. The pest control operator carries that burden: a tech hand-logging 80 stations on a paper grid produces exactly the kind of record that fails an audit and loses the account. PestPac handles this properly but at enterprise price and complexity.

The wedge is the QR-scan-per-station flow with offline-first sync. Scanning makes skipped stations impossible to hide, timestamps every check, and turns visit close-out into an automatic, audit-ready PDF instead of an evening of paperwork.

Who pays

The pest control company owner pays 59 dollars per tech per month, priced against keeping a single commercial account that bills hundreds per month and gets audited yearly. Small operators with two to ten techs and a handful of food-grade accounts are the sweet spot: too small for PestPac, too exposed to lose an account over documentation. Reach them through PCT magazine communities, state pest management associations, and distributors who sell them the physical stations.

MVP scope

  • Site setup with numbered stations and printable QR label sheets
  • Scan-to-log station entry with activity, condition, and photos
  • Offline-first capture with local queue and background sync
  • Visit close-out that blocks unchecked stations and generates the PDF report
  • Auto-email of the report to the client’s QA contact
  • Skip for v1: routing and scheduling, invoicing, barcode hardware support, multi-branch admin, trend analytics beyond last-visit comparison
// Build prompt — paste into Cursor / Claude Code / Lovable / Bolt
Build StationScan, a mobile app for pest control technicians servicing commercial accounts. Stack: React Native with Expo, Supabase (auth, Postgres, storage), server-side PDF generation via a Supabase Edge Function with Puppeteer or pdf-lib.

Core flow: an operator sets up a site (a food plant or warehouse) with a numbered station list, each station having a type (bait station, snap trap, insect light trap) and a location description; generate a printable QR label sheet, one code per station. On a service visit, the tech opens the site, sees the station checklist, and works the route: scan a station's QR, which opens that station's entry screen (activity level, condition, bait replaced yes/no, notes, optional photo), then move on. The app tracks scanned versus missed stations so the visit cannot be closed with unchecked stations unless the tech marks them inaccessible with a reason. Closing the visit generates a PDF service report: site header, tech name and signature, station-by-station table with timestamps, activity summary, and trend versus last visit. The report emails automatically to the client's QA manager contact on file.

Screens: site list, site detail with station map/list, QR scanner, station entry, visit summary and close, visit history. Admin web view can wait; do setup in-app.

Implementation details: everything must work offline inside a metal warehouse; queue writes locally (SQLite via expo-sqlite) and sync when connectivity returns. Timestamps come from scan time, not sync time, because auditors check them.

Pricing: 59 dollars/month per technician seat, billed to the pest control company.

// More B2B ideas