Anyone who runs discrete or process manufacturing in Odoo knows the pain: a finished good is built from sub-assemblies, which are built from further sub-assemblies, phantom kits and purchased components — but Odoo's native mrp.bom form only shows you one level at a time. To understand what a manufacturing order truly consumes, planners open the BOM, click into a sub-BOM component, click again, and lose the thread. The native "BOM Structure & Cost" report (mrp.report_mrp_bom) does render an indented explosion, but it lives outside the manufacturing order, is print-oriented, and gives you no interactive drill-down, no per-node stock/availability context, and no way to see the exploded tree next to the mrp.production record you are actually working on. When BOMs are 4-6 levels deep with shared sub-assemblies, native Odoo runs out of road for day-to-day shop-floor and engineering use.

Manufacturing BOM Structure is a made-to-order module ECOSIRE designs, builds and installs to close that gap. We add a smart-button and an embedded tree view to both mrp.bom and mrp.production that renders the entire recursive explosion — every level, every phantom/kit expansion, operations from the routing, and rolled-up component quantities scaled to the parent quantity — in a single collapsible OWL component. Technically, we implement a compute layer (@api.depends on bom_line_ids, product_qty, and the recursion of child BOMs) that walks mrp.bom.explode() server-side, materializes each node into a lightweight transient/models.Model structure, and streams it to a client-side OWL tree that supports expand/collapse, search, and level filtering. Each node can surface the fields your team needs — on-hand quantity, forecasted availability, unit and rolled-up cost, supplier lead time, or an ECO/version flag — pulled live so the tree reflects the real database, not a static snapshot.

Because it is your module, we tailor it to how you actually manufacture. We wire the correct security with ir.model.access.csv and record rules so the tree respects multi-company boundaries and per-team visibility; we add QWeb report variants if you need a printable exploded BOM for the shop floor or for customer/auditor handover; and we expose the exploded structure over the standard XML-RPC/JSON-RPC API when an external MES, PLM, or costing tool needs to read it. Everything is delivered in a clean __manifest__.py-declared module with no core patching, so it upgrades cleanly and coexists with your other customizations. We build for Community and Enterprise alike, calling out any Enterprise-only dependency (such as MRP workorder/PLM links) up front so there are no surprises.

Delivery is build-to-order and starts with a short scoping call. Once we agree the exact fields, drill-down behavior, security model and target Odoo version, we develop on a staging copy of your database, run UAT with your team, and deploy to production with a documented rollback plan. Typical delivery is 2-4 weeks from confirmed scope. This is not an instant download — we hand you installable source, docs, a training session, and a support window at the end. Pricing starts from $349 (indicative, single-company base scope); multi-company visibility rules, deep costing/availability roll-ups, printable QWeb variants, external API/PLM integrations, and larger data-migration volume increase the quoted scope.