On-site inventory audit

Vehicle Inventory Audit

In production Integrated with dealership data

Audits an automotive dealership's physical vehicle inventory against its dealership management system (DMS), verifying each vehicle by VIN from a phone or Zebra mobile computer.

The physical inventory requires walking the lot and confirming that every vehicle on record is present and in the correct location. The count was recorded on printed forms and entered later, so results were not available until several days after the walk-through.

The application loads the vehicle list from the DMS, and the auditor verifies each vehicle on a mobile device. Corporate staff can see progress and results immediately.

Corporate staff can see inventory progress and discrepancies during the walk-through without waiting for later data entry.

I redesigned version 2 and built the mobile verification workflow, the vehicle receiving module, and support for concurrent inventories by location and brand.

How it works

The DMS vehicle list is checked during the physical walk-through, while corporate staff can follow progress immediately.

Scroll horizontally to view the full diagram.

Parallel physical inventory and vehicle receiving workflows DMS data feeds two independent processes. On the lot, each vehicle is confirmed or recorded as unlisted. In receiving, only eligible vehicles are recorded as received, and completion updates the DMS. SOURCE · DMS WORKFLOW A · PHYSICAL INVENTORY WORKFLOW B · RECEIVING LOAD INVENTORY OPEN YES NO VERIFIED UNLISTED MORE VEHICLES CANDIDATES INELIGIBLE ELIGIBLE NEXT SHARED SOURCE DMS data Vehicles, location, and status COORDINATOR Open inventory Location, brand, and type AUDITOR Verify vehicle VIN and location MATCHING Is it listed? Physical vs. expected MATCH Confirm listed vehicle Verification and location FINDING Log unlisted vehicle Unlisted vehicle details INVENTORY RESULT Progress and completion Updated Excel · manual completion RECEIVING Prepare receiving Candidates and eligibility ARRIVAL Record arrival Completion updates the DMS OPERATING FLOW NEXT VEHICLE / REVIEW RESULT RECORD
Physical inventory and vehicle receiving are separate processes fed by the DMS: one checks vehicles on hand, while the other records eligible arrivals.

Key functions

Product evolution

Version 2 replaced the initial version and expanded its scope with vehicle receiving, separate controls by brand and location, and real-time progress tracking. I redesigned the data model to support multiple concurrent inventories at each dealership location.

Technical details

Backend
NestJS 10 · TypeScript · TypeORM · PostgreSQL 15
Frontend
React 18 · Vite · Tailwind CSS · TanStack Query
Infrastructure
Elastic Beanstalk · RDS PostgreSQL · S3
Data source
DMS vehicle and location list