Inbound
- Receiving against purchase orders
- Putaway to warehouse locations
- Inbound that writes the stock record, not a side list
Inventory & warehouse
Receiving, locations, counts, and movement on the same stock record the POS and handhelds write — not a second file the warehouse keeps for itself.
Warehouse floor
What breaks first
The number in the system is not the number on the shelf.
Stock moving between warehouse and branch is hard to follow.
Goods arrive, then someone types them into inventory later.
Each branch keeps its own stock file.
The warehouse still runs on paper, printouts, and spreadsheets.
What the warehouse does
What it runs on
Counts, receiving, and picking are designed for the devices already in the aisle — then the back office and head office read the same result.
Branches
10+
Live on one network, rolled out site by site
Where it runs today
POS, inventory, handhelds, and RFID on one stock record. Interfaces in English, Arabic, and French.
The same live multi-branch network. Inventory and handhelds on the stock record the counters write. We don’t publish the operator’s name.
A warehouse project
Walk receiving, locations, picking, and the files people actually trust today.
Agree locations, count methods, and how a receipt becomes available stock.
POS, handhelds, purchasing, and ERP planned as part of the same record.
Live on one site, then the next, once counts and receiving are stable.
Training for warehouse staff, branch teams, and the people who adjust stock.
Hosting and maintenance if you want them, and a path when the next warehouse opens.
Receiving, locations, counts, branch files, and the gaps between them. We will say what belongs in the record — and what does not.