The product catalog intelligence system for aftermarket teams.

Purpose-built for analyzing, planning, and monitoring your product catalog. Designed for the AI era.

Now reading · Fitment 4.2 · Vehicle universe 2026.04v0.6
wrench / coverage / ACME-2026-Q2 Live
Population coverageQ2 · 26
67.4%
Catalog: ACME-2026-Q2+2.1 wk/wk
Population in gap
14.7M
Worst category
Brake hardware
21.8% covered
Open gaps
2,318
New this run
+47
Revenue gap surfaced
$4.2M
9 runs · trend+16.2pp YoY
Catalogs read so far .
Tier-1 Brake Co.Northstar FiltrationRIDGEPOINTAnvil HardwareMercer PerformanceSAGA · MOTORSHalberd OE
§ The pitch .

See what your catalog is missing.

Wrench reads your fitment file against the vehicle universe, categorization schema, and live vehicle population — then tells you, by part type and by platform, exactly where coverage ends and revenue begins.

Dashboard
Brake Pads coverage overview
Applications
142,847
Part Numbers
18,392
Mapped PNs
18,392
Makes
24
Mapped
104,632
Opportunity
38,215
Overall Coverage
73.2% mapped26.8% opportunity
Top Makes by Applications
Toyota
Ford
Chevrolet
Honda
Nissan
Hyundai
BMW
Subaru
Mapped vs Opportunity
73%
Distribution by Position
Front
Rear
Front Left
Front Right
Rear Left
Rear Right
Make Summary
MakeAppsOpportunityCoverage
Toyota18,4234,321
76.5%
Honda14,8912,244
84.9%
Ford16,2044,221
73.9%
Chevrolet15,1123,778
75%
Nissan10,8472,713
75%

Wrench dashboard showing coverage analysis for a brake pads catalog. 142,847 applications across 24 makes.

The Engine

Everything connected. Nothing missed.

Wrench brings together the data sources that matter for aftermarket catalog strategy — so you stop toggling between spreadsheets and start seeing the full picture.

Merge
Identify
Analyze
Evaluate
Cover

One Engine

Founder’s Letter

We built Wrench because we were tired of watching catalog managers drown in spreadsheets.

Here's what we kept seeing: smart people at parts manufacturers spending weeks manually cross-referencing fitment files against the vehicle universe, trying to figure out which make-model-years they're missing. Then opening another spreadsheet to look up vehicle population data. Then another to check Manufacturer Data. Then trying to present it all to leadership in a way that justifies the engineering investment.

That process is insane. Not because the people doing it aren't capable they absolutely are. It's insane because the data already exists. It just isn't connected.

Wrench connects it. Your fitment catalog, the vehicle universe, vehicle population data, and Manufacturer Data all in one place, analyzed across 19 purpose-built dashboards. Coverage analysis. Gap identification. Market sizing. EV readiness. Reproducible runs.

We didn't try to build the everything-platform. We built the one tool that catalog managers and product strategists actually need: clear answers about where your catalog stands and where it should go next.

It's opinionated software. It does one thing well. If you're looking for a general-purpose BI tool, this isn't it. If you're looking for the fastest way to understand your aftermarket catalog coverage, we think you'll like it.

See your entire catalog at a glance.

Wrench parses your fitment file and immediately shows you coverage across every make, model, and year. A year-by-year heatmap reveals exactly where your catalog is deep and where it thins out. You stop guessing. You see the shape of your coverage for the first time.

  • Instant heatmap across make-year combinations
  • Coverage percentage across every position
  • Drill down from overview to individual part numbers
Coverage Heatmap — Part Numbers by Make × Year
Make151617181920212223242526
Toyota
42
45
48
51
54
52
49
46
38
30
18
6
Honda
38
40
42
44
46
45
43
40
35
28
15
4
Ford
35
38
40
43
48
50
47
44
36
24
12
3
Chevrolet
30
33
35
38
42
44
41
38
30
20
10
2
Nissan
25
28
30
32
34
33
30
26
20
14
8
Hyundai
18
20
22
25
28
30
28
24
18
12
5
BMW
15
16
18
20
22
21
19
16
12
8
3
Subaru
12
14
15
16
18
18
16
14
10
6
2

Every gap is a revenue opportunity.

Catalog holes. Carryup gaps. Manufacturer Data gaps. Wrench identifies them all and tells you exactly which make-model-years are affected. Export the list. Hand it to engineering. Stop waiting for customers to tell you what's missing.

  • Seven-plus views: holes, gaps, carryup, manufacturer-data research, catalog-vs-manufacturer, part-type, matrix
  • Catalog Health funnel ties research → match → cover → fit → demand in one screen
  • One-click export to CSV for engineering handoff
