Dynamics 365 Commerce Store Commerce: Phone Cart Commands and Sales-Line Details Coming December 2026

The roadmap item is ID 577409. It is marked In development. The preview target is October 2026 and the general availability target is December 2026. Microsoft says all roadmap dates are estimates and may change.

Today is November 4, 2026. The October preview date has passed and the December GA date hasn't arrived. I haven't confirmed that the preview is live, so treat both dates as plans, not delivered facts.

Why the Cart was the odd one out​

Microsoft's POS view extension table lists the Cart view (screen layout based) as supporting custom controls and custom columns, but not custom app bar buttons. Most other listed views, such as the customer and search views, do support app-bar buttons. The POS extension overview says developers can add columns, app bar buttons and controls "depending on the view". It also says the cart view and welcome page are configured in the screen layout designer.

That split is why this roadmap item is a real expansion. Phone Cart commands now get their own registration point instead of borrowing the pattern from other views.

There is a recent precedent for this kind of change. Microsoft's modernized customer details page added app-bar command extensibility on the compact (phone) layout. Developers extend CustomerDetailsExtensionCommandBase and register under components.extend.views.CustomerDetailsView.appBarCommands. The Cart item follows the same naming pattern. As a comparison, not a documented procedure, the roadmap's Cart path is components.extend.views.CartView.appBarCommands, using CartExtensionCommandBase.

What the roadmap says about phone Cart commands​

• Registration: Extensions register commands through components.extend.views.CartView.appBarCommands, using a command class based on CartExtensionCommandBase.
• Where commands appear: On phone layouts, commands show in the existing bottom app bar and its overflow menu. This works in both legacy and React-backed Cart content.
• Lifecycle: Commands take part in Cart initialization, updates, selection changes, processing state, reuse and disposal.
• Wide layouts: Desktop and tablet Cart views are unchanged, because wide layouts don't use this app bar.
• Enablement: The extension point is available by default. It needs no headquarters switch.

The roadmap doesn't give a minimum Store Commerce version, API signatures or sample code. I won't guess at them. Once the feature ships, developers should check the Learn documentation and Retail SDK for those details.

How the existing app-bar pattern works​

The existing Learn sample for the search view shows the general shape of a view command. It is documentation for a different view, not Cart-specific guidance.

• The sample command class has an execute method that handles the button click.
• The Learn sample sets canExecute in selection handlers, and its init method sets isVisible.
• Custom views update a command's isProcessing and canExecute fields to control whether it is enabled and visible.

The roadmap's lifecycle list (initialization, selection changes, processing state, disposal) fits that model. Treat the Cart specifics as unconfirmed until the SDK documentation is published.

Additional sales-line details​

The second half of the item is administrator-facing and lives in the Commerce headquarters Screen layout designer.

1. Open the screen layout designer and go to Receipt > Lines > Additional information.
2. Select the subfields you want. Built-in and extension fields are both supported. The same selection pattern applies to compact and desktop layouts.
3. Save the screen layout.
4. Run distribution schedule job 1090 (Registers) to deploy the configuration.

Selected fields appear beneath each sales line in the order you configured. That keeps the main grid's width intact. Desktop rendering is supported in classic Knockout, modern Knockout and React transaction grids.

No fields are selected automatically. Existing layouts won't change until an administrator opts in.

Learn already describes a similar idea for other views. The POS view extension page says some views support custom columns through row sub fields. Those appear as rows instead of columns, like info code messages, serial numbers or discount values. The roadmap applies a comparable below-the-line pattern to the transaction Cart.

Practical impact and testing advice​

For developers

• Treat phone as the only target. The roadmap gives no sign that a Cart command will appear on tablet or desktop.
• Test visibility, enabled and processing states, selection changes and cleanup in both legacy and React-backed Cart content.
• Check whether the overflow menu behaves sensibly when you add several commands.

For administrators and retail operations

• Pick additional fields deliberately. The roadmap names no field-count limit, so don't assume one.
• Remember the deployment step. Saving the layout isn't enough without the 1090 (Registers) job.
• Don't expect the app-bar extension to need a headquarters toggle. Only the sales-line fields need layout configuration and distribution.

What's still unknown​

• Whether the preview is available to your tenant. The roadmap record lists Worldwide (Standard Multi-Tenant) as the only cloud instance.
• Which fields can be selected, and how extension fields are registered for sales-line display.
• Whether every extension field works in all three desktop grid implementations.
• The minimum Store Commerce version.

One caution about the platform listing: the roadmap record lists "Web" as the platform, while the item discusses Store Commerce POS. The Learn overview describes Store Commerce for web as a cloud-deployed app, and the Store Commerce app as a Windows app from Microsoft Store. The roadmap doesn't say how the feature applies to each, so confirm that against official release notes before planning a rollout.

Bottom line​

This is a targeted but useful extensibility fix. Phone-based retail staff get custom Cart actions, and desktop users and administrators get a configurable way to show more line detail without squeezing the grid. Developers and retail IT teams should plan around the December target. They should also watch for the SDK documentation, since the roadmap alone doesn't give enough detail to build against.