Sharing stock with your team without losing track of who did what

The day one person stops being enough

A shop run by one person does not really need stock software. The owner knows what came in, what went out and what is behind the counter, and a notebook keeps up. The system that stops working is the one that lives in a single head, and it stops working the moment a second person starts serving customers or unpacking boxes.

What breaks first is not the count. It is the explanation. A number looks wrong, and there is no way to find out whether it was a sale, a breakage, a delivery that was booked twice, or a mistake. Everyone is honest and nobody can prove anything, which is a worse place to be than a wrong number.

Two problems arrive at the same time

The first is collision. Two people change the same product within a minute of each other, one in the stockroom and one at the till. If the app saves a new total rather than a change, the second save quietly erases the first, and nobody sees it happen. If it saves the change itself, both apply and the total is right.

The second is permission. A part time assistant should be able to book a delivery in without being able to change what things cost or delete a product. That sounds obvious and most tools get it half right: they either give everyone everything, or they lock the assistant down so hard that they cannot add a product that just arrived, which is the complaint people leave in reviews.

What who did what should mean

The useful version is not a log file. It is being able to open a product, see every change to its quantity as a line with a name, a time and a reason, and understand the story in ten seconds. Sold three. Received twenty. Counted, found two missing, note says damaged.

Two details make the difference. Entries should not be editable, because a history anyone can rewrite answers nothing. And the name on an old entry should stay as it was, even after the person leaves, so last year records still make sense.

Permissions that help rather than block

The right question is not how much to restrict, it is which specific actions carry risk. In a shop the risky ones are a small list: changing a price, editing or deleting a product, and correcting a count to an arbitrary total. Everything else, receiving stock, selling stock, taking a return, is the job, and blocking it just means the assistant asks you to do it and the record is wrong anyway.

So look for permissions per action rather than per role tier. A person who may receive and sell all day but may not touch prices is the most common shape a small business needs, and plenty of tools cannot express it.

Doing it in Invenva

You add someone by sharing a six character code. They join as read only by default, so nothing bad happens if the code is forwarded, and you promote them when you mean to.

An editor then has seven switches you set per person: stock in, stock out, returns, transfers, stock counts, prices, and editing products. The screens follow the switches rather than showing a locked button, so somebody who cannot change prices simply does not see the price fields. The permissions are enforced on the server as well as in the app, which is the part that actually matters.

Every stock change is written as a change and never as a new total, so two people working at once cannot overwrite each other, including when one of them is offline in the stockroom. Each entry keeps the person, the time, the reason and, where relevant, the customer or supplier, and entries cannot be edited afterwards. A mistake is corrected by an undo that writes its own opposite entry, so the history stays honest.

Names on old entries are kept as they were, and tapping any name opens that person profile with their recent activity, which is usually faster than asking them.

The team is part of the paid plan rather than an extra charge per person. The demo shows the history and the roles with sample people in it, and needs no account.