Browse all topics
Store
Where stock lives, and counting it.
See step 3 in the Overview →The stock ledger
Every stock movement writes one permanent line in a ledger: the product, the location, how many units, why, and who did it. The quantity you see on a product is the running total of those lines, not a figure anyone types in. Corrections are written as new lines rather than edits, so any number can be traced back to the event that produced it.
What each location type can do
A location is anywhere your stock physically rests, and its type decides what that stock is allowed to do. Warehouses and retail counters can be sold from online; consignee sites, event stalls and production partners hold real stock that is deliberately never offered on a storefront. Only a warehouse assembles kits, and only a mapped location reaches a given store.
Confirm a transfer in
Confirming a transfer in is signing for the parcel. Open the shipment in your list, check each product against what is really in the box, change any quantity that does not match, and tap Confirm receipt. That tap is what puts the stock on your location's books. Any quantity you change is recorded as a discrepancy for someone to follow up.
Move stock between locations
Moving stock between two of your own sites is a shipment, not an edit. You create a transfer, list the products and quantities, pack it, then dispatch it. The units stay on the sending site's books, reserved, until someone at the receiving end confirms what arrived. Only that confirmation moves the stock, so nothing is ever in two places at once.
Run a stock count
A stock count compares the shelf with the app. You open a count session, walk the products, and type the number you actually see. Blank means not counted; zero means none there. Submitting locks the count, and posting it writes the difference as an adjustment rather than overwriting the old figure, so every change stays traceable.
A stock count does not match what is on the shelf
A count posts the difference between what you counted and what the app believed when the session opened. It never overwrites. So a mismatch usually means the session belongs to another location, or lines were left blank and stayed at the system figure. Less often the session is stale, or units are in transit and still on the books where they left.