Custom collision repair software in Baltimore: the paint doesn't count

The man who made me write this article has run a two‑booth collision shop off Pulaski Highway for twenty‑two years. He called about a customer portal. We spent maybe five minutes on the customer portal.

Then he told me about a 2014 Escape that came in on a Tuesday, went out branded, and cost him a customer he had been repairing cars for since her first Civic. The insurer totaled it. He agreed it was a total — the estimate came out over the value of the car and nobody sane repairs that. What he did not agree with, eleven months later when she called him furious about a trade‑in offer, was that the title had to say so.

He was right, and he had no way to prove it, because the number that would have proved it does not exist in any system he owns.

“I've written maybe forty thousand estimates. Nobody ever told me the state adds it up differently than I do.”

This is the thirty‑second trade we have taken apart in this series, and it is the first one where the statute and the software are looking at the same document and reading two different totals off the bottom of it. In commercial cleaning the tax attached to a room. In home care the deadline attached to a gesture. Here the whole thing is stranger: Maryland accepts your estimate, line for line, and then performs an arithmetic on it that no estimating platform in the country will perform for you — and the answer decides whether a car keeps a clean title.

Let me start with the market, because collision in Maryland is a bigger and more concentrated business than its street‑level appearance suggests.

Five hundred and twenty-nine shops, and half of them are here

The Census Bureau counts 529 automotive body, paint and interior repair establishments with paid employees in Maryland, employing 4,945 people against an annual payroll of $342.2 million. That is not a cottage industry. It is a third of a billion dollars of wages, and just under half of it is in the Baltimore metro.

The six jurisdictions that make up the Baltimore metro — the City, Baltimore County, Anne Arundel, Howard, Harford and Carroll — hold 259 establishments and 2,484 employees between them. That is 49.0% of every collision shop in Maryland inside one commuting radius, at an average of 9.6 people per site. It is the shape I priced everything in this article against: a shop with nine or ten on the payroll, one or two booths, and an owner who still writes estimates.

Collision is not a bigger version of the mechanical shop next door

People outside the trade lump body shops in with repair garages, and the numbers say that is wrong in two directions at once. The same Census file counts 1,631 general automotive repair establishments in Maryland employing 8,625 people — three times as many businesses, but only 5.3 employees each against collision's 9.3. Collision sites are 77% larger by headcount.

And they pay differently. Annual payroll per employee is $69,209 in collision against $55,487 in general repair — a 25% premium. That gap is the whole business model in one figure. A collision technician is a structural repair specialist working to manufacturer procedures on vehicles with bonded aluminum, high‑strength steel and calibrated sensors, and the labor is where the money goes and where the risk lives.

One caveat I want to state before anyone quotes these numbers back at me: County Business Patterns counts only establishments with paid employees. Collision has fewer sole proprietors than the trades we usually write about — you cannot run a frame rack and a spray booth out of a van — so the undercount here is smaller than it was in our landscaping or cleaning pieces. But it is not zero, and the true number of places in Maryland that will paint a fender is higher than 529.

What the platforms charge, and what the four that matter will not say

Every one of these articles starts with the same exercise. I open the vendors' own pricing pages, on one day, and write down what they say. Not what an aggregator says, not what a salesperson said on a call — what the vendor publishes to the open web, with the HTTP status code next to it, so you can check my work.

I have done this for restaurants, law firms, pharmacies, movers, storage operators and a dozen other trades. Collision is the worst result I have ever recorded.

Read the top half of that table again. Five 404s and two 403s, and every one of them belongs to a company whose product a Maryland body shop is, practically speaking, required to run. Not required by statute — required by the direct repair program agreements that route the work. If your volume comes through an insurer's DRP, you write on the platform the insurer specifies. That is not a rumor; CCC says it plainly in its own annual report, describing its software as “the architectural backbone of insurance DRP systems.”

I want to be fair here, because I have been unfair about pricing pages before and had it pointed out to me. There are honest reasons a vendor will not post a number. Collision estimating is not one product; it is a database subscription plus seat licenses plus modules plus data‑exchange fees, and the mix genuinely differs shop to shop. Enterprise software has always been sold this way. Nobody is doing anything improper.

But the effect on a nine‑person shop in Rosedale is the same whatever the reason. You cannot compare. You cannot budget. You cannot walk into a renewal knowing what the alternative costs, because the alternative also declines to say. And when every supplier in a category withholds the same fact, the fact stops being a commercial secret and starts being a structural feature of the market.

