Unroutable orders

There is a chance that the DOMS is not able to route an order due to various reasons:

• No facility can fulfill the requirements of a particular order

• Misconfiguration of the DOMS

Especially in case of a Same Day order it is very possible that an order might not be routed at all, because there might be no facility available which can fulfil the request of the consumer that very day.

In order to prevent that orders are lost in space, a dedicated overview was created for non routable orders. Within this overview, the administrator gets a complete list of all the affected orders as well as some mechanisms to specifically manipulate an order so that it can be fulfilled.

How to deal with unroutable orders?

1. Rerun the routing process to re-evaluate whether a facility now exists that can fulfil the order. This might come in handy when a misconfiguration of the DOMS has been fixed and all orders should be processed in a regular manner.

2. Assign an order to a specific facility by ignoring any configured fences. A possible scenario might be to route a Same Day order to a given facility, change it to a Standard Delivery Order (see Carrier change ) and fulfill it.

3. Cancellation of an order because there is no was that the order can be fulfilled in an acceptable manner. Currently this can only be done via our API

Using a fallback facility:

There might be situations where our customer do not want to perform a process manually in case an order could not be routed. Therefore we implemented a fallback facility to which orders can be routed in case they get the state “not_routable”. This fallback-facility can be defined via the API. Such a facility might be a “super-warehouse” which has kind of infinite capacity and/or infinite stock (or might get a fast replenishment).

One can only define a facility as a fallback facility if the state of the facility is “online”. Once you defined the facility as a fallback this facility cannot be set to “suspended” or “offline” anymore.

It is possible (at a later stage) to define more than one facility as an fallback facility. The order which cannot be routed initially is then routed to the fallback facility chosen by our DOMS ruleset. For this routing all fences are ignored and only the active ratings are used to find the best facility.

In the routing config one can also set a timeframe after which the not_routable order is routed to its final destination. In this timeframe the order is displayed in the “not_routable” Order overview. If the timeframe is set to 0, the order is directly routed to the fallback facility which is also the default value.

How to set up a tenant wide fallback facility via API

{
      "action":"ModifyGlobalRoutingConfiguration",
      "stopRoutingAttemptsAfterTime":"PT0H0M",
      "fallbackFacilityConfiguration": {
          "active": true,
          "facilityRefs": ["89f6d7f3-88ec-4653-96fd-c5b3476c46ce"],
          "fallbackAfterTime": "PT0H0M"
      }
}

How to set up a tenant wide fallback facility via backoffice