Quick answer: I built a Wix tyre finder for Switch Fleet Services. Customers enter their vehicle details. The site calls a UK vehicle data API, gets the correct tyre size, and matches it to tyres in the store. If a match exists, the customer can buy it straight away.
The Problem
Buying tyres online is confusing. Most customers don’t know their tyre size. Pick the wrong one and it won’t fit.
The store needed a way to remove that guesswork. Customers should find the right tyre without reading a sidewall.
How the Wix Tyre Finder Works
The flow has four steps:
- The customer enters their vehicle [registration number / make, model and year].
- A backend function calls the UK Vehicle Data API.
- The API returns the manufacturer’s tyre fitment, such as
225/50R17. - The site searches the store’s products for that exact size.
If matching tyres exist, they appear on screen. The customer adds one to the cart and checks out. [Add: what happens when no match exists, e.g. “an enquiry form appears” or “a message offers to source the tyre”.]
The Technical Build
This is Velo work, not template customization. Three parts matter most.
Backend API integration. The vehicle lookup runs in a Velo backend web module, not in the browser. That keeps the API key off the frontend. Server-side calls also avoid CORS problems.
Tyre size matching. The returned size has to match how the products are stored. A size like 225/50R17 must be compared against each product’s size data. [Add: how you did it, e.g. “stored sizes in a Wix Data collection linked to Wix Stores products” or “used product options”.]
Error handling. Real vehicles produce messy results. A registration may not exist. The API may time out. The size may have no matching stock. Each case returns a clear message instead of a broken page.
Problem and Solution
| Problem | Solution |
|---|---|
| Customers don’t know their tyre size | Automatic lookup from vehicle details |
| Wrong-size orders and returns | Manufacturer fitment data, not user guesses |
| Browsing hundreds of products | Only matching tyres are shown |
| Lost sales when customers give up | Direct path from lookup to checkout |
Results
they did not needed any large data in there website,as api was fetching for them and this way we get good results as every model etc.
Why This Matters for Your Wix Site
The same pattern works beyond tyres. Any store where customers must pick a compatible part can use it. Think batteries, wiper blades, car parts, filters, or accessories.
The core idea is simple. Take one piece of customer data. Call an external API. Match the result to your products.
Need something similar? See how I handle Wix Velo development. You can also run your idea through the cost calculator for a quick estimate.
Frequently Asked Questions
Can a Wix store look up tyre sizes automatically?
Yes. With Velo, a backend function can call a vehicle data API. It returns the tyre size, and the site matches it to your products.
Does the tyre finder work with Wix Stores?
Yes. Matching results can link directly to your store products and checkout.
Which API does it use?
It uses the UK Vehicle Data tyre lookup API.
Can this work for other products besides tyres?
Yes. Any compatibility-based product can use the same approach, such as batteries or car parts.
How long does a project like this take?
It depends on the data setup and product catalogue. I scope this after reviewing your store.i did this project in 4 days.
Message me on WhatsApp with your idea, or check the cost calculator first.