Untangle the Ucommerce shop you already have

Ucommerce Classic is not Umbraco Commerce. Umbraco did not buy Ucommerce. We will tell you which product you are actually on, what the CMS under it is doing, and whether Next Gen is the job — or leaving is.

Book a free 30-minute discovery callTalk through your Ucommerce shop

Australian .NET team. We look at the shop before anyone talks about a rebuild.

Still running Ucommerce?

The shop still takes orders. That is why it has been left alone.

Ucommerce is a Danish .NET commerce platform. For years it was sold as the commerce engine inside Umbraco and Sitecore. The current product is Ucommerce Next Gen — a standalone, headless-friendly platform that can sit next to a CMS, rather than living inside one. The line you are probably on is Ucommerce Classic, including v9.

You might recognise one of these:

  • The shop is “Ucommerce for Umbraco 7” or “Ucommerce for Umbraco 8”
  • Someone said Ucommerce is now called Umbraco Commerce
  • Sitecore still hosts the storefront, on an old Commerce Connect package
  • Custom pipelines and Castle Windsor-style DI are the real product
  • The CMS under the shop is already end-of-life, and nobody is sure which clock to watch
  • You are not sure whether to stay in the Ucommerce family or leave it

You do not need a new brand, or a SaaS pitch. You need a clear read on the shop you already have — and the CMS it is bolted to.

Why these shops stall

Ucommerce is still a real vendor. Next Gen is actively released. The problem is rarely “Ucommerce vanished”. It is two products, two invoices, and a Classic install that does not paste into the current one.

Two clocks

Classic embed

Name trap

Custom pipelines

Ucommerce is not Umbraco Commerce.

They are different products from different vendors. Umbraco HQ acquired Vendr (Outfield Digital) in July 2023 and renamed it Umbraco Commerce. That is a Vendr lineage. It is not a rebrand of Ucommerce, and HQ will not support a Ucommerce Classic database. Buying the Umbraco add-on does not pick up your Classic shop. If someone sold you that story, the first job is to unwind it.

You may be on two clocks.

Commerce is Ucommerce. The CMS is Umbraco or Sitecore. Umbraco 7 has been end-of-life since 30 September 2023. Umbraco 8 has been end-of-life since 24 February 2025. Ucommerce’s own writing has said not to remain on Umbraco 8, and treats Classic → Next Gen as the commerce path. They have not posted a Classic calendar end date on the pages we rely on. Sitecore support for old Classic packages is per-package — “Sitecore is enterprise” is not a support statement.

Classic is Framework-era and CMS-embedded.

Next Gen is a new host application: different templates, Docker-friendly, CMS-optional, current Microsoft stack. The vendor migration guide is not a DLL swap. You upgrade the database to the latest Ucommerce 9 first — if you are not on v9, they say contact them — then install Next Gen templates and migrate data. Custom pipelines, dependency injection, and data-access code are manual. That custom layer is usually why Ucommerce was chosen. It is also the work.

Keeping the old CMS is a transition, not a destination.

Ucommerce lists pointing Next Gen at an existing Umbraco site, then moving the CMS later. On Umbraco 7 or 8 that is a double migration unless you treat the old CMS as temporary. A 2024 Ucommerce post that pointed CMS upgrades at Umbraco 13 is now time-limited: Umbraco 13 itself ends 14 December 2026. Do not land a 2026 project there.

None of that makes the catalogue, prices, or order rules worthless. It does mean “install the Umbraco Commerce add-on” and “drop in Next Gen over the weekend” are both the wrong first move.

How we work

We start with the shop and the CMS, not with a destination.

1

Look at what you have

Ucommerce line (Classic / v9 / already Next Gen), which CMS and version, custom pipelines and DI, catalogue and price customisations, and how the two products are licensed. We will tell you which product you are actually on.

2

Decide the job

There are three honest outcomes. We recommend one, not all three.

3

Do the work in stages

Get to a current Classic v9 database if you are staying in the family, then migrate data into Next Gen. Custom pipelines get rewritten, not pasted. Unused accelerators do not come across.

4

Hand it back so the next person can run it

Source, a short record of what changed, and a shop someone else can understand.

Three honest outcomes

  • Move to Ucommerce Next Gen, keep or later replace the CMS. That is the vendor’s documented path, including a transitional “point Next Gen at the existing CMS”.
  • Change commerce product — Umbraco Commerce on a supported Umbraco LTS, another headless engine, or a full replatform — if you are willing to leave the Ucommerce data model. There is no official Ucommerce → Umbraco Commerce converter we can cite.
  • Stabilise first when the two clocks are unclear: document Classic customisations, confirm licences, and plan the commerce move and the CMS move as separate jobs.

We will not tell you Ucommerce became Umbraco Commerce. We will not tell you WordPress is the answer to every Classic shop. If you already know you want to stay with Ucommerce forever, the vendor’s own Hypercare and migration services may be a better fit. If you want an honest fork in the road, talk to us.

What we need for the first call

A URL and a rough Ucommerce / CMS pair is enough to start.

  • Which Ucommerce line: Classic (including v9) or Next Gen
  • Which CMS it sits in — Umbraco 7, 8, or later, or which Sitecore version
  • Whether someone has already bought Umbraco Commerce by mistake
  • Which pipelines, price rules, and DI customisations are load-bearing
  • Whether you are already on latest Classic v9
  • Hosting today (old Windows / IIS, Docker, someone else’s box)
  • What “done” looks like: stay with Ucommerce, change product, or get a clear picture first

The first call is 30 minutes. You leave with a recommendation you can take to a manager, not a rebuild estimate pulled from thin air.

Related work

We have taken over and modernised ageing .NET systems for Australian organisations, including work with Data#3, Hastie, NESS, and NSW Health. NESS is nopCommerce and Dynamics NAV — related commerce work, not a Ucommerce or Sitecore commerce case study. A Classic shop still starts with its own assessment. We will not pretend it is a project we have already published.

FAQ

Is Ucommerce the same as Umbraco Commerce?
No. Ucommerce is still an independent vendor. Umbraco Commerce is the 2023 rebrand of Vendr, after Umbraco acquired Outfield Digital. Different product, different database, different support desk.
Is Classic already switched off?
Not on a published calendar date we can cite. What we can say: the vendor does not recommend remaining on Umbraco 8, treats Next Gen as the commerce path, and Classic custom code does not paste into that path.
Can we just install Next Gen over the existing shop?
No. The documented path is latest Ucommerce 9 first, then a new Next Gen application and a data migration. Pipelines and DI are a rewrite.
Do we have to leave Ucommerce?
No. Next Gen is the current product. Leaving only makes sense when you also want to leave the data model, or when both the CMS and the commerce engine are past the point of a staged move.
We only have the live shop and an old Umbraco 8 box.
That is common. Bring that.

Talk through the Ucommerce shop you already have

Thirty minutes. Bring a URL and which CMS it sits in. We will tell you whether to move to Next Gen, change commerce product, or leave it alone for now.

Book a free 30-minute discovery call