Dynamics 365 Commerce 10.0.48: Configure POS Inline Actions and Custom Operations

Whether a register sat at a high-speed grocery lane, a luxury boutique, or a B2B trade counter, every store, role, and screen layout got the exact same inline list. Worse yet, custom operations built by partners or independent software vendors (ISVs) through the POS extension framework couldn't be placed on that inline menu at all, even with developer intervention.

With the general availability of inline actions extensibility (tracked under Microsoft Roadmap ID 576816 and documented in Microsoft Learn as a Dynamics 365 Commerce version 10.0.48 enhancement ), Microsoft has removed that limitation. Retailers and implementation partners can now configure which inline actions appear on transaction line items, dictate their exact display order, and integrate custom POS operations directly from the Screen Layout Designer in Dynamics 365 Commerce headquarters—without writing code or running a software deployment to alter the menu.

What Retailers Can Now Configure​

Instead of forcing associates to dig through nested button grids for routine or specialized line-item adjustments, administrators can tailor the inline menu to match specific store formats or associate roles. According to Microsoft Learn's documentation for the modernized transaction grid, three core elements are configurable per screen layout:

• Action Selection: Administrators can pick any eligible out-of-the-box POS operation—such as voiding a product, returning an item, applying a line discount, overriding a price, adding a coupon or line comment, changing a unit of measure, adding a serial number, or changing a delivery method—alongside any custom operation registered in headquarters.
• Display Sequence: You can order the list so the highest-frequency actions for a specific layout sit right at the top, minimizing scrolling or hunting during a live transaction.
• Custom Extension Operations: Operations created via the POS extension framework can now live side-by-side with standard operations in the same inline menu, giving partners and internal developers a unified surface for bespoke workflows.

Section Summary: Retailers are no longer stuck with a one-size-fits-all inline menu; admins can curate and sort both standard and custom POS operations on a layout-by-layout basis.

Prerequisites and Version Boundaries​

Before you go looking for the configuration panel in headquarters, make sure your environment meets the technical baselines. Inline actions extensibility is strictly tied to the modern React-based transaction grid; the legacy transaction grid does not support it.

To use this capability, your environment requires:

• Dynamics 365 Commerce and Store Commerce versions: While the foundational modernized transaction grid applies to version 10.0.42 and later, Microsoft Learn's version history specifies that inline actions extensibility per screen layout requires Commerce version 10.0.48 or later.
• Feature Management Flags: The modern transaction grid must be turned on in Dynamics 365 Commerce headquarters under System administration > Workspaces > Feature management. Note that Microsoft's documentation references this flag in two ways: the release plan lists the internal feature class name RetailModernTransactionGridFeature ("Modern transaction grid"), while the Microsoft Learn setup guide displays the workspace UI label Enable Modern Transaction Grid in POS Transaction View. (If you haven't rolled out the modern grid yet, it also must be toggled to Yes under Retail and Commerce > Channel setup > POS setup > POS profiles > POS visual profiles, followed by running the Registers (1090) distribution job and restarting the Store Commerce app.)

Step-by-Step: Configuring Inline Actions in Headquarters​

Once your environment is on version 10.0.48+ with the modern transaction grid active, rolling out a custom inline action list is a straightforward administrative task in Commerce headquarters:

1. Navigate to Retail and Commerce > Channel setup > POS setup > POS > Screen layouts.
2. Select the target screen layout you want to modify and launch the Screen layout designer.
3. Click the transaction grid component within the layout and open the inline actions configuration.
4. Add your desired out-of-the-box or registered custom operations from the available list, remove any clutter that associates don't need, and set the display order.
5. Save the screen layout.
6. Run the Channel configuration (1090) distribution schedule job to push the updated layout out to your store channels.

The updated inline menu will appear in Store Commerce as soon as the register downloads the new layout configuration.

Backward Compatibility, Security, and the "No-Code" Reality Check​

From an enterprise deployment perspective, the best news about this update is how safely it handles existing setups. Do you need to rush and configure every layout before upgrading? Not at all.

If you do not configure inline actions for a screen layout, Store Commerce simply keeps displaying the default out-of-the-box inline action list. When you do configure a list for a specific layout, it overrides the defaults for that layout only, leaving every other screen layout across your retail channels untouched. This lets IT teams pilot a streamlined cashier layout in a single store format or region before committing to a wider rollout.

Additionally, surfacing an operation inline does not bypass your security posture. Inline actions obey the exact same POS security roles and permission model as standard button grid operations. Administrators can still use role-based access controls to lock down sensitive tasks—like price overrides or line voids—to store managers, while giving front-line cashiers a clean, restricted set of everyday actions.

However, it is worth reading past the marketing gloss on Microsoft's "no code, no deployment" phrasing. While arranging the menu in Screen Layout Designer requires no code, building a custom POS operation in the first place still requires developer work in the POS extension framework. Furthermore, localization behaves differently depending on the operation type:

• Out-of-the-box operations: Automatically localized using existing POS resource strings with no extra effort.
• Custom operations: Automatically fall back to the static operation name configured in headquarters. If your stores operate across multiple languages and require localized display labels for custom actions, developers must still supply resource files and operation mappings inside the POS extension code.

Section Summary: The feature is non-disruptive to existing layouts and respects standard POS role permissions, though multi-language retailers will still need developer support to localize custom operation names.

Broader Context: Store Commerce's Push for Checkout Speed​

This update is one piece of a much broader UX modernization campaign across Dynamics 365 Store Commerce. By moving the POS transaction page onto React and Fluent UI, Microsoft has been steadily chipping away at nested menus and modal dialogs. Between versions 10.0.42 and 10.0.49, Microsoft has layered in inline quantity updates, cart-line product images, threshold discount bars, and—in 10.0.49—high-throughput B2B tools like transaction line search, multiselect cart line updates, and bulk item entry.

Giving administrators layout-level control over inline line actions closes an obvious usability gap in that modernization effort, ensuring that both standard retail operations and third-party POS extensions are never more than a tap or hover away.