A person uses receipt-design software on a computer beside a printer producing a store receipt.
Microsoft has put a new item on its AI at Work roadmap. It would let Dynamics 365 Commerce administrators and designers describe a receipt layout in plain English and have Copilot Cowork build it. The item is roadmap ID 577405, and its status is "In development". Preview is estimated for October 2026 and general availability for December 2026. Microsoft says all roadmap dates are estimates and can change. The listing covers the Web platform and the Worldwide (Standard Multi-Tenant) cloud.

Anyone who has fought a 40-column thermal receipt will see the appeal. Anyone who has been burned by an AI that "helpfully" invents a store address will also see why the guardrails matter.

A person uses receipt-design software on a computer beside a printer producing a store receipt. What the roadmap item describes​

The feature is called the Commerce receipt format designer skill. It works on receipt layouts stored in Commerce headquarters, for receipt formats used by Store Commerce point of sale (POS). Authorized Copilot Cowork users can do the following:

  • Create or adapt formats. Start from an existing format in the modern Receipt designer representation, build a new one, or ask for changes to an existing target.
  • Edit sections. Change header, line, and footer content, field positions, alignment, and supported formatting.
  • Translate and personalize. Translate static labels and add user-supplied text while leaving dynamic fields intact. Microsoft says missing business details are flagged rather than invented.
  • Check without changing. Run structural or geometry checks that look for overlaps, width violations, and truncation risks. The checks return findings and suggested fixes.
  • Verify saves. The saved configuration is re-read to confirm the requested change landed.

Creating a format from a source leaves the source untouched. Microsoft says the skill is available automatically to authorized Copilot Cowork users. Users name the source format and the outcome they want, resolve any ambiguity about source or target, and review the result.

What the skill does not do​

The roadmap is explicit about limits. Structural checks do not establish any of these:

  • visual appearance
  • barcode scanability
  • runtime values
  • legal or fiscal compliance

Users are expected to review the layout in the Receipt designer and run test prints before using it in operations. Assigning formats to receipt profiles or printers, and printing or reprinting transactions, are separate workflows.

That matches how Commerce already works. Microsoft Learn says a receipt profile can contain multiple form layouts, and you assign the receipt profile to a printer by modifying a hardware profile. The Cowork skill therefore touches the layout only. It does not touch the plumbing that decides which layout a register prints.

Prerequisite: the modern structured format​

The key requirement is easy to miss. A Commerce administrator must make sure the source format exists in the modern structured representation. Microsoft's documentation explains why this takes work.

  • The modern receipt designer is a React-based experience in Commerce headquarters. It replaces the legacy ClickOnce designer launch with a browser-based designer opened from the Receipt formats page.
  • It saves structured receipt layout data for the new receipt format path.
  • Enabling the feature does not migrate existing formats automatically. Each existing format must be opened in the modern designer and saved so the structured data is created. Otherwise it isn't available through the modern structured receipt path.
  • Changes saved in the modern designer are not written back to the legacy format. If the feature is later disabled, those changes won't appear in the legacy designer. They return if the feature is re-enabled.
  • Administrators should enable the feature only after updating the Commerce Scale Unit or Retail Server to a version that supports structured receipts. If the endpoint isn't available, receipt preview or printing can fail.

Commerce 10.0.49 introduced the modern designer as a preview. Microsoft's release notes give a preview in July 2026, self-update general availability in September 2026, and auto-update in October 2026. The notes say the designer includes a structured schema (Header, Footer, and Lines) that Commerce Scale Unit, Store Commerce, and Hardware station consume. They also say the designer includes a visual canvas, templates, localized labels, custom fields, validation, and preview support.

The Cowork skill is a natural-language layer on that foundation. It is not a replacement for it. A retailer still on legacy-only formats has migration work to do first. The roadmap's own prerequisite implies this, though Microsoft has not published an adoption guide for the skill itself.

How this fits Copilot Cowork's wider pattern​

Microsoft is pushing Dynamics 365 into Cowork through skills and plugins. Its Dynamics 365 blog describes 30 new CRM skills for Cowork, now generally available. An earlier Microsoft post on the Sales and Service plugins says Cowork does not access the database directly. It composes over governed Model Context Protocol (MCP) plugins and enforces the existing identity and permission model on every call. That post also says Cowork proposes rather than silently acting, and surfaces updates for approve, edit, or dismiss.

The roadmap item is a Commerce skill rather than CRM, so I can't confirm it uses exactly the same architecture. The "preserve the source, re-read the saved result" language fits the same human-in-the-loop approach.

Where it could help​

These are my own analysis, not claims from Microsoft.

  • Localization. Translating static labels while keeping dynamic fields is tedious across many formats and languages. The modern designer already localizes field labels and preview data, so a skill that handles static text could save real time.
  • Layout audits. Bold characters take twice the space of regular ones, and large characters are twice as high. Microsoft Learn warns that this can truncate or overlap text. An assistant that flags width and overlap risks across many formats could catch these before a register does.
  • Variants. Copying a flagship format and adapting it for another brand, store type, or A4 invoice is the sort of repetitive edit natural language handles well.

Cautions​

  • The feature isn't shipping yet. Everything above comes from a roadmap entry marked in development. The roadmap page did not expose the item text directly in the captured page content. The item-specific details come from the submitted listing metadata, not from product documentation or hands-on testing.
  • Structural checks are not print tests. Microsoft documents several printing dependencies that no layout check covers. Logo images should be monochrome bitmaps. Barcode printing needs the C39N2.TTF font installed on the AOS and SSRS servers. Some OPOS printer drivers need a hardware station configuration flag for image printing. Real printers still need real test prints.
  • Compliance stays with you. Fiscal and legal receipt requirements vary by country, and the roadmap excludes them from checking. Treat any AI-generated layout as a draft that a person who knows the requirements must approve.
  • Natural language can be ambiguous. "Move the total to the right" is clear. "Make it look like the other store's receipt" may not be. Microsoft says users must resolve source and target ambiguity, which suggests the skill asks follow-up questions. How it does so isn't documented yet.

Suggested preparation​

  1. Confirm your Commerce headquarters, Commerce Scale Unit, and Store Commerce versions support the modern designer and structured receipts.
  2. Check Feature management for the modern receipt designer feature. Enable it only after the Scale Unit endpoint is in place.
  3. Open and save each receipt format you want to use with the skill in the modern designer. Do this one at a time in a test environment first.
  4. Confirm the users who will use Cowork have the headquarters access they need.
  5. Define your test-print routine for each printer type, including barcode and logo checks and any fiscal review.
  6. Re-check the roadmap and Microsoft Learn for official documentation as preview approaches.

Bottom line​

The Cowork receipt skill promises faster layout editing, translation, and pre-flight checks for Commerce receipts. It comes with sensible disclaimers: structural checks only, with a human review and a test print before anything goes live. Its value depends on the modern structured designer being in place, and the roadmap dates are still estimates. Until Microsoft publishes documentation, the practical move is to prepare your formats and treat the skill as an assistant to your own checks.

 

References

  1. Dynamics 365 Commerce: Author Commerce receipt formats with Copilot Cowork Microsoft 365 Roadmap 2026-10-22T22:58:40.939110Z
  2. Set up and design receipt formats - Commerce | Dynamics 365 | Microsoft Learn learn.microsoft.com
  3. Modern receipt designer in Commerce headquarters - Commerce | Dynamics 365 | Microsoft Learn learn.microsoft.com