Manage inventory defaults /visma-net-erp/help/inventory/manage-inventory-defaults section 2026-02-19T17:09:06+01:00 # Manage inventory defaults Click the links below to learn more about a topic you are interested in. Use the breadcrumb links in the upper left corner to see your location, navigate backwards or go to the starting point. Manage inventory defaults - overview /visma-net-erp/help/inventory/manage-inventory-defaults/manage-inventory-defaults-overview page To help make data entry easier and more error-proof, Visma Net gives you the ability to set up default values and use them when you create stock and non-stock items and when you record transactions that involve stock and non-stock items. 2026-02-19T17:09:06+01:00 # Manage inventory defaults - overview To help make data entry easier and more error-proof, Visma Net gives you the ability to set up default values and use them when you create stock and non-stock items and when you record transactions that involve stock and non-stock items. Any default value you establish can be overridden. For each stock and non-stock item, you can assign appropriate units of measure (UoMs) to measure item quantity, volume, and weight. You can define global UoMs (which are used throughout the system), item-specific UoMs (which are used only for particular items), and conversion rules for units of measure. ## Topics + [About reason codes: definition and usage](/visma-net-erp/help/inventory/manage-inventory-defaults/about-reason-codes-definition-and-usage/) + [About posting classes: definition and usage](/visma-net-erp/help/inventory/manage-inventory-defaults/about-posting-classes-definition-and-usage/) + [About posting settings](/visma-net-erp/help/inventory/manage-inventory-defaults/about-posting-settings/) + [About units of measure and conversions](/visma-net-erp/help/inventory/manage-inventory-defaults/about-units-of-measure-and-conversions/) About reason codes: definition and usage /visma-net-erp/help/inventory/manage-inventory-defaults/about-reason-codes-definition-and-usage page Generally, transactions with items are performed when the items are purchased or sold, and respective inventory receipts or issues are generated by financial documents, such as purchase receipts and sales orders, originating in other workspaces. 2026-02-19T17:09:06+01:00 # About reason codes: definition and usage Generally, transactions with items are performed when the items are purchased or sold, and respective inventory receipts or issues are generated by financial documents, such as purchase receipts and sales orders, originating in other workspaces. Because direct inventory transactions (not based on any financial documents) are not standard operations, the users should explain why the particular inventory transactions were performed. Reason codes are used with direct inventory transactions to provide the reasons for such transactions, as well as account / subaccount pairs to be used to post the transactions to general ledger. You define reason codes in the [Reason codes (CS211000)](/visma-net-erp/help/inventory/inventory-windows/reason-codes-cs211000/) window. For each reason code, you must specify with what inventory transaction it will be used. You can define the reason codes for the following types of inventory transactions: + Receipt + Issue / return + Adjustment + Transfer > [!NOTE] > Identifiers of reason codes may have up to 10 characters and can clearly designate the reason of the transaction, as with **DAMAGE**, **EXPIRATION**, **SHRINKAGE**, and **RETURNS**. ## Reason code account Each reason code provides an account to be used for the transaction. The type of the account depends on the type of transaction the reason code is associated with as well as the reason for the transaction; in most cases, it is a kind of expense account to record specific costs. For example, reason codes defined for issues are used to provide offset accounts for specific types of issues. If the issue is made for kit assembling, the offset account is usually an expense account like material expense. If the issue is made to remove expired goods, the offset account can be expired goods' costs. An inventory return functions similarly to an issue, with the entries reversed. ## Reason code subaccount and subaccount mask Each reason code provides a subaccount associated with it and a subaccount mask to set up the rule for creating a subaccount for transactions by combining segment values copied from the multiple subaccounts involved including the reason code's subaccount. To create a subaccount mask for a reason code, you can choose subaccount segments from the following sources: I (Item) : A subaccount associated with the item W (Warehouse) : A subaccount associated with the warehouse where the transaction is performed P (Posting class) : A subaccount associated with the posting class R (Reason code) : A subaccount associated with the reason code itself ## Usage of reason codes in inventory When an inventory transaction is performed directly in the Inventory workspace, the reason code defines what account will be used as an offset account and what subaccount will mark the transaction. On release of the transaction, the inventory account (coming from the stock item) and the offset account (from the reason code) will be updated with the amount of the transaction. For each type of inventory transaction, you can select the reason code that is used most frequently and assign it as the default reason code for the transaction type. You specify the default reason codes to be used for different types of inventory transactions on the **General settings** tab of the [Inventory preferences (IN101000)](/visma-net-erp/help/inventory/inventory-windows/inventory-preferences-in101000/) window. You can assign default reason codes to the following inventory transactions: + Receipts + Issue / returns + Adjustment + Stocktaking adjustments When you create one of these inventory documents, the system automatically inserts the appropriate default reason code for the type. You can replace it with another reason code defined for the transaction type if necessary. ## Sales account and sales subaccount Reason codes can only provide a sales account and sales subaccount segment source for sales transactions that refer to a specific order type. You can set this in the **Use sales account from** and **Combine sales sub. from** fields in the [Order types (SO201000)](/visma-net-erp/help/sales/sales-windows/order-types-so201000/) window.

