⚡️ Milestone: Crossed 11,600+ verified vehicle records with our July 2026 off-road update!
Selling a database isn't a "build once and forget" business. Automotive wheel fitment specs evolve rapidly, and e-commerce store owners rely on accurate data to prevent costly wheel return shipping.
Today, we just rolled out our July 2026 dataset update, expanding BoltPatternHQ to 11,601 standardized records covering 1992–2026 across 66 makes and 1,461 models!
🔥 What's new in this release:
• Added complete, verified off-road fitment specs for Suzuki Jimny & Jimny Sierra (1998–2026).
• Standardized unique off-road parameters, including large center bores (108.1mm) and zero/negative ET offsets crucial for 4x4 wheel shops.
• Updated our automated Python CSV export pipeline, ensuring 100% UTF-8 cleanliness and standardized column mappings (PCD, Center Bore, Offset, Lug Nuts, Trim/Body Styles).
You can test our 0ms fuzzy search live at https://boltpatternhq.com/, or grab the Free 50-Row Sample / Complete CSV Database directly at https://boltpatternhq.com/data/!
Let us know if there are specific JDM or Euro makes you'd like us to prioritize next! 🚗💨
The interesting part here is that the product isn't just a dataset — it's maintaining trust in data accuracy over time.
Curious what signal tells you which vehicle updates are worth prioritizing: customer requests, search demand, or gaps you find internally?
You nailed it — the real value isn't just the CSV file itself, but the ongoing trust that the numbers are 100% verified and up to date!
To answer your question: it is actually a hybrid of all three signals, but weighted in a specific order:
Search Demand & On-Site Query Logs (The Fastest Signal): Since we run a 0ms client-side search engine, we keep a close eye on search queries that return zero results or high impression spikes in our Google Search Console. For instance, last month we noticed a sudden spike in queries for hardcore off-road and JDM (Japanese Domestic Market) vehicles. That was our direct trigger to prioritize and release our July 2026 update, adding 58 comprehensive model-year records for the Suzuki Jimny and Jimny Sierra (1998–2026).
Customer Requests (The Highest Converting Signal): When B2B buyers (like wheel e-commerce store owners or car exporters) grab our $29 lifetime package, they often email us asking: "Hey, do you have the exact center bore specs for incoming 2026 EV models?" When a paying customer asks for a specific make, it jumps to the absolute top of our internal roadmap.
Internal Gaps (The Foundation): Whenever an automotive manufacturer announces a mid-cycle refresh or platform redesign (where they often sneakily change center bores or transition from 4-lug to 5-lug setups), our internal script flags the gap so we can verify OEM service manuals and patch it before aftermarket shops even notice.
How do you usually prioritize your product roadmap when balancing user requests vs. internal data gaps? Would love to hear your thoughts!
Really appreciate you taking the time to share that. I'd enjoy continuing the conversation outside the thread if you're open to it—what's the best email to reach you on?
Sure thing, @Aryan! Always happy to connect and chat with fellow makers.
You can reach me directly at hello@boltpatternhq.com.
Looking forward to continuing the conversation!
Thanks! I’ve just sent it over.
Looking forward to hearing your thoughts whenever you have a chance.
“Very practical use case. Curious — are most users coming for one lookup, or does this turn into a repeat workflow?”
Thanks! It's actually a mix of both, and that’s pretty much why we structured the business model this way.
We see two main groups. The first is the one-off lookups, mostly individual car owners or DIY enthusiasts coming in from Google search. They just want to check the PCD or offset for their specific trim before buying aftermarket wheels, get the answer instantly, and leave.
Then there's the second group, which is where the repeat workflow comes in. These are workshop mechanics, fitment specialists, and shopify or woocommerce store owners who need these specs every single day. For them, looking up cars one by one on the web is a bottleneck and monthly enterprise APIs are usually overkill. That is why we decided to package all 11,600+ records into a simple $29 one-time buy CSV dataset so they can just import it directly into their own store DBs or parts-lookup widgets and automate their workflow.
This is a really clean split — and the $29 dataset for power users makes a lot of sense.
What’s interesting here: your repeat users already have a workflow dependency, which is gold.
In similar cases, we’ve seen strong upside in turning that into a ‘default tool’ rather than a one-time asset (even lightweight updates, integrations, etc.).
Curious if any of those users are asking for ongoing access vs static data yet
You hit the nail on the head, @Alfie! "Workflow dependency" is exactly the dream here.
To be completely transparent, we are still in the very early stages. We’ve only made our very first sale so far! That first customer bought the static CSV and hasn't come back asking for ongoing access or an API yet.
Because wheel specs for legacy car models don't really change, the one-time static dataset solves their immediate pain perfectly. However, your point is incredibly validating. As new car models are released every year, shifting from a one-time static asset to a lightweight API or a recurring "data update" model is absolutely the natural evolution we want to aim for.
Right now, we are focused on grinding out those next 10 sales, but I'm definitely keeping that 'default tool' integration strategy in mind for the future. Thanks for the brilliant insight!