RepairFlow — Repair & Service Shop Management System

I started building RepairFlow after working with a garage owner who tracked everything in paper notebooks. His real problem wasn't the repairs — it was knowing whether a job was profitable after parts were sourced, and whether his mechanics were working on what they were supposed to be working on. No off-the-shelf script handled that combination, so I built this from scratch for real shop conditions.

It's been running live in production and has processed real repair orders, real invoices, and real inventory movements. This isn't a demo-only project.

Live Demo — repairflow.dreamteams.cloud | Documentation

Demo accounts — password 123456 for all:

Three things that make it different from other repair scripts

1. Digital Vehicle Inspection (DVI) with a customer-facing shareable link
The technician fills out a checklist — Good / Monitor / Needs Repair — and uploads photos per item. The system generates a unique link you send to the customer via WhatsApp or Zalo. The customer views the full inspection report in their browser with no login. When the customer first opens the link, the system records the timestamp. Items flagged as "Needs Repair" can be converted into an estimate in one click — no re-typing. I haven't seen another repair shop script on any marketplace that does this.

2. Remote estimate approval via a shareable link
Send a unique link to the customer. They enter their phone number to verify identity, then approve or decline. No customer account needed. On approval, the estimate converts directly into a repair order with all line items pre-filled. This was designed for situations where the customer drops off the car and you need their sign-off before starting work.

3. One codebase, four shop types
Set the shop type once in General Settings — Auto Workshop, Phone Repair, Electronics, or Custom — and the entire system changes: what the "asset identifier" field is called (plate number / IMEI / serial number), whether odometer is shown, and which inspection templates appear. I'm using this same codebase deployed for different clients with different configurations.

Full module list (17 modules)

Repair Orders — status workflow (Received → In Progress → Parts Waiting → Completed → Returned), multiple technician assignment, internal timeline per order, FIFO inventory auto-deduction on completion, one-click invoice generation. The system prevents double-deducting parts from the same order.

Digital Inspection (DVI) — admin-built templates, technician fills on mobile, photo uploads per item, shareable customer link, first-view timestamp recorded, convert flagged items to estimate.

Estimates with Remote Approval — line items with discount and tax, shareable approval link, phone number verification, approved estimate converts to repair order automatically.

Appointments — book with customer, asset, technician, and service notes. Status: Pending → Confirmed → Arrived / Cancelled. Convert to repair order or DVI with one click — details carry over. Technicians have a personal day-by-day schedule view.

Invoices & Payments — auto-generated from completed repair orders, partial payment support, multiple payment accounts (cash, bank, e-wallet), shareable public invoice preview (no customer login needed), print-ready layout.

Inventory — FIFO batch lot tracking, purchase orders with supplier debt, multi-warehouse + storage location support, stock transfer between locations, kit unbundling with cost allocation, low-stock alerts. Product types: Part, Labor/Service, Bundle/Kit.

Customer Debt & Supplier Debt — aging tracking, partial repayments, overdue highlighting.

Cash Book — income entries auto-created from invoice payments, expense entries from supplier payments, manual expense entries, daily summary per account.

CRM / Leads — prospect pipeline, activity log per lead (calls, messages, notes), source tracking, one-click convert to customer.

5 Report types — Revenue & Profit (gross margin, net profit, trend chart), Inventory value & movement, Debt aging, Operations KPIs & technician performance, Customer & asset history. All reports support Today / 7 Days / This Month / This Quarter / Custom date range.

Roles & Permissions — 4 built-in roles + custom role builder. Powered by Spatie Laravel Permission. Technicians see only their assigned orders and never see cost prices or margins.

Web Installer — 7-step browser-based wizard, no SSH or CLI knowledge needed. Checks PHP extensions, creates the database if it doesn't exist, streams the install log live in the browser. Routes are auto-locked after install completes so the installer can't be re-run.

System Audit Log — every login, logout, failed login, create, update, delete, and restore action is recorded with a before/after data diff. Admin-only access.

PWA — installable from the browser, web push notifications for new orders and completions, mobile bottom nav for technicians, sidebar nav for office roles on desktop.

SMTP Config — configurable from admin settings panel, test email from UI, Gmail App Password supported.

Tech stack

• Backend: Laravel 12, PHP 8.2+
• Frontend: Livewire v3 (v4.x compatible), Alpine.js, Tailwind CSS v4
• Database: PostgreSQL 14+ — MySQL is not supported (JSONB columns are used)
• Auth: Custom provider — staff can log in with phone number or email
• Permissions: Spatie Laravel Permission v6
• Audit: owen-it/laravel-auditing v14
• PDF: barryvdh/laravel-dompdf v3
• Push: laravel-notification-channels/webpush (VAPID)
• Architecture: Livewire component → Service interface → Service → Repository interface → Repository → Model. Every interface is bound in service providers — no concrete class injection.

The codebase uses a custom Enum base class (not PHP 8.1 backed enums) that supports values() for select dropdowns and getLabel($value) with locale-aware translation. All user-visible strings go through translation keys — nothing is hardcoded in English or Vietnamese.

What's in the package

• Full Laravel 12 source code, PHP 8.2+ — no encoded files, no licensing server
• 17 functional modules, all wired up and working
• 7-step web installer (browser-based, no CLI)
• Vietnamese and English language files, fully translated
• 4 built-in roles with a custom role builder
• Inspection template seeders for Auto, Phone Repair, and Electronics shop types
• Demo seeder with realistic data across all modules
• PWA manifest, service worker, web push keys setup guide
• Database migrations and role/permission seeders
• HTML documentation: Installation Guide, User Guide (all 17 modules), Changelog
• 6 months support

Server requirements

PHP 8.2 or 8.3, PostgreSQL 14–16, Apache 2.4+ or Nginx 1.18+, HTTPS (required for PWA and push notifications). Required PHP extensions: pdo_pgsql, openssl, mbstring, tokenizer, xml, ctype, json, curl, gd, zip, fileinfo, intl. Node.js is not needed at runtime — compiled frontend assets are included.

Tested on: Ubuntu 22.04 VPS, macOS local dev (Herd), Hostinger shared hosting (PHP 8.2).

Who this is for

Shop owners who want to stop tracking jobs on paper or in spreadsheets and need something that actually fits how a repair shop works — not a generic CRM with "repair" bolted on.

Developers and agencies deploying a system for a repair shop client. The Service/Repository architecture and interface binding make it straightforward to extend without touching the core layer.

SaaS builders who want a working multi-role, multi-vertical base to clone per customer or build a proper multi-tenant product on top of.

Changelog

v1.0.0 — 2026-08-26 — Initial release
17 modules: Repair Orders, Digital Inspections (DVI), Appointments, Estimates (remote approval), Invoices, Payments, Customer Debt, Supplier Debt, Cash Book, Inventory (FIFO + Kit Unbundling), CRM/Leads, 5 Reports, Roles & Permissions, System Audit Log, SMTP Config, PWA, Web Installer.