It would be very useful in some scenarios to have the ability to set up products in your accounting system but not be able to start selling them in the CRM/marking them as obsolete. One scenario where this could be useful could include a seasonal business who starts setting up new products in the accounts system towards the end of a season which shouldn't be sold until the new season begins. These need to be set up in the accounts system to allow for purchase orders to start being recorded against them, but they don't want to sell them to customers until the new season begins.
Having an 'obsolete' style flag for this in the CRM, that doesn't get re-set whenever the accounts import next runs would be useful as obsolete products don't show in the product search when adding lines to Quotes.
Similarly, it would be useful to have different levels of this 'obsolete' feature. For example, you might have a product that is now out of stock and is discontinued so won't ever be stocked again, or you might have a product that is out of stock for the rest of the season but will be back in stock next season. Having some way to differentiate these kinds of 'out of stock' levels would be useful
This is the same as https://prospectsoft.aha.io/ideas/SPA-I-726 - although for Exchequer users (or any system that only has Active/Obsolete) we might then need to default "Can Sell" to true and then let the customer override this as required.
I actually think we should have a "Can Sell" flag as well as obsolete. Then products can be still active (i.e. not obsolete) but not available to sell (either because these are next season's products, spare parts we dont sell etc. Xero has a "Can Sell" flag, so does Unleashed. I think we should add "Can Sell" instead of mapping these to our "Obsolete" field and then only allow users to quote if Obsolete = False AND Can Sell = True.