Related pages

Tasks

Windows

 About posting classes: definition and usage /visma-net-erp/help/inventory/manage-inventory-defaults/about-posting-classes-definition-and-usage page Every inventory transaction creates an appropriate posting to the general ledger, depending on the particular item, the type of transaction, the warehouse location where the item is stocked, and other conditions. 2026-02-19T17:09:06+01:00 # About posting classes: definition and usage Every inventory transaction creates an appropriate posting to the general ledger, depending on the particular item, the type of transaction, the warehouse location where the item is stocked, and other conditions. A posting class is a set of rules defining for each item which accounts and subaccounts should be used to post specific transactions to the general ledger. Also, posting classes are used to provide default general ledger accounts for stock and non-stock items on sales and purchase orders. You create posting classes by using the [Posting classes (IN206000)](/visma-net-erp/help/inventory/inventory-windows/posting-classes-in206000/) window. The definition of a posting class includes the accounts assigned to the class (specified on the **General ledger accounts** tab) and the settings to be used for transaction posting to general ledger (located on the **Posting settings** tab). ## Default general ledger accounts for items of the class Each posting class has general ledger accounts assigned to it. These accounts will be used in the following ways: + As default general ledger accounts for items assigned to the posting class + As general ledger accounts assigned to the posting class itself as one of the sources for selecting the proper accounts to be used for specific transactions The list of accounts specified for the posting class includes the following accounts: + The inventory ( **Asset** ) account and subaccount to be used to keep the balance of transactions with the stock item assigned to the posting class or the accrual account ( **Expense** ) if the item is a non-stock item + The reason code subaccount to be used to mark direct inventory transactions with the stock item + The sales ( **Income** ) account and subaccount to be used when the stock item is issued from the inventory for sale (based on sales orders) + The cost of goods sold ( **Expense** ) account and subaccount to be used when the stock item is issued for sale or the expense account when a non-stock item is sold + The standard cost variance ( **Expense** ) account and subaccount to be used when the stock item's cost on the purchase receipt differs from the cost on the inventory receipt (for items with the standard cost valuation method assigned) + The standard cost revaluation ( **Expense** ) account and subaccount to be used to record a gain or loss when the standard cost is updated (for items with the standard cost valuation method assigned + The purchase accrual ( **Liability** ) account and subaccount to be used to accrue amounts on purchase receipts related to the stock item + The purchase price variance account and subaccount ( **Expense** ) to be used to record any differences between the item cost on the purchase receipt and the inventory receipt + The landed cost variance account and subaccount ( **Expense** ) to be used to record any differences between the landed costs specified on the purchase receipts on Inventory receipts ## Rules for choosing accounts Accounts and subaccounts for inventory transactions related to sales, purchases and valuation of items can be obtained from the sources, depending on the policies established in your company. For example, if only one inventory account is used in your company for all stock items, you might want to provide very specific subaccounts to track which warehouses were involved in every transaction. In Visma Net, you can choose accounts from the following sources:
