Client project
SwiftFix Auto: a workshop management platform for a UK garage
Online MOT booking, card payments, a customer portal and an offline-ready admin app that runs jobs, quotes, invoices and stock for an MOT and repair garage.
In active development ahead of launch. Card payments run in the gateway's sandbox until then, and the new website is not yet live.
- Client
- SwiftFix Auto, United Kingdom
- Sector
- Automotive services
- Industry
- Automotive Services
- Period
- 2026
- Platforms
- Customer website, Installable admin web app (PWA), REST API
- Key figures
- 3connected apps: website, admin PWA and API
- 7staff roles with server-side permissions
Apps people use
- Customer website
- Installable admin web app (PWA)
Backend and business rules
- Kotlin
- Spring Boot 4
- Spring Security 7
- PostgreSQL
- Flyway
- JWT
- OpenAPI
- Docker Compose
Connected services
- S3-compatible storage
- Global Payments GP API
- Twilio
- Amazon SES
The problem
An independent MOT and repair garage was running bookings, job cards, quotes, invoices and parts across separate tools. It needed one system for the workshop and a customer website where people could book and pay for an MOT, follow their job and pay invoices online.
What we built
We built three connected parts: a Next.js customer website with online MOT and service booking, an installable admin web app for the workshop, and a Kotlin and Spring Boot API that holds the business rules. The API also connects to the UK DVLA and MOT history services, the card payment gateway and messaging providers.
Key features
- Online MOT and multi-service booking from a service catalogue; paid bookings become prepaid jobs
- Vehicle details and MOT history looked up from UK government APIs by registration number
- Card payments with hosted fields and 3D Secure 2 for bookings, invoices and payments at the counter, plus refunds
- Customer portal with invoices, documents and a live job-tracking page
- Job board, job cards, bays, calendar and job templates for the workshop
- Quotes with shareable links, invoices with VAT, and PDF invoices, quotes and completion certificates
- Vehicle health checks that customers can approve
- Parts, stock movements and suppliers, with parts used recorded per job
- WhatsApp and SMS through Twilio, email through Amazon SES, and automatic MOT reminders
- Seven staff roles enforced on the server, with an audit log and restore from trash
- Installable admin app with an offline mode and notifications
- Reports and accountant exports in CSV and PDF
Technology stack
The main technologies used in this project.
- Kotlin
- Spring Boot 4
- Spring Security 7
- PostgreSQL
- Flyway
- JWT
- OpenAPI
- Docker Compose
- S3-compatible storage
- React
- Vite
- vite-plugin-pwa
- TypeScript
- Next.js
- Tailwind CSS
- Global Payments GP API
- Twilio
- Amazon SES
Our role
NinjaNext designed and built the full system: the backend API and its database migrations, the admin web app and the customer website. The invoice and document layouts follow the owner's own designs.
Challenges and how we handled them
A workshop that cannot stop for a bad connection
Workshop staff keep working when the connection drops. The admin app queues changes offline and syncs them later, and any conflict is resolved predictably and written to the audit log.
Access that matches real job roles
Owners, managers, finance staff, parts advisers and technicians see different things. Permissions are checked on the server for every request, not only hidden in the interface, and technicians see only their own jobs.
Payments that hold up in a dispute
Every payment, from online bookings to the counter, goes through the gateway's hosted fields with 3D Secure 2, and the system can produce a payment proof pack for each transaction.
What the client said
Working with NinjaNext Technologies gave us a clear path from our initial idea to a digital product. The team focused on the core features, listened to our feedback, and worked through changes as the project developed. We wanted a solution that was practical for users and could support future improvements, and that was the focus throughout the development process.
Let's build it
Planning something similar?
Tell us about your project. If it is close to SwiftFix Auto, we will explain what we would reuse, what we would do differently and what to decide first.