Blog posts tagged with 'nopcommerce plugins'

What's new in nopCommerce 3.1 ~ Friday, August 16, 2013

The nopCommerce 3.1 release has been out and about for 2 weeks now and we would like to share with you what's new in the system in a little bit more detail than the standard release note. So let's get straight to the point.

NopCommerce 3.1 comes two months after the major 3.0 release so there are no ground-breaking features like the multi-store, multi-vendor, or the new markup. Still there are a few quite important improvements in the system, which are worth an upgrade of your nopCommerce website.

The most important change in nopCommerce 3.1 is the absence of the product variants, which were an integral part of the system in the previous versions. Now in nopCommerce you have just products. And products can be either group or simple. Essentially all your products with product variants are replaced via a group product with simple products underneath. In addition simple products can show individually on catalog pages, like the category page for example. The Product Variants tab is removed from the Product administrator page. What you should be looking for is the Associated Products tab.

NopCommerce Group Products

This change makes the catalog system in nopCommerce simpler, at the same time more powerful. With the grouping between products and at the same time the possibility to show simple products individually you can cover complex catalog scenarios.

For example, let's say that you have a product Levi's Alfresco Jeans and two simple products underneath it: Alfresco Blue and Alfresco Green. The two simple products have separate skus and prices. You also have a separate category called Sale, where you show all your products that are on sale. You decide that the Alfresco Green is not selling very well so it needs to go on sale. Now because the Alfresco Green is just another product you can map it to the Sale category. Mark the Alfresco Green as "Visible Individually" and it will show in the Sale category. Previously this scenario was not possible due to the fact that product variants were tied to one specific product and the product itself was the leading entity in the catalog.

So the new group and simple products in nopCommerce 3.1 are a great feature for the nopCommerce store owner. But let me tell you that the nopCommerce developers as well as the nopCommerce team of course, will have to put a lot more effort when working or customizing the catalog system. But this is a topic worth a whole new blog post (very technical) so let's move to the other new features in nopCommerce 3.1.

If you are a nopCommerce store owner, you will definitely love this new addition to nopCommerce 3.1 as it was an obvious and most requested feature. In nopCommerce 3.1. you can associate a product attribute to a product picture. In other words if you have a certain dress, which you sell in two different colors : black and blue and you have two different pictures of the dress for each color.

NopCommerce Assosciated Product Attributes With Pictures

When the customer goes on the product page and chooses a color, let's say blue, the product picture on the page changes to show the correct image of the blue dress. This UI behavior seems natural and thus important but was missing in nopCommerce up till now. So it alone is well worth considering and upgrade to the newest 3.1 version of nopCommerce.

If you are still not convinced the new product bundling functionality in nopCommerce 3.1 could be it. Now you can have a bundle of products, which works seamlessly with the pricing and the order process in the system.

NopCommerce Bundled Products

To create a product bundle in nopCommerce all you need to do is to associate a product with an attribute value. Then when the customer selects the value, nopCommerce will know that you are actually buying the product associated with the attribute value. Do note that you need to have the Dynamic Price Update setting set to true in order to have the prices update with each product you choose.

Administering NopCommerce Bundled Products

NopCommerce 3.1 also adds several improvements to its multi-store support. Most importantly now you can enable\disable plugins per store.

NopCommerce Plugins

You can also configure payment methods per store as well as shipping rates by weight and dimensions.

NopCommerce 3.1 comes with a few performance improvements, which have to do with new database indexes and more presentation level caching. The release note contains also a list of small but useful bug fixes and improvements. If you are interested do check it out here:

Let's summarize what we have learned so far about nopCommerce 3.1.

  • It simplifies the catalog system for the store owners
  • Adds very useful features for both the owners and the customers of a nopCommerce store
  • Fills multi-store functionality gaps
  • Come with the usual performance and functionality fixes and improvements

So the release is more than worth a look by all involved with nopCommerce.

