nopCommerce Plugins: What’s Built In, What to Add and How to Install Them

Most “best plugins” lists are written by plugin vendors about their own products. This guide takes a different approach: it starts from what nopCommerce already includes, so you don’t buy what you have, then covers what to add for each kind of need, how to judge a plugin, and how to install it without breaking the store.

What a nopCommerce plugin is

A plugin is a folder under /Plugins with a compiled DLL, its views and a plugin.json file that tells nopCommerce what it is and which versions it supports:

{
  "Group": "Widgets",
  "FriendlyName": "Google Analytics",
  "SystemName": "Widgets.GoogleAnalytics",
  "Version": "5.00.6",
  "SupportedVersions": [ "5.00" ],
  "FileName": "Nop.Plugin.Widgets.GoogleAnalytics.dll"
}

SupportedVersions is the line that matters most. nopCommerce only loads a plugin that lists the running version, which is why a plugin bought for 4.90 doesn’t appear on 5.00. Plugins are grouped by type: payment methods, shipping and pickup, tax, widgets, external sign-in, two-factor sign-in, exchange rates, discount rules and miscellaneous.

nopCommerce plugins by category

For each need, the first column is what you already have in the nopCommerce 5.00 download. The second is what stores usually add.

Scroll the table sideways to see every column.

For payments in more depth, see our nopCommerce payment methods guide; for APIs, the nopCommerce Web API guide. In 5.00, forums, news and polls are now plugins; if your store uses them, install those plugins after upgrading. What’s new in nopCommerce 5.0 lists every change.

Free plugins worth knowing

Beyond the bundled ones, these free plugins solve problems most stores have. Two of them are ours:

• Cartenvo StorePulse: a read-only health check for scheduled tasks, emails, errors, database growth, security basics, product SEO and plugin compatibility, with a fix for each finding. For 4.80, 4.90 and 5.00.
• Cartenvo Product Data Exchange: product import and export through Excel and ZIP packages with SKU matching and a review before import. For 4.80 and 4.90.
• Payment provider plugins: most providers publish a free nopCommerce plugin for their own service. Prefer it over a third-party one when it exists, because the provider keeps it in step with their API.

If default search isn’t enough, our paid Advanced Search plugin adds a federated autocomplete for products, categories, brands and FAQs, with default search or Algolia.

Plugins change what the store does; a theme changes how it looks. Our nopCommerce themes guide covers choosing and installing one, and for electronics stores on 4.90 there is our TechOrbit electronics theme.

How to choose a nopCommerce plugin

• Has a build for your exact nopCommerce version (check the Supported versions on the listing)
• Is updated within a few months of each new nopCommerce release
• Has a demo, documentation and a clear support channel
• States whether source code is included, and what the licence allows
• Doesn’t require editing core nopCommerce files
• Doesn’t bundle library versions that clash with the ones nopCommerce or your other plugins use
• Is limited to what you need: one plugin that does ten things you won’t use is still ten things to update

How to install a nopCommerce plugin

1. 1Back up the site and database, and install on staging first.
2. 2Go to Configuration → Local plugins and click “Upload plugin or theme”. Choose the plugin’s ZIP file. You can also copy the plugin folder into /Plugins on the server.
3. 3Click “Restart application to apply changes” (or restart the site in IIS).
4. 4Find the plugin in the list, click Install, and restart again when prompted.
5. 5Configure it. Payment, shipping, tax and widget plugins must also be activated in their own pages, such as Configuration → Payment methods or Configuration → Widgets.
6. 6Test the storefront page it affects, and checkout if it touches the order flow.

Installing a plugin runs its own setup, which often adds settings, language strings and sometimes database tables. Uninstalling removes them, so export anything you need first.

When a plugin doesn’t show up or won’t load

nopCommerce marks a plugin as incompatible for one of three reasons, plus the usual upload problems:

Our StorePulse guide on nopCommerce plugin load errors goes through each error message in more detail.

Keeping plugins under control

• Limit where a plugin runs. Edit a plugin in Local plugins to restrict it to certain stores or customer roles, useful in multi-store setups.
• Uninstall what you don’t use. A deactivated plugin is still loaded and still has to be updated at every upgrade.
• Keep a plugin list. Name, version, vendor, licence and where to download updates. It turns an upgrade into a checklist.
• Check compatibility before upgrading. Our plugin compatibility guide shows how to check every plugin against a target version.

Buy or build a plugin

Buy when a maintained plugin does what you need, or close to it. Build when the requirement is specific to your business, such as a pricing rule, an approval step or an integration with your own systems, or when you’d otherwise stack several plugins to get there. A custom plugin uses the same extension points as any other, so it doesn’t make upgrades harder if it is built properly.

Writing one yourself? Our nopCommerce 5.0 plugin tutorial walks through a complete example. We write custom plugins for payments, shipping, B2B rules and ERP integrations; see nopCommerce plugin development.

Frequently asked questions

Next steps

Start with what’s already in the download, add plugins for the gaps, and keep the list short. If no plugin does what you need, or a plugin you depend on has no build for your version, tell us what it should do.