# Traceability from seed to product

**URL:** <https://farmos.discourse.group/t/traceability-from-seed-to-product/345>\
**Category:** Using farmOS\
**Created:** [May 15, 2020, 8:45am UTC](https://farmos.discourse.group/t/traceability-from-seed-to-product/345 "2020-05-15T08:45:38Z")\
**Posts on this page:** 1\
**Showing post:** 9

<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:** [April 10, 2026, 6:50pm UTC](https://farmos.discourse.group/t/traceability-from-seed-to-product/345/9 "2026-04-10T18:50:49Z")

</div>

Welcome @Tania!

@Symbioquine’s overview is great - start by thinking through that! 🙂

If you go the inventory route, I wanted to mention that Inventory Quick Form, which is configurable so you can make some standardized instances of that for different purposes. More info here:

[https://farmos.org/blog/2024/inventory-quick-form/](https://farmos.org/blog/2024/inventory-quick-form/)

> **[farmOS 3.1.0](https://farmos.org/blog/2024/farmos-3.1.0/)**
>
> farmOS is a free and open source web-based application for farm management, planning, and record keeping.

> [@Tania](#):
>
> What asset and log types would you recommend for modelling these stages?

Here are some thoughts…

> [@Tania](#):
>
> - New seedlings / cuttings — plants entering the system

A CSV importer (either using the default asset/log importers or making a single custom one) might be an easy/fast way to get plant assets (and their location) into the system on an ongoing basis.

> [@Tania](#):
>
> - Media change — substrate is changed during early growth
> - Move to pots — plant gets potted up

These could be input logs, perhaps. And if they are moving to a new location the input logs can also be “movements” ([Movements and location | farmOS](https://farmos.org/guide/location/)).

> [@Tania](#):
>
> - Sold bare root — sold as a cutting
> - Sold in pot — final sale as a potted plant

Sale logs are provided by the farmOS Ledger module (add-on): [https://www.drupal.org/project/farm\_ledger](https://www.drupal.org/project/farm_ledger)

> [@Tania](#):
>
> - Contaminated plants
> - Discarded plants (for any reason — rot, pests, failed cuttings, etc.)

Observation logs (which may also be inventory adjustments) would probably be my suggestion.

> [@Tania](#):
>
> We’re currently trying to set up FarmOS data into a Google Sheet via the API as an intermediate step, and then use that sheet as the data source for Looker Studio dashboards.

Never heard of Looker Studio, but here is an example of connecting Google Sheets to the farmOS API by @ktohalloran: [Google Apps Script proof-of-concept for connecting farmOS API to Google Sheets](https://farmos.discourse.group/t/google-apps-script-proof-of-concept-for-connecting-farmos-api-to-google-sheets/2468)

> [@Tania](#):
>
> We’re running FarmOS v2 self-hosted.

farmOS v4 has just been released. v2 is no longer supported so I would recommend getting updated to v3 and then to v4 as soon as you can! Especially if you want that Inventory Quick Form I described above… 😉

---

_[View the full topic](https://farmos.discourse.group/t/traceability-from-seed-to-product/345)._