Ask any HVAC or plumbing owner how much inventory sits on their trucks right now and you’ll usually get a shrug, a guess, or a number pulled from last quarter’s count. Nobody actually knows. And that gap between what’s on the truck and what’s on paper is quietly costing trades businesses real money every single week.
This isn’t a warehouse problem. It’s a truck problem, and trucks are hard to track because they’re always moving, always getting raided for parts, and rarely get counted with any real discipline.
The manual mess most trades businesses are running on
Here’s what inventory tracking actually looks like at most $1M-$25M trades operations today. A tech grabs a capacitor or a coupling off the shelf in the morning, doesn’t log it. He uses two more on a job he wasn’t scheduled for. By Thursday, the warehouse thinks it has stock it doesn’t, dispatch books a job assuming the part is on hand, and the tech shows up to find he’s short. Now he’s driving to the supply house, the job slips forty-five minutes, and the customer who took time off work is annoyed.
Multiply that by six trucks and fifteen SKUs each carries regularly, and you get a system nobody trusts. Most owners respond by over-ordering “just in case,” which ties up cash in parts sitting in a truck for months. Or they under-order and eat the cost of emergency supply runs, which for firms of this size we usually see running 20-40 minutes of lost billable time per incident, several times a week.
The root cause is almost always the same: inventory data lives in three places that don’t talk to each other. There’s the paper sheet or spreadsheet the tech is supposed to fill out and rarely does. There’s the warehouse system that gets updated when someone remembers. And there’s what’s physically sitting in the truck bed, which is the only version that’s actually true.
What real-time sync between truck and warehouse should look like
The fix isn’t a bigger spreadsheet. It’s connecting truck-level usage to warehouse stock automatically, the moment a part gets used, not at end of week during a count nobody enjoys doing.
A working system does three things without anyone chasing paperwork:
It logs usage at the point of the job. When a tech closes out a work order and marks parts used, that consumption updates the truck’s inventory record and the warehouse total in the same motion. No separate entry, no double handling. If your dispatch and job-costing tools already capture parts used per job (and most decent field service platforms do), the sync is a matter of wiring that data through rather than building a new habit.
It reconciles truck stock against a target par level. Every truck should carry a defined list of what it needs for the jobs it’s likely to run that week, not a random accumulation of whatever’s been thrown in over the years. Once that par level exists, the system can tell you in real time which trucks are running light and which are overstocked, truck by truck, part by part.
It gives dispatch visibility before booking. This is the piece most shops skip entirely. If dispatch can see that Truck 4 is out of a specific part before booking Truck 4 on a job that needs it, you avoid the failed trip altogether. That single check, done automatically instead of by memory, prevents a meaningful chunk of the wasted trips we see in the field service world.
None of this requires ripping out your existing dispatch software. It requires an integration layer and a bit of automation logic sitting on top of what you’ve already got.
Low-stock alerts that actually reach someone
Most inventory software already has a low-stock alert feature. Almost nobody uses it well, because it either fires too often and gets ignored, or it fires into an inbox nobody checks until Friday.
A low-stock alert that works has three properties. It’s tied to actual usage velocity, not a static minimum someone set two years ago and forgot about. It goes to the person who can act on it, meaning the ops manager or the parts buyer, not a general email alias. And it’s timed to give enough lead time to reorder before a job gets scheduled that needs the part.
For a roofing crew, that might mean an alert when a pallet of a specific shingle line drops below three days of typical usage. For an electrical contractor, it might mean flagging breaker stock the moment two trucks report using the same SKU in the same week, which usually signals a run of similar jobs coming through.
The point is that the alert should feel like a nudge from someone who’s actually watching your business, not noise from a system that cries wolf. This is exactly the kind of ongoing, rules-based monitoring that our Omni ops builds handle well, because it’s repetitive, data-driven, and doesn’t need a human making judgment calls on every single alert.
AI reorder predictions based on job type and season
This is where the inventory conversation gets genuinely useful instead of just tidy. Once you have clean usage data flowing from truck to warehouse, you can start predicting what you’ll need before you need it.
HVAC demand for capacitors and contactors spikes in the first heat wave of the season, every year, predictably. Plumbing businesses see a jump in water heater parts the first cold snap after a mild fall. Roofing crews see shingle and flashing usage move with storm season and insurance claim cycles. None of this is a mystery. It’s just rarely built into how trades businesses actually order.
An AI-driven reorder model looks at job type mix booked for the coming weeks, cross-references it against historical parts usage for similar jobs, and factors in the seasonal pattern specific to your trade and your region. If your dispatch calendar shows a run of AC install jobs booked for next week, the system should already be flagging the refrigerant line sets and disconnect boxes you’ll need, before a tech ever calls in short.
This doesn’t replace your judgment. It gives you a recommendation with the reasoning attached, so your ops manager can approve a reorder in two minutes instead of doing the math from scratch every time. For a business running six to twelve trucks, that’s often the difference between a parts buyer spending an hour a day on reordering and one spending fifteen minutes reviewing suggestions.
How this connects to the rest of your dispatch operation
Inventory doesn’t sit in isolation from the rest of your field operation, and neither should the automation around it. The same logic that flags a low-stock part is the same operational discipline that should be answering your phones and following up on your estimates.
Take the 24/7 Dispatch Voice Agent we build for trades clients. It answers every incoming call, qualifies whether it’s an emergency or a scheduled job, and books the slot directly into your dispatch tool. Once inventory data is flowing properly, that same booking step can check truck stock before confirming, so you’re not scheduling a job you can’t actually fulfill on time.
The Estimate Follow-Up Agent works the same territory from a different angle. It tracks every estimate that goes out and follows up on day 2, day 5, and day 14 with messages tuned to the trade and the job size. Estimates that mention specific parts or equipment feed straight back into your reorder forecasting, so a big commercial HVAC bid you’re chasing shows up in your parts planning before you’ve even won the job.
And the Review and Reactivation Agent closes the loop on the customer side, asking every happy customer for a review the day after the job and reaching back out at the right service interval to bring them back in. None of these agents are inventory tools on their own. But they all run on the same principle: capture the data at the moment it’s generated, and let automation act on it instead of waiting for a person to notice.
If you want a broader look at how these pieces fit together across a trades operation, our guides section has more on dispatch, follow-up, and field service automation specifically.
The dollar reality of getting this wrong
Run the numbers on a mid-size trades business with eight trucks. If each truck fails a job once every two weeks due to a missing part, and that failed trip costs an hour of tech time plus a rescheduled visit, you’re looking at roughly 200 hours of wasted labor a year across the fleet. At a loaded labor rate of $75-$100 an hour, that’s $15,000-$20,000 gone before you even count the customer frustration or the lost upsell opportunity from a tech who now has to rush the reschedule.
Add in the cash tied up in over-ordered stock sitting in trucks nobody’s tracking, and the emergency supply-house runs that eat into billable hours, and you start approaching the kind of leakage we see across missed calls, dispatch overhead, and follow-up gaps in businesses this size, typically in the $50K-$200K range annually. Inventory chaos is rarely the biggest single line item in that number, but it touches nearly every other one, because a failed trip cascades into a missed call from the next customer waiting, and a rescheduled job that never gets the same-day follow-up it should.
What an Omni Audit actually shows you
We don’t lead with a deck or a long sales process. An Omni Audit is 60 minutes, and you walk away with three specific things: a breakdown of where your dispatch and inventory process is leaking time and money, a rough model of what automating the worst of it would save you annually, and a straight answer on whether an agent-based build makes sense for your business right now or whether you’re better off fixing a process gap first.
If your team is any good at what they do but keeps getting undercut by trucks running short, phones going unanswered, or estimates that die in someone’s inbox, this audit will tell you exactly where to start. Book a 60-min Omni Audit and bring whatever inventory data you’ve got, even if it’s a mess. That’s usually the most useful starting point anyway.
While you’re getting your team aligned on the phone side of this, it’s worth grabbing our After-Hours Call Recovery Plan for Trades, a practical worksheet for closing the gap on calls that come in after hours and never get followed up. It pairs well with the inventory work, because a business that’s tightened up its truck stock but still losing calls to voicemail is only solving half the leak. You can grab the direct version here.
Where to go from here
Truck inventory tracking isn’t a project you tackle once and forget. It’s an ongoing discipline that either runs on automation or runs on someone’s memory, and memory doesn’t scale past two or three trucks. Real-time sync, alerts tied to actual usage, and reorder predictions built on your job mix and season are all achievable without a system overhaul, using tools you likely already have plus the right automation layered on top.
If you’re running a plumbing, HVAC, electrical, or roofing business anywhere in the $1M-$25M range and you’re tired of guessing what’s on your trucks, see Omni for trades businesses and get a clear look at what’s actually leaking. We also cover related field-service automation topics regularly in our insights section if you want more context before you talk to anyone.
The fastest way to know whether this is worth fixing now is still the audit. See Omni for trades businesses or go straight to booking a slot, no deck required, no pressure to buy anything on the call. Just a clear picture of what’s on the table and what it’s costing you to leave it alone.