Web‑Est deserves its own sentence, because it is the closest thing to an exception and it is not one. Its page is literally titled “Online Collision Estimating Software Pricing.” Its first line is a promise: “There's nothing behind the curtain on our pricing.” Then it asks for your email. There is no price on the page. I checked it three times on 21 August 2026 in case something was rendering late; there is no price on the page.

The only price CCC publishes is in a securities filing

Here is the workaround, and it is the most useful thing in this section. CCC Intelligent Solutions is listed on the Nasdaq. It does not have to tell you what it charges, but it does have to tell its investors what it collects.

From the Form 10‑K for the year ended 31 December 2025: revenue of $1,057.0 million, up 11.9%. Repair solutions “represented approximately 43% of our 2025 total revenues, with nearly 100% of that representing software revenue.” And, from the business description, CCC connects “with more than 30,500 repair facilities through our multi‑tenant cloud platform.”

Divide. Forty‑three percent of $1,057.0 million is $454.5 million. Across 30,500 repair facilities that is $14,902 per facility per year — call it $1,240 a month.

“So the number they wouldn't give me on the phone has been sitting in a public filing the whole time.”

Treat that figure with the care it deserves. It is a crude average across a population that runs from a single‑bay shop in Dundalk to a multi‑state MSO with four hundred locations, and the word in the filing is “more than” 30,500, which pushes the true average down. It also lumps in entities that estimate damaged vehicles without repairing them. No individual shop should expect a quote near it.

But as a sense of scale it is worth more than every aggregator page I have ever read on this subject, and it moves the conversation from “expensive, apparently” to a number with a source. For context, that $14,900 a year is roughly three to seven times what the shop‑management platforms in the bottom half of the table charge for a year. There are good reasons for that — the parts and labor database behind an estimating platform is a genuinely enormous asset that nobody in this article could or should try to rebuild — but the shop paying it is entitled to know the order of magnitude.

One more line from that filing is worth keeping. CCC reports a historical software gross dollar retention of 98–99%. Almost nobody leaves. In most software categories that means customers are delighted. In this one it mostly means they cannot.

The part no national platform models

Everything above is a purchasing problem, and purchasing problems are annoying but solvable. What follows is different. It is a modeling problem, and it is the reason we write these articles at all.

Maryland decides whether a repairable car keeps a clean title with a percentage. That is not unusual; most states do. What is unusual is the numerator.

Maryland does not add up your estimate

Start with the definition. Md. Code, Transportation Article, §11‑152(a) says that “salvage” means any vehicle that

“has been damaged by collision, fire, flood, accident, trespass, or other occurrence to the extent that the cost to repair the vehicle for legal operation on a highway exceeds 75% of the fair market value of the vehicle prior to sustaining the damage…”

Read the bolded phrase slowly. It is not “the cost to repair the vehicle.” It is the cost to repair it for legal operation on a highway. Those are two different quantities and Maryland means the second one.

Then §13‑506(c)(4) makes the distinction operational. In determining the cost to repair a vehicle for highway operation, for purposes of §11‑152, “a person may not use the cost of: (i) Towing, storage, or vehicle rental; or (ii) Repairing cosmetic damage.”

So the statute carves out a category and does not define it — and then, unusually for this series, the state actually went and defined it. §13‑506(c)(6) directs the Administration, in consultation with the State Police, to adopt regulations, and it did: COMAR 11.15.34, titled “Salvage Vehicle Calculation.” The entire chapter is two regulations long. One is a scope note. The other is this.

That right‑hand column is not my interpretation of the spirit of the thing. It is regulation .02C, in full: “Except as set forth in §B(1) of this regulation, the cost for cosmetic damage repairs shall only include the cost of parts and materials and may not include the cost of labor.” Since .02D excludes “the cost for cosmetic damage repair” from the calculation, and .02C defines that cost as parts‑only outside refinishing, the labor to remove and install a bumper cover is not excluded. It stays in the numerator. The cover itself does not.

Add .02E — no tax on parts or labor is included — and .02F, which says fair market value is “the valuation shown in a national publication of used car values or from a computerized database that produces statistically valid fair market values,” excluding titling, registration and taxes. Now you have the complete recipe, and it is five separate transformations of a document your software hands you as a single total.

Here is what that does to a real repair. This is an illustrative front‑end hit on a twelve‑year‑old crossover, priced at Baltimore‑market rates: body labor $64/hour, structural $105/hour, mechanical $110/hour, paint materials $46 per refinish hour.

