What the roadmap says
The roadmap entry is for Point of Sale (Store Commerce). It describes a purpose-built panel on the transaction screen that replaces a generic button grid for a handful of common tasks. Its examples are manual discount amount, manual discount percentage, transaction comments and customer purchase order numbers.
According to the entry:
- A store admin configures the control in the screen layout designer in Commerce headquarters.
- Operations are chosen per screen layout.
- The control respects POS permissions and hides or disables actions based on user access.
- Operations use the same workflows as the button grid.
- Custom fields and operations can be added, so merchants can show extension fields next to built-in ones.
- When nothing is configured, the panel shows an empty state.
The roadmap lists the item as In development. It shows preview in July 2026 and general availability in December 2026, for the Web platform and the Worldwide (Standard Multi-Tenant) cloud. Microsoft says roadmap dates are estimates and can change.
What the documentation already says
The roadmap status is not the full picture. Microsoft's Commerce 10.0.49 (July 2026) release notes list a "Quick Operations panel in Store Commerce." The panel surfaces frequently used transaction-level fields directly on the transaction page, so associates can complete common tasks without opening the button grid.
The modernized transaction grid's version history lists Quick Operations panel improvements under 10.0.49. Microsoft's documentation page, last updated November 4, 2026, also credits Commerce 10.0.50 with sales order header attributes in Quick Operations.
My reading: the December 2026 roadmap date is an estimate, and it may track a different rollout milestone than the one the documentation describes. Treat the roadmap status and the documented version availability as separate facts. Check which Commerce version your environment runs before you plan around either one.
Built-in fields and attributes
Microsoft's documentation names four built-in fields: total discount percentage, total discount amount, notes and customer PO number. In the customization dialog they appear as Discount %, Discount amount, Notes and Customer PO number.
Those labels differ slightly from the roadmap wording ("manual discount" and "transaction comments"). I'd rely on the documented labels when you build your layouts.
In Commerce 10.0.50 and later, you can also add sales order header attributes that are assigned to the channel. Associates can then view and edit merchant-defined transaction information without opening the transaction attributes dialog. You have to define the attributes, assign them to the channel and run the required distribution jobs first.
Each field uses the same runtime operation and validation as the matching button grid operation. The panel is a second way to reach existing workflows. Microsoft does not say it changes the underlying business rules.
Prerequisites
Quick Operations belongs to the modernized transaction grid. To use it you need:
- Dynamics 365 Commerce version 10.0.42 or later, and Store Commerce app 10.0.42 or later.
- The feature Enable Modern Transaction Grid in POS Transaction View, turned on in Feature management (System administration > Workspaces > Feature management).
- Modern transaction grid set to Yes in each relevant POS visual profile.
- The Registers (1090) distribution schedule job run to push the changes to channels.
- A restart of the Store Commerce app.
The documentation notes that the visual profile toggle lets you roll the grid out to specific registers before enabling it broadly. Microsoft also says the throughput improvements, Quick Operations included, are optional. It suggests enabling them only for the layouts, roles and store formats that benefit from faster high-volume work.
Note that the base grid works from 10.0.42, but individual capabilities have their own minimum versions. The Quick Operations panel is tied to 10.0.49 and later, and the attribute support to 10.0.50 and later.
How to configure the panel
- In Commerce headquarters, go to Retail and Commerce > Channel setup > POS setup > POS > Screen layouts.
- Open the screen layout you want to change and launch Screen Layout Designer.
- Add the Quick Operations control to the transaction page layout.
- Open the Quick Operations customization dialog.
- Select the fields to show and put them in the order you want. You can mix built-in fields with channel-assigned sales order header attributes.
- Save the layout, then run the Registers (1090) distribution schedule job to push it to stores.
The layout is the unit of configuration. A cashier-facing layout can show a short list, while a back-office or B2B counter layout can show more. Changes reach registers through the distribution job, so don't expect them to appear instantly.
What associates see at runtime
Associates type or change values directly in the panel. Enumerated attributes offer a list of configured values, and other supported attributes use text entry.
- Each row saves independently.
- Save is available only when a value is valid and has changed.
- If an operation is canceled or rejected, the entered value is kept and the standard error message appears.
In practice, a rejected discount doesn't wipe what the cashier typed, so they can correct it instead of starting over. Because rows save one at a time, a PO number can be committed without touching the discount fields.
A caveat on permissions
The roadmap says the control respects POS permissions. The Microsoft documentation I reviewed states permission parity explicitly only for inline line actions, which use the same POS security roles as button grid operations. The Quick Operations section says its fields share the matching button grid operation's workflow and validation. It does not repeat the permission statement.
The roadmap claim is plausible given that shared runtime. Still, test it in a non-production environment before you rely on it for sensitive operations such as total discounts. Check with a low-privilege role, and don't assume a field will be hidden for that role.
Why it matters
Large carts and trade-counter sales often need a PO number, a note and an order-level discount on almost every transaction. Putting those fields on the screen saves associates from navigating button grids. The attribute support in 10.0.50 matters most to retailers who capture custom order data at the register.
The limits are real too. The panel is optional and works only on the modernized grid. It reuses existing operations, so it won't fix a badly designed approval process. Anything that was awkward to configure per layout stays awkward.
Checklist for admins
- Confirm your Commerce and Store Commerce versions: 10.0.49 or later for the panel, and 10.0.50 or later for order attributes.
- Enable the modern transaction grid on a pilot visual profile first.
- Pick two to four fields per layout and keep the order consistent across stores.
- If you use attributes, define them, assign them to the channel and run the distribution jobs before you add them to the layout.
- Run Registers (1090) after saving, then test with the roles your cashiers actually use.
Quick Operations is a modest feature. It is aimed at fewer clicks and fewer trips through nested menus. Its documentation is ahead of its roadmap listing, so verify your versions before you plan the rollout.
Correction (November 13, 2026): The article originally said to run the "Channel configuration (1090)" distribution schedule job after saving a screen layout. The distribution job numbered 1090 is Registers; Channel configuration is job 1070. The corrected text now names the Registers (1090) job, which is the job Microsoft Learn specifies for pushing saved screen layout changes to registers.