We built OKTAN.store because finding an interesting performance part is often easier than confirming whether it fits a specific model, generation and engine.
Our custom e-commerce flow starts with the vehicle and narrows the catalog to compatible parts. We would love feedback from drivers, builders and e-commerce teams:
Where do compatibility mistakes usually happen?
What information makes you trust a fitment recommendation?
Hi Product Hunt ๐ I'm Marek, maker of OKTAN.store, a store for automotive performance parts.
Finding a part is only half the job. You also need to check whether it matches your car's generation, engine and any application-specific restrictions.
We built OKTAN around that decision. Choose your make, model, generation and engine where available; carry that selection into browsing; then inspect the product's recorded fitment details before ordering.
Vehicle filters already exist in specialist automotive stores. Our focus is connecting those steps in one shopping experience for performance upgrades, with visible fitment details and a route to our team when an application needs confirmation or a part is missing from the catalog.
Try BMW โ M3 โ F80 โ S55 to see a concrete example, then open the heat exchanger and check its listed engine and production years.
For the builders here, this is our custom commerce implementation on Vercel. We'd love feedback on the shopping flow and how clearly it communicates compatibility.
What information would you need to feel confident that a part fits your car?
Coming soon: an AI agent to help you choose parts for your car.
Thanks for checking out OKTAN.store!