The two numbers are $2,472.56 apart, and they fall on opposite sides of the line. On the estimate this car is a comfortable total loss at 106% of its value, and no rational insurer repairs it. Under §11‑152 it is at 70.2% — under the threshold, therefore not a salvage vehicle by the damage test. If the owner keeps it, §11‑152(b) says a vehicle has not been acquired by an insurance company when the owner retains possession on settlement, and the title stays clean.

Both statements are true at once. It is an economic total loss and a legally repairable car. My friend on Pulaski Highway had been in this business since 2004 and had never once been shown that those are separate questions.

Notice which direction the error runs. The statutory figure is always less than or equal to the estimate, because every adjustment is a deduction. So a shop or an adjuster who uses the estimate total as a proxy can only ever err one way: toward branding a title that Maryland would not have branded. There is no case where sloppiness accidentally saves a car. That asymmetry is what makes this worth building software for.

Three hundred and thirty-three dollars, and a sharp edge

Now the part that made me want to write the whole article.

Seventy‑five percent of $6,900 is $5,175.00. Our statutory figure is $4,841.30. The headroom is $333.70 — less than one plastic part.

Go back to regulation .02A, first paragraph, last sentence: “Cosmetic damage shall not include any repair required to enable a vehicle to pass a safety inspection under COMAR 11.14.”

COMAR 11.14 is Maryland's safety inspection standard, and chapter .02 covers passenger cars, light trucks, vans and multipurpose passenger vehicles. Regulation 11.14.02.07 governs bumpers, and it opens: “Bumpers shall be inspected for broken or missing parts, abnormal protrusions, sharp edges, or conditions that could be hazardous to persons.” The rejection list includes “bumper is broken or missing” and “abnormal protrusions or conditions are present which could be hazardous to persons.”

So: our $612 bumper cover is cosmetic under .02B(3) if it is scuffed, scraped or dented. If it is cracked in a way that leaves a sharp edge, repairing it is required to pass a Maryland safety inspection, which means under .02A it is not cosmetic damage at all, which means its $612 goes back into the numerator.

$4,841.30 + $612.00 = $5,453.30. Against a $6,900 value that is 79.0%. Over the line. Salvage.

“Same car, same crash, same estimate. A crack with a sharp edge and it's branded. A crack without one and it isn't.”

I have shown that arithmetic to four people in the trade now and every one of them went quiet for a moment. Not because it is unfair — it is actually a sensible rule, drawing the cosmetic line at the point where appearance becomes safety. It is because there is no field for it. An estimate line says “Bumper cover, front — Replace.” It carries an operation code, a part type, a part price, a labor time and a labor category. Nowhere on it does it say whether the thing being replaced had a sharp edge, and nothing downstream ever asks.

The same regulation, incidentally, has an elegant detail that shows the drafters knew exactly what they were doing. In measuring bumper height, 11.14.02.07B(1)(a) says that “on vehicles equipped with soft bumper covering, the measurement will be made on the reinforcing horizontal bar.” The inspection standard already treats the cover as skin and the bar as the vehicle. COMAR 11.15.34.02 makes exactly the same cut in the salvage calculation. Two different regulations, written years apart by two different units, agreeing that the soft part is not the car. Your estimating platform has one line item for both.

The sticker in the door jamb decides which statute you are under

While we are on that inspection regulation, look at the last sentence of 11.14.02.07A: bumper height “shall be no higher than 20 inches for Class A passenger vehicles and no higher than 28 inches for Class E light trucks or Class M multipurpose passenger vehicles.”

Eight inches of difference, decided by a registration class. And that same class distinction reaches much further than bumper height.

Maryland's aftermarket parts rules live in Commercial Law Article, Title 14, Subtitle 23 — a different subtitle from the repair‑estimate law we covered in our auto repair article. Section 14‑2302 is genuinely demanding. Before beginning work on crash parts a body shop must give the owner a list of the replacement crash parts it intends to use and say whether they are genuine; if they are aftermarket the shop must include a prescribed written statement with its estimate; and §14‑2302(c) requires the notices to be made “in writing in a clear and conspicuous manner in 10 point capital type.” A violation is an unfair or deceptive trade practice under §14‑2304.

