Metal fabrication shops live and die on material yield, machine sequencing, and job costing that Odoo's generic manufacturing model was never shaped for. A fabricator quotes by weight and grade, cuts nested parts from stock sheets and bars, tracks the offcut "drops" that get reused, and routes each part through laser/plasma/waterjet, press-brake bending, and welding before finishing. Out of the box, Odoo's mrp.production treats a BoM as fixed quantities consumed at fixed operations — it has no concept of a nesting layout, no per-cut kerf loss, no reusable remnant inventory, and no way to cost a job by realized material utilization versus what was quoted. Teams end up running the shop in spreadsheets bolted onto Odoo, and the ERP stops being the source of truth.

Metal Fabricator is a build-to-order Odoo application ECOSIRE designs around your actual process. We extend the ORM with the models your operation needs: a nesting/layout model that groups parts onto a stock sheet or bar and records utilization and kerf; a stock.lot-backed remnant (drop) model so offcuts re-enter inventory with grade, gauge, and dimensions; and process routings that map cutting, bending, and welding as real mrp.routing.workcenter operations with per-operation setup and run times. Material is grade- and gauge-aware through product attributes and variants, and cost roll-up is computed with @api.depends compute fields so a job's true material, machine-time, and labor cost is visible the moment production data lands — not a month later in accounting.

Technically, everything is a proper Odoo module: a versioned __manifest__.py, models/ subclassing models.Model with _inherit on sale.order, mrp.production, stock.move, and product.template where we extend rather than replace core behavior, backed views in XML/OWL, and QWeb reports for the quote sheet, cut list, and traveler/router that follows a job on the floor. Access is locked down with ir.model.access.csv plus record rules so operators, estimators, and shop managers each see only what their role should. Automated actions and scheduled jobs handle the repetitive glue — flagging low remnant stock, notifying when a nest is ready to release, and rolling estimated-versus-actual variance onto the job. Where you need machines, MES, or a shipping/CAD-CAM system to talk to Odoo, we build against the XML-RPC/JSON-RPC API. We target Odoo 17.0, 18.0, and 19.0 and build cleanly on Community or Enterprise, using Enterprise-only features (like studio-adjacent widgets or advanced MRP) only when your edition already includes them.

Delivery is build-to-order: it starts with a scoping call to map your grades, machines, routings, and reporting, after which we confirm scope and a fixed quote, build on a staging instance, run UAT with your team, and deploy with a rollback plan and a post-go-live support window. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $349 (indicative, single-company base scope); multi-company shops, additional machine/MES integrations, deep localization, and large historical data migrations increase the quoted scope.