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
  • Description
  • Reasons for unroutable orders
  • Using a fallback facility
  • FAQs

Was this helpful?

  1. Clients
  2. Backoffice
  3. Network view
  4. Orders

Unroutable orders

PreviousOrdersNextPre-orders & Backorders

Last updated 5 months ago

Was this helpful?

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

Introduction

"Unroutable" means that an order was created and could not be assigned to a facility for fulfillment. In order to prevent that orders are lost, a dedicated overview was created for unroutable orders. Within this overview, the administrator gets a complete list of all affected orders as well as some mechanisms to specifically manipulate an order so that it can be fulfilled.

Description

Reasons for 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 it is very likely that an order is not routed at all because there is no facility available which can fulfill the request of the consumer on that very day.

Using a fallback facility

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

FAQs

How to deal with unroutable orders?

You have the following options to deal with unroutable orders:

  1. Assign a new facility for fulfillment: 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. It is possible to assign the partial or the whole order.

  2. Changing consumer address enables the user to handle situations where the shipment could not be delivered and a second attempt (with another address) should be performed.

  3. Trigger a new DOMS decision: 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.

  4. Canceling an order cancels all corresponding Pickjobs of an order. It is possible to cancel the partial order or the whole order.

  5. Reroute a specific order triggers a reroute decision for this selected order. It might be, that the order gets successfully routed or the routing attempt again fails and the order remains unroutable.

  6. Reroute all unroutable orders triggers the same routing like described above, but all orders are taken into account. You find this feature in the three-dot menue in the header of the table.

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?

Go here to get more details on the .

Will an order become unroutable if no facility can fulfill it in case of a ?

No, if "s" is set to "true", the order will stay in the last routed facility. Alternatively, users can , 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.

https://docs.fulfillmenttools.com/documentation
same day order
DOMS ruleset
Routing Configuration API
short pick
blacklistedassignedfacilitie
define a fallback facility