There isn't any out of the box or one-size-fits-all solution to this problem. it all depends on how you manage the physical inventory but more importantly what is the desired process to track In/Out flow of products.
Some systems handle this seamlessly by integrating directly with Sales and Purchasing. When a sale is made, Inventory is automatically reduced. When a Purchase Order is made, Inventory is automatically increased.
Some Inventory Management systems are isolated from Sales and Purchasing. Instead some kind of notification is made of a Sale, or other Outward bound activity, and the quantity. A user then records the activity to adjust Inventory. Same for Inbound products.
In these isolated systems, the In/Out entry can be handled in a single table with some way to indicate which are Inbound versus which are Outbound. Or they could be managed by 2 tables - one for In and a second for Out. It all depends on the processing needs. Other things to consider before deciding are:
1) How to calculate current totals?
2) In the event of a system problem, what needs to be re-loaded to get back on track?
3) How are Inventory adjustments made when physical inventory doesn't match app?
Decisions to these questions will dictate the table structure and processing mechanisms you will need. You will want to consider the long term strategy to make sure you can keep Inventory accurate and keep the app performance acceptable.
I hope this helps!!
LinkedIn
Twitter
