Project context
Inspection centres ran intake, body and paint checks, test-lane measurements and reports on paper, spreadsheets and separate tools. Reports that could be edited afterwards created trust problems between buyers and sellers.
The goal: one cloud panel from intake to payment, verifiable reports, no downtime on weak workshop Wi-Fi, and a product that runs on standard shared hosting without a framework dependency.
Architecture and data flow
- Intake: reception registers vehicle and customer; registration document fields are filled via OCR.
- Work order: appointments follow branch capacity, technicians are assigned, states are timestamped.
- Inspection: the technician records a part-level body and paint diagram, paint thickness, checklists, OBD and test-lane results on a tablet.
- Report: a PDF is generated, its content hash is taken with SHA-256 and bound to a QR code; corrections create a new version.
- Payment and analytics: till, branch performance and revenue on the manager dashboard.
Engineering challenges and solutions
Proving a report was not altered
Each report version's content hash is computed with SHA-256 and the QR code points to that version. Scanning compares the customer's copy with the server record. Corrections never delete the old version; a new one is created, so every change is traceable.
Lost connectivity in the workshop
The technician tablet is a PWA with a service worker; entries are queued on the device and synced when the connection returns. If the same record changed in two places, the user is asked instead of silently overwriting.
Self-service subscription
A company fills in the form, verifies with a 6-digit email code and gets all modules for 7 days. After that the account locks but data is kept; choosing a plan continues where it left off. New sign-ups are emailed to the administrator.
Multi-company, multi-branch
Each company manages its own branches, users and prices; role-based screens show technicians only their work orders and reception only its branch.
The resulting system
Reception works from a desktop, technicians from a tablet and managers from a phone in the same system. Customers receive QR-verified PDF reports. The product is on sale at otoekspertiz.kassa.com.tr with an SEO-optimized landing page, plan table and WhatsApp contact.
Technology stack
Related product and service
Go to the product page: Ekspera Car Inspection
Frequently asked questions
How does QR verification work?
The SHA-256 hash of each report version is stored on the server; scanning the QR compares the customer's report with that record.
What happens if the internet drops?
The technician keeps working. Entries are queued on the tablet and synced automatically when the connection returns.
What does it run on?
PHP 8, PDO and MySQL on standard cPanel hosting, with no special server or framework dependency.