Unroutable orders
Last updated
Last updated
"Unroutable" means that an order was created and could not be assigned to a facility for fulfillment.
There is a chance that the DOMS is not able to route an order due to:
No facility can fulfill the requirements of a particular order
Misconfiguration of the
Especially in case of a it is very likely that an order cannot be routed at all because there is no facility available which can fulfill the request of the consumer on that very day.
A fallback facility can be defined if the user does not want to perform a manual process in case an order could not be routed. If a fallback facility was defined, orders are assigned to this facility in case they get the state “not_routable”. Such a facility might be a “super-warehouse” which has nearly infinite capacity (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 a facility was defined as a fallback it cannot be set to “suspended” or “offline” anymore.
It is possible (at a later stage) to define more than one facility as a fallback facility. The order which cannot be routed initially is then routed to the fallback facility chosen by the . 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 “Unroutable” tab in the Order overview. If the timeframe is set to 0 (which is also the default value), the order is directly routed to the fallback facility.
Go here to get more details on the .
No, if "" is set to "true", the order will stay in the last routed facility. Alternatively, users can define a , that the order will then be directed to. If the settings are not set to "true", our systems will try to re-route the the order to another facility.