Roadmap item 576301, “Improve order capture workflows in Store Commerce,” describes planned improvements spanning transaction-screen operations and customer-record defaults. The important distinction is that this is planned functionality, not a confirmed release.
Timing: December is a target, not a deployment promise
The roadmap listing identifies the work as In development, with October 2026 preview timing and December 2026 general availability timing. It lists Android, desktop, iOS, and web platforms, with Worldwide Standard Multi-Tenant cloud coverage.
October’s presence in the preview field does not establish that a preview is available. The publicly rendered roadmap page did not expose the matching entry’s details, so its implementation and availability could not be independently confirmed there. Microsoft also explicitly describes roadmap dates as estimates and warns that descriptions and timing can change.
For administrators, that makes this a planning item—not yet a reason to promise store managers a particular deployment date.
Keep customer orders when everything becomes carryout
The most consequential proposed change concerns what happens when every line on a customer order is marked carryout.
Microsoft’s existing Commerce documentation says that Carry out all products converts the customer order into a cash-and-carry transaction. That establishes the behavior the planned configuration is intended to change.
Under the roadmap proposal, a new point-of-sale functionality profile configuration would allow associates to save the transaction as a customer order even when all lines are carryout.
That is more than a cosmetic adjustment. The planned behavior preserves the customer-order classification rather than allowing the fulfillment selection alone to force a conversion. For trade-counter businesses, that could provide flexibility when the customer’s collection arrangements change during order capture.
There are explicit boundaries:
- Charges, including delivery charges and deposit amounts, would be recalculated for full-carryout deposit requirements.
- When editing an order, lines could be changed to carryout only if the order has not been partially fulfilled.
- The behavior depends on configuration; it should not be assumed to become universal.
The partial-fulfillment restriction deserves particular attention in testing. An entirely open order and one with goods already fulfilled are not interchangeable scenarios.
Add notes without losing transaction context
A planned Add notes operation would let associates attach free-text information from the transaction screen while creating:
- Customer orders.
- Quotations.
- Pickup transactions.
The roadmap gives pickup-person information as an example. That addresses a familiar operational gap: an associate knows something important, but the transaction has nowhere suitable to put it.
The proposed capability should not be confused with a structured authorization process. The description establishes free-text notes, not identity verification, mandatory fields, customer-facing messages, or a guarantee that notes appear on every downstream document.
For retailers evaluating the feature, the useful question will be whether the information remains accessible to the people who need it at handover. That is a validation task, not an established capability in the current description.
Make the current store the pickup starting point
Another configuration would streamline Pickup all and Pickup selected by defaulting the pickup location to the current store.
Microsoft’s documented pickup procedure currently includes a separate store-selection step before the pickup date is selected. The proposed shortcut therefore addresses a specific interaction, rather than vaguely promising “faster checkout.”
With the setting enabled, the planned flow would proceed to:
- Delivery-mode selection when multiple pickup modes are configured; or
- Select a pickup date.
Associates would still be able to choose another store by selecting Cancel.
That last detail belongs in staff training. In this proposed workflow, Cancel provides a route to another location; it should not automatically be interpreted as abandoning the whole order.
Modernize deposit overrides without assuming new permissions
The planned deposit-override update replaces the previous button-grid experience with the payment dialogs used elsewhere in Store Commerce.
The announcement describes an interface change. It does not establish new override permissions or a new deposit policy.
That distinction matters because Microsoft’s existing documentation already ties deposit overrides to associate privileges and the availability of the operation in the transaction-screen layout. A more consistent dialog should not be mistaken for broader authority to change what a customer owes.
Apply customer defaults across order channels
The final two changes extend beyond the Store Commerce transaction screen.
A new blanket purchase order field on the Commerce headquarters customer profile would store a default PO number. The roadmap says that value would apply automatically to sales orders created through:
- Store Commerce.
- Call center.
- E-commerce.
- Supply Chain Management.
- Statement posting.
The existing Employee responsible field on the customer record would also populate automatically on new orders across those same channels.
These defaults could reduce repeated entry, but their practical value depends on the accuracy of the customer record. A stale value entered once and copied everywhere is not an efficiency win—it is an error with excellent distribution.
The description does not establish how manually entered PO numbers take precedence, how channel-specific employee assignments interact with the default, or what happens during later edits.
What Commerce teams should prepare to validate
This is not yet a supported setup guide: the available description does not provide exact configuration labels, navigation paths, release-version requirements, or rollout sequencing.
It does, however, support a focused acceptance-test plan once the functionality becomes available:
- Compare all-carryout behavior with the new setting enabled and disabled. Check order classification, charges, and deposit amounts.
- Separate open and partially fulfilled order tests. Verify the stated restriction on changing lines to carryout.
- Exercise both pickup routes. Include current-store pickup, alternative-store selection through Cancel, and multiple pickup modes.
- Check note visibility during handover. Do not assume receipt printing or downstream exposure.
- Validate customer defaults in each named channel. Include cases where staff need a different PO number or responsible employee.
- Retest deposit overrides with appropriate user roles. Confirm the revised interaction without assuming permission changes.
The appeal here is practical rather than theatrical: retain context, remove repetitive choices, and preserve order flexibility. If delivered as described, these changes could make Store Commerce better suited to the untidy reality of counter sales. The measure of success will be fewer corrections after capture—not merely fewer taps before payment.