Item: The inventory account for all transactions of the item will be the same regardless of where the inventory transaction occurs.
Warehouse: The inventory account will vary depending on the warehouse where the inventory transaction is made.
Posting class: The inventory account assigned to the posting class itself (as specified on the General ledger accounts tab) will be used. This option is helpful when you need to replace the inventory account previously used for items of the posting class with a new account.
> [!NOTE] > for sales orders, the sales account is retrieved according to settings in the [Order types (SO201000)](/visma-net-erp/help/sales/sales-windows/order-types-so201000/) window. ## Rules for choosing subaccounts Generally, subaccounts to be used for transaction posting can be selected from the same sources as accounts, but since subaccounts consist of multiple segments, you have the option to combine segment values from different sources to get subaccounts that would perfectly reflect all the details of the transaction. A posting class provides the subaccount masks on the **Posting settings** tab, which allows you to configure how the subaccounts should be composed using segment values copied from various sources. Consider a simple example of configuring a subaccount mask for a sales subaccount. Suppose there are four segments in the subaccounts used in your company, which have the format **XX-XXX-XX-XX**. For each segment, you have the choice of three options designating the source of the segment value: + P: Posting class + I: Item + W: Warehouse If you configure the sales subaccount mask as **II-III-II-II**, it means that for sales transactions, the subaccount specified as sales subaccount for the item will be used. If you configure the sales subaccount mask as **WW-PPP-II-PP**, then for sales transactions, the sales subaccount will be a combination of three subaccounts: + The first segment will be copied from the sales subaccount associated with the warehouse, specified on the **General ledger accounts** tab of the [Warehouses (IN204000)](/visma-net-erp/help/inventory/inventory-windows/warehouses-in204000/) window. + The second and fourth segment will be copied from the sales subaccount associated with the posting class of the item, specified on the **General ledger accounts** tab of the [Posting classes (IN206000)](/visma-net-erp/help/inventory/inventory-windows/posting-classes-in206000/) window. + The third segment will be copied from the sales subaccount associated with the item, specified on the **General ledger accounts** tab of the [Stock items (IN202500)](/visma-net-erp/help/inventory/inventory-windows/stock-items-in202500/) or [Non-stock items (IN202000)](/visma-net-erp/help/inventory/inventory-windows/non-stock-items-in202000/) window. ## Using posting classes Posting classes facilitate specifying general ledger accounts for multiple items assigned to specific classes. One of the posting classes can be chosen as the default posting class in the [Inventory preferences (IN101000)](/visma-net-erp/help/inventory/inventory-windows/inventory-preferences-in101000/) window. Then, when a user creates a new stock item using the [Stock items (IN202500)](/visma-net-erp/help/inventory/inventory-windows/stock-items-in202500/) window, the item is assigned to the default posting class. If necessary, the user can choose another posting class for the item. Once the posting class is selected, the **General ledger accounts tab** will have the values (intended for general ledger accounts and subaccounts) filled in for the item, based on the posting class. > [!NOTE] > We recommend that you choose as the default class the posting class with settings that apply to the largest number of items. Other posting classes can be more specific and contain settings that apply to fewer items. Later, on release on a specific inventory document, the system checks the posting class of each stock item and applies the rules of the item's posting class to determine accounts and subaccounts to be used for the transaction. For example, for each line item in a sales invoice, the system checks the posting class of the stock item, and applies the rules of the item's posting class to determine a sales account and subaccount and a COGS-account and subaccount to be used for the transaction. Depending on whether the **Post summary when updating the general ledger** option is selected on the [Inventory preferences (IN101000)](/visma-net-erp/help/inventory/inventory-windows/inventory-preferences-in101000/) window, the system generates a batch with journal entries grouped by the account / subaccount pair or with full details. After that, the system generates a batch using the accounts and subaccounts in accordance with the posting classes of the items listed in the document. When the standard costs for the stock items are changed (at the end of financial year or when needed), the process of updating the standard costs generates inventory adjustments to be posted to the general ledger. The system will use the standard cost revaluation account and the corresponding subaccount determined by the rules defined by the posting class of the item whose cost is being updated. If upon release of the purchase receipt, there are differences between the purchase receipt amount and the inventory receipt amount, the following accounts will be used: + For items with the standard cost valuation method, the standard cost variance account and subaccount. + For items with other valuation methods, the purchase price variance account and subaccount. + For all items, the landed cost variance account and subaccount to record any differences between the landed costs specified on the purchase receipts and inventory receipts.