Then read the definitions. §14‑2301(f): “‘Motor vehicle’ means a passenger car as defined under §11‑144.2 of the Transportation Article,” and expressly excludes a motor home. And Transportation §11‑144.2: “‘Passenger car’ means a motor vehicle, except a multipurpose passenger vehicle or motorcycle, designed for carrying 10 persons or less.”

Maryland's own registration scheme confirms the split. Transportation §13‑937(a): “When registered with the Administration, every multipurpose passenger vehicle is a Class M (multipurpose) vehicle.” The term itself comes from federal safety standards, where a multipurpose passenger vehicle is one “designed to carry 10 persons or less which is constructed either on a truck chassis or with special features for occasional off‑road operation.” Most crossovers and SUVs are certified that way by their manufacturers, and the answer for any individual vehicle is printed on the certification label inside the driver's door jamb.

Which means that on a large share of what rolls into a Maryland collision shop — and light trucks and utilities have been the majority of new US vehicle sales for years — Subtitle 23 arguably does not reach the repair at all. Same shop, same aftermarket fender, same customer. Different statute, decided by a sticker.

There is a second, quieter obsolescence in the same definitions. §14‑2301(d) defines “crash parts” as “exterior or interior sheet metal or fiberglass panels and parts which form the superstructure or body of a motor vehicle including but not limited to fenders, bumpers, quarter panels, door panels, hoods, grills, firewalls, permanent roofs, wheelwells, and front and rear lamp display panels.” Sheet metal or fiberglass. Not aluminum, which has been a mainstream body material since the aluminum‑bodied pickup went into volume production in 2015. Not molded thermoplastic, which is what the bumper cover in our table is actually made of — a fact COMAR 11.15.34.02B(3) knows and Commercial Law §14‑2301(d) does not.

I am not telling you to skip the disclosure. Give it on everything; it costs you nothing and it is good practice, and your own counsel may read these provisions differently than I do. What I am telling you is that your software should know the certification class of every vehicle in the shop, because at least two Maryland rules turn on it and no estimating platform stores it as a first‑class fact.

Salvage with no arithmetic at all

Everything above concerns the damage test. There is a second route into salvage that ignores arithmetic completely, and shops trip over it constantly.

§11‑152(a)(2): a vehicle is salvage if it “has been acquired by an insurance company as a result of a claim settlement.” No threshold. No percentage. If the carrier takes the car, the car is salvage, whatever the estimate said.

And Maryland thought this through. §13‑506(c)(2)(ii) gives the insurer five statements to choose from when applying for a salvage certificate, and the fifth is for exactly this case: the vehicle “has been acquired by an insurance company as a result of a claim settlement and the cost to repair the vehicle is 75% or less of the fair market value.” Under §13‑507(b)(4) the resulting title carries a conspicuous “X‑Salvage” notation — a distinct brand from “rebuilt salvage” and from “Flood Damaged.”

So Maryland produces four different title outcomes from the same subtitle, and which one a car receives depends on a two‑dimensional question: how the arithmetic came out, and who ended up holding the keys. A car under 75% that the owner retains is not salvage at all. The same car under 75% that the insurer takes is X‑Salvage. Over 75% and repairable, it is rebuilt salvage. Over 75% and certified not rebuildable, §13‑507(b)(2)(ii) says the Administration may not issue a title for it ever again.

One useful nuance for anyone in the middle of an argument with a carrier: §13‑506(c)(5) says the 75% calculation “may not affect the right of an insurer or a vehicle owner to make an economic or safety related decision to not repair the vehicle.” Maryland is being explicit that the two decisions are separate. The insurer may decline to repair anything it likes. What it cannot do is make the title follow automatically.

Ninety days, seven sites, and a Tuesday morning

The last piece is the one with a clock on it, and it is the piece a production manager can actually feel.

When an owner retains a salvage vehicle, §13‑506.1 requires the insurer to notify the Administration promptly, and the Administration then sends the owner a notice that the registration will be suspended unless proof of a Title 23 safety inspection arrives within 90 days of the date of the notice.

Ninety days from a letter your shop never sees, addressed to a customer who may not open it, for a car that may not be in your building yet. That is a production deadline living entirely outside the production system.

Then there are two inspections, not one. §13‑507(a)(2) requires the title application to be accompanied by both “a certificate of inspection issued by a county police department or the Department of State Police” and a Title 23 safety inspection certificate. Two agencies, two appointments, two documents, in sequence.

