Blog

How to Set Up a Vehicle Damage Pricing Catalog

Build a vehicle damage pricing catalog that enforces consistent charges across your fleet and learn how operators recover 94% of damage revenue by automating it.

Vehicle damage pricing catalog for fleet operators

Vehicle damage pricing catalog: enforcing consistent charges at every return

A poorly structured pricing catalog is the most common reason fleet operators fail to recover damage revenue. According to Ravin AI's 2024 fleet damage analysis, only about 10% of vehicle returns with damage result in a full cost recovery, and inconsistent pricing is a leading cause. This guide walks you through building a catalog that works, and shows you how to automate enforcement so charges go out every time, without manual follow-up.

Key Takeaways

  • A vehicle damage pricing catalog defines the exact charge for every damage type, zone, and severity, removing guesswork from your billing process.
  • Without a structured catalog, operators leave significant revenue uncollected on every return cycle.
  • A working catalog has five components: damage type taxonomy, zone mapping, severity tiers, pricing per line item, and exception rules.
  • You can build a functional catalog in a spreadsheet, then connect it to an automated billing API to eliminate manual billing entirely.

What Is a Vehicle Damage Pricing Catalog?

A vehicle damage pricing catalog is a structured reference table that assigns a specific charge, or a cost calculation method, to every type of vehicle damage your fleet might encounter. It is the foundation of any consistent damage recovery workflow.

Without one, your team makes pricing decisions ad hoc. One agent charges €150 for a bumper scuff. Another charges €80 for the same damage two weeks later. A renter disputes both. You settle for half. Revenue walks out the door on every cycle.

According to a February 2026 analysis of 1,710 rental car damage claims by CarInsuRent, the average damage claim costs €1,169, with wheel and rim damage averaging €1,315 (CarInsuRent, "Rental Car Damage Claims Analysis 2025," February 2026). Inconsistent pricing means you're likely collecting far less than that on most incidents.

A vehicle damage pricing catalog is a structured table that assigns defined repair costs or pricing formulas to each damage type, body zone, and severity level. Operators that enforce a standardised catalog eliminate per-agent pricing variation and reduce chargeback rates. According to CarInsuRent's 2026 analysis of 1,710 claims, the average rental damage event costs €1,169. Consistent catalog enforcement is the primary lever for recovering that revenue.


What Are the Five Components of an Effective Catalog?

A functional pricing catalog has five distinct layers. Miss one, and you'll face pricing disputes you can't resolve with data.

1. Damage type taxonomy

Start by listing every damage category your fleet encounters. At minimum, this covers: scratches, dents, paint chips, cracks (glass and bodywork), tears (upholstery and soft trim), burns, stains, wheel and rim damage, missing parts, and structural damage. Each type needs its own entry because repair costs differ significantly. A paint chip costs far less to fix than a structural dent, even in the same body zone.

2. Vehicle zone mapping

Divide the vehicle into named zones: front bumper, rear bumper, driver-side doors (front and rear), passenger-side doors (front and rear), bonnet, roof, boot lid, windscreen, rear screen, side windows, wheels (per corner), interior (per subsection). Zone mapping lets you price by location, not just damage type. A scratch on the roof costs more to repair than the same scratch on the lower door sill.

3. Severity tiers

Each damage type needs at least three severity levels: minor (S1), moderate (S2), and major (S3). Define these with objective criteria. For example:

  • S1 scratch: less than 5 cm, paint only, no primer exposure
  • S2 scratch: 5 to 20 cm, or primer exposed, no metal visible
  • S3 scratch: metal visible, or longer than 20 cm, or across a panel join

Severity definitions remove the most common source of disputes. When your catalog defines "minor" with a measurement, a renter can't argue that a 3 cm scratch "barely counts."

4. Pricing per line item

For each combination of damage type + zone + severity, assign one of three pricing methods:

Method When to use Example
Fixed charge Standard repairs with predictable cost S1 bumper scratch: €120
Range + inspection note Variable repairs requiring assessment S2 door dent: €200 to €450 pending assessment
Audatex/Mitchell reference Major or total-loss damage S3 structural: Audatex quote required

