The roadmap entry is thin on detail, so this article separates what Microsoft has said from what it hasn't.
What the roadmap entry says
- Feature: Item margins will be visible on carts and orders, in both the POS app and the APIs.
- Product: Dynamics 365 Commerce, under Unified Pricing Management.
- Status: The roadmap lists it as "In development."
- Timing: Preview is listed for October 2026 and general availability for December 2026.
- Scope fields: The entry lists the Web platform, the Preview and General Availability rings, and the Worldwide (Standard Multi-Tenant) cloud.
Microsoft's roadmap page carries its usual caveat. Dates and descriptions are estimates and all information is subject to change. That caveat is the one to keep in mind here. The entry was published on November 5, 2026, yet it is still marked "In development" while listing an October preview date. That doesn't prove a delay or a launch. Treat October and December as targets, not announcements.
What the roadmap doesn't say
The entry leaves out several things an admin or developer would need before planning anything:
- How margin is calculated, and from which cost basis.
- Which roles can see margin, and whether it appears per line or as a total.
- Which API endpoints or response fields will carry the data.
- Whether it needs a particular Commerce version or a completed pricing migration.
- How it behaves offline or in older POS builds.
It also doesn't describe a margin floor, a discount block or an automatic price change. As described, this is visibility, not enforcement. Treat it as decision support for the person at the register, not a safeguard against bad discounts.
Where it fits in Unified Pricing Management
Microsoft's Learn documentation describes Unified Pricing Management migration as a preview feature. It helps customers move from the legacy Commerce pricing engine to the unified framework. The documentation says you must be running Commerce version 10.0.46 to use it. It also says the migration is split into three incremental phases across versions 10.0.46 to 10.0.48. That Learn page warns that preview features aren't meant for production use.
Those statements apply to the migration feature. Microsoft has not said that margin visibility depends on 10.0.46 or on a finished migration. Don't assume it does.
The developer angle
Microsoft's POS API reference shows that the surface where margin data would appear already exists. It includes GetCurrentCartClientRequest. It also includes operations such as PriceOverrideOperationRequest, LineDiscountAmountOperationRequest and LineDiscountPercentOperationRequest. Extension authors already use these to read carts and change prices and discounts. Microsoft hasn't said which of them, if any, will change or return margin data.
For teams with POS extensions, the practical step is to wait for release documentation. Then check how the new data affects any custom code that reads carts or applies overrides.
Related margin work in Supply Chain Management
Separate coverage from the M365 Admin site describes a related Unified Pricing Management capability. It adds margin checks to price overrides. Margin visibility is built into the price override workflow for orders entered through Commerce Scale Unit or POS. The same coverage says that a price override that breaches a defined margin threshold triggers an approval workflow before the order can proceed. That is a different item from roadmap 577410, and the roadmap doesn't link the two. Still, it shows Microsoft working on both showing margin and acting on it. If the margin-visibility feature turns out to work alongside those threshold checks, the combination would matter more than either alone. That is speculation until Microsoft documents it.
What retail IT teams should do now
- Note the preview and GA estimates, and don't plan around them as commitments.
- Check which Commerce version you run, since Unified Pricing Management migration is documented for 10.0.46 and later.
- List your POS extensions that touch carts, discounts or price overrides.
- Decide, ahead of the documentation, which roles should be allowed to see margin. Margin data is commercially sensitive, so an associate-facing display is a policy question as well as a technical one.
- Watch the roadmap and Learn for permissions, API schemas and calculation rules.
Bottom line
Showing margin at the point of sale is a sensible addition for retailers using Unified Pricing Management. The roadmap entry gives only the headline, though. Until Microsoft publishes details, plan for the feature but don't commit to a rollout.