@pipo regarding original post I was talking about disallowing item sales by calculating how much items you can produce with your current inventory -on the fly-. For example disallowing hamburger sales because your ketchup inventory decreased below 0.
Tracking critical levels for individual inventory items is something different and it is in our to do list.
This only works in real time on the server⊠Our terminal users had to logout, and login again Every time a product tag was changed. Not practical. The Message server seemed to work fine, exept for this. Could this Be solved?
Did you tried to broadcast the Update Program Setting Item Count values using broadcast message action and update terminals with message received action?
@steakresto follow this tutorial itâs a much beter way and works just fine on terminals. Limiting number of Items Sold
You can also lern from this tutorial how to lock items manually if yo donât like to limit them on every work period.
that doesnât work for me⊠i have more then 40 items; @emre⊠is this a bug? or works as designed?
when i update an item tag in the backend application
the terminals (ipads) have to logout and login again to see the modification.
A real time available-indicator in the next version would be nice
You can use Reset Cache action to clear local cache.
To force all terminals to reset their cache use Broadcast Message action to send a message server message to all terminals and use Message Received rule to capture that message and execute Reset Cache action.
Implementing something to auto reset product changes might be useful. Iâll add that to todo list.