Inventory & Price Book
Inventory scanning and QR workflows
Scan bins, trucks, and QR tags to track parts across vans and the warehouse.
Overview
Most shops have no real idea what's on each truck, so techs roll up short and lose a half-day chasing parts. Thorbis is exploring scanning and QR workflows to track inventory across vans and the warehouse with a phone camera. You'll see what's stocked where, move parts between locations, and trigger reorders before a truck runs dry.
What we're building
Most shops have no real idea what's on each truck, so techs roll up short and lose a half-day chasing parts they thought they had.
Thorbis is exploring scanning and QR workflows to track inventory across vans and the warehouse with a phone camera. You'd scan bins, shelves, and trucks to see what's stocked where, move parts between locations, and trigger reorders before a truck runs dry.
It's for warehouse staff and field techs who need an accurate picture of stock without a clipboard count.
What you'll be able to do
- Scan QR tags on bins, shelves, and trucks
- Track stock levels by location
- Move parts between warehouse and vans
- Trigger reorders when stock runs low
- Audit truck inventory from a phone
- See what's stocked on every truck and shelf
- Stop techs from rolling up short on parts
Rollout plan
- 01
Scan-based tracking
In progressScan QR tags on bins, shelves, and trucks to track stock.
- 02
Location movement
In progressMove parts between the warehouse and vans.
- 03
Reorder triggers
In progressTrigger reorders when stock runs low.
Milestones
- Not started:
QR workflow scoped
Define how bins, shelves, and trucks get tagged and scanned.
- Not started:
Stock-by-location tracking
Track what's stocked where.
- Not started:
Inter-location transfers
Move parts between warehouse and vans.
- Not started:
Low-stock reorders
Trigger reorders before a truck runs dry.
More in Inventory & Price Book
How to send useful feedback
Name the blocked role
Product feedback is more useful when it names the owner, dispatcher, technician, office user, or customer affected.
Explain the workaround
Describe what your team does today and where the process fails under real work.
Define success
Share what would change after launch: time saved, fewer manual steps, cleaner records, or better customer follow-up.