Fulfillment operations pages
Last updated
Last updated
This page displays the number and status of , and in various ways to give insights into the stores' performance.
Here the total number of completed entities by date is shown. "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.
This chart breaks down the completed pick jobs according to the value of an order tag. 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 pick jobs were completed for "B2B" customers.
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.
Created pick jobs and successfully closed handover jobs (status HANDED_OVER) are shown here in direct comparison by date to visualize, for example, how the order processing is keeping up with the load.
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. The status “failed” contains several cases in which a pick job is considered unsuccessful (canceled, aborted, expired, ...).
In this example around 40 pick jobs were finished on November 30, but only 16 of them were picked successfully and completely.
In this example, 10 order lines with a total quantity of 11 items were picked on August 3. An item could have had a quantity of 500 grams, for example, but this would only have increased the displayed quantity by 1.
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.
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 finishing 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).
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.
This is the total average calculated over all selected dates and facilities.
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 estimating how large typical deviations from the mean value are.
The average value is given per facility, sorted by the highest value. A maximum of 30 facilities is listed.
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.
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.
As a rule, returns are assigned to the facility that receives them, with the assigned date reflecting the date of the initial processing at that facility. The logic for the order return ratio and product return ratio deviates from this due to the complexity of possible processes (for example, one order can lead to several parcels and several returns on different days and the same product id may be present in several of these entities without a clear connection being possible). An explanation is provided in the corresponding sections below.
Here the number of handovers performed and returns received can be seen, which makes it possible to compare outgoing and incoming parcels. The returns are assigned to the date when the processing took place in the receiving facility.
This is the proportion of orders with at least one return out of all orders for which a shipment was made. The date used for each order is the date when the first handover for that order took place. For example, if 50 orders had their first handover on November 22 and 10 of those had at least one return at some later point in time, the ratio of 20% is assigned to the aforementioned date.
The calculation of these values does not work in conjunction with a facility filter.
Similar to the order return ratio, this is the proportion of returned products (i.e., the total quantity) in relation to the total number of products shipped. To calculate the product return ratio, the return of a specific product within a particular order is assigned to the date when that product in the order was first shipped. All shipments of a specific product from a particular order are also only assigned to the earliest shipping date for each order. This approach is necessary because, in general, a returned item cannot be assigned to a specific handover if it has been shipped several times.
In the example shown, a quantity of 152 products had an earliest assigned shipping date of October 29. Later, 38 of these products were returned.
Calculating these values does not work in conjunction with a facility filter.
This table lists the most returned products in descending order of total quantity.
The average number of order lines per return is shown here. In the example, returns received on November 17 had an average of 3.7 order lines.
This table lists the handovers performed and returns received by facility, sorted in descending order by the number of returns.
The return time or return duration is defined here as the time between the first handover for a specific order and the processing of a respective return of this order. In the chart below, three quantiles of the return time are depicted by date. This allows the typical and more extreme values to be estimated. The assigned date is the day the return is processed. In this example, on December 1, 5% of the returns were received 36 or more days after the original shipment.
The quantities returned for a particular reason are displayed in tabular form and visually against the date. The table lists the reasons in descending order by quantity affected and shows the number of returns containing this reason. The example chart below shows that on November 11, a quantity of 72 was returned with the reason “Bad quality”. It should be noted that each product in a return can have individual and even multiple reasons. The sum of the quantities shown can therefore be higher than the total quantity returned.
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. Products for which it is known from the that they are not counted in pieces are added with the quantity “1” for each order line.
This page provides various data on shipments / and . No orders will be considered on this page.
Two additional tiles show the total value of the goods handed over, by facility as well as by date. The values as well as the currencies are taken from the item . If different currencies appear in the data, they are still added together, with all currencies being listed on the label (e.g., “EUR / USD”). In the example, goods worth €4174.67 were shipped on November 18.