Do not also forget to checkout our nopCommerce themes and plugins, which are available for nopCommerce 3.1. Currently we are developing responsive versions and theme rollers for all our themes as well as new responsive nopCommerce themes. Every new theme we release is added for free to the Nop Ultimate Theme Collection package of existing customers.

So stay tuned as we continue to develop more products for the greatest (there is absolutely no doubt) .NET e-commerce platform on the market.

The Nop Mega Menu plugin adds a powerful and flexible dropdown mega menu to your nopCommerce web site. You can enjoy an easy and effective navigation in your store managed right from your administration panel.

To learn more about the Nop Mega Menu Plugin watch this video.

What's new in Nop Ajax Filters 3.0.2? ~ Tuesday, June 18, 2013

Product filtering in nopCommerce has never been a trivial task, especially when you need your filters to interact with each other, to update on the fly not only the availble products but also the available filter options. Our flagship product the Nop Ajax Filters (it was also our first commercial product) has seen a lot of attention from our development team over the two years since its launch. Most of development on the plugin was driven by our customers.

With the nopCommerce 3.0 released we are starting to see a greater number of large retailers and stores pointing their opportunistic radars in the direction of nopCommerce. Naturally we have been approached by customers who had thousands of products in a single category who required that the Nop Ajax Filters filter the products withing the range of 1 sec.

If you are familiar with the nopCommerce database schema and how the different Price Range, Specification, Attributes and Manufacturer filters interact with each other, you will know that is quite a challenge. Well...challenge accpeted!

And here we are with a brand new 3.0.2 version of the Nop Ajax Filters, which can select among thousands of products from the nopCommerce intricate database in the blink of an eye.

But that's not all. We have also enhanced the Nop Ajax Filters to work not only on a nopCommerce category page but also on a manufacturer page. Now you can make your nopCommerce manufacturer pages much more friendly to your customers, who will be able to find the products they are looking for in no time.

All our 3.0.2 nopCommerce plugins including the Nop Ajax Filters have received a new sidebar menu on their administration pages in order to facilitate the administration of the plugins:

We would like to point out that the Nop Ajax Filters 3.0.2 will work on any nopCommerce 3.0 installation. If you have the plugin already installed, please uninstall it and install the new version.

We would also like to thank all our customers who shared their feedback and most importantly large real-world nopCommerce databases with us!

Next we will be enhancing the Nop Ajax Filters to work on the nopCommerce search page. So stay tuned for more new features and improvments coming out of our amazing nopCommerce development team.

If you have missed the other parts of this blog series, please feel free to read more here:

What's new in nopCommerce 3.0 - part 1 - multi vendor support.

What's new in nopCommerce 3.0 - part 2 - multi store support.

What's new in nopCommerce 3.0 - part 3 - Nop-Tempalates themes and plugins.

The multi-store and multi-vendor are the big stars in the nopCommerce 3.0 release. But there is one more major feature, which we have not talked about yet. NopCommerce 3.0 will be released with a brand new HTML and CSS. The whole markup of the system has been refactored to be clean, optimized, semantically correct, modern and most importantly easy to work with and customize.

This major feature was done by Nop-Templates and contributed to nopCommerce. We have had our top front-end developer work on the system for almost 2 months so that the markup that nopCommerce generates can be, as he likes to put it, "Shining"!

There are three major directions, which were followed during the refactoring.

1. Add or remove elements to achieve flexibility of styling.

Take the sorting options on the nopCommerce category pages for example:

NopCommerce Sorting Options

Imagine you would like to style the sorting options panel, put a background on it or a border. Before the refactoring the sorting options panel elements (the three dropdowns) did not have a parent element and styling the whole panel was quite difficult. You would probably end up overriding the category template view, just to do that. Now these elements have a common panel and if you would like to change it, you only need to work with CSS.

Another good example for this type of refactoring is the product page of nopCommerce where you have a separate line of markup for each product variant:

NopCommerce Product Variant

It is common to divide the elements for each variant (picture, description, attributes, buttons) into two separate panels, left and right. Before the refactoring to achieve this, each element had to be floated separately as there were no elements to act as left and right panel. Imagine doing this also for your theme RTL support. Now this is easily achieved as there are two separate panels, left and right, and elements can be arranged in these panels.

