Inventory control and COGS about pygtk-posting HOT 2 OPEN

You have to explain what your inventory workflow is. There are many possibilities such as:

1. Buy raw parts and have an assembly method/procedure that shows what parts are used to make a stock item (which then has its own part number).
2. Buy COTS that you resale, maybe bundle with other COTS into a new number and sell. You could also "value add" Cots before resale in some way.
3. Buy bolts of cloth, which you sell by the foot/yard/meter etc. (Textile inventory is the worst case IMO).

Which scenario are you?

As an aside, anything owned by the company is potentially saleable (can go on an invoice). I've sold jigs, tools, spare parts, development systems, etc.

from pygtk-posting.

1. I use quite a bit in my business.
2. I don't use, yet. It would be a nice addition.
3. I use for buying and selling wire, heat shrink, and etc. It's not only textile that makes for difficult inventory :(

Besides that is normal inventory. You buy 1 piece(s), and you sell you 1 piece(s).

Ideally, Posting would support all types of inventory and all business scenarios. The real life scenario is that very few people have the programming skills and time to bring an open source accounting system to this level.

from pygtk-posting.