Related pages

Concepts

Windows

 About posting settings /visma-net-erp/help/inventory/manage-inventory-defaults/about-posting-settings page The Inventory workspace of Visma Net is tightly integrated with the General ledger workspace. 2026-02-19T17:09:06+01:00 # About posting settings The Inventory workspace of Visma Net is tightly integrated with the General ledger workspace. The Inventory workspace of Visma Net is tightly integrated with the General ledger workspace. Depending on the configuration settings selected for the Inventory workspace, the inventory transactions can be automatically posted to the general ledger each time an inventory transaction is released. Posting classes give you great flexibility to create appropriate rules for choosing accounts to be updated in the general ledger by specific inventory transactions. ## Inventory–general ledger integration settings The settings used to configure the level of integration between the Inventory and General ledger workspaces are located on the **General settings** tab of the [Inventory preferences (IN101000)](/visma-net-erp/help/inventory/inventory-windows/inventory-preferences-in101000/) window. The following options are available: Update general ledger : If this option is selected, transactions originating in the Inventory workspace will update the general ledger. If this option is cleared, inventory transactions do not update the general ledger, and the inventory can be maintained independently from the General ledger workspace. Post summary when updating the general ledger : If this option is selected, only summary information (for the account / subaccount pair) will be included into the batch. If this option is cleared, the detailed information for each document line will be included in the batch generated for the document. Automatically post on release : If this option is cleared, inventory transactions will not be automatically posted to the general ledger on release of Inventory documents; they should be posted through the General ledger workspace. If this option is selected, inventory transactions will be posted on the release of inventory documents. ## Posting classes A posting class groups stock or non-stock items by the way general ledger accounts are selected for posting specific transactions to the general ledger. The posting class also provides the account and subaccount to be used if the source of general ledger accounts for a transaction is a posting class itself. You create posting classes using the [Posting classes (IN206000)](/visma-net-erp/help/inventory/inventory-windows/posting-classes-in206000/) window. You can assign a posting class to an item class as the default posting class for stock items of the item class. You can also assign a posting class to a stock item using the [Stock items (IN202500)](/visma-net-erp/help/inventory/inventory-windows/stock-items-in202500/) window and to a non-stock item using the [Non-stock items (IN202000)](/visma-net-erp/help/inventory/inventory-windows/non-stock-items-in202000/) window. A posting class defines the rules for selecting general ledger accounts and subaccounts to be used for transactions with items assigned to the posting class. When a transaction with an item is performed, several similar accounts are involved. For example: When a stock item is received at a particular warehouse, a debit amount can be recorded to either the inventory account associated with the warehouse or the inventory account associated with the item. Subaccounts for various types of transactions can be combined from multiple involved subaccounts depending on the policies established in your organisation. Accounts and subaccount segment values can be chosen from the following sources: + Item + Warehouse + Posting class For more details about using posting classes, see: [About posting classes: definition and usage](/visma-net-erp/help/inventory/manage-inventory-defaults/about-posting-classes-definition-and-usage/). ## Reason codes If inventory transactions are generated from the Purchases or Sales workspace, the system will use the purchase accrual account (for purchase receipts) or the COGS account (for sales orders). The offset account and subaccount for a receipt, issue, adjustment, or transfer are determined by the document's reason code, which is selected depending on the specific transaction being performed. For different types of inventory transactions, different types of offset accounts should be selected. Reason codes also can be used to gather statistics about specific inventory transactions. You define reason codes in the [Reason codes (CS211000)](/visma-net-erp/help/inventory/inventory-windows/reason-codes-cs211000/) window. Each reason code is associated with the type of inventory transaction it will be used for. For each type of inventory transaction, multiple reason codes can be created if necessary to further categorise transactions within their types. By using the [Inventory preferences (IN101000)](/visma-net-erp/help/inventory/inventory-windows/inventory-preferences-in101000/) window, you can define the reason codes used most frequently with each type of as the default reason codes for types of transactions. The reason code serves the same two purposes as the posting class does: + To define the sources of the offset subaccount segment values on a per-segment basis + To provide the offset account and offset subaccount, if the source is the reason code itself For more information on using reason codes, see: [About reason codes: definition and usage](/visma-net-erp/help/inventory/manage-inventory-defaults/about-reason-codes-definition-and-usage/).

