Service Memory & Reminders

The shop remembers each vehicle: what was done, at what reading, and when it is next due by kilometres or months from its service schedule. Service Due lists what is coming up and overdue, plus document expiries (PUC, insurance, fitness), so the shop can call or WhatsApp the owner. A general repair shop that bills and forgets leaves this off.

Switch: Settings > Projects > Service Reminders, with Remind This Many Days Ahead, Default Interval (distance) and Default Interval (time).

Where it appears

Vehicle service shell: Service Due group (All Due, Overdue, Documents) in Navigation, Service Intervals under Management, next-due on the Service Desk vehicle card and the dashboard. POS page: Projects > Service Due / Document Expiry.

Flow

flowchart TD
    S[Service Intervals master
service type · km · months · vehicle type] --> V[Vehicle: schedule · odometer · avg km/day] J[Job card delivered or bill with vehicle] --> L[(Service logged: date · odometer · type)] L --> N[Next due = last + interval km or months
projected date from avg km/day] V --> N N --> D[Service Due list: due · overdue · documents expiring] D --> W[WhatsApp / call · reminderSentOn] D --> B[Book: vehicle comes in] --> J DOC[PUC · insurance · fitness expiry on the vehicle] --> D
Delivery writes the log; the log and the schedule give the next due; the list is a query over vehicles.

Screens

Setting it up

flowchart LR
    A[Settings > Project
Service Memory on] --> B[Set the reminder window
and default intervals] B --> C[Create service schedules
km and months per service type] C --> D[Record each vehicle’s current odometer] D --> E[Bill or deliver a job · service logged] E --> F[Next due calculated] F --> G[Service Due list starts filling]
Switch it on, put the master behind it in place, then do the first one — in that order, or the first one will not have anything to pick.