Another good example of this newly added markup to achieve flexibility are new class names added to table elements so that columns in a table could be styled separately. Before the refactoring separate styling of columns could not be achieved via CSS only. Now this is possible and is handy on pages like the shopping cart for example where you might need different font, color, centering, etc for a column:

NopCommerce Shopping Cart

There are numerous such changes through the code, which involve not only the pages mentioned so far but also blog, news, etc. pages. The purpose of this refactoring direction was to add flexibility to the markup so that customizations to the nopCommerce pages could be achieved only via CSS and not by overriding views and working with Razor, which complicates not only the development process but also creates problems with the maintenance and upgrade of these changes.

2. Unification of common elements. This refactoring direction has to do mainly with adding class names to common elements so that they can be styled together.

Take the nopCommerce category navigation for example:

NopCommerce Category Navigation

In this case the Categories and Recently Viewed Products navigation require the same styling as they both present a list ot items. Before the refactoring this could be achieved but without a common class declaration as there was no such class. Now these two panels can be styled with a single class declaration.

Such unification changes were done to many nopCommerce page elements like form elements, form lines, form labels and controls. Before the refactoring the nopCommerce forum for example had a lot of common tables, but without common class names. Now the nopCommerce forum is much easier to style because of this. This is also valid for the MyAccount pages, which depend heavily on form elements. Unification changes were done to whole pages too. The search page of the web site and of the forum were unified for example.

3. Remove deprecated elements and code approaches to achieve standard-compliant and semantically correct markup.

If you are a front-end developer familiar with nopCommerce you could be reading this blog only to find the answer to this question.

Is the <div class="clear"/> still used in nopCommerce 3.0?

The answer is no! This was an old, deprecated approach to clear floats, back from the days when HTML was written with IE 6 in mind. It was semantically incorrect and added waste to the HTML markup of the system, which not only looked bad to developers and search engines but was more difficult to work with. Now floats throughout nopCommerce are cleared only via CSS, which means that you cannot expect it to be perfect in IE 6, but to be honest who cares about IE 6. In fact please do good to developers and the web by not using this browser:

With the <div class="clear"/> out of the way we had to take care of the next big front-end oldie: using table elements for layout. Table elements should be used where there is table data, like the nopCommerce shopping cart for example. But using tables to achieve layout, like presenting the products on the catalog pages for example is wrong and also frowned upon by search engines. So all tables used for layout were removed from nopCommerce.

NopCommerce Products

Another example of semantically incorrect use of HTML markup in nopCommerce, which was corrected by the refactoring is definition lists (dl elements) being used to define forms in the website. This was replaced with a more appropriate markup as definition lists should be used where there is specification data, (color - blue, material - cotton, etc.).

The whole nopCommerce generated markup was rid of all old-fashioned and semantically incorrect elements and approaches to make the system modern and much more appealing to developers and search engines.

The HTML Refactoring is not as widely talked about and advertised as the multi-store and multi-vendor support, which bring direct benefits to the nopCommerce store owner. The refactoring is a feature, which the developers will relate to. But as such it is extremely important. It will boost the theme development in the community and will allow nopCommerce developers to complete more quality nopCommerce projects much faster and with greater ease, which will again result in benefits for the store owners.

If you are a developer keen on looking at all the HTML Refactoring changes, please follow the changes in this nopCommerce branch:

This concludes our insight into the nopCommerce 3.0 major release. I hope you have found the series useful. Do not forget to send us your feedback and thoughts in the comments below or on the related facebook post on our facebook page.

Nopcommerce 3.0 will be released next week so stay tuned and do consider following us on Facebook, Twitter or Google+!

If you have missed the other parts of this blog series, please feel free to read more here:

What's new in nopCommerce 3.0 - part 1 - multi vendor support.

What's new in nopCommerce 3.0 - part 2 - multi store support.

