Barcode scanning for parts check-in/check-out

Hey team — quick question on inventory workflow. We're trying to tighten up our parts tracking and I'm wondering if anyone's using barcode scanning in FieldPulse for check-in/check-out scenarios.

Here's our situation: techs pull parts from the warehouse in the morning, use them throughout the day, and return unused items at night. Right now it's a lot of manual entry in the mobile app and we're seeing delays at both ends of the day. Not ideal when everyone's trying to get on the road.

I've seen the barcode scanning mentioned in release notes but I want to understand the actual workflow before I commit the team to it. Specifically:

  • Does the mobile app camera scan work reliably, or are we talking about needing external Bluetooth scanners?
  • Can techs scan parts "out" to themselves at the start of shift and "in" when they return them?
  • Does this integrate with the existing Reserving Inventory for Upcoming Jobs feature or is it a separate flow?

Also open to hearing how you've structured this if you're doing something similar. I've seen some teams use a hybrid approach with a dedicated "parts runner" role but that feels like overhead we don't need at our scale.

Thanks!

Parents
  • We've been running barcode scanning for about 6 months now. Short answer: camera scanning works fine for most scenarios, but there are some gotchas worth knowing.

    The native camera scan in the mobile app is actually pretty solid on iPhone 12+ and most recent Androids. Where it struggles is:

    • Damaged or wrinkled barcodes (obviously)
    • Very small labels (under 0.5" wide)
    • Glare from warehouse lighting

    Pro tip: If you're doing high volume, Bluetooth scanners are worth it. We use the Socket Mobile S740s — about $350 each, but they pair seamlessly and cut scan time from 3-4 seconds to basically instant. Pays for itself in labor.

    For your workflow specifically: yes, you can do check-out to technician and check-back-in. Go to Inventory → Transfer and select the technician as the "destination." When they return parts, reverse it. The system tracks who has what.

    One thing the docs don't emphasize: this creates a pending location for that technician. It's not the same as a parts reservation for a specific job. So if you're also using job reservations, your tech effectively has inventory in two places — their "pocket" and committed jobs. We've learned to run a weekly report to reconcile.

  • Josh, this is exactly what I needed — thank you. The "pending location" distinction is something I would've stumbled on for sure.

    Follow-up: when you run that weekly reconciliation, are you using the standard Inventory Report or did you build something custom? I'm trying to avoid export-to-Excel gymnastics if I can.

Reply Children
No Data