If you sell wheels online, your entire business runs on one question the customer is silently asking on every page: will this fit my car? Get the answer right and you win the sale. Get it wrong and you eat a return, a chargeback, a one-star review, and the freight both ways on a heavy, awkward product that nobody wants to ship twice.
That single question is why the wheel and rim category has its own ecosystem of data tools — and why so many resellers end up confused about which ones they actually need. People throw around terms like “Hollander,” “ACES and PIES,” and “fitment API” as if they’re interchangeable. They’re not. They solve completely different problems, they cost wildly different amounts, and picking the wrong one can mean paying for capability you’ll never use or, worse, building your store on data that can’t grow with you.
This guide sorts it out. We’ll cover what each tool actually does, which type of reseller needs which, where the real flexibility lives, and — the part everyone wants and nobody publishes clearly — what it all costs.
Start Here: The Fork That Decides Everything
Before you evaluate a single tool, answer one question: are you selling OEM wheels or aftermarket wheels? This is the fork in the road, and almost every tooling decision flows from it.
OEM (Original Equipment Manufacturer) wheels are factory-original rims — the wheels that came on the car from the dealer. Resellers in this lane are often working with used takeoffs, reconditioned factory wheels, or new-old-stock OEM replacements. A customer with a curbed rim on their 2019 Accord wants the same wheel that car came with. The job is identification and exact replacement.
Aftermarket wheels are everything else — the styled, branded rims from companies that didn’t build your car. A customer here isn’t replacing a damaged factory wheel; they’re upgrading. They want something that looks better, fits a larger tire, or changes the stance. The job is matching specs (bolt pattern, diameter, width, offset, center bore) to a vehicle, then helping the buyer choose among options that all technically fit.
These are different businesses with different data needs. The OEM lane lives and dies on part identification and interchange. The aftermarket lane lives and dies on fitment specifications and visualization. A lot of resellers do both, which is fine — but you need to know which tool serves which side, because no single product does it all well.
The Tools, in Plain English
There are really four jobs to be done in wheel commerce data, and the well-known tools each specialize in one or two of them: identifying a wheel, cross-referencing it to equivalents, describing it as a product, and matching it to a vehicle. Here’s how the major players map.
Hollander Interchange (and WheelSpotter)
The Hollander Interchange is the granddaddy of automotive parts data — a system that’s been around since the 1930s and is the recognized standard in the used and salvage parts world. Here’s the key concept most people get wrong: Hollander is not a list of manufacturer part numbers. It’s a proprietary cross-reference layer built on top of them.
Instead of tracking every factory part number individually, Hollander assigns its own short number to a group of parts that are functionally interchangeable. One Hollander wheel number might map to five or six different OEM factory part numbers across different model years and plants — all the same physical wheel. That’s the magic: it collapses a mess of long, error-prone factory IDs into one short number that everyone in the used-parts trade recognizes. When two parts share a complete Hollander number, they swap with no modification.
Critically for wheel sellers: Hollander covers OEM wheels only. It was built for salvage yards reselling factory takeoffs. If you sell aftermarket rims, it’s largely the wrong tool.
The consumer-facing slice of this data is WheelSpotter, a mobile app that uses the camera, filters, and partial part numbers to identify a wheel’s Hollander number, then surface new/used/remanufactured pricing. It’s a freemium app — you can browse, but unlocking part numbers and pricing requires a paid subscription tier. It’s a fantastic field tool for someone walking a yard or grading inbound inventory, less so a backbone for an eCommerce catalog.
ACES and PIES
This pair confuses everyone, so let’s be precise: ACES and PIES are data standards, not databases. They were created by the Auto Care Association to give the entire aftermarket industry a common language for describing parts and what they fit.
- ACES (Aftermarket Catalog Exchange Standard) handles fitment — what fits what. Year, make, model, engine, drivetrain, the works.
- PIES (Product Information Exchange Standard) handles product information — part numbers, dimensions, weight, descriptions, images, pricing, and compliance details.
Together they’re the format in which fitment and product data gets exchanged between manufacturers, distributors, retailers, and marketplaces. They’re delivered as structured (XML) files, one per brand.
Why does a reseller care? Because if you want to sell on major marketplaces, ACES/PIES compliance is effectively mandatory. Amazon, for instance, wants fitment data either directly from the brand owner or from an approved third-party data provider — and they don’t approve just anyone. If your product feed isn’t ACES/PIES-clean, you risk inaccurate fitment, rejected listings, and the returns that follow. The standard itself rides on underlying databases (the Vehicle Configuration Database, or VCdb, for fitment) that require a paid Auto Care Association subscription to access.
Wheel-Size.com
Where Hollander is built for OEM identification and ACES/PIES is built for marketplace data exchange, Wheel-Size.com is built for the exact moment a shopper lands on a wheel store and needs to know what fits their car. It’s the world’s largest wheel and tire fitment database, and it sells access in three flavors that matter to resellers:
- A free embeddable widget (the Finder v2 is the one most stores start with). You drop a snippet on your site, the customer picks year/make/model/modification, and it returns OE and optional wheel/tire specs — diameter, width, offset, bolt pattern. Free usage requires a small attribution link back to Wheel-Size.com.
- A fitment API (REST, with a free sandbox to test). Instead of displaying a spec sheet, you pull the fitment data programmatically and do whatever you want with it — most importantly, filter your own catalog to show fitting products.
- A Wheel Configurator that renders wheels onto high-quality vehicle images (powered by EVOX) so a customer can see the rims on a car like theirs before buying. For aftermarket sellers, that visual confidence is a genuine conversion lever.
The coverage is deep — tens of thousands of vehicle configurations across 200-plus makes and more than a dozen global regions, with near-complete coverage for vehicles built since 2000.
Which Tools Do You Actually Need?
Now the practical part. Match your business model to the stack.
If you sell used or OEM-replacement wheels: Hollander is your backbone for identification and interchange. WheelSpotter handles the field-grading and pricing side. You’ll still want a fitment layer (Wheel-Size or your own structured data) on the storefront so customers can search by vehicle, but the Hollander number is how you organize inventory and communicate with the trade. This is the salvage-adjacent lane, and Hollander is non-negotiable here.
If you sell aftermarket or custom wheels: Skip Hollander. Your stack is a fitment data source (Wheel-Size.com is the cleanest commercial option) plus disciplined ACES/PIES-quality product data on your own catalog. The fitment finder gets the shopper to the right specs; clean product attributes let you filter to fitting wheels; the configurator helps them commit.
If you sell on marketplaces (Amazon, eBay Motors, Walmart): ACES/PIES isn’t optional. Whatever else you run, your product feed needs to be standards-compliant or your listings will be inaccurate, throttled, or rejected outright. Budget for this regardless of which storefront tooling you choose.
If you do all of the above: You layer them. Hollander for OEM identification, Wheel-Size for storefront fitment and visualization, and ACES/PIES discipline across your product data so it flows cleanly to every channel. They’re complementary, not competing — each owns a different job.
The common mistake is buying the wrong tool for your lane: an aftermarket store licensing Hollander data it can’t use, or an OEM reseller trying to force a generic fitment API to do interchange work it was never designed for.
What Provides the Most Flexibility?
If flexibility is your priority — and for a growing store it should be — the answer is clear: an API-first approach built on clean, structured product data beats everything else.
Here’s the reasoning. A display widget, like the free Wheel-Size Finder you can embed in an afternoon, is fast and cheap, but it’s rigid. It shows the shopper a spec sheet and stops there. It doesn’t know your inventory, it doesn’t filter your catalog, and — importantly for anyone who cares about organic traffic — its output renders client-side in JavaScript, which means search engines see an empty container, not indexable content. A widget is a great starting point and a fine convenience feature. It is not a foundation you can build a serious store on.
The fitment API, by contrast, is raw capability you can point anywhere. The same data can power a “find wheels for your vehicle” garage selector, a “will this fit?” check on every product page, a sitewide catalog filter, marketplace feeds, and server-rendered fitment landing pages that actually rank in search. You’re not locked into one display format dictated by a third party — you decide how the data shows up and what it connects to. That’s flexibility.
But the API is only as flexible as the data on your side of the integration. This is the unglamorous truth: the most flexible tool in your stack is your own clean product data. If every wheel in your catalog is tagged with bolt pattern, center bore, diameter, width, offset, and load rating, then any fitment source can be matched against it, any channel can consume it, and any new feature — filters, configurators, marketplace feeds, SEO pages — becomes a build-on rather than a rebuild. Skip that discipline and even the best API can’t save you, because there’s nothing clean to match to.
Hollander sits at the opposite end of the flexibility spectrum, and that’s by design. It’s essential but narrow: OEM-only, licensed under terms that prohibit reselling or building derivative products from the data, and structured for interchange rather than open repurposing. You license it because it’s the standard for what it does, not because you can bend it to new uses.
So the flexibility ranking, roughly: clean first-party product data > fitment API > ACES/PIES feeds > embeddable widget > licensed interchange data. Each step down trades flexibility for either speed, standardization, or specialization. The trick is knowing which trade you’re making and why.
The SEO Catch: Why a Widget Won’t Rank
This deserves its own section because it trips up so many wheel stores. There is a hard difference between a fitment tool that helps the customer who is already on your page and one that helps customers find your page in the first place — and that difference comes down to where the data renders.
A typical embeddable finder, including the free widget most stores start with, runs entirely in the browser. The customer’s selections fire off JavaScript, the fitment results get drawn into the page after it loads, and the shopper sees their specs. Useful for them. But when a search engine crawls that page, it arrives before any of that JavaScript runs and sees an empty container — no vehicle data, no specs, no products. From Google’s perspective, the page is blank. That’s client-side rendering, and while crawlers have gotten better at executing JavaScript, you should never bet your fitment content’s visibility on it. The content that earns rankings has to be in the HTML when the page is delivered.
That’s server-side rendering (SSR): the fitment data and the matching products are baked into the page’s HTML on the server, before it ever reaches the browser. The shopper still gets an interactive experience, but now the crawler also sees a fully-formed page about “wheels that fit a 2024 Cadillac CT4-V” — complete with specs, fitting products, and the supporting copy that makes it a real landing page.
Why this matters so much for wheels specifically: the highest-intent searches in this category are vehicle-specific. Someone typing “wheels for a 2024 Cadillac CT4-V” is far closer to buying than someone searching “alloy wheels.” A vehicle-by-vehicle fitment page strategy can generate thousands of these targeted, commercial-intent pages — but only if they’re server-rendered. Build them client-side and you’ve created thousands of pages that convert the visitors you already have while contributing almost nothing to the organic traffic that would bring you new ones. Same data, completely different business outcome.
The practical takeaway: use the widget for convenience and speed-to-launch, but if organic search is part of your growth plan, the fitment data needs to reach the page server-side. That’s a larger build than dropping in a snippet — it usually means pulling the data through the API and generating real, indexable pages — and it’s the single biggest lever between a wheel store that ranks and one that doesn’t.
The Cost Factors Nobody Lays Out Clearly
This is where resellers get surprised, because the sticker price is rarely the real cost. Let’s break it into license costs and the hidden costs that usually dwarf them.
License and subscription costs
Hollander doesn’t publish pricing. The full Interchange database is a quote-based B2B license — you contact their sales team, and pricing depends on format (printed, downloadable file, or integrated into a yard management system) and scope. The consumer WheelSpotter app is freemium: free to browse, with paid subscription tiers to unlock part numbers and pricing. Expect the field-tool cost to be modest and the full-database license to be a real line item negotiated for your operation.
ACES/PIES has no license fee for the standards themselves, but the underlying databases do. Access to the Vehicle Configuration Database for fitment requires a paid Auto Care Association subscription, and many sellers also pay a product information management (PIM) tool or a data service to ingest, validate, and syndicate their feeds. The standard is “free”; using it correctly is not.
Wheel-Size.com uses a tiered, annually billed model. The embeddable widget is free for standard use as long as you keep the required attribution link. The API bills yearly, with each subscription covering a single website or app — additional sites run roughly +$800/year each. There are daily request quotas (the core fitment method allows several thousand calls per day, increasable on request), and the company notes that most clients — typical local tire and wheel retailers — stay well under those limits. The Wheel Configurator with vehicle imagery is a separate, higher tier. Enterprise and self-hosted data licensing exist for high-volume operators.
The hidden costs that actually matter
Here’s what separates a profitable integration from a money pit:
Data preparation labor. Cleaning and tagging your catalog to ACES/PIES quality — or even just to the fitment attributes an API needs to match against — is frequently the single largest cost, and it’s almost entirely labor. Budget for it honestly; it’s not a weekend project for a catalog of any size.
Development integration. A free widget costs nothing to embed. Wiring a fitment API into your catalog so it filters to your products, building a persistent garage, and connecting it to checkout is real development work. This is where the capability you’re paying for actually becomes revenue.
SEO infrastructure. As covered above, fitment pages that rank can’t rely on a client-side widget — they need to be server-rendered so the specs and fitting products are in the HTML at load. That’s a meaningfully larger build than dropping in a finder, and it’s a cost worth carrying only if organic search is part of your growth plan. If it is, it’s often the highest-ROI line in this whole list.
Ongoing data updates. Vehicle and fitment data changes constantly as new models ship. Whatever source you choose, you’re buying a subscription to current data, not a one-time file. Stale fitment data quietly generates returns.
The cost of getting it wrong. This is the one to anchor on. In a category where the product is heavy, expensive to ship, and unforgiving on fit, every wrong-fit sale costs you twice the freight plus the product handling plus the customer’s trust. Accurate fitment tooling isn’t an expense — it’s returns insurance. Frame every tooling decision against the cost of not having it.
Putting It Together: A Practical Stack by Stage
You don’t need everything on day one. Build in stages.
Starter. Embed the free Wheel-Size finder widget so customers can at least look up their specs, and get your product data tagged with core fitment attributes. Low cost, immediate credibility, and it forces the data discipline you’ll need later.
Growth. Move from the display widget to the fitment API. Use it to power a garage selector and filter your catalog to fitting products, so shoppers see buyable wheels, not a spec sheet. If you’re on marketplaces, get your ACES/PIES feeds clean and compliant here.
Scale. Add the wheel configurator for visual confidence, build server-rendered fitment landing pages to capture organic search, and layer in Hollander interchange if your OEM/used business justifies it. This is the full stack — and by now your clean product data is paying dividends across every channel.
The Bottom Line
Three principles cut through all of it. First, match the tool to your model: Hollander for OEM and used, Wheel-Size for aftermarket fitment and visualization, ACES/PIES for marketplace compliance — and a layered approach if you do all three. Second, flexibility comes from your own clean product data plus an API, not from a widget someone else controls. And third, budget for the labor, not just the license — data prep, integration, and ongoing updates routinely cost more than the subscriptions, while paying for themselves in returns you never have to process.
Sell the right wheel to the right car every time, and the tooling pays for itself. Get fitment wrong, and no amount of marketing will outrun the returns. In this category, the data is the customer experience.
Build It Right the First Time
Choosing the tools is the easy part. Wiring fitment data into your catalog so it filters to your products, structuring your data so it flows cleanly to every channel, and building server-rendered fitment pages that actually rank — that’s where wheel stores either pull ahead or stall out.
That’s exactly the work we do at Four Wheel Digital. We specialize in the automotive space, from local service businesses to eCommerce wheel and parts retailers, and we build the fitment integrations, clean product data structures, and SEO foundations that turn a storefront into a store that sells. If you’re standing up a wheel store — or you’ve got a finder bolted on and you’re wondering why it isn’t moving the needle — let’s talk. We’ll map the right stack for your business, your platform, and your budget. Learn more about marketing for wheel and tire shops here.
Ready to make fitment a competitive advantage instead of a returns problem? Get in touch with Four Wheel Digital and let’s build it right.