DOMS configuration

Introduction

The distributed order management system (DOMS) is a backend component that orchestrates incoming orders from the online shop and decides where and how the orders can be fulfilled best. Routing rules that are configurable by the user are considered to meet the end customers' needs best. Based on these rules, the DOMS decides in which warehouse or store the order should be fulfilled.

Description

DOMS configuration

The DOMS logic is split into two different areas. For both areas there are custom rules which can be set by users as well as predefined rules specified by our platform.

Fences: Can be used to exclude facilities from routing according to the selected fences.

Ratings: Can be used to weigh facilities according to the selected ratings.

It is possible that an order could not be assigned to a facility ("routed"), for example, because all available facilities do not pass a specific fence. In such a case, routing the order is retried whenever another order is passed to the DOMS. After a configurable amount of time, such an order is set into a “not_routable” state. The default is set to 8 hours.

Order types

When creating an order our systems differentiate between two types of orders:

  • Click & Collect, which can also be configured as Click & Reserve

  • Ship-from-Store, which includes standard delivery and same day delivery

Click & Collect orders

A Click & Collect order is not routed by the DOMS logic since the customer has already chosen a facility from where he/she wants to pick up the order within the ordering procedure in the web shop. This means a C&C order must contain facility information and the order is routed directly to the specified facility. Optionally, the same is possible for Ship-from-Store orders (see below).

For Click & Collect orders, the following attributes can be defined:

  • Paid: A flag that indicates whether the order has yet to be billed when picked up by the customer (Click & Reserve) or already has been paid online (Click & Collect). This flag is not evaluated by any fence or rating but merely shown within the Operations App.

  • Primary facility: This is the facility which was chosen by the customer as a pickup location for her order. This attribute will be evaluated by the service type fence (see Fences).

  • Supplying facilities:

    • These facilities are a fallback for the primary facility in case the primary facility cannot fulfill all ordered items. In this case, a reroute (see Rerouting) can be triggered into one of the supplying facilities (which have to be of service type Ship-from-Store). The supplying facility then fulfills the order and sends it back to the primary facility where the customer can pick it up. This limits the amount of facilities that have to be considered by the DOMS. This attribute will be evaluated by the service type fence (see Fences).

    • In case supplying facilities are specified for a Click & Collect order, they will compete against the primary Click & Collect facility already when routing the order initially. In case a supplying facility performs better than the primary Click & Collect facility, this order will be routed to the supplying facility directly. The supplying facility in turn fulfills the order and sends it back to the primary facility.

Ship-from-Store orders

If the order is a Ship-from-Store order it is routed by our DOMS system. In order to perform routing decisions, orders as well as facilities need to be configured. Further input parameters like listings and stock information can improve the routing decision but are not mandatory.

For Ship-from-Store orders, the following attributes can be defined:

  • Service Level: Defines whether the customer requires same day or standard delivery. This attribute will be evaluated by the service type fence (see Fences).

  • Preferred Carrier: Can be used in case the customer wants to have her order delivered by a specific carrier. This attribute will be evaluated by the carrier availability fence (see Fences).

  • Preselected Facilities: Specifies a number of facilities that should be taken into consideration when performing a routing decision instead of all facilities within the network. This attribute will be evaluated by the preselected facility fence (see Fences).

FAQs

How to define order type "Ship from Store" for a facility?
  1. Select “Network view”

  2. Define which Service Type can be selected by the customer

  3. In the DOMS configuration you can enable fences to specify the Ship from Store settings

How to define order type "Click & Collect" for a facility?
  1. Select “Network View”

  2. Select “Facilities” in the Cockpit

  3. Click on the setting-symbol in the facility overview

  4. Define for each facility the preferred order type(s)

How to set order split settings for initial Routing?

1.) Select “Network View”

2.) Select “DOMS configuration”

3.)Open up “Order Split”

4.) Define your individual Order Split Count

How to activate order split after short-pick for ship from store orders?
  1. Select “Network View”

  2. Select “DOMS Configuration”

  3. Open up “Routing decision in case of a shortpick”

  4. Select "Order Split". An press the "Save" Button.

Now the order can be splitted in case of a shortpick

How to set ratings in your order routing?

1.) Select “Network View”

2.) Click on “Doms Configuration”

3.) Open up “Routing rules”

4.) Define the weight of each criteria ( 1 = important, 10 = not important)

How to enable re-route upon short-pick for click & collect / ship to store / interfacility transfer?
  1. Select “Network View”\

  2. Select “DOMS Configuration”\

  3. Open up “Routing decision in case of a shortpick”\

  4. Activate Click & Collect Reroute\

How to activate re-route in case of inactivity?
  1. Define reroute settings for the case if orders are not fulfilled in a certain timeframe. The function can be activated for:

    1. Ship from Store tasks

    2. Same Day Deliveries

    3. Click & Collect tasks

How to activate manual reroute?
  1. Select “Network View”\

  2. Open up “Reroute task manually”\

  3. Activate Reroute to trigger the function\

Last updated