Product usage on report pages shows the number of selected inventory event rows for each product. Product Costs shows the recorded product costs and income for tasks and service requests. You can use these reports to compare how often events occur and the monetary amounts associated with products, but you cannot use the usage count to determine the number of units consumed.

Open the report and select the data

In the browser's main menu, open Dashboard → Report pages and select a report page using the selector at the top of the page. An administrator can add a report using the Add new report button at the top of the page: search for Product usage or Product Costs and drag the report from the selection onto the page. Save the addition with Save the page.

Open Settings in the report's title bar. Under All filters, select Search criteria. In both reports, Product use on a Task and Product use on a Service request are included by default. In the usage report, you can also select Data based on inventory events and Data based on sell events; these are disabled by default.

The product filters in the same section let you select a warehouse, product category and products. The filters work together: for example, selecting a product and a warehouse includes only data for the selected product from the selected warehouse. In Product usage, the warehouse filter applies to the event's source warehouse; in Product Costs, it applies to the warehouse recorded on the work item's product row. The product category filter uses the product's current category.

The data included in Product usage depends on your permissions for inventory events and warehouses. For users other than administrators, Product Costs is limited to completed tasks and service requests that the user has permission to view. The same filters therefore do not guarantee the same results for different users.

Select a time period and time grouping

Tme period for the data in the report settings limits the data included. A new report defaults to the previous and current calendar years. Time grouping for data determines whether the figures are shown by day, week, month or year; the default is month. Daily grouping is not available with a year-based time period. To check individual days, select a start and end date.

For Product usage, the relevant time is the inventory event creation time. For Product Costs, it is the cost row creation time, not the work item's creation date, due date or invoice date. For users other than administrators, the work item's completion time must also fall within the selected period. For example, a cost row created in February for a work item completed in March may be excluded from the February report.

Day boundaries are determined by the user's time zone, which defaults to Helsinki. With weekly grouping, the end of the period falls at the start of the week's last day, so entries from that day may be excluded. Check the full week's figures using daily or monthly grouping before using them as a summary. Other time period options are described in Report time periods and filters.

What does Product usage count?

Each included event row increases the product's count by one. One event using 20 units produces a count of 1. Two events with quantities of 2 and 8 units produce a count of 2, even though 10 units were used in total. The figure is the number of events, not the number of units, the amount of work or a utilization percentage.

One product row on a work item can generate multiple events if the deduction continues from another storage location because the balance is insufficient. These events are also counted separately. Inventory and sales events can be included, but purchases, transfers, reservations and reservation returns are not among the event types selectable for the report. Including an inventory event increases the event count by one regardless of the quantity inventoried or the direction of the balance change.

Simply adding a product to a task or service request does not yet generate a usage event. Completing the work item starts the inventory posting in the background. The posting requires a warehouse and a storage location belonging to it to be selected on the product row, and the product must be active. Product rows saved on Android and iOS are also processed by this server function. Wait for processing and reload the report. For instructions on attaching a product to a work item, see Attaching a spare part to a Spot and a task.

What do cost and income mean in Product Costs?

Product Costs uses the product cost rows recorded on work items. Working hours, travel expenses, other costs, sales made directly from inventory and inventory events are not included in this data. Cost rows are usually created when the work item is completed. Pricing based on purchase batches may finish in the background; product rows awaiting pricing are not yet included in the report.

A product row's cost is based on the product quantity and the cost price used. The recorded sales amount is calculated from the product quantity and the unit sales price. The report uses these recorded amounts and does not reprice old rows using the product's current price.

The product cost pricing setting determines which price is used. If waterfall rules are enabled, the first rule to produce a valid price, including a zero price, takes effect. With FIFO/LIFO pricing, the cost may be refined in the background based on the purchase batches used. If batch events do not provide a price for the full quantity, the missing portion is priced using a fallback price. This does not correct any missing inventory deduction. Price selection, rule order and the basis for the fallback price are explained in Inventory value and product cost. Using a product row's own sales price is explained in Attaching a spare part to a Spot and a task.

The disappearance of the pending status alone does not prove that batch pricing succeeded. If background processing encounters an error, the row can be changed to a regular product cost row without updating its value. Therefore, check the work item's recorded cost and actual inventory events separately, especially if the amount or inventory deduction differs from what you expected.

  • Row defined as a cost: the row's value is added to the Total cost series and the recorded sales amount to the Income series. A missing sales amount does not add income.
  • Row defined as income: the row's value is added only to the Income series. Any separate sales amount on the same row is not added again.

For example, a €80 cost row with a €100 sales amount shows a cost of €80 and income of €100. If a €30 income row is also included, the cost remains €80 and income is €130. The combined height of the series is not profit: the report does not calculate margin by subtracting cost from income. Amounts are calculated separately for each product or folder and time period, then rounded to two decimal places.

Income means the income recorded on the product row, not a payment received from the customer. The report does not filter data by invoicing or payment status. The current inventory value and an inventory event's change in value are also different from a work item's product cost.

An administrator's data is not filtered by the work item's current status. A retained product cost row may therefore still be included even if the work item is no longer completed or has been deleted. For other users, only visible work items that are currently completed and whose completion falls within the period are included. If cost rows are also deleted when the work item is deleted, they are removed from the cost report's data.

Product view and folder comparison

The product view in both reports shows a maximum of 100 products that match the data criteria. This limit does not select the products with the highest usage counts or costs. If there are more products, narrow the selection before drawing conclusions about the totals. The Excel export also exports the data shown in the report; it does not remove the product limit.

In Product Costs, you can switch from products to a folder comparison by selecting By folder under Group by in the settings. You can then select the folders to compare using the Folder selector that appears. Costs from a selected folder's subfolders are combined into that folder's total. The selector normally prevents you from selecting both a parent folder and its subfolder at the same time: first remove the previous selection if you want to examine a different level instead. If no folders are selected, groups are formed from the folders present in the data.

The folder is determined from the current folder of the work item's Spot. Moving the Spot can therefore also move old costs into a different group the next time you search. If the work item has no Spot or its folder can no longer be determined, the row is excluded from the folder comparison. The product and folder results therefore do not always cover the same rows. The Product usage report remains grouped by product.

Save and verify the result

Changing the filters updates the view. An administrator saves the selections for an already saved report using Save Settings in the title bar. A new report is saved to the page using Save the page. The saved change applies to the report on the page when other users open it as well. Other users cannot save the settings permanently. Report filters do not change products, balances or cost rows.

First verify the result using one product and a short time period:

  1. Check the report's time period, data selections and product filters. At least one event type must be selected for Product usage. For Product Costs, keep at least task or service request data included: deselecting both prevents a new search, so an old chart that remains visible does not demonstrate the result of the selection.
  2. Compare the usage count with the number of inventory event rows for the same product, using the same event types and creation time filter. Also check related additional events. See Investigating inventory events and balance errors.
  3. Open the task or service request that is the source of the cost and its Work costs tab. Compare the costs and income of the included product rows separately, and check their quantities, pricing setting and actual inventory events if necessary. If you are not an administrator, check the completion status and time.
  4. If necessary, open the three-dot menu in the report's title bar and select Export to Excel to check the series by time period. After saving, reopen the page and check that the selections were retained.