Dynamics 365 Commerce Modern Customer Details: React POS, Setup and Address Validation

Listed on the Microsoft AI at Work Roadmap under ID 576753 with a General Availability target of October 2026 for Worldwide Standard Multi-Tenant environments, this update—referred to in roadmap materials as the modernized Customer Data Platform (CDP) panel and in technical documentation as the modernized customer details page—overhauls how retail staff view customer history, capture addresses, and act on product recommendations during assisted selling. Because roadmap listings represent development targets that remain subject to change, IT administrators and retail system architects should pair the roadmap overview with Microsoft Learn's technical preview documentation for Dynamics 365 Commerce versions 10.0.48 and 10.0.49, where the underlying mechanics, feature flags, and version boundaries are already detailed.

Why Legacy POS Screens Fail Modern Assisted Selling​

Store Commerce is Microsoft's modern point-of-sale (POS) platform for Dynamics 365 Commerce, handling everything from standard cash-and-carry checkouts to endless aisle ordering, inventory lookup, and clienteling across fixed and mobile devices. However, the legacy customer details view carried structural friction. Critical context—such as loyalty points, past purchases, preferences, and product recommendations—was scattered across multiple screens, forcing associates to leave the active sales context or hunt through separate management views.

Creating or editing a customer profile was similarly fragmented. Under the legacy workflow, creating a customer record and adding their primary address required a two-step process with separate save operations. If an associate got distracted by a growing checkout queue halfway through, the retailer often ended up with an incomplete customer profile. In jurisdictions with strict fiscal compliance rules—where a complete, validated primary address is legally mandatory on customer records—missing that second save step meant compliance headaches and administrative cleanup after the transaction closed.

Inside the React-Based Customer Details Experience​

The modernized customer details experience replaces the legacy view entirely once enabled; administrators cannot run both the legacy and modernized views side by side. Rebuilt using React and Fluent UI, the interface uses a component-based architecture that adapts automatically to the device form factor:

• Desktop Layout: Renders a full-width header card featuring the customer's image, name, and contact details alongside a horizontal command bar (CustomerDetailsCommandBar) with labeled action buttons.
• Mobile and Phone Layout: Switches to a vertical-scroll, touch-friendly design with a compact header and a simplified action bar. To keep small screens uncluttered, every command bar action except Add to sale is tucked into a More actions drawer, while quick communication links—like tapping a phone number to call—remain directly accessible in the header.

In Microsoft's roadmap description for the CDP panel, the interface is designed to surface a high-level customer summary (loyalty points, purchase frequency, average spend, and contact info), inline transaction history showing the items, channel, and location, a "buy-again" workflow for frequently purchased items, a chronological interaction timeline, and inline product recommendations.

Microsoft Learn's documentation for Dynamics 365 Commerce version 10.0.48 and 10.0.49 shows how these capabilities are structured across four fixed content tabs managed by a Fluent UI TabList wrapper, with each tab preloading key data to minimize lag:

At the top of the workflow, the primary command bar focuses on three immediate actions: Add to sale (attaching the customer to the current cart and returning to the cart view), Add to client book, and Edit account. At the bottom of the page, a Recommended products carousel displays AI-suggested products—up to 30 items in a Fluent UI previous/next carousel on desktop, or up to 10 items in a horizontally scrollable card list on mobile—each equipped with a direct Add to sale button. While the roadmap notes that surfacing timely recommendations and spending summaries is intended to drive higher basket values and reduce associate training time, IT leaders should treat those outcomes as Microsoft's business-value goals rather than guaranteed metrics, and note that the underlying Copilot customer insights engine itself is unchanged from prior releases.

Streamlined Customer Creation and the Address Validation Nuance​

Associates can enter the modernized customer experience either by selecting a customer from Customer search or by opening the panel directly inside an Active transaction. Furthermore, version 10.0.48 adds a New customer shortcut directly on the transaction page toolbar, allowing staff to spin up a new profile without abandoning a live cart.

When creating or editing a customer, the modernized workflow (also built on React and Fluent UI with skeleton loading) consolidates Customer information, Contact information, and Address into a single view. Associates fill out the profile and primary address together and commit both in a single save action. If the associate launched the creation flow from the transaction screen, they can select Save and add to transaction to commit the record and immediately attach the new customer to the active basket, bypassing the customer details screen altogether.

