Teslar
An online store for Tesla accessories. Visitors pick their model and year first, so they only see products that actually fit their car.


What had to be solved
Accessories for a Tesla are not generic products: a floor mat, sunshade or organiser has to fit one specific model and generation. A buyer who doesn’t know whether their Model Y is already a “Juniper” either gives up or buys the wrong part.
The store had a large, fast-growing catalogue. It needed to do three things at once: show shoppers only the parts that fit, make the catalogue easy to maintain and stay fast on a phone.
What I did
The starting point is a vehicle registry. Every product is linked to the models and generations it fits. The shopper picks their car and the store shows only matching products. On the product page the fit is stated clearly, so nobody has to guess.
To keep the catalogue maintainable I built a product-entry tool. From supplier data it prepares a draft product: Slovenian title and description, attributes, vehicle fit from the registry, a selection of photos with descriptions and the SEO fields. Publishing stays a manual decision, so quality remains under control.
I treated speed as its own task: the most important CSS is inlined into the page, and third-party scripts load only after the first interaction. The store runs in a Slovenian and a Croatian version.
What’s in the project
Vehicle selection
Shoppers start with model and version, then see only matching accessories.
Fitment registry
Products are linked to vehicles. The fit is visible on the product page.
Product-entry tool
Draft products with descriptions, attributes and SEO fields; a human approves publishing.
Speed
Critical CSS and deferred third-party scripts for a faster first view.
Slovenian and Croatian markets
Two language versions with a local offer.
Pay in instalments
The instalment option is presented right on the homepage.

What is different now
- Shoppers start by choosing their vehicle and see only parts that fit.
- The fit is stated on the product page, not buried in the description.
- New products are created faster as drafts, and a human always approves publishing.
- Two language versions share the same design and the same good practice.
What do you want to solve?
Tell me what you need or where you’re stuck: a new site, a store, a tool or an automation. I’ll reply personally.
