• Replies 10 replies
  • Subscribers 2 subscribers
  • Views 2 views
  • Users 0 members are here
Options
Related

How do you manage parts inventory across multiple vans?

Deja Washington

Hi everyone!

So our team is growing — we just went from 4 vans to 8 vans this quarter (HVAC install and service) — and I am STRUGGLING to keep track of who has what parts. Right now I'm basically texting technicians "do you have any 3/4" couplings??" and it's... not sustainable lol.

What I want to know: Are you using FieldPulse's inventory features for van stock, or is that overkill? Do you track everything down to the fitting, or just the expensive stuff? And how do you handle restocking — do vans come back to the warehouse or do you do mobile restock days?

We're not huge but we're not tiny either and I feel like there's a smarter way to do this that I'm just not seeing. Any workflows that have worked for your team would be SO appreciated!!

Thanks so much!

— Deja

Parents

  • Quick rundown of what works for us (12 vans, electrical contractor):

    • ABC classification: A items = track in FieldPulse, B items = weekly visual count, C items = buy bulk, don't track
    • Par level cards in each van bin — techs mark when something hits reorder point
    • Consolidated restock: all vans return Monday AM, we reload for the week

    We don't use FieldPulse for real-time van inventory — use it for warehouse-to-van transfers only. The rest is physical systems techs can see and touch.

    Biggest lesson: start simple and add complexity only when forced.

Reply

  • Quick rundown of what works for us (12 vans, electrical contractor):

    • ABC classification: A items = track in FieldPulse, B items = weekly visual count, C items = buy bulk, don't track
    • Par level cards in each van bin — techs mark when something hits reorder point
    • Consolidated restock: all vans return Monday AM, we reload for the week

    We don't use FieldPulse for real-time van inventory — use it for warehouse-to-van transfers only. The rest is physical systems techs can see and touch.

    Biggest lesson: start simple and add complexity only when forced.

Children
No Data