A retail worker uses a checkout computer beside a barcode scanner and folded clothing.
Dynamics 365 Commerce retailers can now bind function keys to buttons on the Store Commerce cart view. Cashiers can then trigger common register tasks without reaching for the mouse or touchscreen. Microsoft's AI at Work roadmap lists the feature as launched, with preview in July 2026 and general availability in September 2026. It names void line, price override, discount, change quantity and change delivery mode as typical candidates. The roadmap says these are estimates that can change. Microsoft Learn holds the operational details.

A retail worker uses a checkout computer beside a barcode scanner and folded clothing. What the feature does, and what it doesn't​

The key point is that shortcuts attach to buttons, not directly to POS operations. Microsoft Learn says keyboard shortcuts let associates trigger CartView button grid operations by using configured function keys. If an operation isn't on a button in the relevant grid, it has nothing to hang a shortcut on.

Microsoft's general POS documentation explains how an operation gets onto a button. An operation must be marked as a user operation in Commerce headquarters, under Retail and Commerce > Channel setup > POS setup > POS > POS Operations. Only then can it be added to a button grid in the designer.

The roadmap's example operations map onto real, documented POS operations. These include Void product (102), Price override (104), Set quantity (105), Line discount amount and percent (300 and 301) and Change delivery mode (647). Availability varies by operation. For example, the operations reference marks Change delivery mode as unavailable offline. Microsoft also says its operations table reflects the latest Commerce version and that some operations may differ in earlier versions. Test each button you plan to bind before rollout.

Version and prerequisites​

This feature sits on top of the modernized transaction grid, so there are two version thresholds.

  • Modernized grid: it applies to Commerce 10.0.42 and later. It needs Store Commerce 10.0.42 or later and the Feature management flag "Enable Modern Transaction Grid in POS Transaction View."
  • Shortcut enhancement: Microsoft's version history lists button grid keyboard shortcut enhancements under 10.0.49, along with transaction line search, multiselect cart line updates, bulk item add and Quick Operations panel improvements.

Microsoft says these 10.0.49 improvements are optional. It recommends enabling them only for the layouts, roles and store formats that benefit from faster, high-volume transaction processing.

To enable the modernized grid, administrators do the following:

  1. In Feature management, enable the modern transaction grid flag.
  2. In POS visual profiles, set Modern transaction grid to Yes for each profile.
  3. Run the Registers (1090) distribution schedule job.
  4. Restart the Store Commerce app.

Microsoft notes that the visual-profile toggle lets you pilot the change on specific registers before a broad rollout.

Configuring a shortcut​

Microsoft's documented procedure is short:

  1. In Commerce headquarters, go to Retail and Commerce > Channel setup > POS setup > POS > Button grids.
  2. Open a button grid, and then select Designer.
  3. Right-click the button to configure, and then select Button properties.
  4. In the Keyboard shortcut field, choose a supported function key.
  5. Select OK, save the button grid, and then run the Channel configuration (1090) distribution schedule job.

The 1090 job is easy to forget. Without it, the registers never receive your changes.

Which keys work​

Supported keys are F2, F3, F4, F6, F7, F8, F9 and F10. F1, F5, F11 and F12 are unsupported because the browser or system reserves them. Microsoft documents no letter keys or modifier combinations for this feature, so don't plan around them.

That is a small palette of eight keys. A store with a big button grid will have to choose which operations earn a shortcut.

Conflict checks and runtime behavior​

There are two layers of protection against clashes.

At save time. The designer won't let one function key go to two buttons in the same grid. It also checks other button grids that share at least one tile layout with the current grid and prevents conflicting assignments that could appear together at runtime. That doesn't make assignments globally unique across all grids. Grids that never share a layout can reuse a key.

At runtime. An associate opens the cart view and presses the key. If it maps to one visible, enabled button, the operation runs. If it maps to several visible, enabled buttons, a selector appears so the associate can pick the intended operation. Visibility and enabled state matter, so a key can behave differently depending on what the screen shows at that moment.

The roadmap description adds two points. Shortcuts apply to the currently selected line or lines, and users can find them through tooltips and a help screen. The Learn passage doesn't detail these behaviors, so treat them as roadmap claims. Verify them at a register.

Practical advice for administrators​

These recommendations are my own reading of the documented rules. They are not Microsoft guidance.

  • Start with the highest-volume actions. Void line, discount and quantity change are the roadmap's own examples. Eight keys go quickly.
  • Keep keys consistent across grids that share layouts. The designer's conflict check pushes you this way anyway.
  • Pair shortcuts with role controls. Microsoft says inline actions follow the same POS security roles and permissions as button grid operations. Check that a shortcut doesn't make a sensitive operation, such as a price override, easier for someone who shouldn't have it. A shortcut is a faster way to press the button. Permissions still decide who is allowed to.
  • Test after distribution. Run the 1090 job, restart or refresh a pilot register, and try each key with realistic carts, including multi-line selections.
  • Don't assume parity across clients. The Learn instructions document the CartView button grid. Microsoft's operations reference also notes that some operations aren't available in every Store Commerce variant, including Store Commerce for web. Confirm support on the clients you actually deploy.

Why this matters​

Retail POS is repetitive work. It is also a place where a cashier's hands are often on a keyboard or a barcode scanner. Microsoft has not published measured time savings for this feature, so any speed benefit is an expectation, not a figure. Still, the 10.0.49 package suggests where the modernized grid is heading. It targets large carts and trade-counter or B2B scenarios, with line search, multiselect, bulk add, Quick Operations and now keyboard shortcuts.

The limits are real. The feature offers eight keys, one grid type and a dependency on the modernized grid. It doesn't add keyboard control across all of Commerce. For stores already on 10.0.49 or later with the modern grid enabled, though, it is a low-effort configuration change. It's worth piloting on one register before you roll it out.

 

References

  1. Dynamics 365 Commerce: Map keyboard shortcuts to common POS operations Microsoft 365 Roadmap 2026-11-04T00:02:09.024784Z
  2. Online and offline point of sale (POS) operations - Commerce | Dynamics 365 | Microsoft Learn learn.microsoft.com
  3. Modernized transaction grid in Store Commerce - Commerce learn.microsoft.com