- Overview
- Platform setup and administration
- Platform setup and administration
- Platform architecture
- Data Bridge onboarding overview
- Connecting a Peak-managed data lake
- Connecting a customer-managed data lake
- Creating an AWS IAM role for Data Bridge
- Connecting a Snowflake data warehouse
- Connecting a Redshift data warehouse (public connectivity)
- Connecting a Redshift data warehouse (private connectivity)
- Reauthorizing a Snowflake OAuth connection
- Using Snowflake with Peak
- SQL Explorer overview
- Roles and permissions
- User management
- Inventory management solution
- Commercial pricing solution
- Merchandising solution
Supply Chain & Retail Solutions user guide
Data requirements
This page describes the customer data required by the UiPath solution for inventory management. For details on how to connect and ingest data into the Peak platform, see Data ingestion.
The UiPath solution for the inventory management solution relies on customer-provided data to generate inventory insights and recommendations. This data represents business information that already exists in the customer’s enterprise systems, such as orders, products, inventory positions, and planning parameters.
Data is integrated into the solution during onboarding. The specific data sources, formats, and ingestion methods depend on the customer environment and are configured outside the scope of this guide.
This page explains how this data is used by the inventory management solution and lists the datasets required for solution to function as intended.
How data is used by the solution
The UiPath solution for inventory management uses customer data that already exists in the organization’s systems. This data is not created or maintained manually within the solution user interface.
In practice:
- Customers already have inventory-related data, such as orders, products, inventory positions, locations, purchase orders, transfers, pricing, and planning parameters.
- This data exists in enterprise systems, including ERP systems, planning tools, data warehouses, or other operational databases.
- During onboarding, these datasets are:
- Mapped and ingested into the Peak platform.
- Integrated using supported data ingestion methods.
- Structured according to agreed schemas documented separately.
- The inventory management solution consumes this data to:
- Understand demand patterns.
- Evaluate inventory positions and constraints.
- Generate inventory insights and replenishment recommendations.
Business users do not create or edit these datasets directly in the solution. Instead, they review and act on the insights and recommendations generated from this data.
Required datasets
To deploy and use the inventory management solution, the following datasets are required:
| Business data category | Description | Dataset(s) in this guide |
|---|---|---|
| Product data | Defines the items that are planned and managed by the solution. | Products dataset |
| Location data | Defines the locations where inventory is held, replenished, or planned. | Locations dataset |
| Inventory position data | Provides current on-hand and in-transit inventory quantities by product and location. | Stock dataset |
| Demand history | Provides historical demand or consumption data used to understand demand patterns over time. | Customer orders dataset |
| Replenishment parameters | Defines planning inputs such as lead times, reorder policies, or replenishment constraints. | Order parameters dataset |
| Service-level targets or business objectives | Defines target service levels or objectives used to evaluate trade-offs between availability and inventory cost. | Order parameters dataset (service_level field) |
| Inbound supply data | Represents incoming stock from suppliers or internal transfers used to project future inventory availability. | Purchase orders dataset Transfers dataset |
| Financial context data | Provides cost and price information used to assess the financial impact of inventory decisions. | Pricing dataset |
| Supplier metadata | Defines suppliers associated with replenishment and sourcing activities. | Suppliers dataset |
Data sources and implementation details
These datasets are typically sourced from existing enterprise systems, such as ERP, planning, or supply chain data platforms. The specific systems, data structures, and ingestion methods depend on the customer environment and are configured during onboarding.