When your menu grows faster than your store

An electric bike retailer had the good kind of problem, the range kept growing. The bad side of it was the navigation. New models and categories had been bolted onto the menu one at a time until it sprawled, and customers had to work to find the bike they actually wanted.

What we did

We rebuilt the structure around broader, smarter collections rather than a long list of narrow ones. Bikes group themselves into the right categories by their attributes, so a new model lands in the correct place automatically instead of needing a fresh manual collection each time. That feeds a mega-menu that lays the range out clearly, and the whole thing is driven by metaobjects the team manage themselves. Old collections were redirected to the new ones, so no links or search rankings were lost in the move.

The result

A customer can see the whole range at a glance and reach the right bike in fewer clicks, and the team can add a new model without the menu getting messier. The structure holds as the range keeps growing.

What to take from it

Navigation quietly degrades. Every store adds categories one at a time, and a few years in you are left with a menu that is really just a record of past decisions. If yours has grown by accretion like that, it is worth rebuilding it around how customers actually shop rather than the order you happened to add things.