Picking up from where we left last time we would like to continue our talk about the multi-store support but this time in the context of our nopCommerce themes and plugins. The multi-store support in nopCommerce 3.0 is a big feature and as such it required equal changes to every plugin we have in our valued nopCommerce toolbox. To the store owners and the developers these changes can be summarized by answering a single question.

Will the Nop-Templates themes and plugins support the multi-store in nopCommerce 3.0?

The answer is YES! The configuration of every plugin can now be limited to a specific store or a set of stores.

Take the Nop Anywhere Sliders for example. You can have a slider (with a configuration and a set of images) for one store and another slider (with a different configurations and a set of images) for another store. The multi-store configuration UI in the plugins is consistent with the nopCommerce one. Take a sneak peak at the administration of a slider:

Nop Anywhere Sliders

There is a new tab "Stores", which when required can be used to map a slider to a specific store:

Nop Anywhere Sliders

This plugin multi-store support is available in all our nopCommerce plugins.

What about the themes you would ask? The nopCommerce team thought of this on our behalf and implemented the multi-store in such a way that different themes can be applied to different stores. Combined with the plugins configuration per store, this means that you have no limits to your flexibility and power in a multi-store environment despite the fact that you running only a single installation of nopCommerce.

The multi-store support is a major feature in our plugins and themes. But it is not the only feature you are going to receive with the nopCommerce 3.0 release of our products.

We have implemented numerous new features and improvements in the plugins. In fact by looking at the snapshot of the Nop Anywhere Sliders you can guess one of them? Please do in the comments below and you will receive a free license for the Nop Anywhere Sliders.

Our nopCommerce 3.0 themes are now based on the new nopCommerce HTML\CSS markup, developed by Nop-Templates and contributed to the system. This means that the themes are now modern, optimized, easy to customize and have what is required to be taken to the next level, which is Responsive Design.

The new HTML\CSS markup is what we are going to look at next in this blog series. So stay tuned for more nopCommerce 3.0 exciting news!

We are back with more insight into the currently buzzing and much awaited nopCommerce 3.0 release. Today we are going to look at the multi-store support in nopCommerce.

As usual we have something for all nopCommerce users - store owners, developers and Nop-Templates customers. But let's start with the store owners. So what does it really mean to have more than one store running in nopCommerce?

It means that you can have more than one website\store (different domains or subdomains) running in the same nopCommerce installation. In other words if I was a retailer who was selling two major brands Brand1 and Brand2 and my business required that these brands are sold on separate websites\stores I would not have to create two separate nopCommerce installations to do this.

How does this help?

  • For starters you have only one database and web application to cater for.
  • You have a single administration for all your websites, where you can manage your catalog, customer and order data.
  • Your customers have a single login for all your stores.
  • You can share catalog data between stores, have a product in more than one store for example.
  • Since your customer data is shared you can use it between stores for marketing campaigns and different crosell\upsell implementations.

Most of the entities in your nopCommerce installation like categories, products, etc. can be limited per store. But it is important to note that your customers cannot be.

Why is this important? Because you cannot dedicate an administrator for only one store. Your catalog, customer and order data is visible to all administrators.

This means that the multi-store support in nopCommerce is really for single store owners with more than one online store. You would not have a shopify or bigcommerce style of system. You cannot have such a system anyway, as it requires a multi-tenant application and nopCommerce is not multi-tenant.

So we have established that nopCommerce 3.0 is a good fit for store owners who would like to have more than one store. To be able to plan their multi store implementation, these store owners should know what entities\data can be limited per store. In the initial release of nopCommerce 3.0 these are the entities that will support multi-store (can be limited per store):

  • Categories
  • Products
  • Manufacturers
  • News
  • Blogs
  • Topics
  • Message Templates
  • Settings

Different themes can also be configured for different stores.

And these are the entities that do not support multi-store but will probably do in the future:

Plugins and widgets cannot be enabled\disabled per store but this does not mean that their configurations cannot be made store specific. In fact this is how most of the widgets in nopCommerce 3.0 (Google Analytics for example) work. You might also be wondering if prices or specific attributes can be configure per store. Currently there is no such support and this is not even on the nopCommerce road map. Could this be achieved via customization? Please read more later in this article.

