Product Parts Finders

 The MageDelight Product Parts Finder extension lets shoppers narrow a catalog to the exact products that fit their vehicle, or match any other attribute-based combination, using dropdown filters placed anywhere on the site. An admin builds a finder from existing product attributes, picks year, make, and model as an example chain, and publishes it using a unique embed code that drops into the home page, a category page, or any CMS page. An automotive parts retailer, for instance, can put a year-make-model finder on the home page for first-time visitors and a narrower, category-scoped finder on a brakes category page for shoppers already browsing that section.

Configuration stays entirely in the admin. Each finder gets its own title, "Find" button text, horizontal or vertical layout, and drop-down sequencing, so the filter order matches how customers actually narrow a search. Filter selections are saved automatically, so a returning visitor sees their last choices preselected rather than starting over. When a filter combination matches exactly one product, the extension redirects straight to that product page instead of showing a one-item result list, and universal products can be bulk-imported by CSV so parts that fit many vehicle combinations appear consistently across matching searches.

Compatibility spans Open Source, Adobe Commerce, and Commerce Cloud, with full Hyvä theme support included at no extra cost. Dropdown queries run against indexed attribute data, so filter performance holds up as a catalog grows into the tens of thousands of SKUs, and scoping a finder to a single category narrows the query further for faster results on large catalogs. The extension reads and writes only public catalog attribute data, never customer accounts or payment information, keeping its footprint limited to product filtering.

Most catalog filtering tools only work within category pages, tied to the layered navigation a customer already has to be browsing to see. This extension treats a finder as an independent, placeable component instead: several finders, each with a different attribute chain, category scope, and layout, can run simultaneously across the home page, landing pages, and CMS content without stepping on each other, which suits stores organized around brands, vehicle types, or product families rather than one catalog tree.

Business-Level Overview

For a founder or eCommerce manager selling parts or accessories, the real conversion problem is rarely product selection, it is fitment uncertainty. A shopper who cannot tell whether an item fits their vehicle is far more likely to abandon the search than risk ordering the wrong part, and that hesitation shows up directly in the customer experience as a frustrating, trial-and-error browsing session.

The operational shift is straightforward: instead of commissioning a custom vehicle-fit search tool, admins build finders from attributes the catalog already has, publish them with an embed code, and adjust layout or sequencing without a developer request. A finder that once required a bespoke build is live the same day it is configured.

Revenue impact follows from shortening the path to a confident purchase. Redirecting straight to a product page on a single match removes a step that otherwise gives a shopper time to reconsider, and auto-saved filters keep returning visitors moving instead of re-entering the same vehicle details on every visit.

For CTOs evaluating long-term fit, finders read from the native attribute system rather than a bespoke data structure, so they scale with catalog growth and stay compatible with Hyvä storefronts and standard upgrade paths without additional engineering work.

3rd Party Integrations

No external APIs required.

Storefront User Benefits

• Find compatible parts in seconds using year, make, and model instead of browsing a full catalog
• Skip straight to the product page automatically when only one match is found
• Return to the store with filter selections already saved from the last visit
• Use a consistent, familiar finder across the home page and relevant category pages

Admin Benefits

• Build finders from existing product attributes without custom development
• Place independent finders on the home page, category pages, or CMS pages
• Choose horizontal or vertical layout and control drop-down sequencing per finder
• Scope a finder to a single category to keep results tightly relevant
• Bulk import and manage universal, cross-fitment products via CSV

Full Feature List

• Year-make-model and other attribute-based product filters
• Finder placement on the home page, category pages, and CMS pages
• Unique embed code generated per finder
• Horizontal and vertical finder layout options
• Dynamic drop-down values sourced live from product attributes
• Configurable drop-down filter sequencing
• Auto-saved filter selections for returning visitors
• Single-category scoped filtering
• Automatic redirect to the product page on a single result
• Universal product import and management via CSV
• Custom "Find" button text and finder title per finder
• Multiple independent finders running on one store
• Hyvä theme compatibility
• Compatibility with Open Source, Adobe Commerce, and Commerce Cloud

Business Problem vs Solution

Fitment uncertainty stalls purchases Problem: Shoppers who cannot tell whether a part fits their vehicle tend to leave rather than risk an incorrect order. Solution: Year-make-model filters narrow the catalog to compatible items before a shopper ever reaches checkout.

Filtering limited to category pages Problem: Standard layered navigation only filters within a category, leaving the home page and landing pages without a search shortcut. Solution: Independent finders, each with a unique embed code, can be placed on the home page or any CMS page.

Custom fitment tools require developer time Problem: A bespoke vehicle-fit search normally means a development project before it reaches customers. Solution: Finders are built directly from existing product attributes and configured entirely in the admin.

Cross-fitment products get lost in results Problem: Parts that fit many vehicle combinations often fail to show consistently across every matching search. Solution: Universal product import keeps shared parts appearing across relevant results regardless of vehicle combination.

Large catalogs slow down narrowing Problem: Browsing a big parts catalog by category alone takes many clicks before reaching a relevant product. Solution: Single-category scoping and instant redirect on a single match shorten the path to a relevant product page.

Business Benefits (Measurable Outcomes)

• Reduce abandoned searches caused by fitment uncertainty
• Shorten the path to purchase with automatic redirect on a single matching result
• Increase returning-visitor engagement with auto-saved filter selections
• Cut developer dependency by building finders from existing product attributes
• Improve navigation on high-traffic pages beyond standard category listings
• Simplify inventory visibility for cross-fitment parts through universal product import

Sample Use Case

A multi-store automotive parts retailer serving both wholesale garages (B2B accounts) and individual car owners (D2C) struggled with a single shared catalog that made no distinction between a customer's vehicle and the thousands of parts on offer, leading to frequent returns from mismatched orders.

After installing the extension, the team built a year-make-model finder for the home page and narrower, category-scoped finders for brakes, filters, and lighting sections, all configured from existing vehicle-fitment attributes without a development project. Universal products like cleaning supplies were imported once via CSV to appear across every applicable search.

Within two months, incorrect-part returns dropped noticeably, repeat visitors moved faster through the site thanks to saved filter selections, and single-match searches converted at a higher rate once shoppers were redirected straight to the product page.

FAQs

Q1: Does setting up a finder require custom development? No. Finders are built from existing product attributes entirely in the admin, with no template or code changes needed.

Q2: Is it compatible with Open Source, Adobe Commerce, and Commerce Cloud? Yes. It supports all three editions and includes full Hyvä theme compatibility at no extra cost.

Q3: Can a finder be placed on a specific category or CMS page? Yes. Every finder gets a unique embed code that can be placed on the home page, a category page, or any CMS page.

Q4: Does this extension allow filtering within a single category only? Yes. A finder can be scoped to one category so its results never include unrelated products.

Q5: Will adding several finders slow down the storefront? No. Dropdown queries run against indexed attribute data, so performance holds up as the catalog and finder count grow.

Q6: Can the finder title and button text be customized per finder? Yes. Each finder has its own configurable title, button text, and drop-down sequencing.

Q7: Will this keep working after a version upgrade? Yes. Finders are built on the native product attribute system rather than core overrides, keeping them stable across upgrades.