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
  • DOMS configuration
  • Order types
  • FAQs

Was this helpful?

  1. Clients
  2. Backoffice
  3. Network view

DOMS configuration

PreviousReturnsNextSettings

Last updated 5 months ago

Was this helpful?

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

Introduction

The distributed order management system (DOMS) is a backend component that orchestrates incoming orders from the online shop and decides where and how the orders can be fulfilled best. Routing rules that are configurable by the user are considered to meet the end customers' needs best. Based on these rules, the DOMS decides in which warehouse or store the order should be fulfilled.

Description

DOMS configuration

The DOMS logic is split into two different areas. For both areas there are custom rules which can be set by users as well as predefined rules specified by our platform.

: Can be used to exclude facilities from routing according to the selected fences.

: Can be used to weigh facilities according to the selected ratings.

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

Order types

When creating an order our systems differentiate between two types of orders:

  • Click & Collect, which can also be configured as Click & Reserve

  • Ship-from-Store, which includes standard delivery and same day delivery

Click & Collect orders

For Click & Collect orders, the following attributes can be defined:

  • Paid: A flag that indicates whether the order has yet to be billed when picked up by the customer (Click & Reserve) or already has been paid online (Click & Collect). This flag is not evaluated by any fence or rating but merely shown within the Operations App.

  • Supplying facilities:

    • In case supplying facilities are specified for a Click & Collect order, they will compete against the primary Click & Collect facility already when routing the order initially. In case a supplying facility performs better than the primary Click & Collect facility, this order will be routed to the supplying facility directly. The supplying facility in turn fulfills the order and sends it back to the primary facility.

Ship-from-Store orders

If the order is a Ship-from-Store order it is routed by our DOMS system. In order to perform routing decisions, orders as well as facilities need to be configured. Further input parameters like listings and stock information can improve the routing decision but are not mandatory.

For Ship-from-Store orders, the following attributes can be defined:

FAQs

How to define order type "Ship from Store" for a facility?
  1. Select “Network view”

  2. Define which Service Type can be selected by the customer

  3. In the DOMS configuration you can enable fences to specify the Ship from Store settings

How to define order type Click & Collect for a facility?
  1. Select “Network View”

  2. Select “Facilities” in the Cockpit

  3. Click on the setting-symbol in the facility overview

  4. Define for each facility the preferred order type(s)

A Click & Collect order is not routed by the DOMS logic since the customer has already chosen a facility from where he/she wants to pick up the order within the ordering procedure in the web shop. This means a C&C order must contain facility information and the order is routed directly to the specified facility. Optionally, the same is possible for Ship-from-Store orders (see ).

Primary facility: This is the facility which was chosen by the customer as a pickup location for her order. This attribute will be evaluated by the service type fence (see ).

These facilities are a fallback for the primary facility in case the primary facility cannot fulfill all ordered items. In this case, a reroute (see ) can be triggered into one of the supplying facilities (which have to be of service type Ship-from-Store). The supplying facility then fulfills the order and sends it back to the primary facility where the customer can pick it up. This limits the amount of facilities that have to be considered by the DOMS. This attribute will be evaluated by the service type fence (see ).

Service Level: Defines whether the customer requires same day or standard delivery. This attribute will be evaluated by the service type fence (see ).

Preferred Carrier: Can be used in case the customer wants to have her order delivered by a specific carrier. This attribute will be evaluated by the carrier availability fence (see ).

Preselected Facilities: Specifies a number of facilities that should be taken into consideration when performing a routing decision instead of all facilities within the network. This attribute will be evaluated by the preselected facility fence (see ).

https://docs.fulfillmenttools.com/documentation
Fences
Ratings
Fences
Rerouting
Fences
Fences
Fences
Fences
below