Search returns no results

Common symptoms

  • Catalog page shows 0 results after applying filters or a search query
  • "We couldn't load the tire catalog right now" message
  • Tires load but the size you want is missing

Likely causes

1. Over-filtered

A combination of facets that no tire in the catalog matches. Try:

  • Remove one filter at a time to find the culprit
  • Clear all filters and start fresh

2. Wrong format

The most common mistake is mixing metric and imperial conventions:

  • User searches 205/65R22.5 (mixing metric and imperial) — no tire matches
  • User searches 205 65 15 with odd separators — falls through to a plain text search and likely returns nothing

See Tire size formats for the full parser rules.

3. Compact imperial mis-parsed

A 5-digit string starting with 8 or 9 is treated as single-digit-width compact imperial (8195 → 8R19.5). Any other 5-digit string is treated as double-digit-width compact imperial (10225 → 10R22.5, 11245 → 11R24.5). A 7-digit string in the format XXX YY ZZ is parsed as metric (2056515 → 205/65R15). If you type a tire number that collides with one of these patterns, you may get unexpected results.

4. Tire genuinely not in catalog

Most commonly affects new SKUs released since the last catalog refresh. Tire Library ingests new data weekly, so a brand-new SKU may not be there yet.

5. Catalog loading failed

The catalog page falls back to a friendly error message if the catalog can't be loaded. Wait a minute and try again.

Steps to confirm

If you have an API key, you can query the catalog directly:

GET /api/v1/tires/search?width=205&aspect_ratio=65&rim_size=15
Accept: application/json

If that returns 0 results with no error, the size truly isn't in the catalog.