nopCommerce 4.70 arrived on April 26, 2024, moving the platform to .NET 8.1 That gives store owners a worthwhile reason to discuss support, compatibility and performance.
It does not tell us whether your particular store is ready to upgrade.
The core platform is one member of the household. Plugins, a custom theme, modified workflows and external integrations all have belongings in the hallway. Moving one person doesn’t automatically pack everyone else’s boxes.
I’d treat the release as the beginning of a decision, with the store’s actual operating dependencies in view.
Separate the platform benefit from the project benefit
.NET 8 brings runtime and library improvements, along with a long-term-support basis. Those are meaningful capabilities underneath the commerce platform.
Stephen Toub’s performance analysis demonstrates many improvements in specific operations.3 It doesn’t forecast the speed of a customized store. A slow query or shipping call may still dominate the customer’s wait.
Upgrade when the dependencies have a credible path
Inventory the plugins and custom behavior the store relies on. Check support for the target nopCommerce version and identify anything that needs updating, replacing or rebuilding.
A plugin being available for purchase is different from a verified compatible version of the one installed. Record the exact component and the work required.
Then include the theme, scheduled tasks, authentication and deployment environment. If a checkout integration is essential, its readiness matters more than the fact that an unrelated page builds successfully.
This isn’t a reason to fear upgrades. It is how you turn a vague estimate into work somebody can complete.
As nopCommerce Silver Partners, we’ve put this into practice. See the nopCommerce store we built for Freddy’s Jewelry.
Prepare first when the store cannot yet prove readiness
Sometimes the upgrade is sensible but the project isn’t ready to execute. An undocumented customization, missing staging data or untested recovery process can justify a preparation phase.
That phase should produce something useful: a compatibility inventory, representative test workflows and a rehearsal environment.
Avoid leaving it at We should probably wait. Name the missing evidence and who will supply it. Otherwise, a temporary pause can become the store’s long-term technology strategy by accident.
Rehearse the work the store actually does
A successful test purchase is important. It is not the whole commerce operation, especially where customer roles, shipping rules or staff actions differ.
Use representative journeys. Include a returning customer, the relevant payment and shipping options and the back-office work that follows the order.
Worth reading next: nopCommerce 4.80 and the parts of an upgrade the release notes cannot see.
Let exceptions into the rehearsal
Try a failed payment, a changed address and a canceled order where those apply. Check exports, notifications and records used by staff.
Compare the result with the required business behavior, rather than accepting every old behavior as correct. An upgrade can expose an existing bug; that needs investigation, not automatic restoration out of nostalgia.
Agree how database changes, backups and any rollback would work before the release window. Recovery must account for real transactions made after a change, not simply assume a backup makes time reversible.
The technical team should explain the plan in language the business can use.
An upgrade recommendation should therefore name its purpose, dependency work, acceptance criteria and operating impact. If the main benefit is supportability, say that. If performance is promised, measure the relevant workload before and after.
Zulu Shack recommends making that distinction explicit in the proposal. A store can benefit from a well-planned upgrade without every release feature becoming part of the project.
Once the dependencies fit and the rehearsal passes, choose a release window the team can support. Then check the important journeys again in the actual environment.
Version 4.70 can be a useful step forward. The satisfying part is a store that remains dependable after it takes that step, with everyone’s boxes accounted for.