Do note that even though a category or manufacturer can be limited to a specific store, this does not mean that all products for the given category or manufacturer are automatically limited to the store. Products need to be managed separately. There is a work item to facilitate this process and you can vote for it here:

For the store owners familiar with nopCommerce, here is where you need to begin when setting your multi-store.

1. Create a website on your hosting space for example and install nopCommerce on your website. This is where the nopCommerce installation will run.

2. Create a second website for example and add a CNAME recrod to forward all request to your first website Do not install anything on this website, it should be empty.

3. Go back to your website and configure a domain alias for

The above three steps sound more complex than they are. Still if you have difficulties you can always ask you hosting provider or administrator to do it for you. For detailed information please read this forum post:

4. Setup your stores:

Manage NopCommerce Stores

5. You do need to set the HOST VALUES for each store, because this is how nopCommerce will know which store is the active one for the current request. Read more on this later in this article:

Edit NopCommerce Store

6. Once your stores have been added you need to configure the different nopCommerce settings. Individual settings can be set for all stores or per store:

NopCommerce Settings Per Store

7. Once your stores and settings are configured you can start editing your catalog. Categories, products and manufactures can be limited per store as can be other entities like Blogs, News, etc...The nopCommerce administration to do this is consistent across all entity administration pages. Here is how you can limit products per store:

NopCommerce Products Per Store

I bet that our developer audience, who have not looked at the nopCommerce 3.0 code yet, are wondering how all this magic works? The answer is quite simple, which can only testify to the cleverness of the nopCommerce approach.

As you could see, every store has HOST VALUES mapped to it. Therefore when a request arrives in the nopCommerce pipeline, nopCommerce inspects the HOST HEADER value of the request and sets the current store in the WebStoreContext. The WebStoreContext is available to all controllers and services, so all actions can pass the current store to data retrieval operations which require it. In the database entities (products, categories, manufacturers, etc...) are mapped to the different stores via a general table called StoreMapping.

But what you really would be using in your nopCommerce development code is the StoreMappingService in the Nop.Service.Stores namespace. The StoreMappingService has all the methods required to manage the mapping of the entities to the different stores. Most importantly it has a generic method called Authorize, which when passed an entity (a category or product for example) determines if the entity is visible in the current store.

There is one important aspect of this multi-store implementation. You can have the different stores run on different domains or subdomains, but you cannot have them run in separate virtual directories.

Earlier in this article I mentioned whether entity properties (product prices for example) can be configured per store. Currently this is not supported and because the nopCommerce architecture is not based on EAV (Entity Attribute Value) model like some other well know e-commerce systems, implementing such a configuration could be quite tricky for static properties (those that map to predefined database table columns). However nopCommerce does have a basic GenericAttribute infrastructure, which can be used for custom properties to be added to entities. Fortunately the GenericAttribute class has a StoreId property, so you can limit your custom properties to certain stores. For more information have a look at the GenericAttribute, GenericAttributeExtensions and GenericAttributeService classes.

One last thing we would like to point the attention of the nopCommerce developers to is that nopCommerce 3.0 multi-store, in fact nopCommerce itself is not multi-tenant. All stores run in the same application and app pool. Implementing a multi-tenancy in nopCommerce is not going to be a walk in the park but for those of you who are willing to tackle it, here is a good place to start:

This is our summary of the multi-store implementation in nopCommerce 3.0. In summary we can say that it is cleverly implemented, fairly easy to setup and gets the job done - provides store owners with more than one store. There is a lot to be added to this implementation but we do expect big time projects to be implemented on the initial version.

What is left to cover is how our themes and plugins are going to work with this major feature. We are going to do this in the next part of these series. Do not forget that we also have the new nopCommerce 3.0 HTML markup to talk about. So do stay tuned for more exciting nopCommerce 3.0 content!

With little less than 2 weeks before the nopCommerce 3.0 release we thought it would be useful to share our take on what the new features are in this much awaited major version of our favorite e-commerce system.

