Mass inventory lets you correct the balances of several products in one warehouse. Count the actual quantities by warehouse slot and enter a new total quantity for each row. Spotilla allocates the changes to purchase batches according to the warehouse's inventory usage principle.

These instructions apply to the browser's Mass inventory function. Product inventory on Android and iOS handles a separately selected purchase batch: the mobile field New amount in batch refers to the batch balance, not the total quantity in the slot. To choose the batch to correct yourself, use batch-specific inventory.

Before taking inventory

The warehouse feature must be enabled. You need permission to read products, access to the warehouse being processed and permission to take inventory. In the Manager role, inventory permission is granted through the Edit permission for warehouses or warehouse events. View permission alone is not sufficient.

The warehouse must have warehouse slots. Mass inventory shows product and warehouse slot combinations associated with a purchase batch. Rows with a zero balance may also be included. Deleted and deactivated products are excluded. This function does not add a product to a new warehouse slot. Record a missing receipt as a receipt or purchase transaction.

Agree on how product receipts, issues and other balance changes will be handled during inventory. The new balance is compared with the balance at the time of background processing, which may differ from the quantity when the table was opened.

Select a warehouse and filter the products to count

  1. In the browser navigation, open Manage warehouses → Products.
  2. Open Actions in the header of the product table's checkbox column and select Mass inventory. You do not need to select product rows: selections in the product table do not determine which items this function processes.
  3. In the form that opens, select the warehouse to process in the Warehouse field. The project warehouse Projektilla is not available for selection.
  4. If needed, use the Search by warehouse slots, Search by product category, Search by product name and Search by product code fields under Optional filters. Without filters, all eligible rows in the warehouse are retrieved. The name filter also searches the product's additional name; the name and code filters can match parts of a name or code. All specified filters apply together.
  5. Select Continue and wait for all rows to load before entering shared values. Loading progress is shown above the table. If no products match the filters, the inventory table closes. Start again and check the filters.

Enter new slot balances

Each row represents one product in one warehouse slot. The same product may appear on several rows if it is stored in several slots. Balance in warehouse slot is the total quantity of the product in that slot. Click the row's New balance cell and enter the counted total quantity in the product's storage unit, such as pieces or metres. Do not enter the difference or the quantity of just one purchase batch.

For example, if a slot contains two batches of 4 and 6 pieces, the slot balance is 10. If the counted total quantity is 7, enter 7 as the new balance. Spotilla reduces the quantity by 3 pieces in total.

Zero is an allowed new balance. Blank or negative values, and values equal to the current balance shown in the table, are not submitted for processing. You can enter the reason for the correction in the row's Description cell; the description is optional and can contain up to 512 characters.

If a row should not be included in the inventory, leave its New balance blank, clear the value or remove the row using the trash icon on the right. The trash icon removes the row from this inventory request, not the product or its warehouse data.

Shared values and reviewing rows

You can filter the rows shown in the table using the filters below the column headers. Above the table, Set the same product quantity for all enters the same new balance for all already loaded rows that match the filters, including rows on other pages of the table. Description for inventory transactions enters a shared description for those rows. These values replace any previous entries on the affected rows. Clearing a shared field does not clear values already entered on the rows; clear them individually if needed.

In the Show only selected items menu, you can select Rows that will be sent or Rows that will not be sent. Rows that will not be sent also include unchanged and invalid quantities. The blank option in the menu removes this filter.

Filtering does not exclude rows with values already entered from the inventory. Submission also includes rows hidden by filters if their new balance is valid and has changed. Finally, remove the filters and check all rows that will be submitted. The count on the Inventory … products button refers to the number of product–warehouse slot rows to process, not the number of pieces being counted or necessarily the number of distinct products.

Which purchase batches receive the change?

Check the usage principle in the browser navigation under Manage warehouses → Warehouses. On the Warehouses tab, select the warehouse and check Inventory usage principle in its Basic info section. FIFO is the default for a new warehouse; check the saved selection for an existing warehouse. The section's Edit button opens the warehouse editing form if you have permission to edit the warehouse. Permission to edit warehouse events alone does not allow you to change warehouse settings.

This usage principle determines how changes are allocated. Batches are ordered by their receipt time:

  • FIFO: reductions start with the oldest batch. Increases are allocated to the newest batch.
  • LIFO: reductions start with the newest batch. Increases are allocated to the oldest batch.

If needed, a reduction continues through subsequent batches of the same product in the same warehouse slot. Only batches with a positive quantity are included in a reduction. An increase is applied to one batch, which may already be empty. You do not select the batch yourself in mass inventory.

If the oldest batch contains 4 pieces and a newer batch contains 6, reaching a new slot balance of 3 requires a reduction of 7 pieces. With FIFO, the old batch is set to zero and the newer batch to three. This creates two inventory events. The quantity recorded in an event is the new balance of that batch, so the quantities on event rows should not be interpreted as quantities to subtract.