Fixed charges work best for 70 to 80% of your catalog entries. They're fast to apply, easy to defend in disputes, and can be fully automated. Reserve "requires assessment" only for damage where repair complexity genuinely varies.

5. Exception rules

Define upfront what your catalog does and doesn't cover. Common exceptions:

  • Pre-existing damage documented in the check-out report (excluded from charges)
  • Normal wear and tear thresholds (e.g., tyres under 3 mm tread do not trigger a charge)
  • Fleet age rules (older vehicles may have adjusted pricing)
  • Damage below your minimum billing threshold (e.g., no charge for S1 paint chips under 2 mm diameter)

Exception rules are the difference between a catalog your team applies consistently and one they ignore because edge cases keep creating arguments.

An effective vehicle damage pricing catalog requires five components: a damage type taxonomy, a vehicle zone map, severity tier definitions with objective criteria, per-line-item pricing using fixed charges or cost calculation references, and documented exception rules. Operators who define severity with measurable thresholds (e.g., scratch length in centimetres) report significantly fewer billing disputes, as the damage record itself resolves the disagreement.


How Do You Structure Pricing to Survive Disputes?

Dispute resistance is the practical test of any pricing catalog. According to CarInsuRent's 2026 claims study, 58% of rental car damage claims in 2025 were ultimately not caused by the renter, meaning most disputes involve genuine attribution uncertainty, not bad-faith contestation (CarInsuRent, "Rental Car Damage Claims Analysis 2025," February 2026). Your catalog won't resolve attribution disputes, but it will resolve pricing disputes, which are entirely within your control.

Three practices make your catalog dispute-resistant:

Tie every fixed charge to a labour rate. Charges that feel arbitrary get challenged. Charges derived from a published labour rate (e.g., €85/hour × 1.5 hours = €127.50) are defensible because you can show the math. Document your labour rate assumption once per year and attach it to your catalog.

Reference Audatex or Mitchell for non-standard repairs. For S3 damage, your insurance and legal teams will expect a third-party cost estimate. Reference one explicitly in your catalog so there's no ambiguity about how major damage is priced.

Version-control your catalog. Date every change. If a renter disputes a charge using pricing from your previous catalog, you need a record showing which version was in force at the time of their rental. A simple version number and effective date on the spreadsheet is sufficient.

What does this mean for a fleet of 200 vehicles? If you process 800 returns per month and 10% show damage, that's 80 damage events. At an average recoverable charge of €400 each, a dispute-resistant catalog protects €32,000/month in potential revenue.


What Should Your Catalog Template Include?

Here is a working template structure you can copy directly into a spreadsheet:

Main pricing table columns:

Damage ID Damage Type Body Zone Severity Tier Severity Definition Fixed Charge (€) Pricing Method Notes
SCR-FR-S1 Scratch Front bumper S1 (minor) < 5 cm, paint only 120 Fixed
SCR-FR-S2 Scratch Front bumper S2 (moderate) 5 to 20 cm, no metal 280 Fixed
SCR-FR-S3 Scratch Front bumper S3 (major) Metal visible TBD Audatex quote
DNT-DR-S1 Dent Driver door (front) S1 (minor) < 3 cm, no paint break 160 Fixed PDR eligible
DNT-DR-S2 Dent Driver door (front) S2 (moderate) 3 to 8 cm, or paint break 350 Fixed
DNT-DR-S3 Dent Driver door (front) S3 (major) > 8 cm, or crease TBD Audatex quote
GLS-WS-S1 Chip Windscreen S1 (minor) < 2 cm, outside driver line of sight 85 Fixed Repair only
GLS-WS-S2 Crack Windscreen S2 (moderate) Any crack 420 Fixed Full replacement
WHL-FL-S1 Kerb scrape Front-left wheel S1 (minor) < 30% circumference affected 195 Fixed
WHL-FL-S2 Kerb damage Front-left wheel S2 (moderate) Structural damage or > 30% TBD Audatex quote
INT-ST-S1 Stain Driver seat S1 (minor) < 10 cm, removable 75 Fixed Detail cleaning
INT-ST-S2 Stain Driver seat S2 (moderate) > 10 cm, or permanent 220 Fixed Seat cover replacement
INT-BN-S3 Burn Any interior surface S3 (major) Any burn mark 380 Fixed
MSS-PT-S3 Missing part Any S3 (major) Part absent at return Retail cost + €50 labour Cost-plus

