UiPath Documentation
industry-department-solutions
latest
false
Supply Chain & Retail Solutions user guide

Stock dataset

Stock dataset containing aggregated historical inventory levels per product-location, used by Rebuy & Replenishment to understand stock behavior and exposure over time.

The stock dataset contains aggregated historical inventory levels for each product at each location. It represents how inventory has been held over time and is used by the Rebuy & Replenishment capability to understand stock behavior and exposure.

This dataset should provide a daily view of inventory levels, where possible, to support accurate historical analysis.

Purpose

The Rebuy & Replenishment capability uses stock data to analyze historical inventory performance and assess the impact of inventory decisions over time.

By comparing historical stock levels with recommended inventory parameters, the solution can help estimate:

  • Capital tied up in overstocked inventory
  • Risk and impact of understocked goods
  • Opportunities to improve inventory efficiency and availability

During presales, the stock dataset is also used to evaluate potential value and improvement opportunities.

Required fields

FieldDescriptionTypeUseNotes
product_idUnique identifier for the product SKU.stringApplication / PresalesN/A
location_idUnique identifier for the store or distribution centre.stringApplication / PresalesCan be NULL or blank if only one location is considered.
day_dateDate corresponding to the reported inventory level.datetimeApplication / PresalesN/A
opening_stockNumber of units of inventory on hand at the start of the given date, for the specified product and location.integerApplication / PresalesN/A
closing_stockNumber of units of inventory on hand at the end of the given date, for the specified product and location.integerApplication / PresalesN/A

Usage notes

  • A daily historical record of stock levels is recommended to support accurate analysis.
  • Stock quantities should use the same unit of measure as related datasets (for example, Sales and Products).
  • Product and location identifiers must align with the corresponding Products and Locations datasets.
  • If historical data is incomplete, analysis and recommendations may be less accurate.
  • Purpose
  • Required fields
  • Usage notes

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated