nopCommerce 5.0: What's New for Store Owners and Developers

On Monday morning, two messages arrive about the same release. Your developer writes that the nopCommerce 5.0 beta is out and that it needs .NET 10. Your operations lead asks whether the new EU withdrawal button ships with it, and whether that alone is a reason to upgrade.

We did not want to answer from a changelog alone, so we opened the beta on a test store and went through the admin. This guide splits what is new in nopCommerce 5.0 into what changes for the people who run a store and what changes for the people who build on it. Every screenshot below comes from that beta.

At BSS, a new major version reaches us first as a retest list and only then as a feature list. We have kept that order here: what the team published, what the beta showed us, and what nobody can know until the final release.

Where nopCommerce 5.0 Stands Today

Before any feature matters, the release status decides what you can safely do with it. The beta we opened reports itself as 5.00.0 on .NET 10.0.13, the new runtime baseline in the changelog.

The team shipped the beta as a pre-release with a source-code package, a no-source package for quick deployment and a PDF changelog. A beta can still change, so this guide describes what the changelog lists and what we saw on the beta store, not what you will definitely get.

The release notes also say every minor release inside 4.90 is compatible with the others, so 4.90 plugins and themes keep working as you apply those updates.

What's New for Store Owners

Now to the half of the Monday messages that came from operations. The changelog groups its headline items under "Enterprise features", and for someone running a store they fall into three jobs.

Sell more: AI, product feeds and reminders

Five changelog items aim at conversion: AI recommendation engines, a chatbot built on Jotform AI Agents, a ChatGPT shopping product feed, reminders and AI tools for SEO. On the beta store the AI tools are one panel in Catalog settings, where you switch them on, pick Gemini, ChatGPT or DeepSeek and add your own API key.

What to decide: several of these lean on outside services, so the accounts, data quality and running costs are yours.

Reminders are the easiest to put a value on. The beta ships three types: abandoned carts with up to three follow-ups, pending orders with two, and incomplete registrations with one, each timed in hours or days. If you want to see what the problem is worth first, our guide on why shoppers abandon their carts walks through it.

BSS plugin

BSS Cart Reminder

For a store that stays on its current version for a while: up to two automated reminder emails with the delays you set, and a dashboard of recovered carts.

View the plugin

Sell to businesses: price lists, PunchOut and vendor carts

• Native price lists - the team's notes say nopCommerce had no native per-role price lists, only discounts, tier prices or plugins, which B2B stores find limiting when prices are negotiated. The beta adds a Price lists page under Catalog.
• PunchOut support (cXML) - the protocol that lets a buyer's procurement system open a supplier's store. The changelog lists it without detail, so confirm what the beta covers before you promise it to a customer.
• Vendor carts - a setting, "Allow multi-vendor shopping cart", enabled by default. Switched off, the cart splits by vendor and the customer checks out one vendor at a time.

These are the items a wholesale or marketplace store should read twice. If that is you, our guide on whether nopCommerce is right for B2B stores puts them in context.

From the BSS team

In the B2B stores we work on, a price list only helps once the right customer role sees it, so the roles are the first thing we map. If you want that wiring on the version you run today, our BSS B2B Management plugin puts price lists, contract prices and catalog restrictions in the admin.

Meet EU rules: the withdrawal button and product safety

• EU Withdrawal Button - per the team's notes, EU Directive 2023/2673 requires online retailers selling to EU consumers to offer a clearly visible electronic withdrawal function with an automatic confirmation. In the beta it is built on the returns system, with its own locales and a "days valid" setting for the withdrawal link.
• General safety and performance requirements (GSPR) - product identification, the manufacturer's contact details, an EU Responsible Person where the manufacturer is outside the EU, and safety instructions in the buyer's language.

Smaller changes shoppers will notice

• Desired delivery date - customers pick a date at checkout, controlled by a shipping setting and a range of days.
• Sign-in with phone number and SMS, product 3D images and auto-cancel for unpaid orders.
• Search history for customers, configurable contact-us fields and new social links for TikTok, Snapchat, Pinterest and Tumblr.

Phone sign-in is the change shoppers meet at the login screen. For a store that is not moving yet, BSS Phone SMS Authentication is our plugin for phone-based login, registration and password recovery with OTP verification. Confirm it supports your nopCommerce version before you buy.

What's New for Developers

If the owner's half of the story is about features, yours is about breakage. A common surprise on the upgrades we run at BSS is a plugin that builds cleanly and then fails to load when the store starts, so we read the refactoring list before the feature list.

The toolchain: .NET 10 and Visual Studio 2026

The changelog states the requirements outright: Visual Studio 2026 (v18.0) or above, the .NET 10 SDK (10.0.401) and the ASP.NET Core Runtime (v10.0.12), with the Windows Hosting Bundle on Windows servers. To see what a machine already has, run:

dotnet --list-sdks
dotnet --list-runtimes

Look for a 10.0.401 SDK on every build machine and a Microsoft.AspNetCore.App 10.0.12 runtime on every server. Your host has to support .NET 10 before a 5.0 store can run there, so ask them early. Our nopCommerce hosting guide covers what to ask for.

Changes that can break your code

The changelog gives titles, not diffs, so treat this table as a search list for your own code. The "our read" column is our judgement of where a plugin or theme is most likely to be hit.

In the themes we ship at BSS, everything depends on how views are resolved, so the ThemeableViewLocationExpander line is the one we would read twice.

From the BSS team

On our own beta test store, plugins such as Dynamic Popup, Cart Reminder, Product Details and QuickView run as 5.00.0.x builds. Porting a plugin portfolio is where a team often needs extra hands, and you can hire a .NET developer from BSS for the port while your own engineers stay on the roadmap.

Under-the-hood changes worth knowing

• Performance - compiled property selectors are cached in the localization service, DeleteCategoryAsync updates subcategories in bulk, and a resource-attribute path that used async methods synchronously, which could starve the thread pool, was fixed.
• Database - SQL deadlocks in the repository bulk methods were addressed, and the FluentMigrator runner was split into separate packages for MySql, Postgres, SQLite and SqlServer.
• Security - no email enumeration on the login and password-recovery pages, HTML sanitizing for forum content, a Markdown-editor XSS fix, and missing permission checks added to three plugin configuration pages.

If you need the map of projects and layers before you start porting, our nopCommerce architecture guide is the place to begin, and our plugin guide shows what a plugin looks like on the version you run today.

Should You Move to nopCommerce 5.0 Now?

That brings us back to the two Monday messages: what should each person do this week? One real signal sits in the beta's own admin: the Version filter of its extension feed lists 4.90 as the newest option, so the ecosystem has not caught up yet.

When you do move, the sequence matters more than the date. Our guides on testing plugin and theme compatibility and the nopCommerce upgrade checklist go deeper on each step, and the first run should be on a copy.

If you would rather hand the rehearsal over, the BSS team can run the nopCommerce version upgrade for you, so the first time your store sees 5.0 is on a copy, not on your live checkout.

Frequently Asked Questions

Final Thoughts

Back to the two Monday messages. Your developer gets a short answer: install the .NET 10 SDK on staging, run the three searches, and port one plugin branch against the beta. Your operations lead gets a different one: the withdrawal button is in 5.0, but the date it answers to has already passed, so it is its own task.

Price lists, reminders and the ChatGPT feed are reasons to watch the final release, not reasons to move a live store this month. When it ships, its release notes become the reference, so re-read the tables above against them and let your staging results decide the date.