Opportunities by Make
Ford
4,221
Toyota
4,189
Chevrolet
3,778
Nissan
2,713
Honda
2,244
Hyundai
1,892
BMW
1,456
Subaru
Top Opportunities
MakeModelYearsPos.
FordF-1502022–2026Front
ToyotaRAV42023–2026Rear
ChevroletSilverado 15002024–2026Front
NissanRogue2023–2026Front
HondaCR-V2024–2026Rear

Size the opportunity. Prepare for what's next.

Overlay vehicle population data to size your total addressable market by actual vehicles on the road. The Sweet Spot analysis finds the intersection of high-volume vehicles and catalog gaps — your highest-ROI expansion targets.

  • Total addressable market sized by real vehicle population data
  • Sweet Spot analysis for highest-ROI expansion targets
  • EV readiness across ICE, hybrid, PHEV, and BEV segments
Total vehicle population
178,873,043
Population covered
156,914,636
Population gap
21,958,407
Coverage %
87.7%
Coverage by Fuel Type
ICE91.2%
148.2M vehicles
Hybrid78.4%
18.6M vehicles
PHEV62.1%
7.8M vehicles
BEV34.8%
4.3M vehicles

Numbers that don't drift between meetings.

Wrench freezes each report run against pinned vehicle universe and categorization schema versions, so last quarter's coverage number still means what it meant last quarter. Compare any two runs side-by-side or as a structured delta, and watch the metrics you care about move over time.

  • Frozen report runs — pinned vehicle universe / categorization schema versions so numbers don't drift
  • Side-by-side and delta comparison between any two runs
  • Metric trends over time — coverage %, TAM coverage, gap revenue
Coverage % — Last 9 Runs
CompareQ1·26 vs Q2·26
First run
71.2%
Q2 2024
Latest run
87.4%
Q2 2026
Δ Coverage
+16.2pp
9 runs
Q2·24Q3·24Q4·24Q1·25Q2·25Q3·25Q4·25Q1·26Q2·26
§ 04Built for the work
Three views you’ll live in .

Not a dashboard. A daily ritual.

Wrench is opinionated about what catalog managers, strategists, and channel teams actually do every Tuesday morning. Each of these views earned its place by being used.

Pinned · 2026 Q1.
ACME-2026-Q1
vs.
Live · 2026 Q2.
ACME-2026-Q2
Category
Q1 %
Q2 %
Δ
Brake pads
90.2
92.0
+1.8
Filters
86.1
88.4
+2.3
Rotors
74.4
74.1
−0.3
Sensors
48.6
52.0
+3.4
Wipers
42.1
34.6
−7.5
Hardware
24.0
21.8
−2.2
4 categories closed2 categories regressed →
A · Diff .

What changed since you signed it.

Pin a Coverage snapshot at the end of every quarter. Wrench keeps it forever. The next time you open the catalog, the very first surface is a diff: what closed, what opened, where new launches actually moved coverage versus where they shifted it sideways.

  • Snapshots are immutable — same files, same numbers, every time.
  • Sage means closed. Vermillion means new gap.
  • Diff a release against three quarters back, not just one.
Gap drilldown.

Brake hardware · 2024 Silverado 1500

Over-claimed
Population weight
1.84M
$ at risk
$1.8M
Resolved rows
6 / 6
Implicit axes
Drive · Cab
Model
Trim
Engine
Drive
Cab
Pop ·k
Silverado 1500
LT
5.3L V8
4WD
Crew
17.2
Silverado 1500
LTZ
6.2L V8
4WD
Crew
11.8
Silverado 1500
WT
2.7L L4 Turbo
4WD
Double
8.4
Silverado 1500
High Country
3.0L Duramax
4WD
Crew
6.1
Silverado 1500
Custom
5.3L V8
RWD
Crew
4.7
Silverado 1500
ZR2
6.2L V8
4WD
Crew
3.2
App row · part #BH-44829-AOpen the App XML →
B · Drilldown .

Every gap, resolved to its rows.

A gap isn't a category. It's the six configurations of a 2024 Silverado that your over-claimed App swept under “BaseVehicle.” Wrench shows you the rows the receiver will see — not the rows you wrote.

  • Surfaces the implicit wildcards your file is making.
  • Flags only when PartType demands the axis and the BaseVehicle varies on it.
  • Vehicle population weight on every row — the rows that matter rise to the top.
diff cov|⌘K
Run coverage diff
Q1 → Q2 · ACME
Pin current view
commit · sign · immutable
⌘P
Run TAM report
Brake hardware · all platforms
Open over-claim audit
PartType demands axis
⌘O
Compare release
Catalog v4.1 → v4.2
⌘D
↑↓ move↵ runesc close11 commands
C · Command .

