Outgrowing PowerApps for Inventory Management
A PowerApps inventory app is the Microsoft build-it-yourself route — until per-user licensing, data integrity and the one maker who owns it hit a ceiling. Here's when it's the right call, when you've outgrown it, and what a custom system changes.
PowerApps inventory management means building your own stock app on Microsoft Power Apps, usually with a canvas app for receiving, picking and counting, and a SharePoint list or Dataverse table holding the records. For a business already running on Microsoft 365, it can be a sensible way to replace paper sheets and shared spreadsheets without buying a separate inventory product. When the app has to become the stock system the whole business runs on, an inventory automation system built around your own receiving, picking and counting flow is the main alternative this guide weighs it against.
The practical problem is that the first version is easy and the fourth version is not. Choices made in week one, such as where the data lives, which licence users hold and how stock quantities are updated, decide whether the app still gives a trustworthy figure once you have thousands of rows, several people scanning at once and more than one location.
A stock app is only as good as the movements it records between shelf and screen. Illustrative photograph, not an OpsMavix project.
Image credit: Brian Wangenheim, Unsplash License. No edits.
Key Takeaways
- Power Apps can run a focused stock app well when the scope, data source and licence are chosen deliberately.
- SharePoint is a standard connector; Dataverse is a premium connector with stronger server-side rules and security.
- Delegation decides whether searches and filters see every row or only the first 500 by default.
- Record stock as movements in a ledger rather than overwriting a quantity field.
- Test scanning on the actual devices, barcode types and connectivity your team uses.
- Compare configuration, packaged inventory software, a focused custom application and a full ERP against one shared scenario.
In this guide:
- 1. Decide What the App Must Control
- 2. Choose Between SharePoint and Dataverse
- 3. Understand Power Apps Licensing Before You Build
- 4. Design Around Delegation Limits
- 5. Make Scanning Work on the Warehouse Floor
- 6. Model Stock as Movements Not Overwrites
- 7. Compare Power Apps With Packaged and Custom Options
- 8. Pilot One Stock Flow Before Rollout
- Frequently Asked Questions
- How OpsMavix Can Help
1. Decide What the App Must Control
Start with decisions, not screens
Before opening Power Apps Studio, write down the stock decisions the app must support. Typical examples are: can we promise this order, what needs reordering, where is this item, and why does the shelf disagree with the record. Each decision needs specific records behind it.
A stock app that only lets people edit a quantity field answers none of those questions reliably. A stock app that records receipts, transfers, picks and adjustments with a user, time, reason and location can answer most of them.
Define the scope boundary
| Capability | Usually suitable for a first Power Apps build | Usually needs careful design or another tool |
|---|---|---|
| Item master and locations | Yes, with agreed codes | Many variants, units of measure or kits |
| Goods receiving | Yes, against a simple delivery reference | Matching to purchase orders held in another system |
| Picking and despatch | Yes, for one site and simple orders | Multichannel orders, allocation rules and carrier labels |
| Stock counts | Yes, with counted versus expected quantities | Continuous cycle counting across several sites |
| Valuation and accounting | Read-only reporting at most | Posting cost and value to the ledger |
| Batch, lot or serial tracking | Possible with a deliberate data model | Regulated traceability and recall reporting |
The right column is not off limits. It simply marks where the design work, testing and support effort grow quickly.
Write the rules down
Agree the rules that the app must enforce before anyone builds a screen: who can adjust stock, which reasons are allowed, whether negative stock is blocked, and what happens to a partial delivery. Those rules shape the choice of data source in the next section. If you are not yet sure why your counts drift, our guide on why stock never matches the system covers the common causes.
2. Choose Between SharePoint and Dataverse
What each data source offers
SharePoint lists are familiar and come with most Microsoft 365 tenants. Microsoft classes the SharePoint connector as a standard connector. A list can store up to 30 million items, but Microsoft’s guidance on large lists and libraries sets a list view threshold of approximately 5,000 items, which cannot be changed in SharePoint Online. Indexed columns and filtered views are the recommended way to work within it.
Dataverse is Microsoft’s business data platform. Its overview describes business rules that “validate data across multiple columns and tables”, calculated columns, and a security model that combines role-based, row-based and column-based security. The Dataverse connector is classed as premium in Power Apps.
Compare them for stock control
| Question | SharePoint list | Dataverse |
|---|---|---|
| Connector class in Power Apps | Standard | Premium |
| Where rules are enforced | Mainly in the app formulas | Server-side business rules and logic as well as the app |
| Relationships between tables | Lookup columns with delegation caveats | Relationships defined in the data model |
| Security granularity | List and item permissions | Roles, business units, row and column security |
| Offline for canvas apps | Microsoft’s offline-first guidance is written for Dataverse apps | Offline-first support for Dataverse-based canvas apps |
| Typical fit | Small item lists, one site, low transaction volume | Several related tables, more users, stricter controls |
A practical rule
If your rules can only live inside app formulas, anyone who edits the list directly or builds a second app can bypass them. When stock accuracy matters, the case for keeping validation close to the data is strong, and that usually points to Dataverse or to a database behind a custom application. If the app is a small, single-site tool with low volume, SharePoint can be adequate when the limits above are designed for from the start.
3. Understand Power Apps Licensing Before You Build
What Microsoft 365 already includes
Microsoft’s licensing overview states that some Microsoft 365 licences include limited Power Apps use rights “intended for scenarios that use Microsoft 365 data and standard connectors”, and that these do not provide the same rights as standalone premium licences. In practice, a canvas app on a SharePoint list may be covered by existing Microsoft 365 licences, while a Dataverse app needs premium licensing. Confirm the rights for your specific plans in Microsoft’s licensing guide before building.
Current premium options
At the time of writing, Microsoft’s UK Power Apps pricing page lists Power Apps Premium at £15.40 per user per month, paid yearly and excluding VAT, with a lower rate for organisations buying at least 2,000 seats. The same page lists a free Developer Plan for building and testing, while production users need a Premium licence or the pay-as-you-go option. Microsoft also notes that, from 2 January 2026, the per app licence is no longer available to new customers through some purchasing channels. Prices and terms change, so check the live page and your reseller before budgeting.
Hypothetical worked example: licence cost
A hypothetical wholesaler wants 12 warehouse and office users on a Dataverse-based stock app.
| Line | Calculation | Amount (excluding VAT) |
|---|---|---|
| Monthly licences | 12 users x £15.40 | £184.80 |
| Annual licences | £184.80 x 12 months | £2,217.60 |
| Hypothetical maker support | 4 hours a month x £30 an hour x 12 months | £1,440.00 |
| Hypothetical annual running cost | £2,217.60 + £1,440.00 | £3,657.60 |
The support hours and hourly rate are illustrative assumptions, not benchmarks. The point is that licences are only part of the total. Include the time someone spends maintaining formulas, fixing failed flows and training new staff when you compare options.
4. Design Around Delegation Limits
What delegation means
Delegation is how Power Apps sends a filter, sort or search to the data source instead of downloading records and processing them on the device. Microsoft’s delegation overview explains that when a query cannot be delegated, Power Apps retrieves the first 500 records and processes only those. The data row limit can be raised to a maximum of 10,000, and Power Apps shows a warning on formulas that cannot be delegated.
For inventory, this matters because the wrong answer looks like a normal answer. A search that silently checks only the first 500 items will simply report “not found” for item 501.
Hypothetical worked example: a missed item
A hypothetical business holds 6,000 item records in a SharePoint list. A search screen uses a formula that SharePoint cannot delegate, with the default data row limit of 500.
- Records examined by the app: 500
- Records never examined: 6,000 - 500 = 5,500
- Share of the catalogue invisible to that search: 5,500 / 6,000 = 91.7%
Raising the limit to 10,000 would cover this list today, but it moves more data to each device and fails again once the catalogue grows. The durable fix is a delegable formula or a different data design.
Delegation checklist
- Check the connector’s delegation table. Microsoft’s SharePoint connection guide lists which operators and functions delegate, and notes, for example, that SharePoint ID fields only support the equals operator for delegation.
- Treat every delegation warning as a defect, not a cosmetic issue.
- Test with a realistic row count, not a sample of 50 items.
- Index the SharePoint columns you filter on most often.
- Keep totals and stock positions in a form the source can filter, rather than calculating them on the device.
- Document the data row limit setting so later editors do not change it unknowingly.
5. Make Scanning Work on the Warehouse Floor
Scanning only helps when the device, barcode type and workflow are tested together. Illustrative photograph, not an OpsMavix project.
Image credit: Bluestonex, Unsplash License. No edits.
What the built-in control does
Power Apps includes a barcode reader control that scans barcodes, QR codes and data-matrix codes on Android, iOS and Windows devices. It can scan the first code in view, let the user select one, or scan multiple codes in a session. Microsoft states that the control does not support scanning in a web browser, and supported barcode formats vary by platform.
Plan the scanning workflow
| Decision | Options | What to test |
|---|---|---|
| Device | Phone or tablet camera, Windows device, dedicated rugged handheld | Battery life, gloves, lighting and drop resistance |
| Input method | Barcode reader control or a hardware scanner typing into a text field | Speed, accidental input and focus handling |
| Barcode format | Your suppliers’ codes and your own location labels | Every format on every device platform you use |
| Connectivity | Live connection or offline capture | Dead spots, sync conflicts and duplicate submissions |
| Feedback | Sound, colour, message | Users can tell a failed scan from a successful one |
Offline capture
Microsoft’s mobile offline guidance describes offline-first support for Dataverse-based canvas apps, with automatic conflict resolution. The alternative pattern of saving data locally with SaveData and LoadData has manual conflict handling and a much smaller local data size. If parts of your site have poor signal, test offline behaviour with real users before committing to a data source.
If you are still deciding whether barcodes are worth it at all, our guide to whether you need a barcode inventory system covers that decision separately.
6. Model Stock as Movements Not Overwrites
Why a single quantity field drifts
The quickest Power Apps build stores one quantity per item and lets users overwrite it. When two people update the same item at nearly the same time, or a flow fails halfway, the number changes without a trace of why. Counting fixes the figure for a day; it does not explain the error.
A movement ledger records every receipt, pick, transfer and adjustment as its own row. The on-hand figure is then the sum of movements, and each row carries who, when, where, how many and why.
Hypothetical worked example: rebuilding on-hand stock
A hypothetical item, a box of 50 fixings, sits in one location.
| Movement | Quantity | Running balance |
|---|---|---|
| Opening balance | 120 | 120 |
| Goods receipt | +48 | 168 |
| Pick for order A | -35 | 133 |
| Damage adjustment with reason | -3 | 130 |
On-hand stock = 120 + 48 - 35 - 3 = 130 boxes. If a count finds 126, the variance of 4 boxes becomes an investigation into recent movements rather than an unexplained overwrite.
Ledger design checklist
- One row per movement, never edited after posting; corrections are new reversing rows.
- Mandatory reason codes for adjustments, with permission limited to named roles.
- Location on every movement, so transfers create a matching out and in.
- A clear rule on whether negative stock is blocked or flagged.
- A stock position view that the data source can filter without delegation warnings.
- An export or report finance can reconcile against, without posting values from the app.
For a wider view of how stock records connect to orders, purchasing and reporting, see what an operations system is.
7. Compare Power Apps With Packaged and Custom Options
Match the approach to the gap
Power Apps is one option among several. Packaged inventory software can provide proven workflows, support and integrations without you maintaining the logic. A focused custom application fits a specific process that packaged tools handle badly. A full ERP suits businesses that need finance, purchasing, sales and stock in one coordinated system.
| Approach | Where it fits | What to check |
|---|---|---|
| Configure existing tools | A Microsoft 365 or accounting tool already covers most needs | Edition, permissions and whether the gap is really process |
| Power Apps build | Focused workflow, Microsoft estate, capable internal maker | Data source, licences, delegation, ownership and support |
| Integrate existing systems | Tools work individually but handoffs fail | Record ownership, error handling and reconciliation |
| Packaged inventory software | Standard receiving, picking and counting fit your operation | Module coverage, integrations, subscription cost and exit terms |
| Focused custom application | A valuable, well-bounded process packaged tools handle poorly | Data ownership, support arrangements and documentation |
| Full ERP, packaged or custom | Finance, purchasing, sales and stock need coordinating together | Migration, implementation effort and fit to your processes |
Hypothetical shared scenario
Use one scenario to compare every option: a hypothetical business with two locations, 3,000 items, 10 users, a weekly delivery from 15 suppliers and online plus trade orders. Ask each option to show the same receipt, transfer, pick, count and adjustment, and to show how stock reaches the accounting system. Mark each step as demonstrated, configurable, needing development or unsupported.
Where Power Apps usually struggles
Power Apps is a capable platform, but the limits tend to appear when the app becomes the main stock system for several channels, when only one person understands the formulas, or when integrations with ecommerce and accounting systems need robust error handling. None of these rule it out. They mean ownership, documentation and support need planning as seriously as the screens. Our broader guide to custom inventory systems covers when packaged tools stop fitting.
8. Pilot One Stock Flow Before Rollout
Pick a representative flow
Choose one flow that touches real stock, such as receiving at one location through to putaway, and run it for long enough to include exceptions: short deliveries, damaged items, wrong barcodes and a count variance. Load a realistic number of records so delegation and performance problems appear during the pilot, not after rollout.
Acceptance checklist
- Every movement records user, time, location, quantity and reason.
- Searches and filters return correct results at full data volume with no delegation warnings.
- Scanning works on every device and barcode format in use.
- Users in poor signal areas can capture work without duplicates.
- Licences for every production user are confirmed in writing.
- A second person can explain and change the app using its documentation.
- Stock positions reconcile to a physical count within an agreed tolerance.
- Exports or integrations to accounting can be checked and corrected.
- Permissions stop unauthorised adjustments and direct list edits.
- A named owner is responsible for support, changes and backup.
Decide what happens next
After the pilot, choose deliberately: extend the Power Apps build, move the data to Dataverse, adopt packaged software, or commission a focused custom application. The pilot evidence, not the original enthusiasm, should drive that choice.
Frequently Asked Questions
Is Power Apps good for inventory management?
It can be, for a focused stock workflow inside a Microsoft 365 environment with a clear data design and a responsible owner. It needs more careful design when you have several locations, many users, high transaction volumes or complex integrations.
Should I use SharePoint or Dataverse for a Power Apps inventory app?
SharePoint is a standard connector and suits small, simple lists if you design around the list view threshold and delegation. Dataverse is a premium connector with server-side business rules, relationships and finer security, which suits stock data with stricter controls.
Do I need a premium licence for a Power Apps stock app?
It depends on the connectors and data source. Microsoft states that some Microsoft 365 licences include limited rights for standard connectors, while Dataverse is a premium connector. Check Microsoft’s current licensing guide for your specific plans.
What is the 500 record limit in Power Apps?
When a query cannot be delegated to the data source, Power Apps processes only the first 500 records by default. The data row limit can be raised to 10,000, but delegable formulas are the reliable fix.
Can Power Apps scan barcodes?
Yes. The barcode reader control scans barcodes, QR codes and data-matrix codes on Android, iOS and Windows devices. Microsoft states it does not support scanning in a web browser, and supported formats vary by platform.
Can a Power Apps inventory app work offline?
Microsoft provides offline-first support for Dataverse-based canvas apps. Other approaches, such as SaveData and LoadData, need more code and manual conflict handling, so test them with real users and devices.
When should I move from Power Apps to another system?
Consider it when the app needs constant workarounds, when delegation or performance limits keep returning, when only one person can maintain it, or when integrations need stronger control. Compare options against one shared scenario before deciding.
Can OpsMavix build an inventory management system?
Yes. OpsMavix can build focused applications or a full custom ERP, and can configure or integrate suitable existing tools where those approaches fit the requirements.
How OpsMavix Can Help
OpsMavix can review an existing Power Apps stock app or a planned one, map how stock moves between receiving, storage, picking and despatch, and define the data model and controls the workflow needs.
That may mean improving the current app, moving its data to a stronger design, connecting it to other systems, or building an inventory automation system or ecommerce inventory automation around your operation. Where orders drive stock, a wholesale order management system may be the better starting point.
Contact OpsMavix with one recent stock count variance, the records behind it and the handoff that creates the most rework. We can use that evidence to define requirements and a practical pilot.
Keep reading
Getting value from OpsMavix? Add us as a preferred source on Google — you'll see more of our operations content in your AI Overviews, AI Mode and Search.