The balance of the default batch created by the system cannot be increased through inventory. If an increase is automatically allocated to that batch, the change fails; record the additional products as a new purchase or receipt.

The slot balance must not become negative. However, the inventory balance check does not subtract quantities allocated to ongoing or future reservations from the balance, or verify that the new balance is sufficient for them. Check the quantity required for reservations separately: a successful inventory does not guarantee sufficient stock for reservations.

Effects on balances and history

Inventory updates the slot's total balance, the current quantities of the processed batch rows and the purchase batch statuses. If a batch row's new quantity exceeds its positive original quantity, Original number of products is also increased to match the new quantity. A row created by a transfer whose original quantity starts at zero is not increased in this way.

A batch's status is determined by all its product rows: All used when their current quantities are zero; Partially used if at least one row's quantity is lower than its original quantity; otherwise Received. Setting one slot to zero therefore does not necessarily empty the entire batch. Setting a balance to zero does not delete the product, batch or previous events. New warehouse and batch history events are saved for the correction.

Effects on average purchase price and inventory value

The FIFO/LIFO inventory usage principle is a separate setting from Inventory valuation principle, whose options are FIFO and MAC. Under FIFO valuation, a quantity change affects the value at the allocated batch's purchase price or its applicable manually set current value. A missing purchase price is treated as zero.

An inventory increase recalculates the product's weighted average purchase price. The calculation is (previous total quantity × previous average price + added quantity × allocated batch's purchase price) ÷ (previous total quantity + added quantity). Only the added quantity is included, not the entire final inventory balance. The total quantity is derived from the product's event history across the company and also includes products held at reservation destinations; it is not limited to the slot being inventoried. Internal transfers and reservations do not themselves change the company's total quantity.

If the previous total quantity is zero, the new weighted average price is the unit price of the increase. If the starting quantity derived from the event history is negative because of incorrect history, the calculation uses zero instead. This calculation rule does not correct incorrect balances.

An inventory reduction does not change the weighted average price at the time of the event. However, it reduces the remaining total quantity and therefore the weight of the old average price in the calculation for the next purchase or inventory increase.

For example, a previous total quantity of 10 pieces at an average price of €5 per piece, plus 2 additional pieces found during inventory in a batch with a purchase price of €8 per piece, gives a new average price of (10 × 5 + 2 × 8) ÷ 12 = €5.50 per piece. The unweighted average purchase price is a separate figure: each purchase batch has equal weight regardless of quantity. An inventory increase does not create a new purchase or add a new purchase batch to the calculation.

An inventory increase updates the existing purchase-specific average price data and records the calculation in the average price change history. It does not create a new purchase-specific average price row. If an old purchase has no average price history, inventory does not retrospectively create the missing history for it. The values from the original average price calculation are kept separate from the updated values.

In MAC warehouses, quantities are valued using the product's company-wide weighted average price. An average price changed by an inventory increase can therefore also affect the value of the same product in other MAC warehouses, even though their quantities remain unchanged. A manually set current value overrides the MAC value when valuing that batch row, but the average price calculation for an inventory increase uses the batch's purchase price.

Average purchase prices are displayed to two decimal places: if the third decimal is 5–9, the last displayed decimal is rounded up. The calculation uses more precise values, which are also shown in the price field tooltips. For more details, see how inventory value and product cost price are determined and viewing purchase batches and purchase prices.

Submit and verify the result

  1. Check the rows, new balances and row count on the button. Select Inventory … products at the bottom of the form and accept the confirmation prompt.
  2. Wait for background processing. The notification Operation will be performed in the background, this may take a moment means the request has been received, not that all rows have been completed. Average purchase prices are calculated separately after balance processing, including for increases that succeeded before a possible error.
  3. In the Products table, open the product details using the row's pencil icon and select the Warehouse balances tab. Check the quantity in the correct warehouse and each inventoried slot.
  4. On the product's Warehouse events tab, check the Inventory events created and their descriptions. A reduction split across several batches may create several events from one inventory row. You can also find events for the entire warehouse under Manage warehouses → Warehouses in the navigation, on the Warehouse events tab. Filter the view to the warehouse you processed.

A new snapshot of inventory value history is created in a separate regular calculation that starts in the 23:00 run in the environment's time zone. The snapshot timestamp is the time of the actual calculation. Acceptance of the inventory request therefore does not mean that the value in inventory value history has already been updated.

A request may be completed only partially: an error does not roll back events already saved, and even a reduction for a single slot row split across several batches may remain incomplete. An error may also stop subsequent rows from being processed in the same background job; other background jobs for the request may continue. Do not immediately resubmit the entire inventory. First check the current slot balances and completed events, determine the cause of the error and, if needed, perform a new inventory only for rows that require correction. For help investigating, see investigating warehouse events and balance errors.