Doctor Equipamiento

The website didn’t work.

Not in a subtle way — it was a flat list of links that led to more lists, ending in product pages with no clear action, no pricing, and no way to request anything.

But the real issue wasn’t the site, it was the catalog behind it.

Thousands of products spread across multiple Excel files, with inconsistent formats, duplicated entries, missing data, and no clear category logic. That was the starting point.

The work moved in two directions at the same time: data and experience.

On the data side, the goal was to make the catalog usable.

That meant:

• reviewing source files product by product
• defining a consistent structure for imports
• building a category system that could support both users and the internal team

On the experience side, users don’t browse casually. They search, compare, and request. That became the basis for the structure.

The visual direction moves away from the typical medical aesthetic.

Instead of defaulting to blues and neutral interfaces, the system uses:

• a warm cream base
• a serif wordmark with more character
• a single accent color used with precision

Instead of following a traditional ecommerce pattern, the site is built around a quotation flow.

Products are selected, reviewed, and sent as a request.

That decision affects everything:

• product cards
• category pages
• navigation

Navigation is organized in multiple ways:

• by product type
• by use context (hospital, clinic, lab, home)

The site was built on WordPress using a custom theme, allowing the client team to manage and expand the catalog independently.

From a technical perspective, the focus was on flexibility:

• templates that work with both complete and incomplete product data
• a structure that supports continuous catalog updates
• a quotation system replacing the traditional cart

The platform turns a disorganized dataset into a navigable system.

Users can:

• browse a large catalog without relying on exact search terms
• evaluate products before requesting
• move through categories without losing context

More than a visual redesign, the project depended on turning messy product data into a structure the interface could actually support.