Half past eight on a weekday morning at a service center in Heliopolis, or a large workshop off the Ring Road near El Salam. Seven cars queue at the gate. The receptionist copies plate numbers and complaints into a notebook, then hangs each key on a wooden board with a scrap of paper tied to it. Inside, the electrician calls the parts counter about a sensor that has not arrived. A customer on the phone insists he approved brake pads and nothing else, certainly not new drums. And in the corner stands a sedan that came back with the same fault it was repaired for two months ago, while nobody can find the old paper or remember who worked on it.
The owner sees a busy yard and technicians with their hands full, yet simple questions have no confident answers. How many cars are in the building right now, and what is each one waiting for? What did yesterday's job actually earn after parts and labour? Did every part that left the store this week reach an invoice? Those questions usually start the search for auto repair shop management software in Egypt.
This guide is written for workshop owners, service center managers and operations leads, not programmers. We follow the car from gate to gate: the job card, vehicle history, WhatsApp estimates, parts costing, technicians, reminders, fleet accounts, warranty and shift closing.
At Jad Digital (جاد للتطوير الرقمي) we have been building custom business systems since 2019, and we will say plainly when a ready-made product is the smarter choice, because a three-lift neighbourhood garage does not need what a multi-branch center serving corporate fleets needs.
The short answer
Auto repair shop management software follows every car from intake to delivery on one job card, then links vehicle history, the estimate, customer approval, spare parts, technicians, the invoice, warranty and cash to it, replacing notebooks and scattered phone calls.
- A job card in auto repair shop software records the plate, chassis number, odometer, complaint and intake photos, then tracks the car through inspection, estimate, repair, road test and delivery so anyone can see its status.
- Vehicle history in a workshop management system is stored against both plate and chassis number, so reception sees every earlier visit, part, technician and warranty even after the car changes owner or plates.
- Estimate approval on WhatsApp in a workshop system sends the customer a link with parts, labour and photos of the fault, lets them accept or reject each line, and logs who approved what and when.
- Spare parts control in a car service center system issues each part against a specific job card at its actual cost, which shows the profit on every job and exposes parts that left the store unbilled.
- Service reminders in auto repair shop software calculate the next visit by mileage and by date from earlier odometer readings, then message the customer or the fleet manager with a link to book a slot.
- The cost of auto repair shop management software depends on branches, lifts and users, the size of the parts catalogue, fleet and insurance accounts, integrations with WhatsApp, accounting and e-invoicing, and choosing ready-made or custom.
Symptoms that the notebook has stopped working
The notebook has stopped working when the real information lives in people's heads instead of in a record. These symptoms tend to arrive together:
- Cars in the yard with no known status. A customer calls and nobody can say whether the car is waiting for a part, an approval or a free pair of hands.
- Arguments about what was approved. The deal was verbal, the invoice comes in above expectations, and the dispute happens at the cash desk.
- Parts that leave and never get billed. A technician grabs a part in a hurry, it is never written against the job, and you meet the gap at the stock count weeks later.
- No idea what a job earned. Invoices are written from memory, and nobody can state the margin on an individual job.
- Comebacks nobody can explain. The car returns with the same fault and you cannot tell who fixed it, which part went in, or whether the work is still under warranty.
- Customers who quietly disappear. Nobody remembers that a regular is due for service, so the car goes elsewhere.
- Cars that leave with an open bill. The gate has no link to the cash desk, so a car can leave while its account is still open.
What makes a service center different from a generic ERP
A service center is different because its unit of work is the vehicle and the job card, not the invoice or the stock item. Generic accounting software starts from a sale with a known price. A workshop starts from a complaint whose cause is unknown, cannot price the job until after inspection, and may see the value change mid-repair when a technician finds a second fault.
Several other differences decide whether a system fits:
If you also run a showroom alongside the workshop, that side follows another logic altogether: vehicle stock, instalments and sales commissions. We cover it in our guide to a car showroom management system in Egypt, and the two systems can share one vehicle and customer record.
- The car outlives the customer relationship. Owners change, drivers are often not owners, and one company may send many vehicles. So the record is built around the vehicle.
- Every invoice mixes service and goods. Labour sells by the hour or at a flat rate, parts carry cost and stock, and the margin on each should be visible separately.
- A single part has a world of alternatives. Genuine, aftermarket, commercial grade and imported used, each with its own number, price, warranty and list of compatible models and years.
- Time is inventory. Lifts and technicians are the capacity you sell, and an empty lift hour never comes back.
- Workshops are not all alike. A quick-service oil and tyre bay runs differently from a general mechanical workshop, a single-brand specialist, or a body and paint shop that works in stages and deals with insurers.
Message us on WhatsApp or book a free consultation — we answer plainly, with no obligation.
The modules a car service center actually needs
A service center needs modules that follow the path of the car itself: from the gate, to the estimate, to the lift, to the cash desk, and on to the reminder for its next visit.
Intake and the job card
The job card is the heart of the system, and everything else hangs from it. At the gate the receptionist types the plate and the car appears if it has visited before. Otherwise it is added with make, model, year, colour, chassis number and engine number. Then come the odometer reading and fuel level, the complaint in the customer's own words, and any belongings left in the car.
Most valuable of all are intake photos: a quick walk around the car with a phone records existing scratches before it enters, which closes an expensive argument at handover. The customer signs on screen or receives a receipt on WhatsApp, and the key carries the job card number.
The car then moves through defined statuses everyone can see: waiting, inspection, awaiting approval, awaiting parts, in repair, road test, ready, delivered. One screen at reception answers a customer in seconds and shows the manager where cars are piling up.
Vehicle history by plate and chassis number
A complete vehicle record is what turns a garage that remembers into a center that knows. Each visit stores the date, odometer, complaint, work done, parts, technician, warranty and invoice, and staff can search by either number.
Plate search in Egypt has its quirks: Arabic letters written in different forms and inconsistent spacing. A good system normalises these so the same car does not appear twice. The chassis number, or VIN, is the fixed reference when plates or owners change, and it pins down the exact model and year when you order a part. When a car is sold the record stays with the vehicle, while the previous owner's details stay behind permissions.
Estimates and customer approval on WhatsApp
A written estimate and a recorded approval are the fastest way to cut disputes at the cash desk. After inspection, the service advisor builds the estimate, which Egyptian workshops call the muqayasa, line by line: parts with their grade and price, labour per operation, and outside work if any.
The customer then receives a WhatsApp message with a link that opens the estimate on their phone, along with photos of the fault or a short video from the technician, and accepts or rejects each line separately. The system logs who approved, when, and which version. When a technician finds another fault during the work, a supplementary estimate goes out the same way, so the bill never grows without the owner knowing.
Rejected lines stay on the vehicle record as deferred recommendations, so the next visit starts from a fact: last time you postponed the belts, shall we check them today? That is honest selling rather than pressure.
Spare parts stock and part-to-job costing
The parts store is where workshop profit usually leaks away. The system needs a catalogue with part numbers, alternatives and compatible models, a shelf location for every item, reorder levels, and cost and selling prices that can be updated quickly when the market moves.
The golden rule is simple: no part leaves without an issue note against a specific job card. You then see parts cost next to selling price on every car, and you see anything issued but not invoiced before the job can close. Different items need different handling:
Returns to suppliers and cycle counts are documented movements too. If a central store serves several branches, read our guide to a warehouse management system in Egypt.
- Oils and fluids are bought in drums and issued by the litre, or bought in cans and issued by the piece.
- Batteries and tyres can carry serial numbers where needed, so they link to the supplier's warranty.
- Special-order parts tie to the job card, the deposit the customer paid and the expected arrival, and the job status changes automatically on receipt.
- Urgent street purchases are recorded against the job with the seller, amount and a photo of the receipt.
Technician assignment, lifts and productivity
Assigning work in the system means knowing who is on what right now and how long it took against the expectation. The workshop manager sees waiting cars next to technicians and their skills: mechanical, electrical, air conditioning, computer diagnostics, body and paint. Each line goes to the right person on a specific lift, and one car may pass through several technicians.
The technician starts and finishes a line with a tap on a tablet or phone, which produces two numbers per operation: the standard time agreed for it and the actual time taken. Over time you see who needs training, which operations are underpriced, and how many hours vanish waiting for parts. Incentive pay becomes a calculation tied to completed lines, with comebacks deducted if you agreed that with your team.
Outside work such as machining or an engine rebuild at a specialist shop needs a sub-order with the vendor, cost and return date, so the part does not vanish from view.
Booking and service reminders by mileage and date
Reminders are the cheapest way to fill your lifts on quiet days. Each model has a maintenance schedule, from oil and filters to belts and fluids. The system works out the next visit by whichever comes first, mileage or date. Since customers do not report their odometer daily, it estimates average use from readings on earlier visits and predicts when the car will reach the limit.
The message goes out with the customer's name and car, plus a link to pick a slot that respects lift capacity, and it can sit inside a customer mobile app for your service center if your customer base justifies one. These messages need the customer's consent and a way to stop them. The logic is close to what we describe in what a CRM system is: one record of every contact with each customer.
Company fleet accounts
A fleet customer needs a credit account and approval rules, not a string of cash invoices. Each company has its list of vehicles and authorised drivers, contracted prices for routine operations, a credit limit, and a ceiling per job. Anything above the ceiling goes to the fleet manager for approval, not to the driver who happened to bring the car in.
At period end the system produces a statement detailing every vehicle, job, odometer reading and part, along with maintenance cost per vehicle. A simple portal can let them follow their cars and approve estimates. To see what a well-run fleet will ask you for, read our guide to a fleet management system in Egypt.
Warranty on work done
Documented warranty turns a comeback from a shouting match into a procedure. Each operation and part gets a warranty you define by duration and by mileage, printed on the invoice with its conditions. When the car returns, the record shows at once whether the line is covered, who did it and which part went in.
A warranty job opens linked to the original job card. It is not billed to the customer, but its internal cost is still counted. If a faulty part caused the failure, a claim opens against the supplier and is followed until closed. Over time the comeback report reveals which technician, supplier or operation keeps failing.
Cash and shift closing
Shift closing is the last control point on the center's money. The cashier takes deposits, part payments and full settlement in cash, by card, by mobile wallet or by bank transfer, and every amount links to a job card. Discounts, cancellations and edits after closing need the right permission and a recorded reason.
At the end of the shift the cashier counts the cash, the system compares it with the expected total per payment method, and any difference appears against that person's name and date. Card terminal settlement is reconciled separately, and petty cash spending shows with its documents. A gate pass connects the gate to the cash desk: a car leaves only on a closed and settled job, or with explicit approval on a company's credit account.
The owner's dashboard
One screen to read every morning is enough:
- Cars in the building by status, plus which are late and why.
- Labour revenue and parts revenue with the margin on each, per branch and period.
- Lift utilisation, and technician hours sold against hours available.
- Parts issued but not invoiced, and slow-moving stock.
- Warranty comebacks and their causes.
- Company receivables by age, and cash differences.
Hardware and integrations: what you actually need
You do not need expensive equipment; you need devices that survive a workshop and integrations that stop people retyping data.
If the network drops, floor screens should keep recording and sync later.
The integrations that matter most are WhatsApp and SMS for estimates and reminders, accounting through automatic entries to your accountant's package, and supplier price lists through periodic file uploads.
Then there is e-invoicing and the e-receipt in Egypt. Invoices to companies may fall under the e-invoicing system and sales to individuals under the e-receipt system, depending on how your business is registered and the phase in effect. In practice, the system submits each document with the approved item and service codes, directly or through an intermediary. We walk through the mechanism in our guide to connecting your system to Egypt's ETA e-invoicing. Confirm your current obligations on the official portal and with your accountant.
- Tablets or phones at reception and on the floor, in covers that tolerate oil and dust, for intake photos and for starting and finishing job lines.
- Barcode scanner and label printer for parts shelves and issue notes.
- Diagnostic scanner (OBD). A deep integration is rarely needed at the start. Attaching the scan report to the job card is enough.
- Network and power: solid Wi-Fi across the workshop floor, which metal structures make harder than expected, and backup power for the cash desk.
Ready-made or a custom system?
Ready-made is enough for most small workshops, and custom pays off when the way you operate is itself part of your edge.
When ready-made wins
A workshop or center with one branch, a limited number of lifts, walk-in retail customers and routine services, without fleet contracts or insurance work, is well served by ready-made workshop software. It runs within days and comes with updates you do not manage. Building custom for that situation is usually poor economics. Trial it with real job cards first, check Arabic plate search and estimates, and confirm you can export all your data.
The trade-off is that you adapt your work to the tool, fees grow with branches and users, and it may not handle company contracts or e-invoicing the way you need.
When custom pays off
A custom system starts to make sense with several branches and a central store, fleet contracts with special approval rules and prices, body and paint work with insurers, your own incentive scheme, a corporate portal and an app under your brand, or existing systems you need to connect. You own the code and the database and pay no per-user fees, but the build takes longer and you need a real partner after launch. The general version of this decision is in custom ERP versus off-the-shelf. These are the cases that custom workshop and service center systems are built for.
The middle path
Many centers start with a ready-made tool for daily operations and later build what makes them different on top: a fleet portal, WhatsApp approvals or an owner dashboard. Others build in phases: job card and estimates first, then parts, then technicians and fleets.
What determines the cost of auto repair shop software?
The volume of your operation and the depth of the modules determine the cost, not the name on the box. The main factors:
Compare options over several years rather than on the first invoice, and include what you already lose today to unbilled parts and customers who do not come back. If you would like an estimate grounded in your own center, book a free consultation and we will go through these factors with you line by line.
- The number of branches, lifts and users, and whether central stores and transfers between them exist.
- The size of the parts catalogue, and whether current data is ready or needs cleaning and unified item codes.
- The types of work you run: general mechanical, quick service, body and paint with insurance.
- Fleet accounts: contracted prices, approval rules and a corporate portal.
- Technician rules: standard times, incentives and commissions.
- Integrations: WhatsApp, accounting, e-invoicing and e-receipts, supplier price lists.
- Migrating old data, training, support after launch, and hosting.
- The choice between an ongoing subscription and a custom build followed by support.
What the first 30, 60 and 90 days look like
Safe rollout is gradual: the job card first, then parts, then the numbers. This is an approximate sequence for a mid-sized project, and the actual schedule is set after visiting the center and agreeing the scope.
The first 30 days: understanding and data
A visit to watch a real working day from gate to gate, then mapping statuses and permissions and cleaning the master data: part codes, suppliers, customers, vehicles and operation prices. By the end of this period, reception, the job card and intake photos are ready to test.
Up to day 60: running on the floor
The job card, WhatsApp estimates and the cash desk go live in one branch, with a careful opening count of the parts store and the start of issuing parts against job cards. Reception, technicians and storekeepers are trained where they work, and issues found in live use get fixed as they appear.
Up to day 90: expansion and numbers
Technician assignment and time tracking come on, along with fleet accounts, warranty and reminders, then the e-invoicing connection and the remaining branches. A weekly meeting begins around the owner's dashboard with real numbers: job margin, unbilled parts, comebacks.
A checklist to bring to your first meeting with any software company
Bringing these makes a first meeting far more useful, with any company and not only with us:
To turn this list into a structured document, read our guide on how to write a software project brief.
- Samples of your current paper: job card, estimate, parts issue note, invoice and intake receipt.
- Your number of branches, lifts and technicians with their skills, and your usual daily car count.
- Your current parts file with codes and suppliers, however messy it looks.
- The list of your most frequent operations, with their prices and rough times.
- Current fleet contracts and the statement format each company asks for.
- How you currently handle e-invoicing, e-receipts and your accounting package.
- The three biggest problems you want solved first, in order of priority.
- Expansion plans: a new branch, a body shop, or contracts with insurers.
How Jad Digital builds service center systems
We start from the workshop floor rather than a feature list, and we deliver in phases, each one working before the next begins. Our ERP and business systems work opens with a workshop at your center or over video, where we walk a real car's journey with your team: who receives it, who writes the estimate, who issues the part, who closes the bill, and where information gets lost.
We then agree the first phase that solves the biggest problem, usually the job card, estimates and the cash desk. Interfaces are Arabic and English, technician screens are designed for busy hands with big buttons and few steps, training is by role, and support continues after launch. You own the code and the database at handover.
Our guide to choosing the best software company in Egypt covers how to judge any technology partner. And if we believe a ready-made product will serve you better at this stage, we will say so in the first meeting. Book a free consultation, and we will look with you at where time and margin are leaking today and what is worth building first.
Frequently Asked Questions
What is the best software to manage a car workshop in Egypt?
+
There is no single best product for everyone; the right fit depends on your size and types of work. A small workshop is usually well served by ready-made software that handles job cards, estimates and parts in Arabic, while a multi-branch center serving fleets may need a custom system. Test any option with real job cards.
Can I send a repair estimate to a customer on WhatsApp and get it approved?
+
Yes. The system sends a link that opens the estimate with parts, labour and photos of the fault, the customer accepts or rejects each line, and the time and approver are saved on the job card.
How can I look up a car's service history by plate or chassis number?
+
If its visits are recorded in the system, typing either number shows every visit with dates, odometer readings, work done, parts, technicians and warranty. The chassis number remains the fixed reference even if the plates or the owner change.
How does the software remind customers about an oil change by mileage?
+
It saves the odometer reading at each visit, estimates average use, and predicts when the car will reach the mileage limit. It then messages customers who opted in on whichever comes first, mileage or date, with a booking link.
Does a small garage need this, or is it only for big service centers?
+
Both can use it at different sizes. A small garage needs a job card, estimates, parts issue and a cash desk, and ready-made software usually covers that within days. A larger center adds branches, fleets and insurance, and a custom system for it is normally delivered in phases.
Can the system manage company fleet accounts?
+
Yes, if it is designed for them: each company has its vehicles, authorised drivers and contracted prices, a ceiling that needs the fleet manager's approval, a credit account, and a statement detailed per vehicle and job.
Can workshop software connect to Egypt's e-invoicing and e-receipt systems?
+
Yes. Documents can be submitted from the system directly or through an intermediary, using the approved item and service codes. Because obligations depend on how your business is registered, the type of customer and the phase in effect, confirm your position on the official portal and with your accountant.
