Shop management system

A shop management system is the software an independent repair shop runs its business inside. It holds the repair order from the moment a vehicle is checked in through the invoice, and it carries the customer record, the vehicle record, parts ordering, technician time and the reporting an owner opens on Monday morning. Shops shorten it to SMS, and the phrase covers everything from a full cloud platform down to a system somebody has been running on a server in the back office since 2009.

What does a shop management system hold?

Four things that matter, and the repair order sits at the center of all of them. Customer and vehicle history gives you the last time this truck was here and what was declined. The estimate and invoice give you the money. Technician time gives you hours. Reporting turns the first three into car count, gross profit and the numbers a shop is run on.

Around that core sit the parts of the day nobody talks about at a demo. Workflow labels that say which cars are waiting on parts. The job board a technician looks at. The share link that puts an estimate on a customer's phone. Those are the pieces that decide whether the software fits how the shop already works or fights it.

One of those four is a regulated document. California requires that every job leave the same paper trail: "All work done by an automotive repair dealer, including all warranty work, shall be recorded on an invoice and shall describe all service work done and parts supplied." The same section then requires that "Service work and parts shall be listed separately on the invoice" with its own subtotal for each. Other states write their own version. Whatever your system prints has to carry that split, and software that blends parts into labor gives you an invoice you cannot defend and a gross profit figure you cannot read.

What does the system leave to a person?

The estimate. A shop management system gives an advisor a place to build one and holds it once it exists. The numbers that fill it originate outside the system. Labor hours come from a lookup in a labor guide. Part numbers come from a catalog. Prices come from calling or clicking through two or three suppliers until somebody has stock.

That gap is where the afternoon goes. A digital vehicle inspection finishes, the priced estimate reaches the customer whenever the counter gets to it, and the vehicle holds a bay for the difference. Nothing in the software is broken while that happens. It is waiting for a person with a keyboard. Time the gap on your own tickets, because your number is the only one that argues for changing anything.

How does an SMS shape the way a shop works?

More than owners expect. The workflow labels the system ships with become the shop's vocabulary within a month. The reports it puts on the dashboard become the numbers the owner manages by, whether or not those are the right numbers. Advisors write canned jobs shaped like the system's job structure and stop writing them the moment the structure gets awkward. Give every advisor a week where the old system is still readable before you take it away.

How long does the system have to keep it?

Longer than the subscription. California states the retention rule in one line: "All of those records shall be maintained for at least three years", open to inspection. Federal tax records run on a separate clock, and the IRS treats the software as the books themselves. Publication 583 says that "All requirements that apply to hard copy books and records also apply to electronic storage systems that maintain tax books and records," and that a system replacing paper has to be kept "for as long as they are material to the administration of tax law."

Read that alongside a migration quote. An auditor asking for a 2023 invoice asks the shop, and a vendor you stopped paying has no obligation in that room. History left behind in a cancelled system is an obligation parked on somebody else's server.

What should a shop check before switching?

Start with data export, because everything else is recoverable and your history is not. Ask what comes out and in what format, and whether closed repair orders come with their line detail attached. A vendor that answers slowly is answering.

Then check the daily seams. Which suppliers the system orders from, whether the inspection tool is built in or bolted on, how a technician clocks onto a job, and whether the gross profit report splits parts from labor the way your current one does. Add up the number of times a day somebody retypes a number that already existed somewhere else. That total is the real cost of the system you are on.

Where does automated estimating fit in?

On the repair order, between the finished inspection and the service writer reading it. Mechanica writes the priced estimate onto the ticket the technician was already working, with labor from a published guide, parts from the shop's own suppliers at the shop's own markup, and the source of every number printed on its line. A person reviews it and a person sends it.

The system it writes into today is Tekmetric, and that is the whole of the list. The write-back matters more than it sounds, because an estimate that lands somewhere else is one more thing to retype.

Back to the glossary, or read the guides.