+
−
Can one store see another store's data?
No. Every query carries the store's identity automatically, at the database layer rather than the screen. There is no path by which another shop's sales reach your screen.
+
−
If I change a price, does it change for other stores?
No. The catalogue price is only a suggestion. What you set is yours alone — you may even rename the product for your own shelf without touching the catalogue.
+
−
Can one store run several branches?
Yes. Price stays with the store while stock is counted per branch. Switch branch in the top bar and you see that branch's stock and sales. Stock can also be sent from one to another.
+
−
Can a cashier drop the price on a sale?
Only if the role carries those two permissions — change price and give discount. Without them the field is simply not there, and if someone tampers in the browser the server ignores it and uses the real price.
+
−
How is a credit sale kept track of?
A credit sale needs a named customer; walk-ins cannot buy on credit. The balance goes onto that customer's running ledger, and if a limit is set, a sale that would cross it is refused. Later you open the invoice and collect.
+
−
Does it handle medicine expiry?
It does. Enter a batch number and expiry on the purchase, and the system sells the soonest-to-expire batch first. Anything expiring within ninety days is flagged in both Products and Reports.
+
−
What if the stock count does not match?
Use Adjust stock with a reason — miscount, damage, expiry or theft. The adjustment itself becomes a ledger line, so who changed what, when and why stays on the record.
+
−
Does selling stop when the internet drops?
In this version, yes — a sale is completed on the server. Offline selling is planned: the browser will hold the transaction and reconcile once the connection returns.