fulfillmenttools
API documentationIncident ManagementFeedback
Products
Products
  • Products
  • Core
    • Fulfillmenttools and it's surrounding system
    • Facilities
      • Managed facilities
      • Supplier facilities
      • Facility groups
    • User management
    • GDPR
    • External actions
    • Notification center
    • Incident management
    • Tags
    • Stickers
    • Articles
  • Inventory Management
    • Overview inventory modules
    • Listing
    • Article categories
    • Stock
      • Stock availability
      • Stock properties
      • Stock updates
    • Reservations
    • Inbound process
    • Storage location
    • Zone
    • Inventory traits
    • Channel inventory
    • Measurement units
    • Stow jobs
    • External stock change reasons
    • Configurations
  • Availability & Promising
    • Availability & promising in customer journey
      • Earliest possible delivery date
      • Availability in delivery time period
      • Availability for specific delivery date
      • Checkout options
      • Delivery promise
    • Latest picking start
  • Distributed Order Management
    • Order management
    • Order routing
      • Fences
      • Ratings
      • Order split
      • Routing strategy
      • Item bundles
      • Re-route
      • Decision logs
      • Unroutable orders
      • Pre- and backorders
      • DOMS toolkit
  • Order fulfillment
    • Picking
    • Packing
    • Handover
    • Custom services
    • External documents
    • Load units
    • Interfacility transfer
    • Pick job target time
    • Configurations
      • Picking configuration
      • Packing configuration
      • Handover configuration
      • Printing & document configuration
      • Parcel tag configuration
  • Carrier management
    • Carriers and connection to facilities
    • Carrier country service mapping
    • Same day delivery
    • Custom carrier
    • Available carriers
  • Returns Management
    • Introduction to returns
    • Return reasons
  • Use Cases
    • Creating & executing stow jobs
    • Creating orders with interfacility transfers
    • Demand-driven replenishment
    • Expected stock in availability
    • Incoming goods & storage
    • Multi order picking
Powered by GitBook
On this page
  • Introduction
  • Routing plan
  • Difficulties while routing
  • Examples of routing decisions for an order
Edit on GitHub
  1. Distributed Order Management

Order routing

PreviousOrder managementNextFences

Last updated 4 months ago

Introduction

The dynamic routing in the fulfillmenttools platform finds the best option (facility) to fulfill an order. Users can define multiple factors which should be considered when making the decision for the best fulfillment location.

The order routing can receive orders & order requests from any commerce channel and decides from where and how they can be fulfilled best, taking various flexible & configurable routing rules into account. If there is no fixed facility defined where the order has to be fulfilled, the distributed order management () will determine which facility is the best fit for fulfilling an order.

The system allows to define fences and ratings:

  • : Exclude facilities from order routing according to the fences selected

  • : Weigh facilities against each other according to the ratings selected

Routing plan

The main entity of routing is the routing plan. It can be seen as a vehicle which informs and enables the systems downstream of DOMS in the fulfillment process (like picking) about the routing decision.

The routing plan contains all the information that was relevant for the orchestration of an order like ordered items or delivery preferences. Ultimately, the routing plan contains the result(s) of the routing decision.

Difficulties while routing

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

Examples of routing decisions for an order

More information about the routing plans can be found in the .

More information on unroutbale orders can be found under .

routing plans REST API documentation
Products – Unroutable Orders
DOMS
Fences
Ratings
Drawing