Two changes: remove <p className="text-xs font-sans text-gear-gold shrink-0">{product.price}</p>, and set the dropdown to w-80 (wider than the w-56 input) anchored right so it doesn't overflow the nav:

The price column is removed from each result row, and the dropdown is now w-80 (320px) anchored to the right edge of the search input rather than stretching to match its width — giving the results more horizontal breathing room for long product names and SKUs.

Full context on the data model, PDP page, and catalog cards. Now I'll build the variant system — new data types, a large variant dataset for the end mill family, a variant table component with filters, and update the catalog card to show the variant count badge.

Now I need to update catalog-data.ts to add a variantCount and masterSku field to the Product type, and update the product-card to surface those. First let me read catalog-data.ts:

Now add variantCount to the first product in the catalog (the end mill — p1):

Now update the product cards to surface the variant count badge and "from" price prefix:

Now add the Link import to product-card since it's already there — let me verify:

Good. Now also update the list row card similarly:

The variant system is fully implemented across four layers. The data model (product-variants.ts) defines MasterProduct and ProductVariant types with 200 generated end mill variants across 10 diameters × 4 flute counts × 5 coatings. The catalog card now shows a "200 variants" badge and a "from €24.50" price prefix. On the PDP, the variant selector sits between the purchase panel and the specs section — it has per-axis filter dropdowns with checkboxes, active filter chips with individual clear buttons, a sortable table with SKU / all dimension axes / price / availability / MOQ columns, inline qty stepper and add-to-cart per row (only visible when a row is selected), and paginated results at 20 rows per page to handle the large variant counts efficiently.