On this page
This page collects what we found in the nopCommerce 5.00 source, its GitHub milestone and the changes made between the beta and the stable release. Each feature links to its GitHub issue so you can read the details. We update the page as 5.00 patches ship. Ready to plan the move? Our nopCommerce upgrade guide covers the procedure step by step.
nopCommerce 5.0 release date and status
nopCommerce 5.00.0 was released on 27 October 2026. The stable release is on GitHub (opens in a new tab) and the official download page (opens in a new tab), four weeks after the beta of 30 September 2026. All 195 issues in the 5.00 milestone are closed. The release has these packages:
- Source, for developers who customise nopCommerce or build plugins.
- No source builds for Windows x64, Windows x86 and Linux x64, to deploy straight to a server.
- Upgrade scripts, the SQL scripts for stores on old versions, plus a PDF changelog.
A separate milestone for 5.00 bug fixes is dated 18 November 2026, so expect a 5.00.x patch around then. It already has open reports, for example an import with an invalid value that breaks every storefront page (opens in a new tab) and price list re-imports that turn empty prices into 0.00 (opens in a new tab). If you import catalog or price data, test it on staging first.
nopCommerce 5.0 requirements
| Item | nopCommerce 5.00 | Note |
|---|---|---|
| .NET | .NET 10 (projects target net10.0) | 4.80 and 4.90 target .NET 9 |
| SDK to build from source | .NET 10 SDK 10.0.401 or a later feature band | Pinned in global.json |
| IDE | Visual Studio 2026 (v18.0) or later | Only to build or customise the source |
| Hosting | ASP.NET Core Runtime 10.0.12 or later; Windows Hosting Bundle on IIS | Docker images build on dotnet/sdk:10.0 |
| Databases | SQL Server, PostgreSQL and MySQL | Migrations use PostgreSQL 15 and MySQL 8 specific processors |
| Object mapping | Mapster replaces AutoMapper | Affects custom plugins only |
Check with your host that .NET 10 is available before planning a date. A server that only has the .NET 9 runtime cannot start nopCommerce 5.00.
What's new in nopCommerce 5.0
The 5.00 milestone closed 195 issues. These are the changes store owners will notice, grouped by area.
Pricing and B2B
- Native price lists. Price lists are part of the core, with views on the product and customer pages in the admin area. (#8098 on GitHub (opens in a new tab), #8247 on GitHub (opens in a new tab), #8248 on GitHub (opens in a new tab))
- Request for quote improvements. Quotes gain PDF export, CAPTCHA and server-side quantity validation. (#7841 on GitHub (opens in a new tab), #7895 on GitHub (opens in a new tab), #7915 on GitHub (opens in a new tab))
- PunchOut (cXML). A new official plugin for procurement systems that use cXML PunchOut. (#7389 on GitHub (opens in a new tab))
- Vendor carts. Marketplaces can use one consolidated cart or separate carts per vendor. (#56 on GitHub (opens in a new tab))
Sales and retention
- Reminders. Automatic reminders for abandoned carts, incomplete registrations and pending orders. (#7743 on GitHub (opens in a new tab))
- Auto-cancel unpaid orders. Orders that stay unpaid can be cancelled automatically. (#8120 on GitHub (opens in a new tab))
- Desired delivery date. Customers can choose the delivery date they want. (#7386 on GitHub (opens in a new tab))
- Customer search history. Customers see their recent searches and can remove them. (#8069 on GitHub (opens in a new tab))
AI and product discovery
- AI SEO for any entity. Generate meta titles, descriptions and keywords with AI tools for products, categories and other pages. (#7964 on GitHub (opens in a new tab))
- ChatGPT shopping feed. A new feed plugin exports products for ChatGPT shopping. (#8198 on GitHub (opens in a new tab))
- AI recommendations. A Google AI recommendation plugin suggests products to increase conversions. (#7734 on GitHub (opens in a new tab))
- Chatbot. A Jotform widget plugin adds an AI sales assistant. (#7733 on GitHub (opens in a new tab))
Catalog and compliance
- Product 3D models. Products can show a 3D model on the product page. (#4279 on GitHub (opens in a new tab))
- EU withdrawal button. Support for the withdrawal button required by EU Directive 2023/2673. (#8161 on GitHub (opens in a new tab))
- GSPR. Support for the EU General Product Safety Regulation. (#7400 on GitHub (opens in a new tab))
- Non-returnable digital products. Downloadable products can be excluded from returns. (#8229 on GitHub (opens in a new tab))
Customers and security
- Phone number sign-in. Customers can sign in with a phone number and an SMS code, with a new Twilio plugin. (#2430 on GitHub (opens in a new tab))
- Advanced phone validation. Phone numbers are validated per country. (#8093 on GitHub (opens in a new tab))
- No email enumeration. The sign-in and password recovery pages no longer reveal whether an email address is registered. (#8131 on GitHub (opens in a new tab))
- Configurable contact form. Store owners choose the fields on the contact us form. (#1832 on GitHub (opens in a new tab))
Admin area
- Export reports. Admin reports can be exported, and exports respect the filters you set. (#7574 on GitHub (opens in a new tab), #8313 on GitHub (opens in a new tab))
- System information. Shows memory use and checks for the latest nopCommerce version. (#8073 on GitHub (opens in a new tab), #8074 on GitHub (opens in a new tab))
- Database size and shrink. The maintenance page shows the database size next to the shrink action. (#8075 on GitHub (opens in a new tab))
- New file manager. elFinder replaces Roxy Fileman in the editor and admin uploads. (#7462 on GitHub (opens in a new tab))
What moved, changed or was removed
These changes can break an existing store if nobody plans for them. Check each one against your store before upgrading.
| Change | What happens | What to do |
|---|---|---|
| Forums, news and polls #7336 on GitHub (opens in a new tab), #7340 on GitHub (opens in a new tab), #7368 on GitHub (opens in a new tab), #8115 on GitHub (opens in a new tab) | Moved from the core into the Misc.Forums, Misc.News and Misc.Polls plugins. Private messages are separated from forums. | Install the plugins you use after upgrading and check the content on staging.How to keep forum, news and poll content. |
| Payments.Manual #8170 on GitHub (opens in a new tab), #8169 on GitHub (opens in a new tab) | No longer ships with nopCommerce; the credit card fields it used moved out of the core. | Choose another payment plugin before upgrading.What to use instead of Manual payments. |
| Attribute pictures #8270 on GitHub (opens in a new tab), #8387 on GitHub (opens in a new tab) | Attribute values and combinations move to multiple pictures; the old PictureId columns are removed by a migration. | On stores upgraded from 4.60 or earlier, clear the old picture links before upgrading, or pictures can show twice.Fix duplicate attribute pictures. |
| Order custom values token #7848 on GitHub (opens in a new tab) | %Order.CustomValues% is split into several tokens, one per zone. | Review customised order email templates.Replace the %Order.CustomValues% token. |
| Payment redirects #8223 on GitHub (opens in a new tab) | RemotePost, used by some payment plugins, loses its Post() method and Method property; plugins call PostAsync() instead. | Ask payment plugin vendors for a 5.00 build. |
| Product structured data #8135 on GitHub (opens in a new tab) | Products with variants use the ProductGroup schema type instead of Product. | Recheck rich results in Google Search Console. |
| Not found pages #7870 on GitHub (opens in a new tab) | A missing page keeps the requested URL and returns status 404. | Watch crawl reports for new 404s and add redirects. |
What changed between the beta and the stable release
We compared the release-5.00.0-beta tag with the stable release-5.00.0 tag. The stable release has 66 more commits across 122 files, and 50 of the 195 milestone issues were closed after the beta shipped. Almost all of them are bug and security fixes, which is why the beta should not run a live store:
- Permission checks added to the AI meta-tag endpoint, Reminders page, Google Authenticator and Avalara (#8396 on GitHub (opens in a new tab), #8389 on GitHub (opens in a new tab), #8392 on GitHub (opens in a new tab), #8395 on GitHub (opens in a new tab))
- The 5.00 upgrade no longer loses attribute value and combination pictures (#8387 on GitHub (opens in a new tab))
- 3D model upload only accepts model files (#8390 on GitHub (opens in a new tab))
- Quotes can no longer be used by another customer, and OTP attempt limits are enforced (#8388 on GitHub (opens in a new tab), #8391 on GitHub (opens in a new tab))
- Return requests reject quantities above the ordered quantity (#8414 on GitHub (opens in a new tab))
- Vendors can no longer open price lists or link another vendor’s products, and a failed registration no longer leaves a usable account (#8415 on GitHub (opens in a new tab), #8417 on GitHub (opens in a new tab), #8412 on GitHub (opens in a new tab))
- Category pages respect product display order and count products correctly (#8362 on GitHub (opens in a new tab), #8364 on GitHub (opens in a new tab))
nopCommerce 5.0 for plugin and theme developers
Every plugin and theme needs a 5.00 build. For most plugins this is a retarget and a rebuild, plus fixes where the code touches one of the areas below.
| Area | Change | What to do |
|---|---|---|
| Target framework | net10.0; build with the .NET 10 SDK (10.0.401 or later). | Retarget every plugin project and rebuild against the 5.00 source. |
| plugin.json | SupportedVersions must contain "5.00". Patch releases share the same major.minor value. | Add "5.00". Beta and stable builds use the same value, so rebuild beta builds against the stable tag. |
| Object mapping | AutoMapper is replaced by Mapster. | Rewrite mapper profiles and direct IMapper calls. |
| Synchronous methods | Synchronous versions of service methods move to a separate helper class. | Use the async methods, or call the helper explicitly. |
| Views | A new themeable view engine lets themes override plugin views. | Check plugin views and any theme overrides still resolve. |
| Removed members | PictureId on ProductAttributeValue and ProductAttributeCombination, RemotePost.Post() and RemotePost.Method, the core forum/news/poll services. | Search plugin code for these names before porting. |
plugin.json · a plugin built for nopCommerce 5.00
{
"SystemName": "Misc.YourPlugin",
"Version": "5.00.1",
"SupportedVersions": [ "5.00" ],
"FileName": "YourCompany.Plugin.Misc.YourPlugin.dll"
} Build against the stable release-5.00.0 tag. If you built on the beta, rebuild and test again: a DLL built on the beta can fail at runtime if a method it calls changed in a later fix. Our nopCommerce plugin development team ports custom plugins and themes to 5.00.
Should you upgrade to nopCommerce 5.0?
| Your situation | Our advice |
|---|---|
| Live store on 4.90 | Stay on 4.90.8 for now and rehearse the 5.00 upgrade on staging. Go live after the first 5.00.x patch (planned for 18 November 2026), once your plugins and theme have 5.00 builds. |
| Live store on 4.80 or older | Move to 4.90 first if you need to upgrade now; 4.90 is stable and most of the work carries over to 5.00. |
| Plugin or theme vendor | Rebuild against the release-5.00.0 tag, test, and publish your 5.00 builds. Store owners are checking for them now. |
| Store using forums, news, polls or manual payments | Plan these first: install the new plugins on staging, or choose a replacement payment method. |
| New store | Start development on 5.00 so you do not need a major upgrade soon after launch. |
Whichever path you take, the plugin list decides the date. Before upgrading, list every installed plugin and confirm a 5.00 build exists for each one. The free StorePulse plugin does this check on 4.80 and 4.90: pick 5.00 on its Upgrade readiness page and it lists the plugins without a 5.00 build, plugins whose code uses APIs 5.00 changes, and the store data on this page that needs work first, from forums and news to the Manual payment method and old email tokens.
What comes next: nopCommerce 5.10
The 5.10 milestone (opens in a new tab) is dated 15 September 2027 and has 62 open issues. Planned items include:
- Quick order form
- Import and export of discounts and gift cards
- "See price in cart" (MAP pricing)
- noindex SEO settings
- EU VAT calculation and GST/PST support
- One-page checkout
- Page builder
- Company accounts with sub-users
- Phone orders in the admin area
- Shipping rates per vendor
Milestone contents change during development, and some of these are long-standing requests that may move again.
Frequently asked questions
When is nopCommerce 5.0 released?
The stable nopCommerce 5.00.0 was released on GitHub on 27 October 2026, four weeks after the beta of 30 September. A first bug-fix milestone for 5.00.x is dated 18 November 2026.
What .NET version does nopCommerce 5.0 need?
nopCommerce 5.00 targets .NET 10. Servers need the ASP.NET Core Runtime 10.0.12 or later; on IIS that means the .NET 10 Windows Hosting Bundle. Building from source needs the .NET 10 SDK 10.0.401 and Visual Studio 2026. nopCommerce 4.80 and 4.90 run on .NET 9.
Should I upgrade my live store to nopCommerce 5.0 now?
Only when every plugin and your theme have 5.00 builds and the upgrade has passed on a staging copy. Many stores wait for the first 5.00.x patch, planned for 18 November 2026. Never use the beta for a live store: 50 of the 195 milestone issues, many of them security fixes, were closed after it shipped.
Will my 4.90 plugins work on nopCommerce 5.0?
Not without a new build. A plugin only loads when its plugin.json lists 5.00 in SupportedVersions, and it has to be rebuilt for .NET 10 against the 5.00 libraries. Plugins that use AutoMapper, synchronous service methods, the removed PictureId properties or the old payment redirect helper also need code changes.
What happened to forums, news and polls?
They moved out of the core into official plugins included with the release: Misc.Forums, Misc.News and Misc.Polls. The plugins work with the existing tables, so after upgrading you install the plugin you use. Private messages were separated from forums. Check the result on a staging copy before go-live.
Is the Manual payment method still available?
Not in the box. The Payments.Manual plugin, which collected card details in the store, no longer ships with nopCommerce 5.00. Stores that relied on it need another payment plugin before they upgrade.
Do I need to upgrade from 4.90 to 5.0 straight away?
No. 4.90 is a stable line that received patches through 4.90.8, and it keeps running on .NET 9. Plan 5.00 when your plugins and theme have 5.00 builds and you have tested the upgrade on staging.
Prepare your store for nopCommerce 5.0
Start with an inventory: your current version, every plugin and its vendor, the theme, and any core changes. Check that your host supports .NET 10, then rehearse the upgrade on a staging copy with the stable release.
If you would rather hand it over, our nopCommerce migration and upgrade services cover the assessment, plugin and theme porting, staging rehearsal and go-live. Send your current version and plugin list to contact@cartenvo.com and we will outline the path to 5.00.