Skip to content

Case study · Equipment brands, one distributor

Three brand websites rebuilt on nopCommerce 4.80

A distributor ran its brand websites on a mix of WooCommerce, WordPress and older nopCommerce versions, each maintained differently and some on .NET versions that no longer get updates.

Platform
nopCommerce 4.80 · .NET 9
Moved from
WooCommerce, WordPress, older nopCommerce
Sites
3

Each site was rebuilt on nopCommerce 4.80 and .NET 9 with its own theme plugin, so the brand’s design and features live outside the nopCommerce source and the sites can be upgraded together.

Starting point

The client sells several equipment brands and runs a website for each one. Over the years the sites had ended up on different platforms: some on WooCommerce or WordPress, others on nopCommerce 4.40 to 4.60, which run on .NET versions Microsoft no longer supports. Each one was maintained in its own way.

What we built

  • A fresh nopCommerce 4.80 store on .NET 9 for each brand, using the same set of plugins
  • A theme plugin per brand that carries the design and brand-specific features, so nothing in the nopCommerce source is edited
  • Product document downloads with several files per product, and product videos
  • Sliders with text overlays, HubSpot forms, Google Tag Manager and correct canonical URLs
  • Catalog and content moved over from the old WooCommerce and WordPress sites

Why theme plugins

Earlier brand sites were customised by changing views and code inside each nopCommerce copy, which made every upgrade a separate project. Putting each brand’s changes in a plugin keeps the nopCommerce source untouched, so the next upgrade is the same job for every site.

Speed of delivery

Because the three sites share one base and one set of plugins, each new brand is mostly design and content work. One site was rebuilt to match its existing design in four days.

Related

Have a project like this?

Tell us about your requirements and we will outline how we would approach them.