Units

Units define how a product quantity is expressed: piece, set, box, or another unit used by the company.

In Putaway WMS, a unit is a catalog value used on products. It does not move stock, does not change quantities by itself, and does not perform conversions, but it affects how operators read quantities in receiving, stock, documents, imports, integrations, and reports.

Note

Units are separated by client. The user sees and uses only the units from the account where they are authenticated.

Opening The Page

To manage units, open Catalog -> Units.

The page loads only for users who have permission to view product units. Add and delete actions appear separately, depending on the user’s permissions.

The page does not depend on the selected warehouse. Units are catalog data at account level, not data for a specific warehouse.

What You Can Do On This Page

The page allows:

• listing existing units, sorted alphabetically;
• searching for a unit by name;
• resetting the search filter;
• pagination with page sizes of 10, 15, 25, or 50 rows;
• adding a new unit, if the user has permission;
• deleting a unit, if the user has permission and the unit is not used on products.

The list loads with 15 rows per page by default. If there are many units, use search to find the required unit quickly.

The units page does not have a rename flow. If a name was created incorrectly, create the correct unit, update the products that should use it, then delete the old unit only after it is no longer associated with any product.

When The Unit Matters

The unit appears in several flows:

Area	Why it matters
Products	The unit is selected during create or edit and can be used for filtering. For variants, the unit belongs to the parent product.
Import products	The unit column is required in import mapping. If the unit is missing from the catalog, it can be created automatically within the plan limit.
Goods receiving	The operator reads the received quantity in the product unit.
Goods receipt note	The document displays the unit as part of received quantity checks.
Stock and Traceability	Quantities are easier to verify when the product has the correct unit.
Inventories	Final reconciliation between missing and surplus items is accepted only between products with the same unit.
MerchantPro and Gomag integrations	External units can be mapped or created in WMS during catalog synchronization.

Examples of units:

• pcs;
• set;
• box;
• kg;
• l.

Caution

Do not use the unit as logistic packaging if the packaging must be physically tracked. For boxes, pallets, or containers that group products in the warehouse, use handling units.

Adding A Unit

To create a unit:

1. Press Add Unit.
2. Enter the unit name.
3. Confirm the creation.

The form sends only the name. The client is not selected manually; Putaway WMS uses the account of the authenticated user.

The name is trimmed before saving.

Important rules:

• the name is required;
• the name can have up to 32 characters;
• the same unit cannot be created twice with differences only in uppercase letters, lowercase letters, or leading or trailing spaces;
• creation is blocked if the account’s unit limit has been reached.

Example: if pcs already exists, do not create Pcs, PCS, or piece separately for the same purpose, unless there is a clear operational rule that requires different units.

What The System Validates

Putaway WMS applies the rules on the backend:

• the unit is created, listed, and deleted only for the authenticated account;
• listing can be paginated and filtered by name;
• results are sorted by name;
• creation checks the plan limit before saving;
• creation and deletion update the account’s units counter;
• deletion is refused if the unit is used by products;
• a product cannot use a unit that belongs to another account.

These rules do not depend on browser validation.

Using Units On Products

The unit is selected when creating or editing a product in Products.

In the product form, the unit list is loaded from the current account catalog. The backend checks the unit again on save, so a product cannot be created or updated with an invalid unit or with a unit from another account.

For simple products, the unit belongs to that product.

For products with variants, the unit is set on the parent product. Child variants use the parent unit and do not have a separate unit edit field.

In the product list, the unit can be used for filtering. There is also an option to filter products without a unit.

Note

The unit does not automatically convert quantities. If one product is defined in pcs and another in box, Putaway WMS treats those values as different catalog units, not as conversion formulas.

Importing Products With Units

In Import products, the unit is a required field in mapping.

During import processing, Putaway WMS searches for the unit by name in the current account. If the unit does not exist, the import can create it automatically, together with the product, within the plan limit.

During mapping, Putaway WMS recognizes column names such as:

• unit;
• unit_name;
• unitname;
• um;
• unitate;
• unitatemasura;
• measuring_unit;
• measuringunitname.

For simple products or parent products, the unit value must exist on the row. For a child product imported through Parent SKU, the unit can be missing on the child row because the unit is inherited through the parent product.

The import normalizes repeated spaces in the unit name and searches for the unit case-insensitively. If it finds the unit, it reuses it. If it does not find it, it creates it and increases the account’s units counter.

For clean imports:

• use the same names as in the catalog;
• normalize spelling before import;
• avoid mixed values like pcs, Piece, and buc for the same quantity type;
• check imports completed with issues before running the file again.

Note

Product import does not update existing products with the same SKU. If an SKU already exists, the row is skipped; the unit of the existing product must be corrected from the product page.

Catalog Synchronization

MerchantPro and Gomag integrations can work with units during catalog synchronization.

In these flows, Putaway WMS can:

• import external units as mapping items;
• display external units as unmapped, mapped, created, or ignored;
• link an external unit to an existing WMS unit;
• create missing WMS units when applying the mapping, within the plan limit;
• use the resulting unit on products imported into WMS.

For MerchantPro, the flow is visible in MerchantPro catalog synchronization. For Gomag, units are handled similarly in catalog mapping and apply flows.

Deleting A Unit

A unit can be deleted only if:

• the user has delete permission;
• the unit belongs to the current account;
• the unit is not used by any product.

If the unit is used on products, Putaway WMS refuses deletion. In this case, first check the associated products and decide whether the unit remains or whether the products must be updated.

Caution

Do not delete or replace units without checking the impact on products, stock, documents, and imports.

Common Errors

• Unit name is required: the field was left empty.
• A unit with this name already exists: the account already has the same unit, even if casing differs.
• You have reached the maximum number of units allowed by the current plan: the account plan no longer allows new units.
• The unit cannot be deleted because it is used by products: at least one product has this unit associated.
• Selected unit of measure is invalid or does not belong to the client: the product or import sent a unit that does not exist in the current account.

Difference From Handling Units

Units and handling units are not the same thing.

Concept	Role
Unit	Describes how a product quantity is expressed, for example pcs, set, or kg.
Handling unit	Represents a physical or logistic object, for example box, pallet, or container.

Example: a product can have pcs as its unit, and during receiving it can be placed in a box or on a pallet as a handling unit.

Rules

• Keep names short and clear.
• Use the same name in products, imports, and internal procedures.
• Do not create duplicates, for example pcs, piece, and Piece for the same purpose, unless there is a clear internal rule.
• If the operational name must be changed, create the correct unit and move the products to it before deleting the old unit.
• Do not change a product unit without checking the associated documents, stock, and reports.
• Do not use ambiguous units like unit, misc, or product.
• Do not use the unit to describe boxes, pallets, or containers that are physically tracked.
• Define the convention before large imports to avoid manual corrections after processing.