NopCommerce 3.0 is all about multi-vendor and multi-store support. One curious fact about this is that no open source system supports this out of the box. In other words you would not get these enterprise features for free unless you are using nopCommerce 3.0.

Another big change in nopCommerce 3.0 is the HTML Refactoring of the system, which was done by Nop-Templates and contributed to nopCommerce.

We would like to cover these major changes from the perspective of the store owner, the developer and the Nop-Templates products. This is quite a lot for one blog post, so we will publish it in several parts.

Let's start with the multi-vendor support!

Imagine you would like to create an online market place, where different people or businesses can manage sales of their own products through a common web store. Products from all independent vendors appear in the common store catalog and online customers shop at one store even though the products are supplied by many different vendors. There are numerous examples of such market places. Let's just mention Amazon and Themeforest to give you an idea of two of the biggest - one selling pretty much all types of tangible and some non-tangible goods, the other selling virtual products only.

How does nopCommerce 3.0 can afford you with such a market place out of the box?

With nopCommerce 3.0:

  • You can add unlimited number of vendor accounts and have more than one user mapped to a vendor account.
  • Different vendors have separate administration area for products and orders by default. Since all vendors are added to the Vendor role, the store owner can configure access control to the different administration areas for the Vendor role.
  • Products from all vendors appear in a single store front
  • Customers can place products from different vendors in one order
  • All vendors receive a notification when an order is placed, which includes one of their products.
  • You have a common payment processing

What is missing from this implementation is the ability to do vendor commissions and payouts. But with some customization and automation effort this could be easily implemented, unless you don't mind to do it manually, which is also an option.

This is its initial release and there are a few useful features that could be added to the multi-vendor support in nopCommerce. Certainly it will evolve and be enhanced over time. Still it is powerful enough and will get you a long way in your virtual mall enterprise. Do consider voting for these work items if you would like to affect the future development of the multi-vendor support:

What does the multi-vendor mean for the nopCommerce-savvy store owners?

First of all it means that you need to add the vendors to your store:

NopCommerce Vendors

Second you need to configure the ACL (administration access control) for the Vendor Role:

NopCommerce Vendors ACL

You need to map the users who represent your vendors to their vendor. Note that you cannot map a customer to more than one vendor.

Customer Vendor Management

And you get a new field on the product administration pages:

NopCommerce Product Vendors

You do get to filter your products and orders by vendor:

NopCommerce Product Vendors Filter

NopCommerce Order Vendors Filter

For the nopCommerce developers, the multi-vendor support means that the Product and Customer entities now have a new property: VendorId. This property needs to be taken into account when implementing product or customer searches as well as various custom entity mappings.

The Nop-Templates customers might wonder how our nopCommerce plugins and themes are going to be affected by the multi-vendor functionality. The good thing is that the plugins and the themes are going to work with the multi-vendor support out of the box.

The multi-store support however, which is the other highlight of this nopCommerce release is a completely different story. If you would like to learn more about it, stay tuned for part 2 of this series on "What's new in nopCommerce 3.0?".

Before we introduce our new Nop Customer Reminders plugin, we would like to remind you that the plugin will be added to the Nop Ultimate Plugin Collection shortly, so all customers with valid licenses to the Nop Ultimate Plugin Collection do not need to buy the plugin as they will receive it for free.

NopCommerce has become so powerful and feature rich that you might think that there isn't an e-commerce opportunity that can be missed with it. You have many different shipping and payment methods, a customizable checkout process, powerful tax system, discounts, customer groups, reward points, featured products, price breaks, cross sells and many other marketing and sales capabilities.

Store owners spend a lot of time setting these up and making use of them, and they should if they want their nopCommerce store to be successful. But even if you have your nopCommerce store up and running with the nicest theme and an optimized customer shopping experience, it is not uncommon to have abandoned shopping carts, registrations and even orders.

