I’m currently using an off the shelf ERP system that deals with the Aviation Sector, and I would love, long term to build something for the aviation industry for ERPNext.
The issue I have is how stock stored, and selected in the aviation industry, compared to the FIFO method in ERPNext, where multiple orders of items, are grouped together for valuation/selling/purchasing
With ERPNext, having the main model being an item. In aviation these are parts. Parts can have conditions. (New, Surplus, repaired etc) . Each part also has documentation that goes along with it, it can also have information about how many times its been flown/used, (Cycles).
There are also lots of other attributes, that are very specific to that stock line. I attempted to use the variants of ERPNext but, it just doesn’t fit well since there are so many attributes.
So when you quote the stock, you may quote 3 different lines for different stock lines that are the same item. One may have different documentation, extra cycles, and hence costs a bit more, vs another item, in the same condition.
In the off the shelf erp, every time you purchase buy sell etc, it stores it as a line in a stock table, and has the qty, condition, certification, cycles , price (valuation), serial number. The stock line has a link to the part (the part stores the part number, description, manufacturer, if its seralized, etc.
Any other thoughts as to how I could make this work, apart from forking the whole project, and making a frankenstein version ?