A build-to-order Odoo application that manages production and food-manufacturing recipes — versioned formulations, scaling, yield, and cost roll-up wired into Manufacturing. ECOSIRE builds, installs, and supports it for your Odoo 17, 18, or 19. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
Manifesto do app
Feito em torno do seu fluxo de trabalho
A build-to-order Odoo application that manages production and food-manufacturing recipes — versioned formulations, scaling, yield, and cost roll-up wired into Manufacturing. ECOSIRE builds, installs, and supports it for your Odoo 17, 18, or 19.
Sem configuração por conta própria — um app funcional criado, instalado e com suporte da ECOSIRE.
Comece com um preço único de desenvolvimento. Definimos o escopo com você no início.
A ECOSIRE cria, configura e instala no seu Odoo.
Você entra no ar em cerca de 2–4 semanas, com um período de suporte pós-lançamento.
Teams that manufacture food, beverages, cosmetics, or any batch-produced good live and die by their recipes — the precise quantities, sub-recipes, process steps, and allergen data that turn raw materials into a finished product. Odoo's native Manufacturing gives you a bill of materials and routing, but a BoM is a flat parent-child structure: it has no concept of a formulation percentage, a per-batch yield loss, a graduated scaling factor, a versioned "approved" recipe with an effective date, or the process instructions and quality parameters a production floor actually needs. Prep teams end up keeping the real recipe in a spreadsheet and re-keying it into an mrp.bom, which is exactly where cost drift, allergen errors, and out-of-date formulations creep in.
Recipe Manager is a build-to-order Odoo application we design and build to sit on top of that native foundation and give you a proper recipe layer. At its core is a dedicated recipe model (a new models.Model, e.g. recipe.recipe) with ingredient lines that carry either an absolute quantity or a percentage of batch, a state field for the draft → approved → archived lifecycle, and version tracking so a superseded formulation is retained for traceability rather than overwritten. Ingredient costs, batch cost, and cost-per-unit-of-yield are computed fields (@api.depends on the line quantities, the linked product.product standard or average cost, and the declared yield) so a change to a raw-material price re-rolls the recipe cost automatically. Because recipes reference real product.product records and units of measure, they scale cleanly: a scaling wizard recomputes every line for a target batch size and rounds to the UoM's precision. Where you want the recipe to actually drive production, we generate or synchronise the corresponding mrp.bom and routing so the shop floor keeps using standard Odoo manufacturing orders — no parallel system.
Technically it is delivered as a normal Odoo addon with its own __manifest__.py, declaring dependencies on mrp (and stock/quality where in scope). Access is governed by ir.model.access.csv for the recipe-author, reviewer, and read-only roles, with ir.rule record rules to keep recipes scoped per company in a multi-company database. The UI is built with standard XML views (list, form, kanban by state) plus OWL components where an interactive scaling or costing panel adds value, and printable QWeb reports produce a clean recipe/spec sheet and a batch production sheet for the floor. Automated actions (or base.automation rules) can flag recipes whose linked ingredient cost has moved beyond a threshold or whose approval has expired, and everything is reachable over the standard XML-RPC/JSON-RPC API so an external PLM, e-commerce catalogue, or nutrition/labelling system can read and write recipe data. We build against your exact edition — Community or Enterprise — and target Odoo 17.0, 18.0, or 19.0; Enterprise-only hooks (such as Quality or Studio-adjacent features) are only used when your database actually has them.
Because this is a build-to-order product, nothing is auto-downloaded. It starts with a scoping call to confirm your recipe structure, whether percentages or absolute quantities lead, how yield and by-products are handled, which fields must flow into the BoM, and your reporting and integration needs. From confirmed scope, typical delivery is 2–4 weeks: we develop on a branch, hand over on a staging database for UAT, then install into production with a rollback plan and a training session. Pricing starts from $249 (indicative, single-company base scope); multi-company record rules, deep sub-recipe/BoM synchronisation, nutrition/allergen and labelling logic, external-system integrations, and migrating a large existing recipe library into the new models increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise.
Runs batch manufacturing on Odoo and needs versioned, approved recipes with accurate yield and per-batch cost that native BoMs can't express — and printable batch sheets the floor will actually follow.
Develops and iterates recipes in draft, scales them from lab to full batch, and needs a controlled approval path plus retained history so a superseded formulation is never silently lost.
Wants recipe cost to re-roll automatically when raw-material prices move, with cost-per-unit-of-yield visible before a batch runs, so margins are known rather than discovered after the fact.
Maintains the Odoo instance and needs a clean, upgrade-safe addon with correct manifest dependencies, `ir.model.access` security, record rules, and API access rather than another off-system spreadsheet.
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| Recipe formulation model | Dedicated recipe model with % or absolute lines, purpose-built for your process | Possible, but you design and maintain the data model yourself | Generic recipe structure that rarely matches your exact formulation rules | |
| Versioning & approval | Draft→approved→archived lifecycle with retained history and effective dates | Only if you build and test the state machine | Basic or absent; varies widely by module | |
| Cost roll-up | Computed batch and per-yield cost that re-rolls on price change via `@api.depends` | Depends on the compute logic you write | Often simple totals; per-yield/loss handling limited | |
| Scaling to batch size | Scaling wizard with UoM-precise rounding for any target batch | Build the wizard and rounding rules yourself | Sometimes included, rounding behaviour inconsistent | |
| Fit to your workflow | Scoped to your exact process, reports, and roles before we build | Full control, but full cost and timeline on you | Fixed feature set — you adapt to it | |
| Security & multi-company | `ir.model.access.csv` roles + record rules scoped per company | Your responsibility to design and verify | Baseline access rights, multi-company rules often thin | |
| Support & code ownership | Support window, training, and full git repo handover — no lock-in | You own it, but also own every fix and upgrade | Vendor-dependent; source and roadmap not yours | |
| Delivery model | Build-to-order, 2–4 weeks from confirmed scope, staging UAT + rollback | Weeks to months depending on internal capacity | Instant download, but integration and gaps are on you |
Recipe Manager is build-to-order, not an instant download. After a scoping call to confirm your recipe structure, costing, and integration needs, typical delivery is 2–4 weeks from confirmed scope. We develop on a branch, hand over on staging for UAT, then install to production with a rollback plan.
Pricing starts from $249 as an indicative single-company base-scope figure. The real drivers are multi-company rules, sub-recipe/BoM synchronisation depth, nutrition/allergen logic, external integrations, and migrating an existing recipe library. You get a fixed written quote after the scoping call — never a surprise bill.
Yes. We build against Odoo 17.0, 18.0, or 19.0 and match your edition — Community or Enterprise. Enterprise-only hooks (such as Quality) are only used when your database actually has them, so the addon stays compatible with what you run.
Every build includes a post-go-live support window for defect fixes and questions. Beyond that, we offer ongoing support and can port the addon to a future Odoo release as a scoped engagement. Because you receive the full git repository, you are never locked in.
A native `mrp.bom` is a flat parent-child structure with no percentage formulation, versioned approval lifecycle, yield/loss reconciliation, or graduated scaling. Recipe Manager adds a dedicated recipe model with those concepts, then optionally generates or syncs the BoM so production still runs through standard Odoo manufacturing orders.
Yes. Recipes are exposed over the standard Odoo XML-RPC/JSON-RPC API, so a PLM, e-commerce catalogue, nutrition/labelling tool, or reporting system can read and write recipe and cost data. The specific integration is scoped and quoted based on the endpoints you need.
We deliver a clean, self-contained addon with a proper `__manifest__.py`, standard models, and security files rather than server-side monkey-patches, which keeps it upgrade-friendly. A version-to-version migration is still a scoped task, but the architecture is designed to minimise that effort.
A build-to-order Odoo application that manages production and food-manufacturing recipes — versioned formulations, scaling, yield, and cost roll-up wired into Manufacturing. ECOSIRE builds, installs, and supports it for your Odoo 17, 18, or 19.