How a design update helped a Motorcycle brand cut support tickets by 41%

Why it worked We removed the decision bottleneck (fit uncertainty) without touching the brand or stack: same design, same speed—just completion-proof flows that make buying parts as simple as riding.

CLIENT

Polo Motorrad

Visit site

SERVICES

E-commerce

OVERVIEW

Overview

For POLO Motorrad’s online shop we built a “My Bike Garage”: riders save their bikes (make/model/year) and instantly see only compatible parts across categories and PDPs. The hard constraint: preserve the existing design and platform—no rebrand, no replatform.

CHALLENGES

Where Shoppers Were Dropping

Uncertainty about fit led to low add-to-cart, high returns, and “Does this fit my bike?” support load. Filters were brittle on mobile; PDPs repeated specs without a clear fits/doesn’t fit signal. Any UI had to blend into the current design system and respect performance budgets.

How can we lift conversion and cut fitment-related returns by ~20–30%—while keeping POLO’s current design and platform intact?

SOLUTIONS

How We Shipped It in 5 Weeks

Data model & mapping: normalized Make/Model/Year + OEM/MPN mappings; graceful fallbacks for unknown trims.
Session & account storage: quick “Add your bike” on PLP/PDP; garage persists across devices when logged in.
System-aligned UI (no redesign): tokens/spacing/typography from POLO’s DS; new elements as PDP badges (“Fits your bike”), compatibility panel, and auto-filters on category pages—all visually indistinguishable from existing components.
Behavioral details: when a garage bike is active → auto-filter compatible items; incompatible items collapse with a one-tap “Show all.”
Instrumentation & A/B: events for add-bike, compatibility views, add-to-cart, returns reason codes.