After buying back a product from a customer it should be added to inventory then be removed after its sold automatically.
After we purchase a customers product threw the system the item should be added to inventory then after its sold the item should be removed from inventory. It defeats the purpose of inventory control if that item remains in the inventory system. Each store is linked and that means the inventory list will be hundreds of items long, and those items would not even exist.
Does this mean I just wasted an hour writing this up?
Looks like the auto-remove isn't live yet. Stay tuned.. :)
I don't see how this is done?
@Troy: That's SO AWESOME to hear! Can I please be involved with the Q&A evolution of this new module? I have a lot of experience with working with inventory, both revolving and one-time-use, and I really think I could help make this idea great.
As you may have read on my other post (link below), I have a very intricate process that I think would be the perfect bridge between Inventory and Logistics. I think it's important that this doesn't overlap/mix with regular inventory (which gets regularly restocked), but would track to individual items (rather than a single item group).
There's so much to doing it the right way (I've done it ten different ways and know all the things to avoid). From organizing by categories rather than item names, to tracking purchase prices against sale prices. There's a lot of risk in buying now and getting paid later, but it can all work amazingly if the right workflow and security blocks are in place.
Very excited :) :) :)
@Sabrina: Does my mock up image in the following post sounds like exactly what you're looking for?
Matt Ed commented
Brilliant. This would be a great help to us also. Thanks.