AutoCare PMS is a management system for auto repair shops, with a reminder engine that tells the shop which customers are due for preventive maintenance.
02
The problem
Repair shops lose repeat business because nobody remembers when a car is due for its next service. Job orders, parts and invoices live in different notebooks, so stock and billing never match.
03
What I built
Customers, vehicles and full service history
Maintenance forecast by mileage and date: overdue, due soon, on track
Job orders from intake to release, with technician assignment
Parts stock deducted per job, with low-stock alerts
Quotations and invoices
SMS outbox with a queue, retries and personalised blasts
Reports on revenue, fleet health and technician workload
04
Architecture
A React and TypeScript app keeps its state in a Zustand store and talks to serverless functions. Photos and documents go to cloud storage. A reminder engine forecasts the next service and queues SMS messages with retries.
Architecture · AutoCare PMS - Car Shop Management
A high-level view. Endpoints, hosts and security details are left out on purpose.
05
Key decisions
01
Forecast by mileage and by date
Why: Some cars run a lot, some sit; using both catches whichever comes first.
Trade-off: Mileage has to be recorded at every visit to stay accurate.
02
SMS goes through a queue
Why: Messages are queued and retried, so a network hiccup does not lose a reminder or send it twice.
Trade-off: Reminders are not instant; they go out as the queue runs.
03
Parts deduct per job
Why: Stock follows the work done, so the low-stock alert reflects reality.
Trade-off: Every job order has to list the parts used.