Inventory Manager App for Power Apps
Three screens for stock management: dashboard, product catalog and an add item form. Scroll to see why each part of the screens is there, then copy the YAML at the end.
Screen 1 of 3
The dashboard
The warehouse at a glance: stock health, what needs reordering, and what just happened.
A KPI row answers "are we okay?"
SKUs, stock value, alerts, locations. The tiles are plain containers with a label and a value; the demo numbers are placeholders for your own. The form is what you keep: add or remove tiles freely, every tile is a copy of the first.
The alerts table is why this app exists
Every item below its minimum quantity, with the badge computed from how far under it is: Critical or Low Stock. Computed, not typed, so the moment your data changes, the badges follow. This table is the screen people come back for.
The activity feed is the audit trail
Receipts, transfers, scans and alerts with timestamps. A feed like this answers "who did what, when" without anyone writing a report. One gallery template renders every entry.
The app title setting
This is the same screen with the app title changed to Warehouse. The title is a setting and lands in the sidebar of the generated YAML.
How it holds up in dark
The dashboard preview carries a dark palette, shown here. To be clear about what you get: the generated YAML for this app currently ships the light palette; dark shows how the layout itself holds up.
Screen 2 of 3
The product catalog
The full product list, readable two ways: cards for browsing, a table for comparing.
Two layouts, one dataset
The grid/table toggle stores a single context variable, and both layouts read the same products. That is the cheapest way to serve two reading styles: browsing and comparing. The pasted screen switches the same way.
Status badges are computed, not typed
Critical, Low Stock or In Stock comes from quantity against minimum quantity per item. Nobody maintains a status column; the formula does. Clicking a product opens its detail drawer, driven by the same selection variable pattern.
The primary color setting
The primary color is a setting. Change it once and the generated YAML uses it everywhere. This is the same screen with a different primary color.
Screen 3 of 3
The add item form
The form for new products. In Power Apps, a clean form layout is most of the work.
A form layout you do not have to fight
Labels, inputs and dropdowns in a two column rhythm, sized to match the rest of the app. Aligning this by hand in Studio takes an afternoon; here it is the template.
Bring the save logic, keep the layout
The screen ships as a layout with the Add Item button in place. Wire its OnSelect to a Patch or Collect on your own data source, for example the SharePoint lists from the SharePoint Structure tool.
Try the product catalog
This preview is interactive. Switch between grid and table, and click a product to open its detail drawer. The pasted screen behaves the same way in Studio, driven by context variables.
Work with the screens
Pick a screen and copy its YAML into an empty screen in Power Apps Studio. All three screens paste into one app without name collisions.
Set up in 4 steps
1.Set the app layout to Responsive
In Power Apps Studio open Settings, then Display, and set App layout to Responsive. With the Fixed layout the app shrinks on a phone instead of reflowing.
2.Copy the Dashboard
Pick a screen in the tabs below and press Copy YAML. Start with the Dashboard.
3.Paste on the Screens node
In the Tree view, right-click the word Screens itself and choose Paste, or press Ctrl + V. Not inside an existing screen: that keeps the controls but drops the screen's OnVisible.
4.Repeat for the other 2 screens, then wire the sidebar
Paste each screen the same way. Then set the screen field of each sidebar item to the screen it should open. The Instructions tab shows the exact lines.
Inventory Manager
ULTRACreate a free account
Copy any of the 13 free components. The rest come with a plan.
If you already have an account, we'll log you in
What Users Say
“I was able to create a requested feature while still on the phone with management so they could view the result in real time.”
Mike B.
Verified PowerLibs User
“It really helps me customize how I want, instead of trying to figure it out myself. It's saved me hours.”
PowerLibs User
Power Apps Developer
“Both saved me a tremendous amount of time since I didn't need to build reusable components from scratch.”
Kathleen Henry
Power Platform Developer