What Is an Auto Care Back Office?
An independent repair shop often runs daily work from a shared spreadsheet only one person knows how to use. You can build an auto care back office with Claude Code to replace that with one system for the front desk and mechanics. The back office keeps Today, Jobs, Customers, Invoices and Parts tied to live shop records. An agent generated this and the result is a structured ToolJet application, with data, queries and interface together. By the end, you can reproduce the back office from the prompt below and keep bookings, repair work, billing and stock in one flow.
Today page: four KPI cards with month-over-month trends, revenue by week, jobs by service and the next six bookings.
Jobs page: a full-width Kanban board with five status columns and wrapping job cards.
A 28-second read-only walkthrough of all five pages, including the job modal.
Parts page: stock bars, low-stock tags and the receive-a-delivery panel.
How Do You Run Repair Shop Work?
Track repair work by keeping jobs, parts and invoices in one shared system, then review each booking and update it as the day changes. ToolJet MCP lets a coding agent turn the brief into a working app with the same pages, data and actions the shop needs.
- Collect mechanics, customers, vehicles and bookings in one database
- Load jobs, line items, invoices and parts into the same store
- Open the dashboard to review KPIs and the next bookings
- Move work through the board and update status and mechanic
- Search customers, mark invoices paid and receive deliveries
How Do The Five Pages Work Together?
The app opens on Today, where the desk sees the day's KPIs, revenue trend and upcoming bookings in one glance. Jobs is the main working surface, because a card opens a modal that lets the user change status, reassign the mechanic, and attach labour or parts without leaving the board. Customers uses a search-first grid with a side panel for cars and history, while Invoices stays action led with a single paid action. Parts shows stock bars and a delivery intake panel so the shop can keep inventory in the same flow as repair work. The layout stays dense so the screen fits a working day, not a presentation.
- Today dashboard with KPIs, revenue trend and upcoming bookings
- Jobs Kanban with status changes, mechanic assignment, labour and parts
- Searchable customer records with cars and service history
- Invoices with payment state and a Mark paid action
- Parts inventory with stock bars and a receive-delivery panel
Build an Auto Care Back Office with Claude Code in ToolJet
Want to build it yourself? Start with the ToolJet MCP repository and connect it to Claude Code.
Why Is The Prompt Condensed?
The build took several passes across data, pages and interactions. The requirements are consolidated into the prompt below so you can reproduce the result in one shot.
Build a polished internal app called Auto Care Back Office in ToolJet.
Keep it to five pages in this order: Today, Jobs, Customers, Invoices and Parts. Today shows the date, upcoming bookings, KPI cards, weekly revenue, service mix and the next bookings. Jobs is a Kanban board where a card opens a modal to change status and mechanic and add labour and parts. Customers is a searchable grid with a service-history panel. Parts shows stock levels and a receive-delivery panel.
Design it as a dense shop operations app with steel-slate and safety-orange styling, white cards, soft borders and slightly larger text. Use US dollars for every amount.
Use eight ToolJet DB tables: nac_mechanics, nac_customers, nac_vehicles, nac_jobs, nac_job_lines, nac_invoices, nac_parts and nac_bookings. Seed realistic shop records around today, including mechanics, customers, vehicles, jobs, invoices, parts and bookings.
Compare dates in local time. Keep all data in ToolJet DB. Keep the app dense and practical, with only native ToolJet components.
How Does MCP Assemble The App?
The agent reads the requirements and shapes the data model, pages, components, queries and wiring into one structured ToolJet application. The result stays inside the platform as an app the team can keep working on, with data connectivity, workflows, access control, auditing and lifecycle management where supported, and the path stays open from AI generation to visual editing to code. For setup details, see the ToolJet MCP documentation.
What Broke The Invoice Trend Baseline?
The first invoice seed put every record in the same recent window, so the month comparison on Today read flat. Reseeding the invoices with older dates fixed the baseline and made the revenue trend line up with the rest of the shop data.
What Did The Build Checks Show?
The results table summarises the live checks that confirmed the data, pages and write paths in the finished back office.
| Metric | Result |
|---|---|
| Pages | 5 |
| ToolJet DB tables | 8 |
| Queries | 15 |
| Components | 98 |
| Code files to maintain | 0 |
| Repair cycles | 1 |
| Final validation | 0 errors |
The components Claude Code created, in the ToolJet inspector
Which Shops Use This Back Office?
Independent garages, tyre and brake shops and small fleet maintenance teams that want one app for the day's bookings, the job board, customer history, invoices and parts stock. The same pattern suits bike shops, appliance repair and any small service business with jobs, invoices and inventory.
Who Can Use The Back Office?
No groups or per-page permissions were built. Anyone with access to the app sees all five pages: the owner and front desk use Today, Customers and Invoices, mechanics use Jobs and Parts.
Self-Hosting ToolJet: Open Source, On-Premise and Air-Gapped Deployment
An Auto Care Back Office app often works with data that cannot leave your network, and ToolJet lets you run the whole platform on infrastructure you control instead of a vendor cloud. Both the community edition and the enterprise edition can be deployed on-premise, and air-gapped deployment is available for environments with no internet access.
Auto Care Back Office holds customer details, vehicle records, repair history and invoices. Keeping that data on company infrastructure gives the shop's IT review a clean control point for local deployment.
Self-Hosting ToolJet: Open Source, On-Premise and Air-Gapped Deployment
Deployment Options: Docker, Kubernetes and Major Clouds
ToolJet's self-hosting setup guides cover the common ways to run it in your own environment:
- Docker Compose deployment: run ToolJet on a single server, with optional Terraform scripts to provision a VM on AWS, Azure or GCP first.
- Kubernetes deployment: run ToolJet on your own cluster, with dedicated guides for EKS, GKE, AKS, Helm and OpenShift.
- Your own PostgreSQL: ToolJet stores app definitions, encrypted data source credentials and user authentication data in a PostgreSQL database that you manage.
Open Source Core and Air-Gapped Enterprise Deployments
- Open source community edition on GitHub: the ToolJet repository is released under the GNU Affero General Public License v3.0 (AGPL), so your team can inspect the code and self-host the community edition.
- Air-gapped deployment: run ToolJet in fully isolated environments without external network access, listed on the ToolJet Enterprise plan.
- ToolJet AI Enterprise: deploy the AI server image inside your own environment so AI requests are processed on your servers, which suits private-cloud and air-gapped setups.
Self-hosting keeps the Auto Care Back Office app, its data and its credentials inside the network and security boundary your team already governs, and a self-hosted community edition can be upgraded to the enterprise edition when you need enterprise features.
Enterprise Features for Your Auto Repair Back Office
An auto care back office handles customer details, vehicle records and invoice history. ToolJet covers that governance at the platform layer, so you configure it once instead of rebuilding it in every app.
- SSO and SCIM: sign in with SAML, OIDC or LDAP, and provision users automatically
- Role-based access control: scope permissions to the app, the data source, and each query
- Audit logs: track every login, edit, and approval decision for compliance review
- Air-gapped deployment: self-host on Docker or Kubernetes so your data stays in your network
- Multiplayer editing: several builders work on the same app, with versioning and Git sync
- ToolJet AI inside your own deployment: run the AI features in your tenancy rather than a shared service
You could add a notification layer with ToolJet Workflows. For example, a workflow could fire when a job moves to Ready for pickup, post a Slack message to the front desk, email the customer through Gmail, and write the follow-up back to nac_jobs.
Final Takeaways
This article shows how a repair shop back office comes together as a structured ToolJet application from one prompt, not as a static screen. Today, Jobs, Customers, Invoices and Parts cover the shop's daily flow, from bookings and job status to customer history, payment handling and stock checks. That matters because the front desk and mechanics keep working in the same place as the day changes. You can build an auto care back office with Claude Code, then keep shaping the result in ToolJet as the shop's process changes and the records stay connected.
Try ToolJet MCP With Claude Code
Build your own auto care back office with Claude Code, then request a ToolJet demo to map it onto your shop data. Start free on [ToolJet Cloud].
FAQs
What is Claude Code in the Auto Care Back Office workflow?
Claude Code is the coding agent that reads the prompt and assembles the ToolJet application structure. It handles the pages, queries and interactions as one build task, so you get a working back office rather than a loose code fragment or a screen mockup.
What does the Auto Care Back Office include?
The app includes a Today dashboard, a Jobs Kanban, a Customers grid, Invoices and Parts. Those pages cover bookings, job status, customer history, billing and stock for an independent repair shop that needs one place for daily operations and follow-up work.
How do I reproduce the Auto Care Back Office?
Start with the prompt in the page and generate the app in ToolJet. Then connect the same ToolJet DB tables, seed shop records and confirm the Today, Jobs, Customers, Invoices and Parts pages match the intended interactions and refresh behavior.
Do I need to write code for the Auto Care Back Office?
You do not need to write the whole app by hand. Visual editing covers the layout and most interactions, and code is available when a specific interaction needs a custom step or a small adjustment.
Can I start the Auto Care Back Office with my own shop data?
Yes, you can map the pattern to your own repair records as long as the tables match the pages you want. The build here uses ToolJet DB for mechanics, customers, vehicles, jobs, line items, invoices, parts and bookings, and the same page flow still applies.
What happens to the Auto Care Back Office after the agent finishes?
The output is a structured ToolJet application, not a throwaway screen. The runtime keeps the data, queries and interface together, and you can continue adjusting the app visually or with code where needed without rebuilding the whole back office.
Can several people edit the Auto Care Back Office in ToolJet?
Yes, several people can work in the same project as the shop process changes. One person can review the data and write actions while another refines the screens and keeps the back office aligned with daily work.
Top comments (0)