A logistics dashboard organizes orders, inventory, shipping, and payments into a streamlined workflow.
Microsoft has put a new item on its roadmap for Dynamics 365 Commerce. It would let pricing managers define procurement charges, such as freight, handling or supplier surcharges, by attributes. Purchase orders would then pick up the right charges automatically. The roadmap lists it as In development, and the details come from that listing. It is a planned feature, not something you can switch on today.

A logistics dashboard organizes orders, inventory, shipping, and payments into a streamlined workflow. What the roadmap says​

The entry is tagged to Dynamics 365 Commerce, the Web platform and the Worldwide (Standard Multi-Tenant) cloud. Microsoft's dates are:

  • Preview: April 2027
  • General availability: June 2027

Microsoft says roadmap dates and descriptions are estimates and can change. Entries are also removed when a feature ships, is cancelled or is postponed. Treat both dates as targets, not commitments. The listing doesn't name the attributes, the setup screens, the licensing, or how conflicting rules would be resolved. This article doesn't guess at any of those.

Where it fits: Unified pricing management​

Unified pricing management (UPM) is the pricing framework shared by Dynamics 365 Commerce and Supply Chain Management. Microsoft Learn says it enables attribute-based pricing rules that use attributes and data from customers, products, and order segments. The framework is built from a few pieces:

  • Price attributes: They use information about customers, products, sales order headers, and sales order lines.
  • Price component codes: these group price attributes and act as the building blocks of a price structure.
  • Price structures: these set the sequence of the component codes.
  • Concurrency modes: these decide how the final price is calculated when several rules share a component code.

Charges are already part of that model. Microsoft's pricing TechTalk says Dynamics 365 offers enhanced functionality for applying charges based on product, customer, and order attributes. The roadmap item appears to extend that approach to the purchasing side. That is my reading of the listing, not something Microsoft states.

Automatic purchase-order charges already exist​

This would not be the first way to automate procurement charges. Supply Chain Management already has automatic charges. Microsoft Learn says Automatic charges (auto charges) are automatically applied when you create a sales order or a purchase order. Those rules can be defined for specific vendors, vendor groups, or all vendors. They can apply at the header or line level. They also support criteria such as:

  • a minimum order amount
  • a sales tax group
  • a site and warehouse

Microsoft also warns about overlap. Auto charges set up for both specific vendors and all vendors can produce duplicate charge calculations. The documentation says the system applies all relevant auto charge configurations, regardless of hierarchy when a new purchase order is created. That is why any attribute-based replacement will need clear precedence and stacking behavior.

Microsoft hasn't published how the new feature handles overlap or how it compares with the existing criteria. If you already have a mature auto-charge setup, you can't yet tell whether the new feature is better or merely different.

Migration caveat for existing Commerce customers​

Microsoft's UPM migration article is marked as preview and says it is prerelease documentation subject to change. It says you must be on Commerce version 10.0.46 to use UPM. Its rule-support table lists charges as supported in new attribute-based rules. For existing charge rules it says there is no migration, and that migrating them is planned.

In practice, plan on rebuilding charge logic in the attribute-based model rather than expecting a conversion. That is an inference from Microsoft's table, and the table covers current preview documentation, not this roadmap item. The same article describes a separate process for migrating Commerce price groups and pricing setup. It is not a setup guide for the new procurement-charges feature.

What admins can do now​

  1. List your current charges. Note which freight, handling and surcharge rules rely on vendor, vendor group, or manual entry today.
  2. Look for patterns. Charges that depend on product category, vendor class, or order characteristics are the best candidates for attribute-based rules.
  3. Check your version. UPM migration documentation names Commerce 10.0.46 as the baseline.
  4. Review overlap. If you have both vendor-specific and all-vendor auto charges, check for duplicates before anything else changes.
  5. Wait for documentation. Get the attribute list, the precedence rules and the preview terms before you commit to a rebuild.

Why it matters​

Charges that aren't applied consistently make landed costs unreliable and invoice matching harder. Pricing managers often maintain these rules separately from the purchasing team, so a central, attribute-driven approach could help. If it works as described, the gain is fewer manual entries per purchase order and more consistent freight and surcharge handling. That benefit is my inference from the roadmap description. It is not a measured result.

The preview window in April 2027 will be the first chance to see what the feature actually does.

 

References

  1. Dynamics 365 Commerce: Unified pricing management - manage procurement charges with attribute-based pricing Microsoft 365 Roadmap 2026-11-18T00:49:47.347009Z
  2. Migrate to Unified pricing management (preview) - Supply Chain Management | Dynamics 365 | Microsoft Learn learn.microsoft.com
  3. Unified pricing management module overview - Supply Chain Management | Dynamics 365 | Microsoft Learn learn.microsoft.com