With a launched update to Dynamics 365 Commerce tracked under Microsoft’s AI at Work roadmap ID 576811 (and previously communicated to administrators via Message Center notice MC1301477 ), Microsoft has corrected that hardware-routing mismatch in the Store Commerce point-of-sale (POS) application. When a sales associate selects a dedicated hardware station (HWS) from the POS interface, Store Commerce now pairs with and routes the payment request to the payment terminal physically assigned to that selected station, rather than defaulting back to the terminal attached to the associate’s home register.
What Changed in Store Commerce Hardware Station Routing
To appreciate why this seemingly small routing adjustment matters for enterprise IT and retail operations, it helps to look at how Store Commerce handles peripherals. According to Microsoft Learn documentation, Store Commerce is the unified generation of POS software for Windows and mobile platforms, supporting local hardware stations, offline usage, and direct integration with payment terminals, receipt printers, and cash drawers.
Before this update, peripheral pairing when switching stations had an annoying blind spot:
- Receipt printers already followed the associate’s selected dedicated hardware station as expected.
- Payment terminals, however, remained stubbornly tied to the terminal configured on the associate's base register.
Feature ID 576811 brings payment terminal behavior into alignment with printer pairing. Once an associate chooses a dedicated hardware station in Store Commerce—typically the station physically closest to where they are assisting the customer—the payment request is directed to the PIN pad or payment terminal associated with that station.
It is worth noting what the word "nearest" means in Microsoft’s feature title: Store Commerce is not using indoor GPS or Bluetooth beacons to automatically guess where the associate is standing. Rather, "nearest" refers to the human workflow. The associate manually selects the closest pre-configured dedicated hardware station from the POS screen, and the software now respects that choice when it is time to collect payment.
Release Timeline and Platform Scope
According to Microsoft’s AI at Work roadmap and the corresponding Dynamics 365 2026 release wave 1 documentation on Microsoft Learn, the rollout details for this capability are straightforward:
| Attribute | Details |
|---|---|
| Roadmap ID / Message Center | ID 576811 / MC1301477 |
| Product & Application | Dynamics 365 Commerce — Store Commerce (POS) |
| Release Status | Launched (General Availability reached June 5, 2026) |
| Cloud Instance & Platform | Worldwide (Standard Multi-Tenant), Web |
| Enablement | Enabled for end users automatically (no extra feature flag required once configured) |
While the feature is automatically enabled in the software without requiring an extra feature flag in Commerce Headquarters, it does not change store behavior in a vacuum. Retailers must have their dedicated hardware stations and payment terminals properly mapped in Headquarters before associates will see any difference on the sales floor.
Prerequisites and Setup for IT Administrators
If you manage Dynamics 365 Commerce environments, getting this workflow running across your retail channels comes down to verifying a few specific configuration rules in Commerce Headquarters and on the registers themselves.
1. Configure Dedicated Hardware Stations in Headquarters
An IT administrator or store manager must configure dedicated hardware stations in Commerce Headquarters before associates can select them on the floor. Each dedicated hardware station must have an associated payment terminal assigned to it.
In Microsoft’s general Commerce documentation for network peripherals and the Dynamics 365 Payment Connector for Adyen, administrators configure dedicated stations in Headquarters by navigating to Retail and Commerce > Channel setup > Stores, selecting the relevant store, adding a station on the Hardware Stations FastTab with the type set to Dedicated, associating the appropriate hardware profile and terminal IP or device identifier, and running distribution schedule 1070 (Channels) to push the channel configuration down to the store. (Keep in mind that exact terminal parameters, such as local IP addresses versus cloud POIID strings, depend on your specific payment connector and architecture.)
2. Check Shared Shift and Cash Drawer Rules
Microsoft’s documentation for feature 576811 highlights an important operational requirement regarding shifts:
- When a cash drawer is present: The register must have shared shift enabled, and the sales associate must operate within a shared shift on their register.
- The cashless exception: If no cash drawer is present in the setup, the associate does not need a shared shift enabled to use this nearest-terminal payment routing feature.
This exception is particularly useful for modern showroom formats, furniture stores, electronics retailers, or apparel boutiques where floor associates carry mobile POS devices solely for assisted selling and electronic card or digital wallet payments, leaving cash handling to a single central desk—or operating entirely cash-free.
3. The Associate Floor Workflow
Once Headquarters configuration and shift prerequisites are met, the day-to-day workflow on the floor follows five steps:
- The administrator ensures dedicated hardware stations—each paired with a payment terminal—are active in Headquarters.
- The associate signs into the POS with a shared shift enabled (unless operating without a cash drawer).
- While assisting a customer on the floor, the associate selects the desired dedicated hardware station from the POS interface.
- When the shopper is ready to check out, Store Commerce routes the payment tender request directly to the payment terminal attached to that selected hardware station.
- The customer taps or inserts their card at that station, and the associate finishes the transaction on the spot without walking back to the fixed register.
Section Summary: Feature 576811 requires no special feature flags, activating automatically once admins map payment terminals to dedicated hardware stations in Commerce Headquarters and ensure registers with cash drawers are running in shared-shift mode.
Architectural Context: Two Ways Retailers Handle Mobile Peripherals
From an enterprise IT architecture perspective—synthesizing how Microsoft structures its broader Dynamics 365 Commerce peripheral documentation—it helps to distinguish this update from another similarly named setup in Microsoft Learn.
Microsoft’s documentation on Dedicated payment terminals and prompts for a printer and cash drawer describes an inverse scenario: a mobile POS device that carries its own dedicated, tethered payment terminal everywhere it goes, while only prompting the associate to select a networked hardware station when a customer specifically asks for a paper receipt or pays with cash. That model works well when every associate carries a payment sled or handheld terminal, using network printers from vendors like Epson or Star Micronics on an as-needed basis.
Feature 576811 solves the opposite physical layout: the associate’s POS session is moving around the store (or operating from a browser-based Web POS station), and the payment terminals themselves are stationed at fixed pods or service points around the sales floor. Previously, selecting one of those floor pods as your active dedicated hardware station worked fine for firing off a receipt, but left the payment prompt marooned back at the primary register's terminal. By making payment terminal routing follow the selected dedicated HWS, Microsoft allows retailers to place shared payment pods throughout a large store without buying a 1:1 mobile payment sled for every single tablet or associate.
Practical Verification Checklist for Deployment
Because Microsoft’s peripheral documentation notes that hardware-station behavior and device capabilities vary depending on the Store Commerce client platform (Windows, Android, iOS, or Web) and the payment connector in use, IT teams rolling this out across multiregion or large-format stores should run a quick validation pass before briefing store staff:
- Verify connector and client support: Confirm that your payment connector (such as the out-of-box Dynamics 365 Payment Connector for Adyen or a custom Commerce SDK connector) supports your target Store Commerce platform and network architecture. For instance, Microsoft Learn notes specific platform boundaries, such as the Adyen connector not supporting Store Commerce for iOS with local network or cloud architecture configurations.
- Confirm terminal exclusivity rules: Remember that in standard Dynamics 365 Commerce hardware profiles, if a single payment terminal is shared across multiple POS devices simultaneously, Microsoft’s connector guidance notes you may need to deploy an IIS hardware station to manage communications rather than relying on conflicting 1:1 local mappings.
- Run an aisle-to-pod test transaction: After running the 1070 distribution job, sign into a test register (both with a cash drawer in shared-shift mode and in a no-drawer configuration if applicable), switch the active dedicated HWS in Store Commerce to a secondary floor station, and trigger a card payment to verify the prompt wakes up the secondary station's PIN pad rather than the home register.
By closing the gap between receipt printer pairing and payment terminal pairing, Dynamics 365 Commerce eliminates one of those quiet, daily operational annoyances that make retail staff sigh at their screens—letting mobile checkout actually stay mobile.