Retailers evaluating this feature for regional tax and fiscal compliance need to pay close attention to how address validation is configured in practice:

1. Roadmap Description vs. Current Architecture: The roadmap entry describes inline mandatory address validation as an opt-in feature configured at the channel level to ensure fiscal compliance before a record is committed.
2. CSU Flight Requirement in 10.0.48: According to Microsoft Learn's documentation for the modernized creation and editing workflow in version 10.0.48, mandatory Address completeness—which blocks saving a customer record unless an associated address is completed—is controlled by a Commerce Scale Unit (CSU) flight and is not enabled by default. Organizations must contact Microsoft support to enable this CSU flight for their environment.
3. Regex Name Validation: For organizations with strict formatting rules, version 10.0.48 also supports configurable name pattern validation using regular expressions (regex) defined through POS extensions, prompting associates inline if an entered name violates the required pattern.

In version 10.0.49, address handling on the Account details tab matures further. Associates can use the overflow (...) menu on the Shipping addresses tile to Edit, Set as primary (which unmarks the previous primary address after a confirmation prompt), or Remove (which soft-deletes/deactivates the address after confirmation). Every change refreshes the address tile in place without reloading the page or resetting the current tab, and the standalone React-based Manage addresses view now integrates cleanly with the cart shipping workflow. Version 10.0.49 also fixes a notable regional bug so that shipping addresses outside the United States render in their proper regional formats.

Custom Attributes, Visual Profiles, and Extensibility​

Retailers rarely rely solely on stock name-and-address fields; clienteling depends on tracking membership tiers, sizing preferences, or loyalty specifics. The roadmap highlights a conditional Custom information tab that appears only when custom attributes are configured for a customer record, keeping the interface clean for retailers who do not use them. In Microsoft Learn's documentation, customer attributes appear within the Account details tab (and can be edited in version 10.0.49), while custom controls defined by developers for CustomerDetailsView automatically render inside a conditional Additional tab.

For administrators and developers planning an upgrade, there are concrete technical boundaries and setup procedures to follow:

• How to Enable the Feature: The roadmap notes that once the feature flag is turned on in Commerce headquarters, no register-level configuration is required. However, Microsoft Learn specifies the exact operational sequence required to push that flag to stores:
  1. Ensure your Store Commerce app is running version 10.0.48 or later.
  2. In Commerce headquarters, navigate to System administration > Workspaces > Feature management.
  3. Search for Enable modernized customer details page and click Enable now (this single flag activates both the modernized customer details page and the modernized customer add/edit view).
  4. Run distribution schedule job 1110 (Global configuration) to synchronize the change to channel databases.
  5. Restart the Store Commerce application.
• No-Code Layout Customization (Version 10.0.49+): Starting in 10.0.49, administrators can show, hide, and reorder page sections—and individual components within paired sections like Addresses & Loyalty cards or Affiliations & Attributes—without writing code. In Commerce headquarters, go to Retail and Commerce > POS setup > POS profiles > Visual profiles, open your store's visual profile, and under Usability options on the General FastTab, set Enable customer detail page layout to Yes. After arranging sections in the Customer detail page grids, save the profile and run distribution schedule job 1090 (Registers). Hidden sections leave no blank space on POS terminals, and the four main tab names remain fixed.
• Developer Extensibility Compatibility: Existing POS extensions built for the legacy customer details and add/edit views continue to work without code modifications. Developers can extend CustomerDetailsExtensionCommandBase (under PosApi/Extend/Views/CustomerDetailsView) to add app bar commands and subscribe to lifecycle message handlers (initializeHandler, affiliationAddedHandler, loyaltyCardsLoadedHandler, and wishListsLoadedHandler), or extend CustomerAddEditExtensionCommandBase and CustomerFieldDefinitions for the creation form.

By moving Store Commerce's customer management workflows onto React and Fluent UI, Microsoft is eliminating the screen-jumping and double-save rituals that slow down retail associates on the shop floor. For Dynamics 365 Commerce administrators, the key to a smooth rollout is testing the Enable modernized customer details page flag alongside versions 10.0.48 and 10.0.49 in a sandbox environment, verifying how existing POS extensions behave in the new component lifecycle, and coordinating with Microsoft support early if CSU-flighted address completeness is part of your compliance checklist.