Run the report from the keyboard.

Eleven reports, one keystroke. ⌘K opens the bar. Type “diff”, “tam”, “ev split” — the same words your engineers paste in Slack. Power-users live here. Everyone else still works in the UI.

  • Every report has a deterministic command — paste it in chat, get the same artifact.
  • Schedule any command. Pinned snapshots arrive at 9am Monday.
  • Keyboard-first, but never keyboard-only.
§ 05From file to insight
Eleven minutes, median .

Four steps. No batch jobs.

Most analytics tools are a queue. Wrench is a stream — the parser starts the moment you drop the file, the first metric resolves before you’ve finished sipping your coffee.

§ 01
Drop the file
Fitment XML or zipped batch. The parser streams from byte one — no batch queue.
§ 02
Resolve
Every fitment claim expanded against vehicle junctions. Implicit wildcards counted as wildcards.
§ 03
Pin
Sign the snapshot. Immutable from this moment, citable in the next quarterly.
§ 04
Diff
Next release, the system tells you what closed, what opened, what shifted sideways.
§ 06By the numbers
Methodology, in measure .

Numbers that don’t drift between meetings.

Every metric you see is reproducible from the source files. Snapshots are immutable; the same selection of fitment, vehicle universe, categorization schema, and vehicle population data will compute to the same result, every time, forever.

Median time-to-insight
11min
From file selection to first pinned Coverage snapshot.
Largest catalog parsed
2.4M apps
Single-tenant, in-memory, no batch wait.
Sources resolved per app
5
Fitment · Vehicle universe · Categorization · Vehicle population · Manufacturer Data. All version-pinned.
Avg revenue gap surfaced
$3.8M
Across the first ten enterprise pilot accounts, Q1 2026.
§ Field note · Q1 2026 .
It’s the first tool that talks about catalog the way the CFO talks about catalog. Six weeks of spreadsheet ritual collapsed into a Tuesday afternoon.
Jordan ReyesVP Catalog · Northstar Filtration
FAQ

Questions people actually ask

What data formats do you support?

Wrench ingests standard fitment XML files. We also connect to the vehicle universe, vehicle population data, and Manufacturer Data sources. If your catalog conforms to industry fitment standards, it works.

How long does it take to get up and running?

Import your fitment file, connect your data sources, and you'll have 19 dashboards populated in minutes. There's no multi-week implementation. No consultants required.

Who is this built for?

Catalog managers, product strategists, and anyone responsible for aftermarket coverage decisions at parts manufacturers. If you spend time wondering which make-model-years you're missing, this is for you.

How is this different from doing analysis in Excel or Power BI?

Those are general-purpose tools. Wrench understands fitment data structure natively — it knows what catalog holes, carryup gaps, and Manufacturer Data gaps are. You don't have to build the analysis framework. It's already there.

What does the EV readiness analysis actually show me?

Coverage broken down by fuel type: ICE, hybrid, PHEV, and BEV. You'll see your coverage percentage for each segment and a ranked list of EV-specific gaps by vehicle population volume. It answers: am I ready for the vehicles people are buying now?

Is my data secure?

Your catalog data stays in your environment. Wrench runs locally against your data — we don't store your fitment files or catalog data on shared infrastructure.

Can I export the gap lists?

Yes. Every gap report exports to CSV. Hand the list directly to your engineering team.

Can I compare this quarter's catalog to last quarter's?

Yes. Every report run pins the vehicle universe and categorization schema versions it was generated against, so the numbers don't drift. Pick any two runs and Wrench shows them side-by-side or as a structured delta — coverage point changes, new gaps, closed gaps, revenue shifts. The Trends view plots the metrics you care about (coverage %, TAM coverage, gap revenue) across all of your runs.

Can I narrow analysis to just the makes/models/years I sell into?

Yes. Research Scope lets you define tiers, assign part types to them, and cap by cumulative vehicle population %. Every downstream report — coverage, gaps, TAM, sweet spot — respects the scope. Import and export your scope definitions as CSV to keep teams aligned.

Do I have to upload my files to your servers?

No. Wrench runs locally against your data. For one-off analyses, Parc is a fully in-browser analyzer — drop in a fitment XML and a vehicle population CSV and it generates a complete coverage, market, and EV-readiness report without anything leaving your machine.

Bring your catalog. .

Stop guessing
where your gaps are.

Twenty minutes with one of our engineers, your fitment file, and a fresh vehicle population snapshot. You’ll leave with the three numbers your next quarterly is missing.

SOC 2 · Single-tenant · Customer data never trains a model.
Get a demo →Open the sample report
No login · No credit card