Around 70% of the customers abandon their shopping carts for example. And a big part of this does not happen because your buy button was not big enough or green enough or your checkout was too long. Some customers got distracted, some had problems with their credit card or your payment provider, some were unsure of the price, some wanted to save the items for later, some left but could not remember your url. Yet some thought that they ordered the items. In nopCommerce it is easy to place an order but not pay for it.

But now you can win all these customers back using the Nop Customer Reminders plugin. The plugin can be configured to send automatic reminder messages to:

  • Recover abandoned shopping carts
  • Recover incomplete registration
  • Recover unpaid orders

The Nop Customer Reminders plugin uses a flexible configuration framework where the store owner can specify as many reminders as they need and configure various settings for each reminder.

Nop Customer Reminders

You can specify, which customers are eligible to receive a reminder depending on when they took the action of the reminder rule (added a product to their shopping cart for example). In this particular example a reminder will be sent to all customers, who added a product to their shopping cart but did not buy it at most 30 days ago but not less than 30 minutes ago. In addition to this specific customers can be excluded from the reminder.

You can also configure the plugin to send more than one message and the interval between the messages.

In the message template you can make use of tokens like: %Store.Name%, %Customer.FullName%, %ShoppingCart.ProductsWithPictures%, etc. Some tokens are common to all reminder rules, some are specific to the currently selected reminder rule.

But that's not all. We have also thought of the more technically-savvy store owners. If none of the three predefined rules fits your reminder purpose you can add your own rule from code. To do this you need to reference the SevenSpikes.Nop.Plugins.CustomerReminders.dll, implement the IReminderRule interface and register it as a service in nopCommerce.

Once again we would like to remind you that the plugin will be added to the Nop Ultimate Plugin Collection so all customers of the Nop Ultimate Plugin Collection will receive the plugin for free.

For anyone else a free trial is available on the Nop Customer Reminders product page. Feel free to give it a try and send your valuable feedback to us.

And do not forget the three key actions to your successful nopCommerce sales: Remind, Reassure, Promote!

Our Nop Ultimate Plugin Collection has grown quite a lot since we started developing for nopCommerce more than an year ago. One of the greatest advantages of the collection over the individual plugins is that customers receive new plugins added to the collection for free. So we decided to share how the Nop Ultimate Plugin Collection was developed over time, what nopCommerce plugins were added to it and when. We started with one plugin, the Nop Ajax Filters and kept the development rolling and adding a new nopCommerce plugin every month. Then we took a break and for several months worked on adding new features and improving the plugins. Now we are again stepping up on the new plugins development, which started with the Nop Quick View last month.

Two more nopCommerce plugins will be added to the Nop Ultimate Plugin Collection with our coming release this month while the price of the collection will remain the same.

Guess the functionality of any of these plugins by writing in the comments below and win a license for them for free. Customers of the Nop Ultimate Plugin Collection will get the plugins for free anyway, but they are more than welcomed to participate.

Nop Ultimate Plugin Collection

We are extremely proud to announce the release of our new nopCommerce plugin - the Nop Quick View.

The Nop Quick View makes your product catalog much easier and faster to navigate by providing a pop-up details view for every product on the category page. Just hover over the product and click the "Quick View" button.

Nop Quick View

The various product detail sections are all configurable from the administration of the plugin. You can choose what exactly to be shown on the Quick View window.

Nop Quick View Administration

As with all our nopCommerce plugins, the Nop Quick View is open to modifications and has already been integrated in our free and premium nopCommerce themes. It supports single and multi variant products.

Nop Quick View

The Nop Quick View supports a Cloud Zoom and an Ajax Cart. With all this product information and functionality you customers will seldom have to go to the product details page, navigate back and forth and waste time choosing the products that they need. This dramatically improves your online store shopping experience resulting in better conversions and more sales.

Best of all, the Nop Quick View is included in the Nop Ultimate Plugin Collection, which provides 11 nopCommerce plugins for less than half the price. Do not also forget that our products are backed by the support of the one of the top nopCommerce teams - the Nop-Templates development team, who are setting the trends on the nopCommerce extensions market.

1 2 3 4 Next
Find us on Facebook