Stock
Last updated
Last updated
Stocks represent items in a facility and carry information on how much of a product is present as well as metadata and operational data. Stock is typically linked to a listing which holds information on the attributes of the item within the facility. Only stock-specific information, which differs from item to item, like expiry dates or storage locations is tracked via stocks. Stocks can exist without listings and the other way around. However, we advise to always create listings for stocks so that stocks are assigned to the corresponding item and item information can be displayed in clients.
Please go to the for more information on managing stocks via API. The API documentation can be found here.
Stock represents one or more items with the exact same attributes, e.g., items with the same expiry date, lying in the same storage location. Two stocks can be merged if all information on the respective stocks is identical, adding up their amounts. However, our systems still allow having two separate stocks with identical attributes.
The example below shows a listing with tenantArticleId "9999". As stocks for that item are firstly, distributed over two locations and secondly, have different attributes, three stocks were created.
Attributes which are relevant for operational processes are handled via Stock Properties. A common example for properties are values such as expiry date or batch number.
The receipt date represents the time and date when a stock enters a facility. The information can be used for various purposes, e.g., to ensure that picking follows a first-in-first-out strategy. This ensures that the timestamp is set to the value when the stock is accepted in the inbound process and not changed afterwards.
When the stock is created via API, it is the responsibility of the integration layer to provide the correct time point. If no receiptDate is provided, the platform defaults to the moment when the stock is created.
The fact that there is no stock left for an item in a facility can be represented in two ways:
Having no stock entities
Having stock entities with amount 0
It is possible that stock is delivered to a facility in a defective state or that it gets damaged during storage. In that cases, the stock condition can be set to "defective". Prior to setting a stock's condition to defective, it must first be marked as not pickable and not accessible. This ensures that the defective stock is no longer considered for sales processes. If rejected items are accepted during goods receipt, this stock is automatically marked as defective and labelled as not pickable and not accessible.
A stock with amount 0 that is assigned to a storage location can be used to indicate that the product should always be stored there. This is, for example, helpful when using the for picking or the including storage location recommendations. If stock is set to 0, our systems will remove the stock entity by default. This can be prevented by adding the trait KEEP_ON_ZERO to a storage location.
