Unified pricing management or the module it replaced — which are you on?

Unified pricing management or the module it replaced — which are you on?

Tier: Finance & Operations. This sounds like a question you answer by opening a menu. You cannot — and the reason is one clause in a Microsoft deprecation notice.

Why looking at the screen will not answer it

From The Pricing management module is deprecated and no longer available to new customers (ms.date 2026-04-20, updated_at 2026-07-01):

"Both the deprecated pricing management module and the Unified pricing management module use similar or identical navigation paths in the Supply Chain Management user interface, so only one of these modules can be active at a time."

Similar or identical navigation paths. Two different pricing engines, one menu structure, and exactly one of them live. A user who has always gone to Pricing management > Setup > Price component codes has no way to tell from that journey which module answered.

That also explains a common support experience: an instruction from documentation that does not match what is on screen, in a menu whose path matched perfectly.

The deprecation, in the register's words

The same statement appears in the removed or deprecated features register (ms.date 2026-06-24), under Features removed or deprecated in the Supply Chain Management 10.0.41 release → Pricing management module (preview):

"Deprecated and will be removed in a future release. It is replaced by the Unified pricing management module, which offers nearly all of the same functionality as the deprecated Pricing management module, plus several important enhancements."

The register's "Reason for deprecation or removal" row says the same in one line, and "Replaced by another feature?" answers "Yes".

The old module was never generally available. Its own title carries "(preview)", and the notice page says "previously in preview". So this is not a migration off a shipped product — it is the retirement of a preview that some tenants enabled and kept.

The test that actually answers the question

Here is the rule, and it is a clean decision procedure:

"As of Supply Chain Management version 10.0.41, if you never enabled the deprecated pricing management module in your environment, you can only use the Unified pricing management module. If you enabled the deprecated pricing management module, you can continue to use it until its removal, but transition to the Unified pricing management module as soon as possible."

So the question which module am I on reduces to a historical one: did anyone ever switch on Pricing management in this environment? If no, you are on Unified pricing management and cannot be on anything else. If yes, you may still be on the deprecated one, and nothing in the interface will volunteer that.

This is not a question your users can answer. It is a question for whoever ran feature management during your implementation — and if that was a partner engagement several years ago, the honest answer may be that nobody currently knows.

The word "nearly" is doing real work

"offers nearly all of the same functionality" is a careful phrase and Microsoft does not enumerate the gap on either page. We are not going to guess at it: we searched the register entry and the deprecation notice and neither lists what is missing, and there is no comparison table on either. If you are planning a transition, that gap is the thing to establish in a sandbox rather than infer from documentation.

The register does name the recovery: "For help transitioning from the deprecated pricing management module to the Unified pricing management module, contact Microsoft Support."

What happened to the old documentation

The clearest signal of intent is structural. The deprecated module's documentation is now a single page of 169 words whose title is the deprecation notice itself — The Pricing management module is deprecated and no longer available to new customers. We tried one of the module's old topic URLs — its concurrency page — and landed on that notice.

Where there was a documentation tree, there is a notice. If you are running the deprecated module today, its reference material is no longer available to you in the place you would look for it.

That is worth stating plainly because it changes the cost of staying. A deprecated module you can still run is one thing. A deprecated module you can still run and can no longer look up is another.

What "deprecated" means here, precisely

The register defines its own vocabulary, and it is worth quoting rather than paraphrasing:

"- A removed feature is no longer available in the product. - A deprecated feature isn't in active development and might be removed in a future update."

Might be removed. Not is being removed on a date. Unlike several other entries in the same register — which carry dates such as end-of-support deadlines and "one year after the release of version 10.0.x" — the Pricing management entry gives no removal version and no removal date. Its status text says only "will be removed in a future release".

So the honest planning position is: no deadline is published, active development has stopped, and the documentation has already gone. The absence of a date is not reassurance.

How we build it: on the supported module, and we will say so

Pricing & Discount Optimizer writes rules into Unified pricing management's price component codes, under your concurrency modes, behind an approval step. If your environment is still on the deprecated module, the honest answer is that the transition comes first — that is your implementation partner's work, not ours, and we would say so rather than build against a module with no active development.

A working demo exists; it is not off the shelf. We build it against your systems and your constraints on request, and we have no delivered pricing engagements — so this is a capability, not a report on somebody's business. We do not touch your ERP core.

Three things to check this week

1. Ask who ran feature management during your implementation, and whether Pricing management was enabled. That single historical fact determines the answer, per the quoted 10.0.41 rule.
2. Check your version against 10.0.41. The rule above is stated as of that version, and it is also the floor for the behaviour described.
3. Try to open the documentation for a screen you use. If you land on a deprecation notice rather than a reference page, that is your answer arriving from an unexpected direction.

Chapter 4 is what the supported module is made of. Chapter 8 is the tier comparison, if you are not certain you are on Finance & Operations at all.

About Cognilium Cognilium is the AI optimization layer for Dynamics 365 — complementary apps that optimize the pricing, inventory, warehouse and planning decisions your ERP manages but can't optimize. Built on Power Platform, Dataverse and Azure. https://cognilium.ai · https://www.linkedin.com/company/37180269/

Not sure which pricing module your environment is running? Book a 15-minute call — we'll walk the decision and the model with you, on your data if you bring it. No deck.

Sources

• Removed or deprecated features in Dynamics 365 Supply Chain Management
• The Pricing management module is deprecated and no longer available to new customers

Sources

• learn.microsoft.com — removed deprecated features scm updates
• learn.microsoft.com — pricing management overview