Microsoft is now working to expose those exact workflows to AI agents. On October 13, 2026, Microsoft added Roadmap ID 574124 to the AI at Work roadmap, titled Dynamics 365 Commerce: Enable MCP tools for POS returns. Currently listed as in development for Worldwide (Standard Multi-Tenant) cloud instances across Android, Desktop, iOS, Mac, and Web platforms, the feature is slated for preview availability in October 2026 and general availability in March 2027. As Microsoft notes on the AI at Work roadmap, these dates and descriptions are estimates and remain subject to change.
Rather than inventing a separate shadow system for handling refunds, this roadmap update introduces reusable Model Context Protocol (MCP) tools for Store Commerce POS returns. These tools expose existing Dynamics 365 Commerce return capabilities as structured actions so enterprise developers, implementation partners, and retailers can build conversational or agentic return experiences directly into POS-embedded agents, chat-based copilots, or workflow orchestrators.
Why Model Context Protocol Matters at the Register
To understand what Roadmap ID 574124 actually delivers, it helps to look at Microsoft's broader architectural shift across its enterprise resource planning (ERP) and retail portfolio. According to Microsoft Learn documentation on the Dynamics 365 Commerce MCP server (published in September 2026) and Microsoft's Finance and Operations MCP documentation, MCP provides a standardized framework that replaces brittle, custom point-to-point API integrations.
Instead of forcing developers to wire up custom connectors every time they want an AI assistant to interact with store systems, the Commerce MCP server provides tools that map directly to the headless Commerce engine. According to Microsoft Learn, this design is agent-platform neutral: organizations can build their commerce integration once and connect compliant clients including Microsoft Copilot Studio, ChatGPT, Azure AI Foundry, or custom agent hosts. In a September 23, 2026 blog post by Sameer Verma, Vice President and Chief Product Officer of Microsoft Dynamics 365 AI ERP, Microsoft confirmed that the Dynamics 365 Commerce MCP server entered public preview alongside plans to expand its toolset and extensibility support through March 2027. Earlier, in a June 29, 2026 Microsoft Dynamics 365 IT Professional blog post, Microsoft highlighted that MCP server-powered agents can allow store associates to complete returns, exchanges, and order lookups without manually stepping through multi-screen POS flows.
Roadmap ID 574124 represents the specific build-out of those structured POS return actions.
Inside the Planned POS Returns MCP Toolset
According to the AI at Work roadmap description for ID 574124, the upcoming MCP tools break the return lifecycle down into discrete, structured actions that an agent can invoke and present back to a user interface:
- Transaction Lookup: Agents can search for the original purchase using supported identifiers—specifically the receipt ID, order number, invoice ID, or confirmation number.
- Line-Level Retrieval and Eligibility Classification: Once matching transactions are found, the tools retrieve the transaction lines and classify items as returnable, partially returnable, already returned, or not returnable.
- Policy Explanation: Beyond a simple yes or no, the tools are designed to explain return eligibility, policy restrictions, and the specific reasons why individual lines may or may not be eligible for return.
- Return Creation: Agents can initiate a return using the selected line items, specified quantities, and required return reason codes.
- Refund Determination and Execution: For original-tender refund scenarios, the tools determine eligible refund options and execute eligible original-tender refunds through existing Dynamics 365 Commerce return and payment logic.
- Return-Risk and Pattern Analysis: The tools can analyze prior returns and refunds to surface duplicate-refund risks, frequent-return patterns, cross-store return history, or other return-risk indicators.
Because the tool responses return structured data, the host application—whether that is a tablet in a store associate's hand or a customer-facing copilot—can render clean summaries, selection prompts, and next steps without guessing at the underlying ERP state.
Section Summary: Roadmap ID 574124 packages Dynamics 365 Store Commerce return workflows—from receipt lookup and line-item eligibility to original-tender refund execution and risk analysis—into standardized MCP tools scheduled for preview in October 2026 and general availability in March 2027.
Grounding AI in Existing Dynamics 365 Commerce Rules
A common fear among IT administrators and retail finance directors is that an overeager AI agent might "hallucinate" a store policy and hand out unauthorized refunds. Microsoft's roadmap entry explicitly notes that these MCP tools execute through existing Commerce return and payment logic, and that administrators or implementation partners maintain existing return policies, reason codes, tender rules, and payment configurations.
When we compare the roadmap description against Microsoft Learn's official Create returns in POS and Create and update a returns and refunds policy for a channel documentation, it becomes clear how tightly the planned MCP actions map to established Store Commerce guardrails:
| Return Workflow Stage | Planned MCP Tool Capability (Roadmap ID 574124) | Underlying Dynamics 365 Commerce POS Logic (Microsoft Learn) |
|---|---|---|
| Purchase Lookup | Look up original purchase via receipt, order, invoice, or confirmation number. | The POS Return transaction operation searches cash-and-carry or customer orders using Receipt ID, Order number, Channel reference ID (order confirmation ID), or Invoice ID. |
| Line & Quantity Checks | Identify returnable, partially returnable, already returned, or nonreturnable lines. | POS displays original purchase quantities alongside previously returned quantities; return quantity must be less than or equal to the Available to return field. |
| Blocked Items | Explain policy restrictions and why specific lines are not returnable. | The Controlled return of specific items in POS feature lets HQ block individual items or categories (Block item return = Yes), hiding them from standard return views unless overridden by staff with the Allow return of non-returnable items permission. |
| Reason Codes | Create a return using selected lines, quantities, and reason codes. | Cash-and-carry returns use info codes in the store's functionality profile; customer order returns use reason codes configured in Commerce headquarters. |
| Ledger Posting | Execute through existing Commerce return logic. | Under the mandatory Unified return processing experience in POS (introduced in Commerce version 10.0.20), POS returns are posted to headquarters as sales orders with negative-quantity lines rather than legacy RMA orders. |
| Tender & Refund Rules | Determine and execute eligible original-tender refunds. | Channel return policies restrict allowed refund tender types based on the original payment method. Original credit card refunds rely on the payment processor, system configuration, and original payment token. |
This architectural alignment is the real story for enterprise IT teams. An agent calling these MCP tools isn't making up refund rules on the fly; it is querying and executing against the exact same headless Commerce engine that enforces whether a cash purchase can be refunded to a credit card or whether a customized item is blocked from return.
Section Summary: The MCP tools do not replace Dynamics 365 Commerce governance; they expose established headquarters rules—such as Unified return processing, item-level return blocks, and channel tender policies—to agentic interfaces.
Operational Realities IT Admins Must Prepare For
While exposing POS returns via MCP promises to speed up register workflows, enterprise architects and Dynamics 365 administrators should pay close attention to a few real-world operational boundaries documented in Microsoft Learn before turning agents loose on store returns.
1. Cross-Store Synchronization and Duplicate-Refund Risk
One of the most compelling features in the Roadmap ID 574124 description is the ability for MCP tools to analyze prior returns and surface duplicate-refund risk and cross-store return history.
Why is that so critical? In Microsoft Learn's documentation for POS returns, Microsoft details a known operational scenario in environments using multiple Commerce Scale Units (CSUs). Normally, POS makes a Real-time Service (RTS) call to Commerce headquarters to validate the current quantities available for return. However, if network issues prevent an RTS call, or if Store A and Store B operate on different CSUs that haven't synchronized, Store B's database might not immediately reflect a return just processed at Store A.
To mitigate this in standard POS deployments, Microsoft instructs administrators to:
- Enable the Improved user experience for POS returns feature in Commerce headquarters (
System administration > Workspaces > Feature management). - Run the Update return quantities batch job at high frequency (matching the P-job frequency that pulls channel transactions into headquarters).
- Run the Return quantities (1200) distribution schedule job at high frequency to push updated returnable quantities back out to channel databases.
Notice that even with standard offline/channel-side validation, POS only displays a warning message when RTS is unavailable—it does not hard-block the associate from processing the return. While the roadmap notes that the new MCP tools can surface duplicate-refund risk indicators and cross-store history, Microsoft has not yet published technical documentation specifying whether those MCP risk flags act as informational warnings for the host agent or hard programmatic blocks. Either way, any agentic return analysis will only be as fresh as the underlying RTS connection and headquarters batch synchronization.
2. Original-Tender Refund Nuances and Manager Overrides
The roadmap specifically highlights determining and executing eligible original-tender refunds. In Dynamics 365 Commerce, returning funds to the original payment method is governed by two layers: the Channel return policy (pushed to POS via the 1070 distribution job) and payment processor tokenization.
For example, if a customer paid with a credit card, Dynamics 365 Commerce can issue a linked refund back to that card without requiring a physical swipe—provided the payment processor and system configuration support using the original payment token. Conversely, if a customer wants to deviate from the allowed tender matrix (say, requesting cash back on a restricted tender), Microsoft Learn notes that store managers or associates granted the Allow using all payment methods for refund POS permission (introduced in Commerce version 10.0.44) must initiate that override on their register. Notice how Roadmap ID 574124 scopes its automated execution claim specifically to eligible original-tender refunds, staying squarely inside the lane of automated token and policy rules rather than promising autonomous exception handling.
3. Guarding Against Unvalidated Return Operations
In standard POS layouts, Microsoft offers both a Return transaction operation (which validates against an original receipt or order) and a separate Return product operation (which does not validate against original transactions and allows any item to be returned). Microsoft explicitly warns retailers to restrict the unvalidated Return product operation to authorized staff or require a manager override. By contrast, the MCP tools described in Roadmap ID 574124 are anchored around looking up the original purchase via receipt, order, invoice, or confirmation number first—mirroring the validated Return transaction path.
4. Offline POS Constraints
Although Store Commerce supports Android, iOS, Windows desktop, Mac, and Web footprints, Microsoft Learn notes that when a POS terminal goes completely offline and cannot reach its Commerce Scale Unit, it can only process returns for transactions that were created offline and still reside in that local offline database. Since the Dynamics 365 Commerce MCP server maps to the headless Commerce engine, IT teams designing POS-embedded agent experiences will need to account for how their host interfaces degrade gracefully if store connectivity drops.
Section Summary: Deploying MCP return tools successfully will still depend on core Dynamics 365 hygiene, including high-frequency Update return quantities and 1200 distribution jobs across multi-CSU environments, properly distributed 1070 channel return policies, and payment processor support for tokenized original-tender refunds.
What Remains Unverified Ahead of Preview
Because Roadmap ID 574124 was just published to the AI at Work roadmap in mid-October 2026 and remains in development, Microsoft has not yet published the granular schema documentation for these specific POS return tools. Specifically, administrators and developers are still waiting on:
- Exact MCP tool names, JSON input/output schemas, and error codes for the POS return actions.
- Specific role-based access control (RBAC) mappings for how an authorized agent inherits or restricts POS permissions (such as
Allow return of non-returnable items). - Whether the return-risk and frequent-return pattern analysis relies solely on standard Commerce transaction tables or integrates additional fraud-protection telemetry.
For now, retail IT leaders and Dynamics 365 architects have a clear runway between the October 2026 preview window and the March 2027 general availability target. If your store return policies, reason code mappings, and cross-store synchronization jobs are already dialed in, your environment will be ready when AI agents start stepping up to the return counter.