The State Police salvage certification inspection is by appointment only, the fee is $75, and it runs at seven sites statewide: Beltsville, Frederick, Hagerstown, La Plata, Perryville, Salisbury, and the Finzel weigh station out on I‑68 in Garrett County. Read that list again with the establishment table in mind. Not one of them is in Baltimore City or Baltimore County — the two jurisdictions holding 121 of Maryland's 529 collision shops. The nearest options for a Baltimore shop are Beltsville, down in Prince George's, or Perryville, up at the head of the bay.

And where the VIN plate is missing or damaged — which after a hard front‑end impact is not rare — the vehicle must be inspected by the Auto Theft Unit at the Glen Burnie site on Tuesdays between 8:30 a.m. and 12:30 p.m. A four‑hour window, once a week, for the entire state.

“If you miss that Tuesday, you don't lose a day. You lose a week, and the car sits on my lot the whole time.”

The inspection also requires the owner to present the repair receipts. That is your paperwork, in a customer's hands, at a state facility, weeks after the car left you. If your documentation is a folder of PDFs someone emailed, this is where it fails.

None of this is exotic. It is a queue with a weekly cadence, a geographic constraint, a document dependency and a ninety‑day countdown that starts on an event you are not party to. It is completely ordinary software. It is simply not the software anyone sells to body shops, because the platforms are built around the estimate and the insurer, and this entire sequence happens after both of them are done with you.

What custom actually costs

We publish our prices, which after the table above feels almost confrontational. Here they are against the problem I have just described.

The comparison worth making is not against the subscription, because you are not going to cancel the subscription and we would not advise it. It is against a single misclassified total loss. An Operations System is $12,000 once and you own the source code; a diminished‑value dispute over a title that should have stayed clean is not a $12,000 problem, and it does not arrive alone — it arrives with a customer who tells everyone she knows.

What we would actually build

If a Baltimore collision shop called us tomorrow, this is the shape of what we would put in front of them, in the order we would build it.

First, the second total. Every estimating platform can export its line detail, and every line already carries the two facts you need: what the operation is and what it costs. What is missing is a classification layer. We would build a mapping from your platform's operation and part codes onto the eleven categories in COMAR 11.15.34.02B, with the split between parts and labor preserved rather than summed, so the deduction can be computed the way .02C actually describes it instead of the way everyone assumes it works. The output is two numbers and a printable reconciliation showing every deduction and its citation. It is the document you hand an adjuster, and it is the document you keep in case anyone asks a year later.

Second, the inspection carve‑out, because it is the part that moves the answer. When an estimator writes a bumper cover, a grille, a lamp panel or a fender, the system asks one extra question: is this repair required to pass a Maryland safety inspection? Not a free‑text note — a structured flag with a short list of reasons drawn from COMAR 11.14, sharp edges and abnormal protrusions among them, attached to the photograph that shows it. That flag is what moves a line from the deduction column back into the numerator, and it is the difference between a defensible calculation and a guess.

Third, the vehicle record. Certification class from the door jamb label captured at intake alongside the VIN, because bumper height limits, the aftermarket parts subtitle and any number of downstream questions turn on it. Title status and brand history. Whether the car is owner‑retained or carrier‑acquired, since that single fact decides which of four title outcomes applies. This is fifteen minutes of data modeling that no platform in the category has done, because none of them is built around Maryland.

Fourth, the clocks. The ninety‑day registration countdown from §13‑506.1, the two‑inspection sequence from §13‑507, the appointment calendars for the sites your customers can actually reach, and the repair‑receipt package assembled from documents the shop already has. All of it visible on one board so nobody discovers on day eighty‑eight that a registration is about to be suspended.

Fifth — and only fifth — production. Boards, parts status, technician efficiency, cycle time, photo documentation, customer updates. Everybody sells this; some of them sell it well. We would build it last and we would build it thin, and if you already have something that works we would leave it alone and integrate with it.

Notice what is not on that list. We would not rebuild estimating. We would not attempt a parts and labor database. We would not try to replace the DRP connection, and we would tell you to keep paying for all three.

When you should not call us

I would rather lose the work than sell someone a system they do not need, so here is the honest version. There are four situations where custom software is the wrong answer for a collision shop, and I run into all of them.

