Measurement Units
Introduction
In the fulfillmenttools platform each product (identified by one tenantArticleId in a facility) is tracked in one unit. The meaning of a unit is completely arbitrary but will commonly represent a physical unit like "g" or "kg" or for countable goods something like "pieces" or "pcs". Since each product is kept in just one measurement unit, operations like adding or moving stock do not need to validate or convert units between stocks.
Units can be defined in the measurementUnitKey
in the Iisting. The key that is defined will be displayed in our clients, e.g., during picking if no measurementUnit is defined for the key. It is not required to define units for products. When no unit is set in the listing
, no validation will take place and our clients will default to a localized version of "pieces".
Please see here for the API documentation.
Unit validation in inbound processes
If you are using our system for goods receipts, we highly recommend defining units for each product in the respective listing
of this product's facility.
Since no conversion between units take place automatically it is important to specify the correct unit when new goods are accepted into the system. This eliminates a common source of critical errors in stock levels.
When a measurementUnitKey
is set on the corresponding listing
each new line item in inboundProcess.purchaseOrder.requestedItems
and inboundProcess.receipts.receivedItems
is validated against it: All quantities MUST match the unit of the Listing
.
Attention: When creating an InboundProcess with a PurchaseOrder with unit "xyz" and changing the listing.measurementUnitKey
to something else ("qwe") the inboundProcess.purchaseOrder
must now be patched/replaced to reflect the correct unit again before a receipt can created in the inventory app. This is intentional and ensures the consistency of new stock levels in the facility. In general it is not advised to change the unit of a product in a facility without careful consideration, but in some cases it might be desired to start with no unit on the listing
(= no validation) and transition to stricter rules later.
Last updated