Related pages

Concepts

Windows

 About units of measure and conversions /visma-net-erp/help/inventory/manage-inventory-defaults/about-units-of-measure-and-conversions page In Visma Net, you can maintain any number of different units of measure (UoMs) to be used for products that are purchased, stocked, or sold by your company. 2026-02-19T17:09:06+01:00 # About units of measure and conversions In Visma Net, you can maintain any number of different units of measure (UoMs) to be used for products that are purchased, stocked, or sold by your company. In Visma Net, you can maintain any number of different units of measure (UoMs) to be used for products that are purchased, stocked, or sold by your company. Multiple units of measure are required because items can be sold by the piece or grouped into boxes, packages, crates, and so forth. Some units of measure apply to many products and as such are defined globally. Other units of measure are used only for particular products or for groups of similar products. Visma Net allows you to define UoMs and conversion rules at all of these levels, as the sections below describe. ## Global units of measure You use the [Units of measure (CS203100)](/visma-net-erp/help/common-settings/common-settings-windows/units-of-measure-cs203100/) window to define units of measure that can be used globally for all items. You can add new units of measure to the unit conversion reference table in this window and specify how they are converted to units already defined in the table if applicable. The global UoMs specified in this table can be used throughout Visma Net, including when a user is selecting default UoMs for a new item class or item. ## Product-specific units of measure If (for each item class, which is defined and modified in the [Item classes (IN201000)](/visma-net-erp/help/inventory/inventory-windows/item-classes-in201000/) window) the **Multiple units of measure** functionality in the [Enable/disable functionalities (CS100000)](/visma-net-erp/help/common-settings/enable-or-disable-functionalites/enable-disable-functionalities-cs100000/) window is enabled, you can specify the base, sales, and purchase units to be used by default for items of the class: Base unit : The unit of measure used for stock keeping and to calculate unit costs. Quantities of the stock item at warehouses are counted using the UoM specified as the base unit for the stock item. Sales unit : The unit of measure typically used when your company sells the product. Purchase unit : The unit of measure typically used when your company purchases the product. You can select globally defined units of measure or type a class-specific UoM. For all units selected for the class, unit conversions are specified with respect to the class' default base unit. In the [Stock items (IN202500)](/visma-net-erp/help/inventory/inventory-windows/stock-items-in202500/) and [Non-stock items (IN202000)](/visma-net-erp/help/inventory/inventory-windows/non-stock-items-in202000/) windows, you can select the base, sales, and purchase units for particular items. (This information is specified on the **General settings** tab of either window.) You can select units from the list of UoMs defined for the class or manually enter units for a particular item. The system will not automatically add item-specific UoMs either globally or for the class. If you want the new units to be available for selection when users create other new items, add them for the class. For a stock item stocked at a particular warehouse, you can select warehouse-specific sales and purchase units by using the [Item warehouse details (IN204500)](/visma-net-erp/help/inventory/inventory-windows/item-warehouse-details-in204500/) window. If the **Multiple units of measure** functionality is disabled in your system, you can use only base units for item classes as well as for individual stock and non-stock items. If you decide at any moment to enable this functionality, the sales and purchase units of each stock and non-stock item will get their values from the currently used base unit of the item. > [!NOTE] > The system will not automatically add class-specific units to the global unit conversion reference table in the [Units of measure (CS203100)](/visma-net-erp/help/common-settings/common-settings-windows/units-of-measure-cs203100/) window. ## Choosing the base unit In general, you may want to choose for each item a base unit that is the smallest unit you would ever use when buying or selling the product, so you can avoid any problems caused by rounding. To understand this guideline, consider a simple example: You purchase and stock a product (canned juice) in boxes of 12 cans, and choose a box as the base unit for this product. If you then decided to sell the product by cans, you will need to specify quantities in fractions or define the sales unit (if sales and purchase units are enabled in your system) as 0.0833333 (one-twelfth) of the base unit. Further, suppose the quantities in your system are calculated up to 3 decimal places, as specified in the [Inventory preferences (IN101000)](/visma-net-erp/help/inventory/inventory-windows/inventory-preferences-in101000/) window. Imagine that one customer wants to buy 5 cans, and another wants to buy another 5 cans. In both cases the sales order will specify 0.417 units (5 \* 0.0833333), and both customers will get 5 cans. The remaining 0.166 units doesn't actually equate to the 2 cans left in the box! During a financial period, in a warehouse, such rounding problems can cause a significant discrepancy between the quantities on books and physical quantities. During stocktaking, counting is performed in base units, so if the base unit for the product is not the smallest UoM applicable to the item, counting results may prove incorrect. Considering the above example, counting only boxes can result in incorrect total number of cans because some of the boxes may not be full. ## Specifying conversion rules If different UoMs are used as base, sales, and purchase units, you specify conversion rules with respect to the UoM chosen as the base unit for the item. For instance, imagine a product is sold to customers by the piece (**PIECE**), making **PIECE** its sales unit. It is stocked in boxes, and each box (**BOX**) includes 6 pieces. The product is purchased from a supplier in containers. Each container (**CONTAINER**) contains 12 boxes, and the purchase unit is **CONTAINER**. As the base unit, you can choose **PIECE** or **BOX**. (The smallest unit is usually chosen.) If you chose **BOX**, you would specify the following conversion rules: |From unit|Multiply / divide|Conversion factor|To unit| |---|---|---|---| |CONTAINER|Multiply|12|BOX| |PIECE|Divide|6|BOX| ## Priority of conversion rules When you enter a transaction and specify the quantity of a stock item and the unit of measure in which the quantity is measured, the system follows the following rules to determine how the specified UoM can be converted to the base unit for cost-of-sold-goods calculation and to sales units for finding the proper price: 1. The system first searches the unit conversion table for the item–warehouse pair. 1. If no unit is found, the system checks the unit conversion table specific for the stock item. 1. If no item is found, the global unit conversion table is searched. ## Units of weight and volume When a third-party (a carrier) is used to deliver products from a supplier to your company or from your company to a customer, the carrier can charge your company for freight, depending on the weight or volume of the shipment, or set restrictions on the package weight and volume. Landed costs incurred for shipments can be allocated by weight or by volume. To allow the system to automatically calculate the weight and volume of shipments, in the [Inventory preferences (IN101000)](/visma-net-erp/help/inventory/inventory-windows/inventory-preferences-in101000/) window, select a globally defined unit of measure as the measure of weight and another as the measure of volume. For each stock item, you can specify the weight (measured in weight UoMs) and the volume (measured in volume UoMs) of its base unit on the **Packaging** tab of the [Stock items (IN202500)](/visma-net-erp/help/inventory/inventory-windows/stock-items-in202500/) window.

