Air Monitor
A shared product idea is not a build instruction.
Product configuration and revision tracking
Keep every product variant on the right BOM revision
Separate the structure for each manufacturable variant, preserve the current revision, and trace shared components without creating an uncontrolled workbook for every model.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
Sign in to inspect fictional sample records. Copy the app before adapting it to live product data.
Worked example
One product family can have several valid current structures
BOM revision C
Uses the standard filter, enclosure and fan set.
BOM revision A
Stays current while proposed revision B has an unpriced replacement filter.
Model the differences that change a build
Configuration identity
Record model, market, voltage, size or other attributes that distinguish the actual finished item. Do not use a display label as the only key.
Variant-specific revision
Let one variant advance without making every sibling appear revised. Keep the previous current reference until the proposed structure is ready.
Shared-component impact
Trace a component across variant and revision lines. Where-used evidence starts an assessment; it does not approve a substitution automatically.
Choose the right level of product control
A tracker is useful, but it is not a product configurator
| Requirement | This Jodoo example | When to consider a specialist system |
|---|---|---|
| Explicit structures by variant | Yes—each variant retains its current BOM revision. | When thousands of combinations must be generated from option rules. |
| Where-used traceability | Yes—component lines link back to variant and revision. | When CAD geometry and engineering effectivity must be evaluated natively. |
| Release coordination | Yes—an assigned release review separates pending from applied decisions. | When several product objects must release atomically across a PLM configuration. |
| Sales configuration | No. | Use CPQ when quotes must validate allowable option combinations. |
Move from variant spreadsheets
Establish one trusted current revision before adding automation
Map the structures you already use
Begin with the variant codes that production and purchasing already recognize. Import each active structure as its own revision, keep the source file as an attachment, and mark unclear substitutions for review instead of silently merging them.
Shared parts should point to the same item record. Variant-only parts remain visible on their own BOM lines, which makes later where-used checks meaningful.
Acceptance checks for the first family
- Every variant resolves to exactly one current revision.
- Line quantities and units match the released source.
- Pending changes do not alter the current build.
- Shared components return every affected variant.
Once those checks hold, a business administrator can add review steps, exception fields or new filtered views as the release process changes.
Practical questions
BOM variant questions
What is a variant BOM?
It is the component structure for a specific sellable or manufacturable configuration, such as a model, size, voltage or market version. The variant should retain its own current revision even when several variants share most components.
Should every variant have a completely separate BOM?
Not always. Stable shared subassemblies or rules may reduce duplication in a specialist configuration system. This Jodoo example keeps explicit variant revisions so teams can understand what differs; it is not a rules-based product configurator.
How do I find variants affected by a component change?
Use the component usage view to find each BOM line that references the item, then inspect its variant and revision. Treat the result as impact input; it does not automatically authorize a substitution.
Can one variant have a pending revision while another stays current?
Yes. Current revision is stored on each variant. A draft or review-stage BOM does not replace that reference until its release conditions are met.
Does this manage sales configuration?
No. It does not select options from a quote or validate every allowed combination. Use a CPQ or product configurator when commercial configuration rules are the primary requirement.