How to Transfer Parts Between Service Trucks Without Losing Them

Two vans, one timestamp

A transfer should name the from truck, the to truck, the part, the qty, and the user. If any of those are missing, you have a story. Stories do not restock vans.

Do it in the parking lot before anyone leaves. Parking-lot transfers that get “entered later” are the ones that never get entered.

Receive is optional; honesty is not

Small shops can one-step the transfer. Larger shops may want the receiving tech to confirm. Either model works. What does not work is a text message and a hope.

If you add receive-confirm, make it one tap. A three-screen approval flow will be bypassed by the first busy morning.

Dispatch can start the transfer

When dispatch sees Truck 8 needs a board that lives on Truck 3, they should create the transfer and tell both techs to meet. The software is the instruction, not a follow-up chore.

FleetStock transfers are office-visible. That is how you stop two techs from “handling it” in three different ways.

Never transfer into the void

There is no location called Mike. There is Mike’s assigned van. If Mike is in a shop truck today, transfer to that truck. Personal names as locations collapse the first time someone rides along.

Assign techs to vehicles in the team screen so the default destination is obvious.

Audit the weird ones

Transfers at 9 p.m. Transfers of ten expensive boards. Transfers that reverse an hour later. Those are the rows a manager glances at once a week. Most will be innocent. The glance keeps them innocent.

You are not building a surveillance state. You are building a parts ledger that matches reality.

FAQ