# Inventory Apps on Android: What Works in a Shop

> What an Android inventory app has to do in a Kenyan shop: deduct on the sale, work offline, handle receiving, and survive being the shop

Canonical: https://veirahq.com/blog/inventory-app-android

Most Kenyan shops that start tracking stock start on a phone, because that is the device already in the building. It works, with conditions. The app has to deduct stock as part of the sale rather than as a separate chore, it has to keep working when the data does not, and it has to survive being the only device the shop owns. This covers what to require and what a phone genuinely cannot do.

- An inventory app not attached to the till is a spreadsheet with a login.
- Receiving has to be as quick as selling, or the count drifts in the other direction.
- Test with the data off, mid-sale and mid-delivery, then check for duplicates on reconnect.
- Start with the fast and valuable lines, not the whole catalogue.
- Confirm the records do not live only on the device.

1. An inventory app that is not attached to the till is a spreadsheet
2. What to require
3. Where phone-based stock control breaks
4. A worked example: the app that was used for nine days
5. How Veira handles it
6. Frequently asked questions

## An inventory app that is not attached to the till is a spreadsheet

The failure mode is always the same. An app holds a number, somebody updates it when they remember, and within three weeks the number is decoration. That is true of a notebook, a spreadsheet and a beautifully designed phone app alike.

What makes the difference is attachment to the sale. If selling an item is also what deducts it, the figure stays true without anyone maintaining it, and the maintenance is the part that always stops: [what stock software has to do](https://veirahq.com/blog/stock-management-software).

Which is why &#x27;inventory app&#x27; and &#x27;POS app&#x27; tend to converge in practice. A shop does not want two apps and a person joining them up; it wants the sale and the stock movement to be one event.

Want to see it running in your own business first?

## What to require

Five things, each testable in an afternoon.

1. 1Deduction on the sale, not a separate screenIf reducing the count is a second action, it will be skipped during the busy hour, which is the hour that matters most.
2. 2Receiving that is as quick as sellingStock moves in two directions. Apps that make selling effortless and receiving tedious produce counts that drift upward-wrong rather than downward-wrong.
3. 3Working with the data offTurn it off mid-sale and mid-delivery, then reconnect and check nothing duplicated: [offline behaviour](https://veirahq.com/blog/offline-pos-kenya).
4. 4A slow-mover view you would actually readThe list of what is not selling is where the cash is trapped, and it is the report most phone apps either lack or bury.
5. 5An export you have seenAsk what leaving looks like before you load a year of stock history in. The answer is usually short and occasionally alarming.

## Where phone-based stock control breaks

### Running the inventory app beside a separate till

Two apps, one person joining them, and the join stops happening on the first busy day.

### Loading everything before starting

Begin with the fast and valuable lines. A complete catalogue nobody finished is the commonest reason a rollout dies.

### One phone, one login, three staff

Nothing is attributable, so a variance cannot be narrowed to a shift and every investigation covers everybody.

### Counting only when something feels wrong

By then the gap covers weeks. A section counted weekly is explainable; the same gap at year end is a write-off.

### Assuming the phone is a backup

If the records live only on the device, a lost phone is a lost business. Confirm where the data actually sits.

## A worked example: the app that was used for nine days

A hardware shop in Nairobi adopted a well-regarded Android inventory app. The owner loaded four hundred items over a weekend and trained two staff on the Monday.

Selling was done on the till as before, and the app was updated afterwards. For nine days somebody did it most evenings.

By the third week the figures were wrong enough that nobody trusted them, and by the fourth the app was not being opened. Nothing had failed except the assumption that a separate updating step would survive contact with a busy shop.

Stock you cannot see is stock you lose: dead capital sitting on slow shelves, empty shelves on your fast movers, and shrinkage no one can explain.

Veira tracks every item in and out with reorder alerts, so you hold the right stock and losses surface early.

## How Veira handles it

Veira runs on Android phones, and stock moves because the sale moved it: there is no second step to remember and nothing to reconcile in the evening.

Receiving is as quick as selling, so the count stays true in both directions, and the slow-mover view is a list you can act on rather than a report to assemble.

Records are not held only on the device, so a lost or broken phone is an inconvenience rather than the end of the shop&#x27;s history, and each member of staff signs in as themselves.

## Frequently asked questions

A phone is a perfectly good place to run stock, as long as the stock moves because the sale moved it. Every failed rollout of a phone inventory app has the same cause: an updating step that somebody had to remember.

## Keep reading

[See all Business guides](https://veirahq.com/blog/business)

## Veira for your business

On the Veira side of this: [download Veira for Android, Windows or Mac](https://veirahq.com/download).

[Browse Veira by business type](https://veirahq.com/solutions) · [Who we serve](https://veirahq.com/industries)

Veira files a compliant invoice on every sale and keeps selling when the line drops.
