Product and roadmap perspective as of October 19, 2026.
Point of sale is no longer just the final step in a retail sale. It is increasingly the place where customer information, pricing, inventory availability, payments, and fulfillment decisions come together. For Microsoft Dynamics 365 Commerce, the 2026 release cycle reinforces that direction: a more modern selling experience at the front counter, deeper connections across channels, and capabilities with relevance well beyond traditional retail.
That evolution deserves attention from distributors. A contractor arriving at an electrical supply branch, an HVAC technician collecting replacement parts, or an industrial buyer placing a replenishment order needs more than a cash register. The counter must support a relationship built around the customer’s account and connect the immediate transaction to a broader order and fulfillment process. The opportunity is to evaluate Dynamics 365 POS not simply as retail checkout software, but as a potential workspace for serving distribution customers.
Where Dynamics 365 POS stands today
The current POS experience is the Store Commerce app within Dynamics 365 Commerce. It uses Commerce Scale Unit to connect the selling experience to shared commerce business logic, including pricing, products, customers, and orders. Its scope extends beyond payment acceptance to assisted selling, customer orders, inventory operations, returns, and fulfillment. Supported deployment configurations also provide offline operation, although not every workflow is available offline. This article concerns Dynamics 365 Commerce, not a POS extension for Business Central. Microsoft: Store Commerce app capabilities; Microsoft: Online and offline POS operations.
Microsoft’s modernization effort is particularly visible in the interface. Views built with React and Fluent UI are replacing legacy experiences across the transaction grid, product search, product details, and customer workflows. The practical goal is less navigation and more useful information in the flow of the sale. Availability is not uniform, however: Microsoft identifies the modern transaction grid, search results, and product details experiences as generally available, while its modernization overview still labels the newer customer experiences as preview. Installing a service update should not be confused with every feature in that update becoming generally available or automatically enabled. Microsoft: Modern workflows in Store Commerce POS.
The last three 2026 releases: What changed
10.0.47: Modern selling and a stronger B2B foundation
Microsoft lists January 2026 preview availability, March self update availability, and April automatic update availability for version 10.0.47. The release documentation describes B2B multioutlet ordering using contacts, allowing a buyer to work across associated outlets within one authenticated session, with catalog access and pricing specific to each outlet. It also lists transaction archiving and purging as generally available and introduces payment link and QR code checkout support for ecommerce using the Adyen connector. These are broader Commerce advances, not all of which are specific to POS. Microsoft: Commerce 10.0.47 release notes.
At the counter, the modernization documentation associates 10.0.47 with the refreshed search results and product details experiences and further transaction grid enhancements. Inline actions let users perform common cart line tasks without repeatedly leaving the sale. For distributors evaluating POS, that direction matters: frequent changes to quantities, units of measure, or line details are better assessed as part of the live counter workflow than as isolated back office functions. Multioutlet ordering also strengthens the digital side of an account relationship, although its inclusion in release notes is not, by itself, proof of the feature’s general availability date. Microsoft: POS modernization overview; Microsoft: Modernized transaction grid.
10.0.48: Customer context and broader fulfillment
Version 10.0.48 follows an April preview, June self update, and July automatic update schedule. Its release notes introduce the modernized customer details page in Store Commerce, replacing the legacy view with a responsive experience built with React. They also describe order fulfillment across legal entities, including fulfillment groups spanning companies, intercompany order creation, and POS fulfillment. For a distributor with multiple operating companies, this points toward a more connected sourcing model, but release inclusion requires an important qualification. Microsoft: Commerce 10.0.48 release notes.
Microsoft’s archived 2026 plan lists fulfillment across legal entities for a December 2026 general availability target, despite its appearance in the 10.0.48 notes. The appropriate interpretation is that documented functionality and production release status are separate questions; the earlier notes should not be used to claim unrestricted general availability. Separately, the archived plan records June 30, 2026 general availability for credit management support for Commerce orders. That enhancement extends standard credit management rules into Commerce fulfillment while retaining specific order capture checks and cash and carry safeguards. For distribution driven by customer accounts, this alignment is a meaningful development. Microsoft: Archived 2026 feature schedule; Microsoft: Credit management for Commerce orders.
10.0.49: A more configurable workspace for serving customers
Microsoft lists July preview, September self update, and October automatic update availability for 10.0.49. The release expands the modernized customer details experience with shipping address management, a chronological timeline of purchases and activities, customer attributes, and additional account management interactions. Administrators can show, hide, and reorder sections through POS visual profiles rather than requiring code for those layout changes. The notes also introduce a receipt designer built with React embedded in Commerce headquarters for A4 and thermal receipts. The modernized customer experience remains controlled by a feature setting, and its preview designation should be checked before production adoption. Microsoft: Commerce 10.0.49 release notes.
For a distribution branch, the significance is not simply a more contemporary screen. Better access to customer history, shipping destinations, and account information can help the counter conversation stay focused on the buyer. Configurability also creates an opportunity to emphasize information relevant to a trade customer instead of assuming every location should look like a conventional retail store. These are potential operational benefits, not measured productivity improvements or a guarantee that specialized distribution requirements are covered out of the box.
The trade counter opportunity: Why distributors should care
The most compelling distribution story is the convergence of fast counter transactions with order management that accounts for customer relationships. Microsoft documents catalogs tailored to individual customers and trade agreement pricing in Commerce, customer orders for later pickup or shipment, and the newer alignment with credit management. Together, these capabilities provide a stronger basis for evaluating trade counter scenarios than the narrow idea of scanning products and accepting a card. Some foundations predate 2026; what is new is the additional modernization and B2B investment around them. Microsoft: Commerce capabilities; Microsoft: Customer orders in POS.
Consider an illustrative electrical distribution scenario: a contractor visits a branch to collect materials, adds another item, and needs a remaining item supplied later. A useful counter experience should connect the customer’s identity and applicable pricing to inventory and fulfillment choices, then handle payment or account treatment according to policy. Dynamics 365 Commerce offers documented building blocks for that type of journey. The complete scenario, including mixed immediate and deferred fulfillment, credit holds, warehouse execution, and document requirements, still needs to be demonstrated in the intended configuration rather than assumed from a feature list.
A necessary distinction: the Microsoft sources reviewed for this article do not establish a separately named, newly released native “Trade Counter” module or a confirmed launch date for such a feature. Here, trade counter describes the distribution use case supported by a combination of existing and newer Commerce capabilities. It should not be read as a Microsoft product announcement. Partner counter sales products are separate offerings and should not be confused with native Store Commerce functionality.
The potential benefit for distributors is substantial: a counter experience that is easier to use while remaining connected to the customer’s wider buying relationship. But fit depends on detail. Quote conversion, job or project references, customer purchase order capture, authorized purchasers, substitutions, special orders, unit conversions, partial fulfillment, and returns against account purchases are examples of requirements to validate, not capabilities that this article asserts are all newly native. The business case should also include Commerce licensing and infrastructure, payment integration, offline limitations, and any extensions needed to support warehouse and branch processes.
What comes next: Published targets, previews, and open questions
The clearest dated upcoming item in the reviewed Commerce plan is order fulfillment across legal entities, with a December 2026 general availability target. For distributors operating across companies, the proposed value is access to a broader inventory network with coordinated intercompany processing. However, that date comes from an archived plan, not a newly verified October roadmap commitment, and should be treated as a historical target requiring confirmation. Other items in that plan, including multioutlet B2B ordering, asynchronous payments, and call center pay by link, carried September 2026 targets. A past target alone does not confirm that each feature has launched. Microsoft: Archived Commerce feature plan.
A second area to watch is agentic commerce. Microsoft documents a preview Commerce Model Context Protocol (MCP) server that exposes commerce workflows to compatible AI agents, including product discovery, inventory lookup, carts, checkout, and order activity. This is a foundation for new buying experiences, not evidence of a generally available autonomous trade counter assistant. Its relevance to any distributor depends on supported buyer identities, permissions, business rules, and the specific workflows being implemented. Microsoft: Commerce MCP server preview.
There is also a change in how Microsoft publishes what comes next. Beginning in September 2026, Dynamics 365 roadmap content is moving from release waves published twice a year to continuous disclosure through the AI at Work roadmap. Consequently, a conventional “2026 wave 2” feature list is no longer the right basis for describing future Commerce investment. The sources reviewed do not establish a confirmed POS feature list for the next version or a native trade counter release date beyond the items discussed here. Buyers should distinguish an announced roadmap item, a preview, a service update inclusion, and confirmed general availability before committing to deployment dates. Microsoft: Moving to a continuously updated roadmap.
The bottom line: Evaluate the counter, not the retail label
Dynamics 365 POS in 2026 is evolving along two complementary paths: a more modern frontline experience and closer coordination across customers, channels, credit, and fulfillment. Traditional retailers remain an important audience, but the capabilities warrant a fresh evaluation by distributors with meaningful branch and counter operations.
The strongest argument is not that every distributor now has a complete native trade counter solution waiting to be switched on. It is that the distance between POS designed for retail and distribution selling built around customer accounts is narrowing. For organizations that can align Store Commerce with their pricing, credit, inventory, and warehouse processes, the counter can become a connected service point rather than a disconnected transaction terminal. That is the opportunity worth testing, and the more useful conversation than whether POS belongs only in retail.