fulfillmenttools
  • Welcome to the fulfillmenttools Platform Documentation
  • Getting Started
    • Setup your access to fulfillmenttools
    • Make your first API Calls
      • Add your first facility
      • Add your first listing
      • Place your first order
    • Core concepts & terminology
      • Order Flow
    • Postman Collection
    • Client SDKs
    • FAQ
  • Clients
    • Backoffice
      • First steps - Registration
      • Network view
        • Home
        • Orders
          • Unroutable orders
          • Pre-orders & Backorders
          • Order History
        • Inventory Management
          • Stock Overview
          • Channel Inventory
        • Facilities
        • Users
        • Returns
        • DOMS configuration
        • Settings
        • Analytics
          • DOMS Pages
          • Fulfillment Operations Pages
          • Inventory Pages
          • Downloads Page
      • Facility view
        • Home
        • Inbound
        • Tasks
        • Listings
        • Storage Locations
        • Facility
        • Users
    • Inventory app
      • Registration Inventory App
      • App sections
        • Inbound
        • Storage and relocation
    • Operations app
      • Android
        • Manual Registration
        • Android Enterprise Registration
        • Sections
          • Picking
            • Load Units (legacy)
            • Substitute items
            • Weighed or measured products
            • Scanning configuration
            • Picking Methods
              • Batch Picking
              • Multi Order Picking
          • Packing
          • Handover
          • Returns (legacy)
        • Printing
        • Notifications
      • Webapp
        • Packing
      • Overview features Android & Webapp
    • Technical requirements
      • Zebra Hardware Scanner Configuration
      • Honeywell Hardware Scanner Configuration
      • Supported barcodes for camera scanning
      • Requirements for fft applications
      • Zebra printer
    • Returns app
      • Handle unannounced returns
      • Handle announced returns
  • Products
    • Core Functionality
      • Process
        • External actions
      • Add and manage facilities
      • Notification Center
      • Checking on features
      • Tags and Stickers Concept
      • GDPR
      • Remote Configuration
      • Expiry
      • Target time
      • Time calculation for queries of future availabilities (LPS-calculation)
      • Interfacility Transfer
    • Carrier Management
      • Overview
        • Available Carriers
      • Concepts
        • Carrier Country Service Mapping (CCSM)
        • Non-delivery-days
        • Custom Carrier & Headless operation of Carriers
      • Providing needed data
    • Fulfillment Options
      • Fulfillability Check
      • Checkout Options
        • Available fulfillment options based on basket
        • Earliest possible delivery date
        • Available delivery dates within time-period
        • Availability for delivery date
      • Delivery Promise
    • Inventory Management
      • Configurations
      • Entities
        • Listing
        • Stock
          • Stock Properties
        • Storage Location
        • Zone
      • Global Inventory
        • Stock availability
        • Channel Inventory
        • Expected stock
        • Inbound Process
        • Reservations
        • Safety Stock
      • Inventory Control
        • Inventory Traits
        • Measurement Units
        • Outbound Inventory Tracking
        • Storage Location Recommendations
    • Order Fulfillment
      • Headless Order Fulfillment
      • Pick Jobs
      • Zone picking
      • Load Units
      • Custom Service
      • Handover Jobs
      • Add External Documents
      • Configurations
        • Picking Configuration
          • Picking methods
          • Short Pick Reasons
        • Packing Configuration
          • Packing Container Types
        • Print / Document Configuration
        • Tag Configurations
          • Parcel Tag Configuration
        • Handover Configuration
        • Operative Container Types
    • Order Routing
      • Entities
        • Ship-from-Store Orders
        • Click-and-Collect Orders
        • Locked Orders
        • Custom Services Orders
          • Simple Custom Service Order
          • Complex Custom Service Order
      • Fences
      • Ratings
      • Order Split
        • Order split - initial routing
        • Order split after shortpick
        • Item bundles
      • Reroute
      • Shape the routing with the DOMS Toolkit
      • Decision logs
    • Returns Management
      • Returns legacy
        • Available status
      • Returns 2.0
        • Return Reasons
        • Item Conditions
        • Integrating Returns with Events
    • Use Cases
      • Demand-Driven Replenishment
      • Expected stock in availability
      • Multi Order Picking
      • Interfacility transfer
      • Assigned Users
  • Connecting to fulfillmenttools
    • General Topics
      • Use external identity providers to authenticate to fulfillmenttools
        • Microsoft Entra ID / Azure Active Directory (AD)
      • Public Event Export
      • Available Regions
      • Backup Policies
    • GraphQL API
    • RESTful API
      • General Topics
        • API Release Life Cycle
        • Versioning
        • Authorization
        • Customization via Attributes
        • Update Guarantees
        • Rate Limits
        • Resource Timestamps
        • Pagination Interface
        • Localization
        • Custom Attributes
      • OpenAPI Specification
        • Swagger UI
        • OpenAPI 3.0 Spec
    • Eventing
      • Structure of an Event
      • Available Events
      • Tutorial
    • commercetools Connect
    • Integration Tutorial
      • Adding facilities
      • Adding listings to facilities
      • Configuring stocks
      • Carrier configuration
      • Placing orders
      • Checkout Options
      • Distributed Order Management System (Routing)
      • Local fulfillment configuration
  • Incident Reporting
    • How to report incidents in fulfillmenttools
    • How to define incident priorities
  • Release Notes
    • Release Summary – May 2024
    • Release Summary – June 2024
    • Release Summary – July 2024
    • Release Summary – August 2024
    • Release Summary – September 2024
    • Release Summary – October 2024
Powered by GitBook
On this page
  • Introduction
  • Overview of pre-defined fences
  • Stock availability
  • Service type
  • Preselected Facilities
  • Carrier availability
  • Custom attributes
  • Same Day possible
  • Country
  • Facility Capacity
  • Ensure minimum picking
  • Static and reactive fences

Was this helpful?

  1. Products
  2. Order Routing

Fences

PreviousComplex Custom Service OrderNextRatings

Last updated 5 months ago

Was this helpful?

This page is outdated. Please go to our new documentation under .

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 unroutable.

Overview of pre-defined fences

The predefined fences below are available.

Stock availability

[ “Complete Stock” ] / complete fulfillment of individual order Checks if all articles of an order are available within the facility. This check calculates the stock and reserved stock in.

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

Service type

Checks if the service type of the order (Ship-from-Store Standard / Ship-from-Store Same Day / Click & Collect) can be fulfilled by the facility, see for more elaboration.

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, see for more elaboration.

Carrier availability

Custom attributes

(e.g. special services, carrier capacity, facility capacity, shipment destinations, delivery date…)

Same Day 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.

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

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

In order to know which reactive fences would have made an order unroutable we sort the sequence of fences from static to reactive and make sure that all reactive fences are processed with all entities. One fence would be enough to make an order unroutable but we need to know which other reactive fences would have been activated. By this we collect information about all filter reasons.

Checks if the carrier the customer has chosen for is enabled in a certain facility and thus can fulfill the order, see for more elaboration.

(checks if there is a facility which has the service type ship-from-store and at least one active Same Day carrier AND whether there is enough time for the facility to perform a Same Day delivery? (Today´s date + buffer time < cut off time of that Same Day carrier), see for more details.

checks if there are any free capacity slots available for a facility within a predefined timeframe in the future (see for details and examples)

checks that at least 1 ordered item is in stock. If this is not the case the facility is not considered in order routing Items which are bundled 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.

https://docs.fulfillmenttools.com/documentation
DOMS Configuration
DOMS Configuration
Settings
Same Day
Facilities
custom services