The load is delivered.
The paperwork should follow.
SherHaul helps independent truck drivers keep receipts, track unloading fees and waiting-time charges, and prepare reports for brokers.
A delivery has a second job attached.
An owner-operator can finish a delivery and still have work to do: keep the unloading receipt, track the cost of waiting, and explain those charges to a broker. A missing receipt or a scattered record makes that next conversation harder. SherHaul starts with that practical problem.
Build around the driver’s next action.
I built and launched SherHaul around a focused workflow: capture, track, report. Lumper fees are charges for loading or unloading help; detention costs concern time spent waiting. Giving those records a home keeps the product close to the work a driver already needs to do.
Two people may share one job.
A driver may capture information at the dock while an owner or family member handles the paperwork. That changes the design: fast capture in the field, clear records later, and multilingual support as a useful service capability.
The system behind the workflow
The app uses React Native with Expo, Supabase, TanStack Query, Zustand and RevenueCat. The architecture includes an offline queue, location capture, PDF output, notifications and server-side AI-assisted receipt processing. Optical character recognition (OCR) reads text from receipt images to reduce retyping while the app organizes the records a carrier needs to report costs.
A failed scan is a product state.
Receipt scanning needs a clear ending. The workflow replaces an indefinite spinner with pending, complete, partial and failed states, a deadline and a retry path. That is a product lesson: a driver needs to know what happened and what to do next, especially on an unreliable connection. A measured improvement in scanning accuracy is not published here.
From records to follow-through
The next proposed step is a collection workflow: claim status, aging and follow-up steps, plus Punjabi voice capture that produces an English draft for the carrier to review. These are roadmap directions. They extend the original capture-and-report workflow toward the question a carrier actually cares about: what is still unpaid, and what should I do next?
What is established
I built and launched SherHaul on the App Store. The product website and store listing are linked below. Payment recovery rates, customer counts and OCR accuracy benchmarks are not published in this case study.
A few useful answers
Who is SherHaul for?
SherHaul is built for owner-operator truckers who need to capture, track and report lumper and detention costs to brokers.
What technology does SherHaul use?
The repository uses React Native, Expo, Supabase, TanStack Query, Zustand and RevenueCat, with documented OCR, offline queue, location, PDF and notification workflows.
Sources and scope
Based on Adnan’s professional profile, SherHaul’s current product brief and package manifest reviewed in October 2026. The brief separates shipped work from the collection-engine roadmap. The product and App Store links are public artifacts; no measured recovery or OCR-accuracy improvement is claimed.
