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
  • Orders
  • Routing

Was this helpful?

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

DOMS Pages

PreviousAnalyticsNextFulfillment Operations Pages

Last updated 5 months ago

Was this helpful?

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

Orders

This page contains various data about orders, including order time, status and line items. As this information exists independently of the routing of the orders, there are no references to facilities here.

Incoming Orders

Finished Orders and Order Finishing Time

The chart below shows three quantiles of the finishing time by date. This allows you to assess both the typical and the more extreme times. In this example, about 5% of orders that finished on July 16 took more than 51 minutes to finish.

The arithmetic mean is not given here as experience has shown that rare but often unavoidable outliers in process times strongly distort the mean value and lead to incorrect impressions.

In this chart you can see the orders by the date they were created, but separated by their current status. This allows you to identify older orders that have not yet been finished. In this example, 167 of the orders created on August 1 have not yet been finished.

Lines per Order

Most Ordered Products

Canceled Orders

Orders by Service Type

Routing

Successful Routings

Reroutes

If a picking task is aborted and rerouted as a result, this also leads to an entry under 'shortpick'. A manual reroute can occur both when an individual task or the entire order is reassigned manually. Even if an order is automatically routed again after a reset of the entire process, this is counted as a manual reroute.

In addition to the source location, the chart below also shows the target location of reroutes, together with the associated frequency. In this example, 708 tasks were routed from Hamburg to Frankfurt.

If an order split occurs during the reroute, it is not clear which target facility should be displayed. In this case, only the first facility that was used during the routing is counted as the target facility.

Reroute Ratios

An obvious definition of the reroute ratio seems to be "What proportion of my routings were rerouted later?". However, since these events can happen on different days, this KPI cannot be calculated in conjunction with a selected time period.

For this reason, a different definition is used here, which answers the question "What proportion of the finished tasks in a facility ended with a reroute?" More precisely, for the example of manual reroutes:

manual_reroute_ratio = number_of_manual_reroutes / (total_number_of_reroutes + number_of_pickjobs_finishing_any_other_way)

Note that the denominator has two parts, as a reroute can occur before a pick job has been created. In the chart below, 1640 tasks were somehow finished on August 6, 43 of them with a reroute by shortpick. This corresponds to a ratio of 2.8%.

A high reroute ratio alone might not be too alarming if the total number of routings to the location is rather low. For this reason, both values are also plotted against each other in a scatter plot, with each point representing a location. Attention should be paid to data points in the top right-hand corner, as they indicate facilities with both a high number of routings and a high reroute ratio. In the example, this applies to Munich.

Unroutable Orders and Fallback Routings

Since it makes a difference whether orders were only temporarily or permanently unroutable, this is displayed separately. In the example below, there were about 2000 routings on July 10 that went into the unroutable status, but only 144 remained in it ("Last status is unroutable") while the rest changed their status subsequently to something else ("Earlier status is unroutable").

Order Splits

In the following graphic, each order leads to a single entry. Here, on August 5, there were 61 routings of orders that led to exactly 2 splits (3 parts). Only routings that have not been rerouted are taken into account. This means that if there was initially a split, but not after a reroute of the entire order, no split is counted for this order.

Completely Picked Pick Jobs

completely_picked_pickjobs(ratio) = closed_and_completely_picked_pick_jobs / (total_number_of_reroutes + number_of_pickjobs_finishing_any_other_way)

In addition, the percentage of successfully closed but only partially picked pick jobs is also shown in the graphic below. In this example, 1202 pick jobs were completely picked on August 7, while 1480 tasks ended in some way overall.

The number of incoming / created orders is displayed in different ways (total, by date, by time of day, by day of the week). The relevant time used here is the as set by the upstream system, not the time when the order entity was created in the fulfillmenttools platform.

Orders are considered finished when the is set to FINISHED. The finishing time is the period of time between of the order and the time at which an order is considered finished.

and finished orders are shown here in direct comparison so that you can see, for example, how the order processing is keeping up with the load.

This is the average number of order lines per order for orders that were within the selected time span or on a specific date. This value is shown both in total and by date

The table lists the products that were present in the most orders within the selected time span.

This chart shows the number of orders that were canceled per day using the or the .

This graph allows you to see what proportion of the orders are Orders or Orders.

Here you will find -related figures and KPIs such as the number of successful routings, re-routes and order splits, displayed both by date and by location. Use the dropdown to also see some of these values as a scatter plot on the map.

A routing is counted as successful if an assignment to a location has taken place. Due to and , an order can lead to several (successful) routings.

Usually, a is also generated in each case. An exception to this are , where a pick job is only created after unlocking.

The number of is listed separately by reason: 'shortpick', 'inactivity' and 'manual'. The facility assigned to a reroute corresponds to the facilty from which is routed away, not the one to which may subsequently be routed. For example, in the picture below 4102 tasks have been removed from the munich store and routed elsewhere.

A definition of these terms can be found . The number of non-routable orders and fallback routings are shown both in total and by date. In the case of order splits or if an order generates several failed / fallback routings, several entries per order can actually arise.

The occurrence of is shown separately according to how many parts an order is split into. "1 split" means a split into two parts.

The routing should assign an order to a location where it can be fulfilled in the best possible way. For this reason, the “completely picked pick jobs” indicate the proportion of incoming tasks that lead to successfully closed and fully picked pick job. More precisely, analogous to the :

orderDate
API
Backoffice
routing
pick job
locked orders
reroutes
here
order splits
status of the underlying process
creation
Incoming
created
created
click-and-collect
ship-from-store
created
reroutes
order splits
calculation of the reroute ratios
https://docs.fulfillmenttools.com/documentation