• You have fewer than four people and one booth. At that size a shop‑management subscription at $179 to $215 a month is not the constraint on your business; the constraint is capacity, and software does not paint cars. Buy the cheap tier and spend the difference on a technician.
• You do 90% DRP volume for a single carrier. The workflow is largely dictated to you, the estimating platform is specified, and the room for original process is genuinely narrow. Build when you have somewhere to put the leverage.
• Your real problem is cycle time and you know it. If parts are arriving late and blueprinting is thin, that is a process and staffing problem wearing a software costume. Fix the process, then automate the fixed process. In that order, always.
• Nobody in the building will own it. Custom software needs one person who cares whether it is right. If the answer to “who is going to look at this every day” is silence, we will build you a beautiful thing that quietly rots, and we have both wasted our money.

If you read that list and thought “that's me,” take the subscription. Genuinely. We will still take your call and tell you which one to buy.

How we work

Fixed price, agreed before we start, and the number does not move because the work turned out to be harder than we thought — that is our problem, not yours. You talk to the people writing the code; there is no account manager between us. You own the source code outright at the end, in your own repository, and you can take it to any developer alive. We do not charge per seat, per estimate, per repair order or per anything else, because the entire argument of this article is that meters are the problem.

We start with a free thirty‑minute call. Bring an estimate export, your last three total‑loss files, and the two most annoying things about your current setup. By the end of it you will know whether we think you should build anything at all. Quite often the answer is no, and we say so on the call rather than at the bottom of a proposal.

Questions we get from body shop owners

What does collision repair software cost a Baltimore body shop in 2026?

It depends entirely on which layer you mean, and the layer you cannot avoid will not tell you. On 21 August 2026 we requested eighteen pricing pages. CCC, Mitchell, Audatex and their parent companies publish no figure: cccis.com/pricing returns a 403, and mitchell.com/collision-repair-shops, enlyte.com/pricing, audatex.com/pricing and solera.com/pricing all return 404. Rome Technologies, Nexsyis and Bodyshop Booster also 404 on their pricing URLs. Web‑Est serves a live page titled “Online Collision Estimating Software Pricing” that promises there is nothing behind the curtain and then contains no number. The general shop‑management platforms that do publish land between roughly $179 and $449 a month: AutoLeap and Tekmetric both at $179, $309 and $409 billed annually, and Shopmonkey at $215, $359 and $449 billed annually with three to five user licenses included and $20 per month for each one beyond that.

How much does the average collision shop pay CCC per year?

CCC will not publish a price, but it is a public company and it has to tell its investors. Its Form 10‑K for the year ended 31 December 2025 reports revenue of $1,057.0 million and states that repair solutions “represented approximately 43% of our 2025 total revenues, with nearly 100% of that representing software revenue.” The same filing says CCC connects with “more than 30,500 repair facilities.” That is about $454.5 million across more than 30,500 shops, or roughly $14,900 per shop per year — on the order of $1,240 a month. It is a crude average across everything from a single‑bay shop to a hundred‑location group and no individual shop should expect a quote at that figure, but it comes from the vendor's own securities filing, which is more than any aggregator can offer.

What is Maryland's total loss threshold?

Md. Code, Transportation Article, §11‑152(a)(1) defines a salvage vehicle as one damaged to the extent that “the cost to repair the vehicle for legal operation on a highway exceeds 75% of the fair market value of the vehicle prior to sustaining the damage.” The phrase that matters is for legal operation on a highway, which is not the same as the cost of the repair. §13‑506(c)(4) then says that in determining that cost, a person may not use the cost of towing, storage or vehicle rental, or the cost of repairing cosmetic damage. Maryland's 75% test therefore runs on a smaller number than the total at the bottom of your estimate, and on the worked example in this article the gap is $2,472.56.

What counts as cosmetic damage in Maryland's salvage calculation?

COMAR 11.15.34.02B lists eleven categories: refinishing labor and materials; external trim molding and fascia; molded non‑metal bumper covers; grilles; entertainment systems; audiovisual, telephone and mapping equipment; emblems, stripes and decals; hubcaps and wheel covers; interior carpet; upholstery excluding the driver seat; and interior door trim panels. Two details do most of the work. Regulation .02C says that except for refinishing, the cost of a cosmetic repair includes only parts and materials and may not include labor — so a bumper cover's part price comes out of the calculation while the labor to fit it stays in. And regulation .02A says cosmetic damage does not include any repair required to enable the vehicle to pass a safety inspection under COMAR 11.14, so the same part moves in and out of the calculation depending on how it is broken.

Does Maryland's aftermarket crash parts law apply to SUVs and pickups?

