# General Request about BOM's as Excel (or similar) tables

**URL:** <https://lookmumnocomputer.discourse.group/t/general-request-about-boms-as-excel-or-similar-tables/1319>\
**Category:** KOSMO MODULES\
**Created:** [June 28, 2020, 7:29am UTC](https://lookmumnocomputer.discourse.group/t/general-request-about-boms-as-excel-or-similar-tables/1319 "2020-06-28T07:29:25Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![analogoutput](https://yyz2.discourse-cdn.com/free1/user_avatar/lookmumnocomputer.discourse.group/analogoutput/32/29663_2.png) [@analogoutput](https://lookmumnocomputer.discourse.group/u/analogoutput)\
**Post date:** [June 28, 2020, 2:04pm UTC](https://lookmumnocomputer.discourse.group/t/general-request-about-boms-as-excel-or-similar-tables/1319/7 "2020-06-28T14:04:10Z")

</div>

KiCad does provide a way to export a BOM to various formats including a csv file. And Sam provides a csv/xlsx version of the BOM, at least he did for the 2399. But I would guess Sam doesn’t use KiCad’s BOM export because the 2399 BOM had errors in part quantities that wouldn’t have occurred. Nor am I surprised because generally the human readable export forms are only barely human readable; it’s why I wrote a [Markdown export script](https://lookmumnocomputer.discourse.group/t/kosmo-sequential-switch/1177/12). Besides, such a csv file would not contain specific part numbers unless those were put into the schematic (for each and every part individually, unless they were made part of a custom symbols library), and that is, as @devicex says, time consuming and, as @fredrik says, of limited utility.

---

_[View the full topic](https://lookmumnocomputer.discourse.group/t/general-request-about-boms-as-excel-or-similar-tables/1319)._
