# Asset Type - "Product"

**URL:** <https://farmos.discourse.group/t/asset-type-product/1864>\
**Category:** Using farmOS\
**Tags:** feature-request\
**Created:** [January 30, 2024, 1:01pm UTC](https://farmos.discourse.group/t/asset-type-product/1864 "2024-01-30T13:01:44Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![graffte](https://avatars.discourse-cdn.com/v4/letter/g/b38774/32.png) [@graffte](https://farmos.discourse.group/u/graffte)\
**Post date:** [January 30, 2024, 1:01pm UTC](https://farmos.discourse.group/t/asset-type-product/1864/1 "2024-01-30T13:01:44Z")

</div>

I think FarmOS asset types are missing a one for farm end products. As a farm with a crop operation, FarmOS has Assets for Seed and Plants, but the end product for me is Grain. Today I sort of get by using the Lot Code field for tracking my end product through my record system. I think it would be useful to have an Product asset that could then utilize all the inventory tracking FarmOS has in place.

Definition Per USDA NOP 205.2 **Agricultural Product - Any agricultural commodity or product, whether raw or processed, including any commodity or product derived from livestock, that is marketed in the United States for human or livestock consumption** from [USDA NOP Terms](https://www.ecfr.gov/current/title-7/subtitle-B/chapter-I/subchapter-M/part-205#205.2)

[Seed Asset Discussion](https://farmos.discourse.group/t/asset-movements-planting-seeding-locations/883)

---

<div class="post-metadata">

**Author:** ![mstenta](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/mstenta/32/4_2.png) [@mstenta](https://farmos.discourse.group/u/mstenta)\
**Post date:** [January 30, 2024, 5:28pm UTC](https://farmos.discourse.group/t/asset-type-product/1864/2 "2024-01-30T17:28:40Z")

</div>

Glad you brought this up @graffte! We actually had a discussion recently that you might be interested in: [Tracking Products and Inventory - Product Quantity](https://farmos.discourse.group/t/tracking-products-and-inventory-product-quantity/1613)

I actually created a Product asset module to experiment with here: [GitHub - mstenta/farm\_product](https://github.com/mstenta/farm_product)

I think there’s general agreement that a “Product” asset type makes sense. Lots of next step questions after that… but maybe it would be worth proposing we add this asset type as an optional module to farmOS core, so that that experimentation can begin in earnest. And so current users could start tracking product assets themselves in the meantime.

---

<div class="post-metadata">

**Author:** ![mstenta](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/mstenta/32/4_2.png) [@mstenta](https://farmos.discourse.group/u/mstenta)\
**Post date:** [January 30, 2024, 6:40pm UTC](https://farmos.discourse.group/t/asset-type-product/1864/3 "2024-01-30T18:40:09Z")

</div>

> [@mstenta](#):
>
> I actually created a Product asset module to experiment with here: [GitHub - mstenta/farm\_product](https://github.com/mstenta/farm_product)

I was feeling inspired so I made a pull request to add this new Product asset type to farmOS core. 🙂

> <https://github.com/farmOS/farmOS/pull/787>
>
> I originally started this in a separate module (https://github.com/mstenta/farm\_…product), but I think we should consider adding it to farmOS core as a standard asset type.
> 
> Inspired by this forum topic today: https://farmos.discourse.group/t/asset-type-product/1864
> 
> For more discussion/context see: https://farmos.discourse.group/t/tracking-products-and-inventory-product-quantity/1613

---

<div class="post-metadata">

**Author:** ![graffte](https://avatars.discourse-cdn.com/v4/letter/g/b38774/32.png) [@graffte](https://farmos.discourse.group/u/graffte)\
**Post date:** [February 4, 2024, 12:39am UTC](https://farmos.discourse.group/t/asset-type-product/1864/4 "2024-02-04T00:39:38Z")

</div>

Glad to see the continued effort. I think this can lead to supporting a critical inspection requirement for organic crop operations. Possibly other systems as well. The inspectors need to complete a mass balance evaluation. This evaluates seeding rates. yelds, and resulting product produced to ensure all ties and makes sense. I think FarmOS could genenerate a mass balance report for a given crop. This would be a huge help to inspection process.

---

<div class="post-metadata">

**Author:** ![mstenta](https://yyz2.discourse-cdn.com/free1/user_avatar/farmos.discourse.group/mstenta/32/4_2.png) [@mstenta](https://farmos.discourse.group/u/mstenta)\
**Post date:** [February 4, 2024, 11:07am UTC](https://farmos.discourse.group/t/asset-type-product/1864/5 "2024-02-04T11:07:14Z")

</div>

@graffte Agreed! Small step for a pull request, big step longer term. 🙂

FYI: The pull request was merged and farmOS 3.1.0 was released on Friday. I’m in the process of updating Farmier-hosted instances this weekend, so Product assets will become an option for you soon.

Note that this does NOT include any UI features specifically to support the creation/maintenance of products. They are just another asset type. So essentially they are part of the data model now, but there’s more work to do to make helper features to make them more usable in the frontend.

One related feature in v3.1.0 is a new Inventory quick form, which when combined with Product assets makes it easier maintain product inventory levels. My next idea is to create a Harvest quick form that offers options for automatically creating/incrementing Product assets, which will also help.

The promise and benefits of product data is obvious! The challenge, as always, is making it easy to enter and maintain that data. One step at a time… and love to hear all ideas folks have! 🙂
