Custom Modules
All custom modules follow the nugget_<feature> naming convention to distinguish them from standard Odoo modules.
| Module | Technical Name | Risk | Status |
|---|---|---|---|
| Variant Name | nugget_variant_name | Low | Active |
| Inventory Status | nugget_inventory_status | Low | Active |
| Task Analytics | nugget_task_analytics | Low | Active |
| Component Inventory | nugget_component_inventory | Low-Med | Active |
| Purchase Configurator | nugget_purchase_configurator | Med | Active |
| Service Requests | nugget_service_requests | Med | Active |
| Per Diem Tracking | nugget_per_diem | High | Active |
Module Design Principles
- One module = one business capability. If you can't explain it in one sentence without "and," it's probably two modules.
- Minimal customization. Always propose standard Odoo solutions first.
- Dependencies flow one direction. If module B depends on A, module A should never need to know B exists.
- Separate cosmetic from behavioral. Terminology changes and business logic changes have different risk profiles.