Every drum traced. Every application logged. Every auditor answered.
From purchase order to customer application, every batch of chemical is traceable. Oldest stock gets consumed first — automatically. Expiring batches generate their own write-off paper trail. Included in Core. Built for pest control, sanitation, and fumigation operators whose customers include food plants, hospitals, and hotel chains.
Three scenarios that describe the real change.
A food-plant auditor asks which batch of Imidacloprid was used at DMart Koregaon on 14 March
Under your prior setup, this was a four-hour reconstruction across WhatsApp, a paper register, and a warehouse supervisor’s memory. In Upgear, you open the customer record, filter visits to 14 March, see the chemical consumption line, click through to the specific batch — with its purchase order, its supplier, its manufacturing date, and its expiry. You answer the auditor in thirty seconds.
Forty thousand rupees of expired Cyfluthrin gets written off with the paper trail
A drum of Cyfluthrin hits its expiry date in your warehouse. The Expired Inventory workflow flags it, moves it to a quarantine state with a back-reference to its original purchase order, and generates the write-off journal entry automatically. Your accountant has the paper trail for the ₹40,000 write-off in the books the same day. No one has to reconstruct “why did we throw this away” at year-end.
Your oldest batches get consumed first without anyone remembering to look
When a technician goes out with a 5-litre bottle of Imidacloprid, the system allocates from the oldest-dated batch first — automatically. The drum purchased in January goes before the drum purchased in March. Your shelf-life-to-disposal ratio improves without anyone managing it consciously. What used to be a warehouse supervisor’s daily judgement call becomes a software-enforced rule.
Six things that ship with Chemical Traceability.
Every drum or pack of chemical enters Upgear at the purchase-order stage with its batch number, manufacturing date, and expiry date. Every application at a customer site links back to that specific batch. The audit trail is end-to-end — purchase → warehouse → technician → customer site.
When a technician issues chemical for a job, the system allocates from the oldest-dated batch first. Your shelf-life wastage drops without anyone having to think about it. Override is possible for specific cases (a batch that must be reserved for a particular client), but the default is FIFO.
An Expiry Report surfaces any batch coming within a configurable window (30, 60, 90 days) so you consume oldest stock first. When a batch passes its date, it moves to an Expired Inventory table with a back-reference to the original purchase order. Your write-off has paperwork automatically.
Every visit records exactly which chemicals were used in what quantities against which customer. The consumption log aggregates by customer, by chemical, by technician, by branch, and by month. Your "which customer gets more chemical than their contract covers" question becomes one dashboard filter.
The branded treatment certificate issued to the customer after a visit references the batch number applied — so your corporate clients have the paper trail their own auditors ask for. Printable, emailable, WhatsApp-able. You stop recreating these in Word.
A Consumption Insights report compares actual chemical usage against what a contract assumes. Over-consumption signals either under-pricing or pilferage; under-consumption signals under-service (and customer risk). Your annual pricing review is data-driven, not gut-driven.
Four steps. Most of the effort is the one-time opening-stock import.
Import your current stock with batch information
The opening-stock import takes a single Excel with chemical name, batch number, manufacturing date, expiry date, quantity, branch, and supplier. Most operators have this information in various places (purchase invoices, warehouse registers); we help consolidate it into one upload. Takes one working day.
Set your expiry alert window
You choose how far in advance you want to be warned about expiring batches — 30, 60, or 90 days is typical. This drives the Expiry Report and the FIFO allocation priority. Most operators start at 60 days.
Configure your chemical master with pack sizes and HSN codes
Each chemical in your catalogue has a pack size (5L drum, 1L bottle), a base unit for consumption tracking, and an HSN code for invoicing. A 15-minute exercise during onboarding; rarely needs revisiting.
Train technicians on chemical-issue and visit-consumption entry
Technicians enter chemical consumption when they complete a visit — either through the phone interface or via voice (with the AI Copilot addon). Training is ten minutes: pick the chemical, the quantity, confirm the batch (system auto-picks oldest). After one week your techs are fluent.
Included in Upgear Core. No separate “Compliance” addon gate. Audit-readiness is a baseline need, not an upsell. Pricing tailored to your operation — quoted on the demo.
FIFO allocation, expiry workflow, consumption logs, and treatment certificates all ship in Core.
Chemical Traceability sits across Field Operations and Finance & Compliance.
Field Operations uses it at visit-time (chemical issue, application log, treatment certificate). Finance & Compliance uses it at month-end (consumption report, expiry write-off journal entry, audit-ready records). Together they make the pest-control-operator audit readiness case.
Three honest constraints before you lean on this for compliance.
Traceability is records management, not regulatory filing. These are the boundaries.
Manual disposal documentation is still required
When you write off an expired batch, Upgear gives you the internal paper trail — purchase order linked, journal entry generated, inventory record updated. But the physical disposal (handing the expired drum to a hazardous-waste vendor, getting the disposal certificate) remains a manual operational step. Upgear stores the disposal certificate when you upload it, but it doesn’t replace the regulatory requirement to actually dispose correctly.
Batch naming conventions matter
Traceability is only as clean as your batch-number discipline at the purchase-order stage. If your warehouse supervisor enters "Batch 23" on one PO and "B-23" on another for the same supplier, the traceability gets fuzzy. We help set naming conventions on onboarding; they are easy to keep once established, but drift if not watched.
CIB&RC licence filing remains manual
Upgear produces the underlying records licence auditors look for — chemical-use logs, batch traceability, treatment certificates, consumption-versus-inventory reports. But the licence filings themselves with state and central authorities (CIB&RC, state pest-control boards) remain a manual process with those authorities. You gather the supporting records in thirty seconds instead of three days; the filing is still your team's work.
What pest control and sanitation operators ask.
See chemical traceability running on your own catalogue.
30-minute demo, founder-led. Bring one of your recent purchase orders for a chemical drum and a sample customer visit. We’ll trace it end-to-end in Upgear on the call — PO, batch, warehouse, technician, site, treatment certificate. The audit-readiness case writes itself.