Items and variants
Keep a stable identity for each component and finished-product configuration. Store the current BOM reference on the exact variant it governs.
Bill of materials and revision control
Control BOM revisions without losing the product context
Know which structure is current, what the proposed revision changes, and which component or decision is holding release. Keep product variants, BOM lines and review history connected instead of maintaining one fragile file per model.
Sign in to inspect fictional sample records. Copy the app before adapting it to live product data.
Revision control in practice
A BOM is a released product decision—not just a component table
A useful BOM management system answers three different questions: what is in the product, which version is approved for this variant, and what must happen before a proposed version can replace it. Combining those questions in one editable sheet makes a quick start, but it also makes draft changes look deceptively current.
The example app separates item identity, product variants, BOM revisions, component lines and release reviews. The Outdoor Air Monitor can remain on revision A while revision B waits for a price on its replacement filter. The team can see exactly why revision B is not ready to replace the current structure.
Connected records
Give each fact one dependable home
Revisions and lines
Prepare a proposed structure without overwriting the current one. Every line retains its component, quantity, unit and placement context.
Reviews and effects
Route a release decision with the line count, unpriced-line count and component context visible. Only the accepted, ready revision updates the related variant.
Design views around decisions, not around data storage
| View | Question it answers | Action it supports |
|---|---|---|
| Current BOMs | Which revision is effective for each product variant? | Open the exact variant or current revision before production uses it. |
| Revision review queue | Which proposed structures are pending, applied, returned or rejected? | Inspect readiness and make or follow up a decision. |
| Component usage | Which variants and revisions reference this item? | Assess impact before a substitution, shortage response or change. |
| BOM line entry | Is the selected component, quantity and unit explicit? | Add or correct one structured requirement without copying the whole product. |
Adapt without rebuilding
Let the product process change without turning every change into an IT project
Start with the controls the team actually needs
Add a market, voltage, approved-source or make/buy field when it changes the decision. An authorized business administrator can update forms, relationships, review assignments and dashboards in Jodoo.
Know when a specialist system is the better fit
The app coordinates product structures and human release decisions. It does not claim native CAD redlining, option-rule solving, material requirements planning or inventory posting. Integrate only after agreeing which system is authoritative.
Practical questions
BOM management software questions
What does BOM management software control?
It should identify the product or variant, retain revision history, define component quantities and units, distinguish draft from current structures, and show where a component is used. Manufacturing planning, purchasing and inventory may remain in ERP or MRP; decide which system owns each record before integration.
Can Jodoo replace a PLM or MRP system?
Not in every situation. Jodoo is a good fit when the missing layer is configurable BOM records, review routing, exceptions and cross-team visibility. Choose specialist PLM for native CAD and product-configuration control, or MRP/ERP when material planning, work orders, inventory and costing must be one transactional system.
How does the example prevent a draft BOM from becoming current too early?
A revision review checks the selected BOM and its component readiness before an approved record updates the exact product variant. The public example includes a pending revision with an unpriced component so visitors can see the difference between a prepared structure and a releasable one.
Can business administrators change fields and review steps?
Yes. An authorized Jodoo administrator can change forms, choices, relationships, assignments and dashboards as the product process changes. Test calculations, permissions and both accepted and blocked cases before applying changes to live product data.
Does this example calculate production demand or post inventory?
No. It organizes product structures, revisions and review decisions. It does not explode demand from sales orders, reserve stock, issue material or post accounting transactions. Connect those functions only after agreeing system ownership and reconciliation.
Inspect a revision that is not ready to become current
Open the release queue, compare the pending Outdoor Air Monitor revision with the current structure, and inspect the unpriced component that keeps the proposal from silently replacing revision A.