The roadmap carries Microsoft's usual caveat that its dates and descriptions are estimates. Microsoft says information can change, and items are removed when a feature ships, is cancelled or is postponed. The detail below comes from Microsoft's roadmap listing, supplemented by Microsoft Learn documentation on Store Commerce.
What Microsoft says is coming
The listing describes three stages that split work between Commerce headquarters and the store.
1. Set up in Commerce headquarters
- Administrators define label formats in a label format designer.
- They can reuse a retailer's existing label designs or create new ones, so labels carry the product information that retailer needs.
- They configure the label printers available to each store.
- That includes more than two printers on the same hardware profile.
2. Create label print requests
- A headquarters user selects products and variants.
- For each line, the user sets the label type and the number of copies.
- The user picks the stores to send the request to, then releases it.
- A request can cover one product or a full list, and one store or many.
3. Print in Store Commerce
- An associate opens a released request and reviews its lines.
- The associate can adjust label types and copy counts, then print the labels needed right now.
- Associates can also print on demand. They find a product by scanning or searching, print all variants or pick one, and send the job to a configured label printer.
The listing ties headquarters requests to moments when prices or promotions change. It says a headquarters user creates and releases requests. It does not say that a price change automatically generates one.
Platforms and availability
The roadmap lists these platforms:
- Android
- Desktop
- iOS
- Mac
- Web
It lists the cloud instance as Worldwide (Standard Multi-Tenant). The platform list fits Microsoft's Learn documentation, which says the Store Commerce app is supported on web, Windows, iOS, and Android platforms. The current English capabilities page also lists macOS.
Not a brand-new idea
Label printing is not new to Commerce. Microsoft's Store Commerce capabilities page already lists it under merchandising. It says labels can be generated that contain product information such as the batch number, serial number, and expiration date.
This roadmap item looks like a reworked, more structured workflow. It adds a format designer, multi-store request distribution and associate-side adjustment. Microsoft's capabilities page does not describe those specifics, so I can't confirm how the new flow differs from the current one in detail.
Retailers have long had other routes to shelf labels. Dynamics 365 Finance and Operations has a shelf-label print queue. A Hackernoon walkthrough describes that queue as receiving a label when a product's price changes, if a shelf label report is assigned to the item. That walkthrough is old, and it describes a different part of the product. Independent software vendors have also sold label tools for Dynamics retail. Retail Realm's MAX Labels is one example, which lets retailers configure and print product labels such as hanging butterfly and shelf edge types. A first-party Store Commerce option could reduce the need for add-ons, but Microsoft hasn't said how it compares with them.
What IT and retail operations teams should check
Microsoft's roadmap doesn't answer several practical questions. They are open items, not known limitations:
- Printer support. The listing doesn't name supported printer models, connection types or label stock.
- Hardware station requirements. Store Commerce for Windows supports a local hardware station and can integrate directly with printers. The label feature's prerequisites aren't stated.
- Offline behavior. Learn says in-app deployment supports offline mode and hybrid deployment doesn't. Microsoft hasn't said whether label requests work offline or how they synchronize.
- Version and licensing. The listing gives no minimum Commerce version, feature flag, licensing tier or permission model. It doesn't say who can use the format designer.
- Tracking. The listing doesn't say whether headquarters can see completion status, or whether an associate's edits to copy counts are recorded centrally.
Deployment points that already apply
Store Commerce for Windows has its own prerequisites that affect any peripheral-driven feature. Microsoft's documentation says it:
- Supports Windows 11 and Windows 10 editions, plus Windows Server 2019 and 2022.
- Isn't supported on ARM processors.
- Uses Microsoft Edge WebView2 for rendering.
Microsoft also recommends explicitly managing the WebView2 version, to avoid regressions between the app and the latest runtime. If label printing goes through a local hardware station, those prerequisites and the WebView2 testing advice are worth including in a pilot plan.
Preview is listed for October 2026, which is the current month. If your tenant is in a preview ring, Microsoft's documentation and release plans are the place to confirm whether the feature has reached you. I couldn't verify its live availability.
Bottom line
This is a worthwhile workflow addition for multi-store retailers. It gives them a central place to design labels, a way to push label jobs to many stores, and in-store flexibility for associates. The listing alone doesn't confirm hardware compatibility, offline behavior or prerequisites, so confirm those with Microsoft's documentation or your partner before building store procedures around it.