What the roadmap says is coming
The entry describes a guided flow from item entry through payment and completion. It names Windows, web, iOS and Android devices in the description. The metadata lists only "Web" as the platform, and I couldn't confirm which is correct. Check this before you plan hardware around it.
The planned pieces are:
- Customer and loyalty prompts that can attach an active linked loyalty card.
- Back and Home navigation from category and search views.
- A persistent call-for-assistance panel, plus authorized inline actions once a manager signs in.
- An optional app bar with Call for help, Language, visual styling and extensible custom actions.
- Inactivity warnings that safely end unpaid transactions and keep an audit record. If payment has already been captured, the system requests assistance instead of voiding.
- Admin setup: enable "Retail self-checkout" in Feature management. Then configure the new experience through a visual profile in headquarters and assign it to Self checkout registers.
None of this is verified as shipped. I found no public documentation beyond the roadmap text for the inactivity, audit-record, app-bar, language, linked-loyalty-card or custom-action behavior. The roadmap's wording on captured payments is a design intent. Don't read it as a described technical mechanism.
What already exists
Microsoft's current self-checkout documentation, last updated January 31, 2026, shows this isn't a new product. The 2024 wave 1 release plan introduced point-of-sale self-checkout on the Store Commerce app using existing workflows. It was framed as scan-and-pay-by-card self-checkout. The Dynamics 365 blog described it as the same Store Commerce app running in self-checkout mode. The 2026 wave 1 plan also mentions Store Commerce's self-checkout for customers who want to skip the queue.
The roadmap item therefore looks like a usability and configurability pass on a feature that already exists. It is not a first launch.
Version requirements for today's feature
Microsoft Learn says the current feature needs Commerce 10.0.40 or later, Store Commerce 10.0.40 or later, and Commerce Scale Unit 9.50 or later. These apply to the documented feature. Microsoft hasn't published minimums for the new roadmap experience, so check again once preview documentation appears.
Enabling and configuring self-checkout today
- In Commerce headquarters, go to System administration > Workspaces > Feature management.
- Check for updates, then search for Configure POS self-checkout register.
- Select Enable now.
- Under POS Registers, open the register setup and set Self-checkout to Yes.
Setting a register to self-checkout changes some defaults:
- Enable task and test recorder becomes No.
- The Hardware Station options "Select upon tendering" and "Select at start of transaction" become No.
- The auto logoff/lock option "After each transaction" becomes No.
- In consumer mode, the header and side navigation bars are hidden. Navigation to payment methods from totals is disabled.
If Manage device is Yes on a user's POS position permissions, the bars stay visible. That lets staff do setup or admin work at the kiosk without moving to a cashier register.
To keep a product out of self-checkout, set Blocked at self-checkout to Yes under Released products. A shopper who scans a blocked item gets an error telling them to ask a cashier.
Locking the kiosk to shopper tasks
- Create a generic user with limited permissions for the kiosk.
- Assign that user the SCO kiosk permission group, which limits it to consumer operations such as scanning and paying.
- Activate self-checkout on the kiosk.
- Turn on shifts for the generic user.
- Sign in with that user ID so shoppers can use the kiosk all day.
To let cashier registers turn kiosk shifts on or off, set Allow manage shared shift to Yes in cashier permissions. For initial peripheral setup, an administrator can sign in with their own credentials. Their screen layout must be assigned to their user ID in headquarters.
Microsoft also ships an out-of-box customer-facing layout in demo data. Assign it under Retail and Commerce > Screen layouts. The demo uses Houston Register 49 and layout SCO_POC1. User 000815 is the sample customer and 000813 is the sample manager. These are sample values, not deployment requirements.
Shopper and staff operations today
Supported shopper actions are:
- Scan and add items.
- Enter a loyalty number on a numeric keypad.
- Key in an item code when a barcode is missing or unreadable.
- Browse categories by search.
- Pay by credit or debit card. This is the only payment operation listed. After payment, the shopper is offered a receipt.
When a shopper selects Call for assistance, a manager or associate has to sign in or swipe in. They can then do any of these:
- Void the transaction, or one item at a time.
- Override tax on a line or on the whole transaction.
- Suspend the transaction and resume it on a regular cashier register.
- Override an item's price.
- Apply a percentage or amount discount.
- Log out, or cancel the assistance request.
If you're updating an older demo environment, you may need to add operation 718 – Allow request for assistance by hand. In headquarters, go to POS operations and select +New. Enter 718 as the Operation ID and 1002 as the Permission ID. Tick both Check user access and User operation, then save.
What this means for retail IT teams
The roadmap's persistent assistance panel and inline manager actions would address a real pain point. Today, staff intervention runs through a separate Call for assistance flow. The inactivity handling targets an equally common problem. Abandoned kiosk sessions are a nuisance, and a clean policy for unpaid versus paid transactions is a sensible thing to want. The audit record would also help with loss-prevention reviews. I can't say how any of it will work until Microsoft documents it.
Practical steps before preview:
- Confirm your Commerce, Store Commerce and CSU versions meet today's baseline.
- Audit your kiosk permission groups and the assistance operation setup.
- Review which products are blocked at self-checkout.
- Decide which languages and branding you'd want in a visual profile.
- Plan for the preview in a non-production environment, and treat the dates as provisional.
The roadmap lists only General Availability and Preview rings for the Worldwide (Standard Multi-Tenant) cloud. Retailers on other cloud instances shouldn't assume availability.
The roadmap text is Microsoft's own description of unreleased work. It carries no independent testing, performance data or customer results. Treat the listing as a signal of direction, and wait for Microsoft Learn documentation and preview behavior before committing to rollout dates.