Can you build a Magento auto-parts catalogue with VIN + part-number + vehicle-fitment lookup?

Yes, this is our flagship Pune-region specialism. A typical Chakan-belt auto-parts B2B catalogue ships with five lookup paths, all native to the Magento 2 EAV catalog: (1) VIN decode, chassis number (17-char) decodes via API into year / make / model / engine / trim, the customer pastes a VIN and we filter the catalogue to fitting SKUs; (2) Vehicle-fitment cascade, year → make → model → variant → engine, a 5-level dependent dropdown on category / search pages; (3) OE part-number search, one-shot search by Mercedes / VW / Bajaj / Tata Motors / Mahindra OE part numbers; (4) Cross-reference / supersession chains, map Bosch / Bajaj / aftermarket equivalents to the OE part; (5) Application-data table, on each PDP, a full list of vehicles this part fits across years. We ship this on Hyvä with a React VIN-search component for sub-1.5s LCP on dealer 4G connections in Chakan / PCMC. Shipped for an anonymised Chakan auto-parts OEM-supplier, 15k SKUs across part-numbers + VIN cross-reference, scaled to 200+ dealers across 5 states.