What the feature does
The change has three parts, all in Store Commerce, the POS app for Dynamics 365 Commerce.
1. A Contacts section on the customer details page. The page now lists all contacts associated with a customer account. Associates with the right permissions can add, edit, and deactivate contacts that are no longer valid. Changes are synchronized with Dynamics 365 Finance and Operations in real time.
2. Stamping a contact on a transaction. Once a customer is in the cart, the associate picks a contact from that customer's list and attaches it to the transaction. The selected contact identifies the individual acting on behalf of the customer's organization. Microsoft's description lists four transaction types:
- Cash-and-carry transactions
- Customer orders
- Quotations
- Return orders
3. Printed output. The contact's name is printed on receipts and other order documents. That gives the retailer and the business customer the same reference for who was involved.
Why it matters
Microsoft says that without this, retailers have limited visibility into who performed specific actions, which creates accountability gaps. It also says this makes disputes harder to resolve and compliance requirements harder to meet. Microsoft's Message Center announcement, as reproduced by the PupuWeb digest, frames the aim as an audit trail of who placed, paid, or collected an order. The same text says merchants can control which contacts are authorized to place or collect on-account orders, helping reduce the risk of unauthorized purchases.
Some caution is warranted here. These are Microsoft's stated goals. The available material does not describe how identity is verified, how long the audit data is kept, or how the on-account authorization controls are configured. A name stamped on a receipt is a record of who the associate said was acting, not proof of identity. A retailer with strict compliance needs should test the feature against its own policies rather than assume it settles them.
This is also different from the general phone number and email on a customer account. The attribution is per transaction, so one company account can show different people on different sales, quotes, and returns. That is the practical gain at a trade counter, where a contractor's office manager might order on Monday and a site foreman might collect on Thursday.
Availability and configuration
The Message Center post says public preview begins October 2, 2026. It says the message is for awareness and that no action is required. That does not mean the feature is on for everyone by default. The same post says the feature is permission-controlled, and administrators assign the appropriate permissions to roles that require the ability to manage contacts. Associates who are not given those permissions will not be able to manage contacts.
The sources do not give several details:
- The exact permission names.
- The minimum Commerce version.
- Any regional exceptions.
- A step-by-step setup guide.
Microsoft Learn documents a separate modernized customer details page for Commerce 10.0.48 and later. It is enabled in Feature management. This article does not establish that the contacts feature depends on that page, so don't treat it as a prerequisite. If you use that page, check which version and visual-profile settings you have before assuming where the Contacts section will appear.
How it fits with other Commerce POS changes
Microsoft announced several related Store Commerce items around the same time. One is an item on improving order capture workflows. It adds a free-text Add notes operation for customer orders, quotations, and pickup transactions, where notes can capture details such as pickup person information. Notes are free text, so they are easy to type but hard to report on. A structured contact record tied to the customer account is easier to query and print consistently. That is an inference from how the two features are described, not something Microsoft states.
What to do next
Microsoft gives no prescribed rollout steps. Based on the documented behavior, a sensible check is:
- Decide which store roles should be allowed to add, edit, or deactivate business-account contacts.
- Assign the relevant permissions to those roles in headquarters.
- In a test environment, add a contact to a business customer and confirm it syncs to Finance and Operations.
- Add the customer to a cart, select the contact, and complete each transaction type you use. Confirm the name appears on the printed receipt and order documents.
- Pay particular attention to pickup and on-account orders. Microsoft's announcement mentions both, but the sources do not define exactly how they work.
Bottom line
This is a modest but useful change for retailers selling to businesses through Dynamics 365 Commerce. It adds a structured way to record who acted for a company on a sale, quote, or return, and it prints that name on the paperwork. The open questions are the permission names, version requirements, and how the on-account authorization controls are set up. Retailers should confirm those in their own environment during the rollout.