Granted, and all good points, but they weren't listed in the original question, so it gives a better idea of what you are looking for.
On Tue, Dec 20, 2022 at 5:47 PM Michael or Penny Novack < stepbystepf...@comcast.net> wrote: > On 12/20/2022 6:00 PM, R Losey wrote: > > I guess it would depend on how detailed you wanted to be... you could > > create an Inventory asset category, and create as many sub-categories as > > you need to. Purchases add to the inventory; sales delete from it, etc. > > Yes, but the connection to general ledger (the sort of things here) are > only a small part of an :"inventory system". OTHER pieces would be > things like (but not limited to) > > 1) Where are these widgets kept? (in what building, on what shelf, etc.) > > 2) What is the re-order point? (when the number of widgets left falls > below X, order more_ > > 3) From whom are they ordered? (supplier information) > > 4) Alternate suppliers (if the one in "3" can't fill the order) > > 5) Usually batch information (cost not necessarily the same for widgets > added to inventory at different times). I've usually just used an > account per batch in the general ledger and so could store that > information in the description but the organizations tended to be > selling very few different sorts of things. > > ...... > > Michael D Novack > > > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. > -- _________________________________ Richard Losey rlo...@gmail.com Micah 6:8 _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
