DISTRIBUTED ORDER

MANAGEMENT - RETAIL
& COMMERCE
Introduction
Having an optimized fulfillment, allocation, and distribution can be achieved with the adoption and
implementation of a distributed order management system, which comes out-of-box with Dynamics 365
Commerce.

The purpose of the distributed order management (DOM) capability in Commerce is to help retailers meet
customer expectations by achieving efficiency in their supply chain process. This achievement can help
retailers intelligently manage orders by fulfilling them accurately, timely, and in a cost-effective way. This
document helps to understand the DOM out-of-the box functionalities in D365.

From where you can create the Orders?

DOM looks only at orders that are created from commerce channels which includes brick-and-mortar stores,
online stores, and call centers. Through headless Commerce, orders can be placed from multiple channels like
mobile commerce, social commerce, and more. Now that you know where the source is, let's see how we can
set up the DOM.

Set up DOM.

The first step is to make sure on the System administration > Setup > License configuration, expand the retail
node and enable the Distributed Order Management option.

Now navigate to Retail & Commerce > Distributed order management > Setup > DOM parameters.

Go to General Tab and set the following values:

 Enable distributed order management – Set this option to Yes.

 Confirm Bing Maps usage for DOM – Set this option to Yes.
After enabling the General, set the Retention period in days under fulfillment data. Retention period in days
is to specify how long the fulfillment plans that DOM runs generate are kept in the system. The DOM
fulfillment data deletion job setup batch job will delete any fulfillment plan that is older than the number of
days that you specify here.

Then set the Rejection period (in days) under Assignment rejection – Rejection period (in days) is to specify
how much time must pass before a rejected order line can be assigned to the same location.

On the Solver tab, set the following values:

Max auto-fulfillment attempts – Specify how many times the DOM engine will try to broker an order line to a
location. If the DOM engine can't broker an order line to a location in the specified number of attempts, it will
flag the order line as an exception. It will then skip that line in future runs until the status is manually reset.

Local store region radius – Enter a value. This field helps determine how locations are grouped and
considered equal in terms of distance. For example, if you enter 100, every store or distribution center within
a 100-mile radius of the fulfillment address is considered equal in terms of distance.

Solver type – Select a value. Two solver types are released with Commerce: Production Solver and Simplified
Solver. For all machines that will run DOM (that is, all servers that are part of the DOM Batch group),
Production Solver must be selected.
The Production Solver requires the special license key that, by default, is licensed and deployed in production
environments. In newer Tier 2+ environments, the Production Solver will already be enabled. For non-
production environments, this license key must be manually deployed.

Note: The Simplified Solver is provided so that retailers can try out the DOM feature without having to deploy the special license.
Organizations should not use the Simplified Solver in production environments.

The Production Solver improves performance (such as the number of orders and order lines that can be handled in a run) and
convergence of results (since a batch of orders might not yield the best result in some scenarios). The Partial orders rule requires
Production Solver.

Then finally make sure the number sequence is also set against the Profile & Order fulfillment plan id. Now
your DOM parameters are set and good to go. The next process is to setup a fulfillment profile where you can
setup the different rules.

The DOM rule run against the fulfillment groups, so make sure the fulfillment group is set with the location
that you want to run the DOM.

Fulfillment Profiles

Fulfillment profiles are used to group a collection of rules, legal entities, sales order origins, and modes of
delivery. Every DOM run is for a specific fulfillment profile. In this way, organizations can define and run a set
of rules for a set of legal entities, on orders that have specific sales order origins and modes of delivery.
Therefore, if different set of rules must be run for different sets of sales order origins or modes of delivery,
the fulfillment profiles can be defined accordingly.

The rules are important if you are running DOM. To define rules, go to Retail and Commerce > Distributed
order management > Setup > Manage rules.

If you navigate to manage rules, you can define the rules as per the business requirement.

The following DOM rules are currently supported:

 Partial orders Rule

 Minimum Inventory Rule
 Fulfillment Location Priority Rule
 Maximum Distance Rule
 Maximum Orders Rule
 Maximum Rejects Rule
 Offline Fulfillment Location Rule

To know more on rules, visit: https://learn.microsoft.com/en-us/dynamics365/commerce/dom#set-up-dom

Once you have finished setting up the rules, the next step is to define sales order origin & Modes of delivery
against your fulfillment profile.
Note: A mode of delivery & sales order origin can't be associated with multiple active profiles

The last step is to click save and enable the profile by click Enable profile button. Now you are all set with the
fulfillment profile. The next step is to configure the batch jobs for the DOM to run.

Batch Jobs

DOM will run only in a batch job. To configure the batch job for DOM runs, follow these steps.

 Go to Retail and Commerce > Distributed order management > Batch processing > DOM processor job
setup.
 On the Parameters FastTab, in the Fulfillment profile field, select a profile that DOM must be run for.
At the time of processing, DOM will consider the order and order lines as described below:

Order lines that meet the criteria for sales order origins, modes of delivery, and legal entity as defined in the
DOM profile, and that also meet any of these criteria:

 They are created from commerce channels.

  They have never been brokered by DOM.
 They have been brokered by DOM before, but they are marked as exceptions and are below the
maximum threshold for attempts.
 The mode of delivery isn't pick-up or electronic delivery.
 They aren't marked for delivery.
 They aren't manually excluded.
 Orders that aren't on hold

What Happens After?

If the fulfillment profile is set to Auto apply, the results of the run will be automatically applied to the sales
order lines, and the fulfillment plan can be viewed separately.

If the fulfillment profile isn't set to Auto apply, the results of the run can be seen only from the fulfillment
plan view.

To view all the fulfillment plans that are generated, follow these steps.

 Go to Retail and Commerce > Distributed order management > Distributed order management.
 In the Distributed order management workspace, select the Fulfillment Plans tile.
Besides the standard sales order line fields, the order details section also includes the following three DOM-
related fields:

 Fulfillment type – This field indicates whether the sales order line is fully brokered, partially brokered, or
not brokered at all to a location.
 Split – This field indicates whether one sales order line has been split and brokered to different locations.
 Number of fulfillment locations – This field indicates how many fulfillment lines were created for one
sales order line (based on the number of locations that the original sales order line was brokered to).

You can also view the DOM logs against sales order level if you navigate to View DOM logs under Manage in
the All-sales order page.
Points to remember.

 If you set the Exclude from DOM processing option on the sales order line to Yes, the order or order line
will be excluded from DOM processing.
 The order line has been brokered but can't be assigned to a location. Exceptions have multiple subtypes
that can be viewed from the DOM workspace.
 DOM can be run in an interactive mode. You then see a list of locations that is based on DOM rules that
can fulfill the quantity on the order line. For this functionality to work, there must be an existing, active
fulfillment profile that matches the sales origin and delivery mode on the sales line.
 Over time, the system will keep numerous fulfillment plans. To manage the number of fulfillments plans
that the system keeps, you can configure a batch job that deletes older fulfillment plans, based on the
Retention period in days value.

Thank you for taking the time to read this document. I hope that it has provided you with a clear
understanding of how the DOM works in D365 Commerce.