After a short scoping call we confirm your WooCommerce/WordPress versions, theme, data source and catalog size. A typical build runs about 2–4 weeks: we develop against a copy of your site, install on staging for your review, then deploy to production. Larger catalogs or a custom VIN data source can extend that — we give you a firm timeline in writing before any work starts. There is no marketplace download link; you receive a plugin built and installed for your specific store.

Your plan includes a post-launch support window for bug fixes and compatibility maintenance as WordPress and WooCommerce release updates (including HPOS and Store API changes). Because ECOSIRE built it, support is from the people who wrote the code — not a generic ticket queue. We can also extend support and add features (new selector levels, additional data sources) as your catalog grows.

VIN decoding needs a data source. We can wire the lookup to a free/public source such as the NHTSA vPIC VIN API, or to a paid commercial fitment/VIN provider you license. The same applies to the Year/Make/Model/Engine catalog: most clients already maintain this as a CSV or in an ERP, which we import. We don't resell a third-party vehicle database, but we integrate the one you choose during scoping.

Yes — the finder ships as a shortcode and a Gutenberg block, so it drops into Elementor, the block editor, or a hard-coded template. We integrate it against your live theme and test it alongside your existing setup on staging before going live. It's built HPOS-compatible and exposes WordPress actions and filters so your developers (or ours) can extend the selector and the product query.

Yes. Fitment is stored as structured data with indexed queries rather than free-text attributes, AJAX results are cached, and the CSV importer runs in WP-Cron-friendly batches so a multi-hundred-thousand-row file won't hit a PHP execution-time limit. We load-test against a copy of your real catalog during the build.