Often it does not, and this surprises almost every shop we show it to. Commercial Law §14‑2302 requires a body shop to list replacement crash parts before work begins, say whether they are genuine, and attach a prescribed statement in 10 point capital type if they are aftermarket. But §14‑2301(f) defines “motor vehicle” in that subtitle as a passenger car under Transportation §11‑144.2, and §11‑144.2 defines a passenger car as a motor vehicle “except a multipurpose passenger vehicle or motorcycle.” Most crossovers and SUVs are certified as multipurpose passenger vehicles and register in Maryland as Class M under §13‑937. The same subtitle defines crash parts as “sheet metal or fiberglass” panels, a materials list written before aluminum bodies and molded thermoplastic covers were normal. Give the disclosure on everything anyway — it costs nothing and your counsel may read this differently — but check the certification label in the door jamb before you assume which rules you are under.

Can a car be salvage in Maryland even if the damage is under 75%?

Yes. §11‑152(a)(2) makes a vehicle salvage if it “has been acquired by an insurance company as a result of a claim settlement,” with no damage threshold attached. §13‑506(c)(2)(ii)5 covers exactly that case — the insurer certifies acquisition and a repair cost of 75% or less — and §13‑507(b)(4) then produces a title carrying a conspicuous “X‑Salvage” notation. The arithmetic route and the ownership route are independent. And §11‑152(b) runs the other way: a vehicle has not been acquired by an insurance company if the owner retains possession on settlement, so an owner‑retained car under the threshold is not salvage at all.

Where does a rebuilt salvage vehicle get inspected near Baltimore?

Not in Baltimore. §13‑507(a)(2) requires two separate inspections before a salvage certificate becomes a title: a certificate of inspection from a county police department or the Department of State Police, plus a Title 23 safety inspection. The State Police run the salvage certification inspection by appointment at seven sites — Beltsville, Frederick, Hagerstown, La Plata, Perryville, Salisbury and the Finzel weigh station in Garrett County — and none is in Baltimore City or Baltimore County. The fee is $75 and the vehicle must arrive with valid ID, the salvage certificate, proof of ownership, the appointment confirmation and the repair receipts. Where the VIN plate is missing or damaged, the inspection is done by the Auto Theft Unit at the Glen Burnie site on Tuesdays from 8:30 a.m. to 12:30 p.m. — four hours a week, statewide.

Is custom software cheaper than a collision platform subscription?

Not usually, and we will say so plainly: keep renting your estimating platform. Insurers require it, the parts and labor database behind it is worth what it costs, and rebuilding that would be foolish. The honest comparison is narrower than replacement. Our Operations System is $12,000 once and you own the source code, and the work we would give it is the work the platform is not designed to do: deriving Maryland's §11‑152 figure from your own estimate line by line, holding the ninety‑day registration clock, sequencing two inspections at sites forty miles away, and carrying the certification class of every vehicle in the building. A shop writing sixty estimates a month that misreads two or three total losses a year has already paid for it.

This article describes Maryland law and regulation as we read it in August 2026 and is not legal, regulatory or insurance advice. Md. Code, Transportation Article §§11‑144.2, 11‑152, 13‑506, 13‑506.1, 13‑507 and 13‑937; Commercial Law Article, Title 14, Subtitle 23; COMAR 11.15.34; and COMAR 11.14 all change, and the reading of COMAR 11.15.34.02C that keeps labor on cosmetic parts inside the calculation is our reading of the text rather than a published agency position. The worked estimate is illustrative and uses assumed Baltimore‑market labor rates and part prices; run your own numbers on your own file. Whether any particular vehicle is a passenger car or a multipurpose passenger vehicle is determined by the manufacturer's certification and is not something to infer from body style. Establishment data is County Business Patterns 2023 (NAICS 811121 and 811111) and counts only establishments with paid employees; the Maryland totals include establishments the Census Bureau reports statewide without allocating them to a county. CCC figures are taken from CCC Intelligent Solutions Holdings Inc.'s Form 10‑K for the year ended 31 December 2025, and the per‑facility figure is our arithmetic, not the company's. Vendor pricing pages were requested on 21 August 2026 and change without notice; where a vendor published no figure we have said so rather than quoting an aggregator. Salvage inspection sites, hours and fees are published by the Maryland Department of State Police and change — confirm before you send a customer anywhere. Verify your own position with the Motor Vehicle Administration, the Maryland Insurance Administration, the Department of State Police or your own advisers before relying on anything here.