Generator.az — Product Catalog Website Rebuild

Generator.az sells and rents diesel and petrol generators and supports customers with equipment-related services from its Baku operation. The website project began with an existing online presence, but the published case study shows that the main problem was not simply the visual style. Product information, category structure and navigation did not give the site a clear product-discovery path.

Mono’s work focused on rebuilding that structure. The objective was to make the website easier to scan, separate generator categories more clearly and give the product catalog a more deliberate role in the customer journey. The project remained a website and catalog rebuild; there is no public evidence that it included CRM automation, paid acquisition, custom operational software or other wider growth-infrastructure layers.

The Challenge

The previous Generator.az website presented the company and its products, but the hierarchy was difficult to follow. The original case study identifies unclear navigation, weak product categorization and a static page structure as the main limitations.

That mattered because Generator.az does not sell one simple product. The business presents different generator types, fuel options, brands and power ranges, alongside sales, rental and after-sales services. A visitor therefore needs to move from a broad need to a relevant product group without having to interpret an unstructured collection of information.

The redesign needed to address that information problem first. Visual changes were useful where they made product groups, page sections and navigation easier to distinguish.

What Mono Built

The website was reorganized around clearer product discovery. Mono reworked the page hierarchy, visual separation and navigation so the product offer could be presented as a structured catalog rather than a largely static company website.

The updated site gives prominent space to generator categories such as diesel, petrol, stationary and portable units. It also separates the product area from company information and after-sales services, giving each part of the site a clearer purpose.

The catalog adds a more detailed discovery layer. Generator.az currently exposes filtering controls for price, brand, engine, capacity, generator type and fuel type, alongside structured product listings. This gives the product section a practical browsing model for customers who already know some of the specifications they need.

For this project, the primary Mono capability is Web Development: the central work was website architecture, interface restructuring and product-catalog presentation rather than a separate marketing or automation engagement.

How the Website Was Structured

The rebuilt experience works in layers.

The homepage introduces the main generator groups and the wider business offer. This gives visitors a high-level route into the catalog without forcing detailed technical choices immediately.

The product area then supports more specific browsing. Filters for attributes such as fuel, power range, brand and generator type allow the catalog to reflect the way industrial equipment is evaluated. Product cards provide the next step from category-level discovery into individual items.

The wider navigation also separates products, after-sales services, company information, content and contact routes. This is a simpler information architecture than treating every part of the business as content on one presentation page.

The result is not an automation system or a custom SaaS platform. It is a focused website system in which navigation, category hierarchy and catalog controls work together around the product-selection task.

Implementation

The published project material documents three important states: the earlier Generator.az interface, the redesigned long-form homepage and the product catalog view.

The implementation concentrated on structural changes already identified in the original case study: reorganizing product categories, simplifying navigation, improving spacing and readability, and using stronger visual separation between sections. The redesigned homepage gives the generator categories distinct content areas instead of presenting the offer as one continuous block.

The catalog interface extends the same logic. Rather than relying only on navigation menus or text links, it exposes product attributes as filtering controls and presents multiple generator models in a consistent grid.

These are observable interface and information-architecture changes. The available public evidence does not justify claims about a particular WordPress plugin stack, custom API integrations, development duration, conversion-rate improvement or revenue impact, so those are intentionally not presented as project outcomes.

The Outcome

The clearest verified outcome is structural: Generator.az now presents its generator categories, product listings and catalog filters through a more organized product-discovery path.

The current site visibly separates diesel and petrol generators, stationary and portable types, product listings, sales and rental context, and after-sales services. The catalog allows visitors to narrow products using several technical and commercial attributes.

This is a defensible improvement over the earlier interface shown in the case study because the change can be verified directly in the published project material and the current website. It does not require an unsupported claim that traffic, leads or sales increased.

What the Project Established

Generator.az is a useful example of a website rebuild where the main value came from information architecture and product structure rather than adding unrelated digital layers.

The project established a clearer foundation for presenting a technical product range online: high-level category routes on the main site, more detailed product discovery in the catalog, and simpler navigation between products, services and company information.

Within the current Mono architecture, the closest business-problem framing is the Website Conversion System. In this case, “conversion” should be understood narrowly and truthfully: the website was reorganized to make the offer and the next product-discovery steps clearer. No public metric is available to claim a quantified conversion increase.