Fitment-aware search for parts catalogs
Parts shoppers search by vehicle, VIN, and OEM number — not marketing titles. Seekmodo ranks with fitment context where your platform connector supports it, with clear labels for what ships today vs roadmap.
- BigCommerce (GA) — YMM garage, VIN decode, Vehicle Landing Pages, cart vehicle stamp. See /solutions/bigcommerce-vehicle-search and /docs/bigcommerce/install#fitment.
- Zen Cart (GA) — vehicle context and recommendation cascades on Growth-tier plans via the reference connector. See /solutions/zen-cart-search.
- Shopify (roadmap) — YMM and VIN on the in-development App Store connector. Join early access at /plugins/shopify.
Technical setup
This page covers the product and SEO story. First-party install guides and custom-connector API docs (for platforms we do not ship) live in the developer docs.
Platform-dependent fitment features
- BigCommerce (GA) — YMM garage, VIN decode, Vehicle Landing Pages, cart vehicle stamp. See /solutions/bigcommerce-vehicle-search and /docs/bigcommerce/install#fitment.
- Zen Cart (GA) — vehicle context and recommendation cascades on Growth-tier plans via the reference connector. See /solutions/zen-cart-search.
- Shopify (roadmap) — YMM and VIN on the in-development App Store connector. Join early access at /plugins/shopify.
- Magento 2 — vehicle context widgets on Growth-tier where configured. See /solutions/magento-search-module.
- Any other platform — implement the same APIs yourself: /docs/fitment (index fits_vehicles, taxonomy sync, search.by_vehicle).
Custom connectors and unsupported platforms
Seekmodo cannot ship and maintain a first-party plugin for every CMS. Third-party and in-house teams build connectors against the public HMAC REST / MCP contract. Start at /docs/connectors/custom, then follow /docs/fitment for vehicle-scoped search, VIN (decode locally), and fitment-aware recommendations.
Search beyond fitment widgets
Typo-tolerant AI catalog search, synonyms, pins, and zero-result rescue apply on every supported commerce connector. Fitment context boosts compatible SKUs; universal-fit parts remain discoverable without a garage vehicle.
Recommendations and LTR
- PDP and cart recommendation cascades on Growth-tier BigCommerce and Zen Cart rollouts.
- Beacon-driven relevance learning from shopper clicks — training on Seekmodo servers.
- Custom field mapping for part numbers, OEM, FCC, and merchant-specific attributes.
Case studies
Seekmodo is built and operated by Numinix — production search for automotive BigCommerce and Zen Cart merchants. Public case studies ship when clients approve; contact us for vertical references.
Frequently asked questions
Which platforms support VIN decode today?
BigCommerce connector GA — VIN decode pre-fills vehicle context where your catalog supports it. Shopify VIN is on the roadmap with the App Store connector. Custom connectors decode VIN locally (for example NHTSA vPIC) then call /docs/fitment APIs.
Do I need a separate fitment data vendor?
Fitment assignments sync from your catalog and configured sources. Map custom fields in the connector admin for merchant-specific part number schemas. Custom connectors push fits_vehicles and vehicle_taxonomy themselves — see /docs/fitment.
Can WooCommerce auto parts stores use this?
WooCommerce connector improves product search today; dedicated YMM garage widgets are not GA on WooCommerce yet — use BigCommerce or Zen Cart for full fitment UX today, or build YMM on WooCommerce via /docs/fitment.
How does pricing work for high-traffic parts sites?
Search-volume tiers from $29/mo — not GMV bands. Use /solutions/search-volume-pricing and the calculator during trial.
Is MCP included for parts catalogs?
Yes — every paid plan exposes per-tenant MCP for agent and internal copilot workflows. See /solutions/mcp-catalog-search.
Try fitment-aware search
Install a connector, start a 14-day Growth trial, and map your part fields.