示意预览Visual multi-level BOM tree with cost roll-up, where-used reverse lookup,
and mass component replacement for Odoo 17/18/19.
什么是 Multi-Level BOM & Where-Used Explorer？
Visual multi-level BOM tree with cost roll-up, where-used reverse lookup, and mass component replacement for Odoo 17/18/19. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
核心功能
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Odoo 上构建、配置并安装。
- 3
上线 + 支持
约一个工作周内上线，并包含两周上线支持。我们交付的代码中的缺陷免费修复。
技术规格
- Odoo 兼容性
- Odoo 17, Odoo 18, Odoo 19
- 版本
- 企业版和社区版
- 许可证
- 许可证需要确认
- Python 要求
- Python 3.10+
- 数据库
- PostgreSQL 12+
关于此产品
Deep BOM structures are where Odoo's standard Manufacturing app runs out of road. Native mrp.bom shows one level at a time, cost is only computed on demand per variant, and there is no built-in way to ask "which finished goods use this raw material?" When engineering revises a component or a supplier hikes a price, costing and planning teams are left clicking through nested sub-assemblies by hand — slow, error-prone, and impossible to audit.
The Multi-Level BOM & Where-Used Explorer is a build-to-order Odoo module that ECOSIRE designs, builds, installs, and supports for your database. It gives engineering and costing teams a single indented tree that expands every sub-assembly down to raw materials, a live cost roll-up that aggregates standard or purchase cost across all BOM levels, a reverse "where-used" lookup that answers component-impact questions in one click, and a guided mass-replace wizard that swaps a component across every BOM it appears in — all inside your existing Odoo Manufacturing workflow.
This is not a one-size-fits-all download from apps.odoo.com. It is a scoped engagement: we start from your BOM depth, your costing method (standard vs. average vs. FIFO), your Community or Enterprise edition, and your Odoo version (17, 18, or 19), then deliver a module tailored to those realities. Under the hood it is clean, upgrade-safe Odoo — new models extending mrp.bom and product.template, computed fields driven by @api.depends, ir.model.access.csv plus record rules for security, OWL/QWeb views for the tree and simulator, and a printable QWeb cost report. Typical delivery is one working week depending on scope.
你得到什么
- Complete, installable Odoo module (source code) packaged for your target version — 17.0, 18.0, or 19.0 — with a clean __manifest__.py and dependency declaration on mrp
- Installation and configuration on your environment (or a staging database first), including security-group setup and menu placement inside the Manufacturing app
- Configuration tuned to your costing method (standard/average/FIFO) and your Community vs. Enterprise edition
- Technical documentation covering the data model, computed fields, wizards, and how the roll-up and where-used algorithms work
- End-user guide and a live training session for your engineering and costing teams on the tree, where-used lookup, simulation, and mass-replace wizard
- Post-go-live support window (bug fixes and adjustments) for a defined period after handover, with a clear escalation path
- UAT sign-off on a staging copy of your database before anything touches production, plus a documented rollback plan
- Source ownership and a git repository handover so your team can maintain or extend the module later
这是给谁的
Costing & Cost Accountant
Owns product standard costs and margin accuracy. Needs a trustworthy rolled-up cost across every BOM level and wants to simulate the margin impact of supplier price changes before they land in the ledger.
Manufacturing / Product Engineer
Maintains BOMs and drives engineering change orders. Needs to see the full indented structure at a glance and to replace a superseded component across dozens of BOMs without hand-editing each one.
Supply Chain & Procurement Analyst
Assesses the blast radius of a component shortage, price hike, or supplier switch. Relies on where-used lookup to know exactly which finished goods and customer orders a single part affects.
Operations / Plant Manager
Wants a defensible, auditable view of product cost build-up and change impact for pricing, tenders, and continuous-improvement decisions, exported cleanly for review meetings.
Multi-Level BOM & Where-Used Explorer 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Odoo 原生 |
|---|---|---|---|---|
| Multi-level indented BOM tree in one view | Full recursive tree down to raw materials, collapsible per node | Possible but you build and maintain the recursion yourself | Varies; many show limited depth or a flat popup | One level at a time — no recursive indented view |
| Cost roll-up across all BOM levels | Automatic bottom-up roll-up via @api.depends computed fields | Hand-coded aggregation, prone to depth/UoM bugs | Some offer it; accuracy and UoM handling vary | Cost computed per level on demand, not aggregated across the tree |
| Where-used (reverse BOM) lookup | One-click direct and indirect parent lookup for any component | Requires custom reverse-traversal code and a UI | Rare; usually a paid add-on if present | Not available out of the box |
| Mass component replace across BOMs | Guided preview-and-confirm wizard, security-gated | Manual script or per-BOM edits, no safe preview | Occasionally offered without a preview/rollback step | Edit each BOM line manually, one at a time |
| Cost simulation on price changes | Simulate hypothetical costs and see rolled-up impact before committing | Would need a bespoke simulation model | Seldom included | No simulation — you change the price and recompute live |
| Fit to your Odoo version, edition & costing method | Built for your exact 17/18/19, Community/Enterprise, and costing method | Fully custom but at full in-house build cost and time | Generic; may not match your version or costing method | Generic core behavior, no tailoring |
| Support, source ownership & rollback plan | Support window, git handover, staging UAT, documented rollback | Depends entirely on internal team availability | Vendor support varies; source often obfuscated | Community support only; no dedicated engagement |
关于Multi-Level BOM & Where-Used Explorer的常见问题
How long until the module is delivered and installed?
This is a build-to-order module, not an instant download. Typical delivery is one working week from a confirmed scope, depending on your BOM depth, costing method, and any custom requirements. We begin with a short scoping call, build on your target Odoo version, deliver to a staging database for UAT, and only then install on production. If you have an urgent deadline, tell us up front and we will confirm whether an accelerated timeline is feasible.
What support and updates do I get after delivery?
Every engagement includes a post-go-live support window for bug fixes and adjustments after handover, with a defined escalation path. You also receive the full source and a git repository, so your team can maintain the module independently. For Odoo major-version upgrades (for example 18 to 19) or new feature requests beyond the original scope, we offer a separate maintenance/upgrade agreement — we will scope and quote that when you need it.
Which Odoo versions and editions does this work with?
We build for Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. The module depends on the standard Manufacturing (mrp) app, which exists in Community, so Enterprise is not required. We confirm your exact version and edition during scoping and package the module accordingly so it installs cleanly and stays upgrade-safe.
Will this conflict with our existing MRP setup or other custom modules?
No. The module extends standard models (mrp.bom, product.template) with new computed fields and dedicated wizards rather than overriding core behavior, so your existing manufacturing, inventory, and costing flows keep working. We install to a staging copy of your database first, run UAT against your real BOMs, and check for interactions with any custom modules before touching production. A documented rollback plan is part of every delivery.
How does the cost roll-up and where-used lookup actually work under the hood?
The roll-up walks each BOM recursively, multiplying quantities and applying unit-of-measure conversions at every level, then aggregates component, operation, and sub-assembly cost bottom-up using computed fields declared with @api.depends so totals recalculate automatically when inputs change. The where-used lookup is the inverse traversal: it indexes every BOM line referencing a component and returns the direct and indirect parents. Both respect company-specific costs and active BOM/variant selection.
Can external systems read the BOM tree and rolled-up costs?
Yes. On request we expose the where-used graph and rolled-up cost through Odoo's standard XML-RPC/JSON-RPC API, so your PLM, BI, or external ERP can pull the data programmatically. Access is governed by the same security groups and record rules as the in-app views, so external calls only return what the calling user is permitted to see.
相关模块
Multi-Level BOM & Where-Used Explorer
Visual multi-level BOM tree with cost roll-up, where-used reverse lookup, and mass component replacement for Odoo 17/18/19.
- Indented multi-level BOM tree view that recursively expands every sub-assembly and phantom (kit) BOM down to raw-material leaves in one collapsible OWL widget
- Roll-up cost aggregation across all BOM levels, summing component cost, operation cost, and sub-assembly cost bottom-up so the top-level total is always reconciled
- Where-used (reverse BOM) lookup: pick any component and instantly list every parent BOM and finished product it feeds into, at direct and indirect levels
- Mass component replace wizard that swaps one product for another across every BOM line it appears in, with a preview-and-confirm step before writing changes