We use necessary cookies to make this site work. With your permission we also use Google Analytics to understand how the site is used and Google Ads cookies to measure which of our ads lead to purchases. You can accept all cookies, reject the optional ones or choose which ones to allow. Cookie policy
Choose which cookies you allow. Necessary cookies are always on because the shop cannot work without them. You can change your choice at any time with the "Cookie settings" link.
Needed for the basket, checkout, login and security. They do not track you.
Google Analytics: how many people visit, which pages they read and how they found the site. It sets the _ga cookies and sends usage data to Google.
Google Ads: measures which of our ads lead to a purchase. It sets the cookies _gcl_au and _gcl_aw (90 days) and, when you buy, sends Google the order details and a hashed form of your contact details for matching. See our cookie and privacy policies.
Parts finder for Magento 2: Year > Make > Model style finders with dependent dropdowns, fast CSV import with dry run and delta files, fitment notes, SEO result pages with layered navigation, My Garage, a fit check on the product page, Luma, Hyvä and GraphQL.
One-off payment, with 12 months of updates.
No subscription or automatic renewal. Keep using the versions included in your update period. Update and licence details
Composer package commercegears/module-parts-finder
Fitments live in their own tables and in the catalog search index, so category pages and layered navigation filter without slow database joins.
The product page tells shoppers whether the part fits the car they chose, with notes such as "Front axle only".
Every import can run as a dry run first. Problems are listed by line, and replacing a dataset never leaves the shop empty.
All features
Feature tour
01 / 06
Each selection has its own page such as /parts/car/2015/ford/focus, with heading, text, notes under the products and working layered navigation.
02 / 06
The product is checked against the shopper's remembered car. Another car can be checked right there, and a compatibility list shows everything it fits.
03 / 06
Consecutive years are combined into ranges, with the note of each fitment.
04 / 06
Labelled dropdowns that fill one after the other, with saved selections as one-tap chips.
05 / 06
The dry run reads every line and lists each problem with its line number and content. One click then imports the file.
06 / 06
Pick a car in the admin and see every product that matches, why it matches, its note and whether it is shown.
Live demo
A full Magento store with the module installed, on Luma and on Hyvä. The admin demo signs you in with one click.
Compatibility
| Magento | 2.4.6 – 2.4.9 |
|---|---|
| Platforms | Magento Open Source and Adobe Commerce (one price) |
| Storefront themes | Luma Blank Hyvä |
| PHP | 8.2 – 8.5 |
| Latest version | 1.1.1 |
| composer.json requires | php ~8.2.0||~8.3.0||~8.4.0||~8.5.0 magento/framework ~103.0.6 commercegears/module-core ^2.0 free, installed by Composer with this module magento/module-backend * magento/module-catalog * magento/module-catalog-search * magento/module-cms * magento/module-config * magento/module-customer * magento/module-elasticsearch * magento/module-advanced-search * magento/module-indexer * magento/module-store * magento/module-ui * magento/module-widget * |
Installation
After you buy, create a Composer key in your account. Then, in the root of your Magento project:
01Add the repository and your key (once per project)
composer config repositories.commercegears composer https://repo.commercegears.com composer config --auth http-basic.repo.commercegears.com PUBLIC_KEY PRIVATE_KEY
02Install the module
composer require commercegears/module-parts-finder
03Enable it
bin/magento setup:upgrade bin/magento setup:di:compile bin/magento setup:static-content:deploy bin/magento cache:flush
The last three are only needed in production mode.
Prefer a zip? Every version you are entitled to can be downloaded from My modules. More about Composer access
User guide
The user guide has its own page: how to install Parts Finder, what each option does and how to use it in your store. Written for version 1.1.1; a copy ships with the module.
Changelog
FAQ
Something else on your mind? The developers who wrote the module answer before and after you buy.
Ask a question →Already installed it? Open a support ticket
No. A finder can have any 1 to 6 levels: Brand > Printer for ink, Device > Model for phone cases, Make > Model > Year for bikes. You can run several finders side by side.
Fitments are stored in their own indexed tables and imported in batches by cron, so the size of the file does not block the admin, and an import can continue over several cron runs. Files with hundreds of thousands of lines work; files too big to upload can be placed on the server or imported from the command line.
Yes. "Check only" is on by default: every line is checked and you get a list of problems with line numbers (also as CSV), without any change to your data. One click then imports the same file.
No. Switch on "Range" for the Year level and write 2010-2015. You can also list values (Focus|Fiesta), put several SKUs in one cell, and use * for "every model" or "every value from here down".
Yes. "Add and update" adds the lines of the file, and an optional action column with delete removes single fitments in the same file. "Replace" swaps the whole dataset without an empty storefront during the import.
Yes. The filter runs in the catalog search index, so price and attribute filters, sorting and paging work as on any category page, with correct counts.
Each selection has its own URL such as /parts/car/2015/ford/focus, with its own heading, text, meta description, canonical URL and breadcrumbs. You choose whether search engines may index them.
The shopper gets links to a wider search and to all products, and a short "Ask us about a part" form. You see the requests with the vehicle in the admin and can be notified by e-mail.
Yes. Pages are the same for everybody; the shopper's remembered selection, the fit check and the garage are added in the browser. Option lists and fit checks are cached responses that are cleaned when your data changes.
Yes, Hyvä templates are included in the module. Luma is supported as well.
Yes. Every search goes into "My Garage": in the browser for guests and in the account for customers, with a My Garage page in the customer account. Guest selections move into the account when the shopper signs in.
Yes. GraphQL queries return the finders, the dropdown options, selections from result page URLs, the fit check and the customer garage, and the products query accepts a commercegears_fits filter.
Support
From the blog
A shopper picks brake pads for the wrong car, and the parcel comes back. Here is why Magento's own filters struggle with fitment, and what a proper Year, Make, Model search needs.