Add a tab for your exception rules and a tab for your version history. That's a complete, dispute-ready catalog in under two hours of setup time.

A vehicle damage pricing catalog template should include a versioned header (version number, effective date, labour rate), a main pricing table with columns for damage ID, type, zone, severity tier, severity definition, pricing method, and fixed charge or cost reference. Separate tabs for exception rules and version history make the catalog audit-ready for dispute resolution. Operators can build a functional 80-item catalog covering all standard damage events in approximately two hours.


How Do You Connect a Catalog to Automated Billing?

A spreadsheet catalog is a starting point, not a destination. The real revenue recovery comes when your catalog is connected to your damage detection and invoicing system, so charges apply automatically, every time, without a staff member manually reviewing each case.

Spectiv's platform works by connecting three systems: computer vision damage detection at vehicle return, pricing catalog enforcement (your catalog, digitised), and invoice generation via API. When a renter returns a vehicle, the detection layer logs every damage event with a photo, zone, and severity score. The catalog layer matches each event to the correct line item. The billing layer generates and sends the invoice. The process takes 60 seconds from return to invoice, compared to the industry standard of 3+ days for manual processing. Spectiv operators report a 94% damage charge recovery rate and 96% reduction in per-return operational costs (self-reported, based on operator deployments).

What does this mean in practice? An operator running 500 returns per month, recovering €300 average per damage event at a 10% damage rate, adds €15,000/month in recovered revenue, without adding headcount.


Frequently Asked Questions

01

How many line items should a vehicle damage pricing catalog have?

A functional catalog for a standard car sharing or car rental fleet typically has 80 to 150 line items, covering the most common damage types across all body zones at three severity levels. You don't need to document every possible edge case upfront. Start with the 20 damage types you see most often, cover all three severity tiers for each, and expand the catalog from there as you encounter new damage patterns.

02

How often should you update your pricing catalog?

Update your catalog at minimum once per year to reflect changes in repair labour rates and parts costs. If you're in a market where labour rates have shifted significantly (labour costs in the EU increased 4.2% in 2025 according to Eurostat), a mid-year update is worthwhile. Version every change with a date so historic charges remain defensible.

03

Can you use the same catalog across different vehicle classes?

You can use one master catalog with vehicle-class modifiers. A dent on a premium SUV costs more to repair than the same dent on a compact car, partly because paint matching is more complex and partly because labour time differs. A common approach is to create one base catalog and apply a multiplier per vehicle class (e.g., 1.0× for compact, 1.3× for SUV, 1.6× for premium). Spectiv's catalog engine supports per-vehicle-class pricing natively.

04

What's the difference between a pricing catalog and a damage waiver?

A pricing catalog defines what you charge for each damage event. A damage waiver (CDW/LDW) is a product you sell renters to reduce or eliminate their liability for those charges. They're separate tools. Your catalog defines the underlying charge; the waiver determines how much of that charge the renter actually pays. Operators with clear catalogs find it easier to price waivers accurately because they have real cost data behind each line item.

05

How do you handle pre-existing damage in your pricing catalog?

Pre-existing damage should be excluded at the catalog level by design. The catalog charges for damage, not for damage that existed before the rental. The critical workflow is documentation: your check-out report (photo or video evidence of vehicle condition before the rental) is what protects you from charging for pre-existing damage. Your catalog should reference your check-out documentation standard explicitly, and your billing system should link every charge to a comparative photo pair (check-out vs. check-in).

Let AI run your fleet with you.

Book a Demo