Related pages

Concepts

Tasks

Windows

 About units of weight and volume /visma-net-erp/help/inventory/manage-inventory-defaults/about-units-of-weight-and-volume page When a third party (a carrier) is used to deliver products from your company to a customer, the carrier can charge your company specific freight amounts that depend on the weights or volumes of the packages in shipments. 2026-02-19T17:09:06+01:00 # About units of weight and volume When a third party (a carrier) is used to deliver products from your company to a customer, the carrier can charge your company specific freight amounts that depend on the weights or volumes of the packages in shipments. When a third party (a carrier) is used to deliver products from your company to a customer, the carrier can charge your company specific freight amounts that depend on the weights or volumes of the packages in shipments. The carrier may also set restrictions on the weight or volume of packages. Landed costs incurred for shipments delivered from suppliers to your company can be allocated by the weight or volume of the items in the shipment. In Visma Net, you can select the base units of measure for weight and volume and set up the automatic calculation of weights and volumes for sales and purchase orders. ## The base weight and volume UoMs In the [Units of measure (CS203100)](/visma-net-erp/help/common-settings/common-settings-windows/units-of-measure-cs203100/) window, you should create a unit of measure (UoM) to be used in your system as the base UoM for weight. The weights of all sales and purchase orders will be calculated in this UoM. However, if the items differ in weight significantly, you can create other UoMs for measuring the weights of the base units of stock and non-stock items. For each additional weight UoM, you must specify the rules for converting this UoM to the base weight UoM. In the [Units of measure (CS203100)](/visma-net-erp/help/common-settings/common-settings-windows/units-of-measure-cs203100/) window, you should define a UoM that will be used in your system to measure the volume that specific quantities of the items listed on sales and purchase orders can take. Define all other UoMs that may be used to measure the volumes that the base units of various items can take and specify the conversion factors with respect to the base volume UoM. In the [Inventory preferences (IN101000)](/visma-net-erp/help/inventory/inventory-windows/inventory-preferences-in101000/) window, select the base weight UoM in the **Weight UoM** field and select the base volume UoM in the **Volume UoM** field. ## Weight and volume of stock items For each stock item, you can specify the weight (measured in a specific weight UoM) and the volume (measured in a specific volume UoM) of its base unit on the **Packaging** tab of the [Stock items (IN202500)](/visma-net-erp/help/inventory/inventory-windows/stock-items-in202500/) window. For non-stock items, you can specify such values (if applicable) by using the [Non-stock items (IN202000)](/visma-net-erp/help/inventory/inventory-windows/non-stock-items-in202000/) window. For the item-specific weight and volume UoMS there must be rules for conversion to the appropriate base UoMs specified either in the [Stock items (IN202500)](/visma-net-erp/help/inventory/inventory-windows/stock-items-in202500/) window or in the [Units of measure (CS203100)](/visma-net-erp/help/common-settings/common-settings-windows/units-of-measure-cs203100/) window. If the **Multiple units of measure** functionality is enabled in your system, make sure that rules for converting each sales and purchase unit to the base UoM selected for the item are defined in the system. Also, if the **Use a price adjustment multiplier** check box is selected on the **General settings** tab of the [Sales orders (SO301000)](/visma-net-erp/help/sales/sales-windows/sales-orders-so301000/) window, you can specify a price adjustment multiplier for the item. ## Weight and volume calculation for sales orders With the base weight and volume UoMs selected in the [Inventory preferences (IN101000)](/visma-net-erp/help/inventory/inventory-windows/inventory-preferences-in101000/) window and with weights and volumes of the base units of the items specified in the [Stock items (IN202500)](/visma-net-erp/help/inventory/inventory-windows/stock-items-in202500/) window, the system can calculate the weight and volume of the ordered quantities of stock items for each sales order. For each item, its quantity specified in the sales units is calculated in the base units and multiplied by the weight of the base unit. You can view the weight and volume totals for the order on the **Totals** tab of the [Sales orders (SO301000)](/visma-net-erp/help/sales/sales-windows/sales-orders-so301000/) window. The freight rates are specified for shipping zones based on the total shipment weight and (optionally) volume. The weight of a shipment is compared to break points, and the first one that is less than the shipment weight provides the freight rate. The system calculates the freight cost based on the calculation method, **Per unit** or **Net**. If the **Automatic packaging** functionality is enabled in your system, the system uses the packaging options specified in the [Ship via codes (CS207500)](/visma-net-erp/help/inventory/inventory-windows/ship-via-codes-cs207500/) window and the items' weight and volume to determine the packages (that is, the set of boxes) for each shipment. ## Weight and volume calculation for purchase receipts The system can calculate the weight and volume of the received quantities of stock and non-stock items for each purchase receipt. The landed cost specified for each purchase receipt can be split over the items listed in the receipt in proportion to the item weights or volumes (among other options).

