BOM
BOM is a simple Django app to manage a bill of materials. It supports multiple part numbering schemes, tracking component sourcing information, estimates costs, and contains smart integrations with Mouser to pull in the latest component pricing and Google Drive for part file management. BOM is written in Python 3 and Django.
BOM can be added to an existing (or new) Django project, or stand alone on its own, which can be more convenient if you're interested in tweaking the tool.
If you already have a django project, you can skip to Add Django Bom To Your App, otherwise Start From Scratch: Add to new Django project to add it to a new django project, or Start From Scratch: Use as standalone Django project.
Table of contents
- Start From Scratch: Add to new Django project
- Add Django Bom To Your App
- Start From Scratch: Use as standalone Django project
- Customize Base Template
- Integrations
- Contributing
- Installation pitfalls
Start From Scratch: Add to a new Django project
- Create and activate a virtual environment (Python 3.10+):
python -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
- Install Django and set up your project:
pip install django
django-admin startproject mysite
cd mysite
python manage.py migrate
python manage.py createsuperuser # make a user for your development environment
- Continue on to Add Django Bom To Your App.
Add Django Bom To Your App
django-bom is a reusable django application. If you don't already have a django project, you can follow some quick steps below to get up and running, or read about creating your first django app here.
pip install django-bom
- Add "bom" to your INSTALLED_APPS setting like this::
INSTALLED_APPS = [
...
'bom',
'social_django', # to enable google drive sync in bom
'djmoney', # for currency
'djmoney.contrib.exchange', # for currency
'materializecssform',
]
- Update your URLconf in your project urls.py like this::
path('bom/', include('bom.urls')),
And don't forget to import include:
from django.conf.urls import include
- Update your settings.py to add the bom context processor
'bom.context_processors.bom_config',to your TEMPLATES variable, and create a new empty dictionary BOM_CONFIG.
TEMPLATES = [
{
...
'OPTIONS': {
'context_processors': [
...
'bom.context_processors.bom_config',
],
},
},
]
and
BOM_CONFIG = {'standalone_mode': False}
-
Run
python manage.py migrateto create the bom models. -
Start the development server
python manage.py runserverand visit http://127.0.0.1:8000/admin/ to manage the bom (you'll need the Admin app enabled). -
Visit http://127.0.0.1:8000/bom/ to begin.
Start From Scratch: Use as a standalone Django project
- Clone the repo and create a virtual environment:
git clone https://github.com/mpkasp/django-bom.git
cd django-bom
python -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
- Install dependencies and start the server:
pip install -e .
cp bom/local_settings.py.example bom/local_settings.py
python manage.py migrate
python manage.py runserver
Customize Base Template
The base template can be customized to your pleasing. Just add the following configuration to your settings.py:
BOM_CONFIG = {
'base_template': 'base.html',
}
where base.html is your base template.
Integrations
Mouser Integration
For part matching, make sure to add your Mouser api key. You can get your key here.
Google Drive Integration
Make sure to add the following to your settings.py:
AUTHENTICATION_BACKENDS = (
'social_core.backends.google.GoogleOpenId',
'social_core.backends.google.GoogleOAuth2',
'social_core.backends.google.GoogleOAuth',
'django.contrib.auth.backends.ModelBackend',
)
SOCIAL_AUTH_GOOGLE_OAUTH2_SCOPE = ['email', 'profile', 'https://www.googleapis.com/auth/drive', 'https://www.googleapis.com/auth/plus.login']
SOCIAL_AUTH_GOOGLE_OAUTH2_AUTH_EXTRA_ARGUMENTS = {
'access_type': 'offline',
'approval_prompt': 'auto'
}
And if you're using https on production add:
SOCIAL_AUTH_REDIRECT_IS_HTTPS = not DEBUG
FIXER
Fixer.io is used to handle exchange rate calculations. This is helpful if you may be purchasing parts from another currency (especially via Mouser) and you still need to estimate your part costs.
To set this up you just need to add your API key to local_settings.py as shown in the example.
To update rates, migrate and run python manage.py update_rates. Some day we will need to add a (celerybeat?) task to update rates on a schedule. Explained more here.
Contributing
Contributions welcome! Before contributing your work please read the contributing readme.
Also reach out to mike@indabom.com to discuss features, and join our slack channel.
Installation Pitfalls
Windows
Sqlite
You may get an error during your pip install -r requirements.txt related to sqlite. This may be fixed by installing Visual C++ for python...
Cryptography
Sometimes you'll have issues installing cryptography, if this is the case you may just need to set up some environment variables. This stackoverflow may help.
1 maintainer
Metadata
1 maintainer
Release files for django-bom 1.311
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| django_bom-1.311.tar.gz | 655.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_bom-1.311-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 MB
Release files / django_bom-1.311.tar.gz
| Download URL | django_bom-1.311.tar.gz |
|---|---|
| Size | 655.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6fc4c39ae3706b492c591fef4326d086c941c916749640d3f6bb7a7f72d01b0e
|
|
BLAKE2b-256 checksum How to use checksums |
07d6534a64387d8a2e3e3cfaa6545bfdd82fdfd95e09b02c8330a4ff77a83935
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / django_bom-1.311-py3-none-any.whl
| Download URL | django_bom-1.311-py3-none-any.whl |
|---|---|
| Size | 742.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
01d83cbde194163e67a02589e443d310201375a2d3207e13175c7cf332db695c
|
|
BLAKE2b-256 checksum How to use checksums |
346e141938f2182e0efb036a8ae078a3be1cf698ebeb1308ff8182f048b4a907
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency log
