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
  • Overview of pre-defined fences
  • Complete stock
  • Service type
  • Preselected facilities
  • Carrier availability
  • Same day delivery possible
  • Country
  • Facility capacity
  • Ensure minimum picking
  • Static and reactive fences
Edit on GitHub
  1. Distributed Order Management
  2. Order routing

Fences

PreviousOrder routingNextRatings

Last updated 3 months ago

Introduction

Fencing is a concept which describes an absolute requirement for a routing decision. If a facility cannot meet the requirement of an order, the facility is excluded from the routing decision. This can lead to a situation where no facility can meet the requirement of the order. If this is the case the order is brought back to the pool and is included in upcoming routing decisions or becomes.

Overview of pre-defined fences

The predefined fences below are available.

Complete stock

[ “Complete Stock” ] / complete fulfillment of individual order Checks if all ordered items are available in the facility. This check already considers reservations and other stock that is not available for certain reasons.

Please note that the complete stock fence can not be combined with order split

Service type

Checks if the of the order (ship-from-store standard / ship-from-store same day / click & collect) can be fulfilled by the facility.

Preselected facilities

Reduces the facility candidates which should be considered from all facilities within the network to only specified ones. This list may contain 1-n facilities and is only applicable for ship-from-store orders.

Carrier availability

Same day delivery possible

Country

Checks if the address of the facility is within the same country as the address of the consumer. Only those facilities are taken into consideration.

Facility capacity

Ensure minimum picking

Static and reactive fences

A fence can be a static fence or a reactive fence.

In order to know which reactive fences would have made an order unroutable the sequence of fences are sorted from static to reactive and make sure that all reactive fences are processed with all entities.

Checks if the the customer has chosen is enabled in a certain facility and thus can fulfill the order.

Checks if there is a facility which has the service type ship-from-store and at least one active carrier AND whether there is enough time for the facility to perform a same day delivery.

Checks if there are any free available for a facility within a predefined timeframe in the future.

Checks that at least one ordered item is in stock. If this is not the case the facility is not considered in order routing. Items which are so that they are not split within routing (see: ) are considered as one in this fence. Meaning that if one item is missing in such a bundle all items within this bundle are seen as missing.

A static fence is a fence where there is no event trigger. If an order becomes because of a static fence this order will remain in the unroutable order section.

A reactive fence has an event trigger. This means that systems constantly check for events which might dissolve this fence so that the order becomes routable. For now, only the “” fence can be set as a reactive fence. If an order becomes unroutable due to an out of stock situation and the items are , the order gets routed automatically if stock becomes available.

carrier
same day
bundled
custom services
unroutable
pre-/backorderable
complete stock
unroutable
Toolkit fence REST API documention
service type
fulfillment capacity slots