Select a useful pilot matrix
Choose a limited set of store routes that represent different receiving arrangements and vehicle configurations. Identify who drives each route and which truck is normally assigned. A pilot is more informative when the tested combinations are named before the demonstration.
Include loading, receiving work, returns and any relief-driver arrangement. Keep stock availability, order completion and customer inventory outside the driver-log scope unless a separate integration is verified.
Retail replenishment evaluation worksheet
| Pilot combination | Evidence to record |
|---|---|
| Usual driver / usual route | Correct vehicle and complete sample-day review |
| Different receiving arrangement | Actual waiting and unloading duties |
| Spare truck | Engine/connector fit and parked vehicle handoff |
| Relief driver | Named-account change and earlier-record access |
Bring the actual truck configuration
Use the vehicle-selection and log-review workflow in the PT30 manual for the applicable version. Record the exact truck, mobile device and app used in each trial.
Ask Factor ELD which configurations the proposal covers and which need another test. Keep unresolved combinations out of a fleet-wide acceptance decision.
For the broader fleet discussion, see private fleets. Use the ELD rollout checklist to assign training and review responsibilities, and check ELD applicability for the actual operation.
Retail replenishment questions
Can the easiest store route represent every fleet configuration?
Only if it covers the relevant differences; otherwise add representative tests for the missing combinations.
Does the ELD confirm that store shelves were replenished?
No. Stock and receiving records remain separate from driver activity records.