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
  • Completed Tasks
  • Process Times

Was this helpful?

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

Fulfillment Operations Pages

PreviousDOMS PagesNextInventory Pages

Last updated 5 months ago

Was this helpful?

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

Completed Tasks

This page displays the number and status of , pack jobs and in various ways to give you an insight into the performance of your stores.

Completed Tasks

Here you can see the total number of completed entities by date. "Completed" here means that the entities must have reached a successful final status. Final statuses that correspond to a failure (e.g. a cancellation) are not counted.

The assigned date corresponds to the time when the final status was reached. If an entity was reopened and closed again after completion, the time of the second completion is used.

Completed Pick Jobs by Order Tag

Since tags can be created freely by you, the tag key by which the breakdown is made must be configured for the dashboard. Otherwise this chart will not be visible.

Incoming vs. Completed Tasks

Created pick jobs and successfully closed handover jobs (status HANDED_OVER) are shown here in direct comparison by date so that you can see, for example, how the order processing is keeping up with the load.

Pick Job End Status

These charts show how often pick jobs were finished with which status. For "closed" pick jobs, a distinction is made as to whether they were completely or partially picked.

Here around 40 pick jobs were finished on August 18, but only 16 of them were picked successfully and completely.

Picked Order Lines and Quantity

Here, 10 order lines with a total quantity of 11 articles were picked on August 3. An article could have had a quantity of 500 grams, for example, but this would only have increased the displayed quantity by 1.

Process Times

This page is intended to provide detailed information on how long different process steps take within the facilities. The page is divided into two parts: the upper section provides a quick overview of three important durations, while the lower section provides further details on a single selectable duration.

Time Until Picking, Picking Time and Handover Time

The following three durations are shown both aggregated as a total value and by day/week/month:

  • Time until picking is the time that elapses between the creation of a pick job and the first time that picking is started. If a pick job is somehow ended, reopened and picked again, this is not taken into account here. An analogous restriction applies to the following periods.

  • Picking time is the time that elapses between the first time picking is started and the first time a pick job is closed (status CLOSED).

  • Handover time is the time that elapses between the creation of the handover job and the first time the handover job is closed (status HANDED_OVER).

Process Details

As there may be many process times of interest, the details are shown for a single selected one of these times. The selection is made using the dropdown in the filter bar:

The following graphs then refer to this selected duration.

Total Process Time

This is the total average calculated over all selected dates and facilities.

Process Time by Date

In addition to the average value per day/week/month, the band within which 80% of all cases lie is also shown here. This allows you to estimate how large typical deviations from the mean value are.

Process Time by Facility

The average value is given per facility, sorted by the highest value. A maximum of 30 facilities are listed.

Process Time and Number of Instances by Facility

A high process time alone might not be too alarming if the total number of cases is rather low. For this reason, both values are also plotted against each other in a scatter plot, with each point representing a facility. Attention should be paid to data points in the top right-hand corner, as they indicate facilities with both a high duration and a high instance count. In this example, the rather high number of 373 pick jobs in Berlin was created and then picked. The average time between these events was around 9 hours, which is in the midfield.

Process Time Distribution

This graph shows the frequency of cases where a certain amount of time was required. In the example below, it can be seen that the majority of the selected durations were less than 10 hours. In 560 cases, however, the time was around 33 hours.

This chart breaks down the completed pick jobs according to the value of an . In the example below, orders could have an order tag "customer type", with three possible values "B2B", "B2C" and "Internal". On the selected day, 16 pickjobs were completed for "B2B" customers.

The number of picked order lines and the sum of the picked quantity can be seen here, both per day and in total. For the assignment to a day the time when the respective pick job was closed is used. Articles for which it is known from the that they are not counted in pieces are added with the quantity “1” for each order line.

All durations shown here are arithmetic means, with outliers removed on the basis of anomaly detection. This will be replaced by median/quantile data analogous to the .

order tag
measurement unit
https://docs.fulfillmenttools.com/documentation
pick jobs
handover jobs
order finishing time