Related pages

Concepts

Tasks

Windows

 Define weight UoMs /visma-net-erp/help/inventory/manage-inventory-defaults/define-weight-uoms section You can define new units of measure for weight and specify the rules for conversion one UoM into another UoM by using the Units of measure (CS203100) window. 2026-02-19T17:09:06+01:00 # Define weight UoMs You can define new units of measure for weight and specify the rules for conversion one UoM into another UoM by using the Units of measure (CS203100) window. For more information: [Units of measure (CS203100)](/visma-net-erp/help/common-settings/common-settings-windows/units-of-measure-cs203100/). You can define new units of measure for weight and specify the rules for conversion one UoM into another UoM by using the [Units of measure (CS203100)](/visma-net-erp/help/common-settings/common-settings-windows/units-of-measure-cs203100/) window. For the example illustrated in this procedure, we will create weight UoMs for a gram (**GRAM**) and pound (**LB**) and define conversion rules to convert the weights measured in pounds to weights measured in grams and to convert the weights measured in grams to weights measured in pounds. ## Create a new UoM 1. Go to the [Units of measure (CS203100)](/visma-net-erp/help/common-settings/common-settings-windows/units-of-measure-cs203100/) window. 1. Click ![icon-add](/media/visma-net-erp/icon-add.png). 1. In the **From unit** column, type a name for the new unit, such as **GRAM**. 1. In the **To unit** column, type the name of the new UoM that you specified in the **From unit** column ( **GRAM** in this example). 1. In the **Multiply/divide** column, select **Multiply**. 1. In the **Conversion Factor** column, type **1.0** 1. Click ![icon-save](/media/visma-net-erp/icon-save.png). For this example, repeat the steps above to create the **LB** (pound) UoM. ## Specify the conversion rule from LB to GRAM 1. Go to the [Units of measure (CS203100)](/visma-net-erp/help/common-settings/common-settings-windows/units-of-measure-cs203100/) window. 1. Click ![icon-add](/media/visma-net-erp/icon-add.png). 1. In the **From unit** column, select **LB**. 1. In the **To unit** column, select **GRAM**. 1. In the **Multiply/divide** column, select **Multiply**. 1. In the **Conversion factor** column, type **453.5923**. 1. Click ![icon-save](/media/visma-net-erp/icon-save.png). ## Specify the conversion rule from GRAM to LB 1. Go to the [Units of measure (CS203100)](/visma-net-erp/help/common-settings/common-settings-windows/units-of-measure-cs203100/) window. 1. Click ![icon-add](/media/visma-net-erp/icon-add.png). 1. In the **From unit** column, select **GRAM**. 1. In the **To unit** column, select **LB**. 1. In the **Multiply/divide** column, select **Multiply**. 1. In the **Conversion factor** column, type **0.0022046**. > [!NOTE] > Here we specified the conversion factor as 0.0022046 with 7 decimal places. This value shows how many pounds one gram contains. In your system, the decimal precision is defined in the **Quantity decimal places** field in the [Organisations (CS101500)](/visma-net-erp/help/organisation-structure/organisation-structure-windows/organisations-cs101500/) window. Make sure that the selected decimal precision does not cut off any meaningful digits. For instance, if we set the number of decimal places for quantities to 2, this would result in incorrect conversions from grams to pounds. 1. Click ![icon-save](/media/visma-net-erp/icon-save.png).

Related pages

Concepts

Tasks

Windows