A build-to-order Odoo module that captures employee material demand, routes multi-level purchase requisition approvals, and turns approved lines into RFQs or internal stock transfers. ECOSIRE scopes, builds, installs, and supports it on 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.

A build-to-order Odoo module that captures employee material demand, routes multi-level purchase requisition approvals, and turns approved lines into RFQs or internal stock transfers. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17, 18, or 19.
今すぐのお支払いはありません。これはチームへの見積もり依頼を送信します。価格と次のステップをメールでご案内します。
Most teams running Odoo hit the same wall the moment a warehouse operator, technician, or site supervisor needs material: there is no first-class place for an employee to say "I need 40 units of this to keep working." Odoo core gives you Purchase Requisitions (purchase.requisition) as a Manager-facing tendering tool and Purchase Agreements — but those are procurement instruments, not shop-floor demand capture. The gap gets filled with spreadsheets, WhatsApp messages, and internal transfer requests raised by whoever has stock access, which means no audit trail on who asked for what, no budget check before someone commits spend, and no clean handoff from "employee raised a need" to "buyer raised an RFQ" or "stock team issued an internal transfer." When procurement, inventory, and the requesting department each keep their own version of the truth, over-ordering, stock-outs, and unapproved purchases follow.
`material.requisition` and `material.requisition.line` models with a full `state` machine (`draft → submitted → approved → sourced → done`, plus `rejected`/`cancelled`) and enforced transition guards
Configurable multi-level approval matrix driven by amount thresholds, department, or product category, using Odoo activities and automated actions for escalation and reminders
`@api.depends` compute fields showing on-hand, reserved, and forecasted availability per line by joining `stock.quant` and `product.product` in real time
Smart line dispatch: available items raise a `stock.picking` internal transfer; buyable items seed a draft `purchase.order` line, preserving requester, analytic account, and source warehouse
Optional multi-vendor tendering path that generates a `purchase.requisition` (Purchase Agreement) when a line needs competitive bidding
Row-level security via `ir.model.access.csv` plus record rules so employees see only their own requisitions while approvers and buyers see scoped queues
We build a made-to-order Odoo module that gives every employee a governed way to request material and gives Purchase and Inventory a single approval spine to run it through. At its core is a material.requisition model (header + material.requisition.line) with state transitions (draft → submitted → approved → sourced → done / rejected / cancelled), compute fields via @api.depends for on-hand vs forecasted availability pulled from stock.quant and product.product, and a configurable approval matrix driven by mrp-style routing or an amount/department threshold. Each approved line is dispatched intelligently: if the item is available in a source warehouse it raises a stock.picking internal transfer; if it must be bought it seeds a draft purchase.order line (or a purchase.requisition tender when you want multi-vendor bidding), carrying the requester, analytic account, and budget line through so nothing loses its origin. Access is locked down with ir.model.access.csv plus record rules so employees see only their own requests while approvers and buyers see their queues; multi-level approvals use Odoo's activity/automated-action framework so escalations and reminders are native, not bolted on. Everything is exposed through standard views (list, form, kanban by state, a pivot for demand analysis), a QWeb PDF requisition slip for signature, and the XML-RPC/JSON-RPC API so an external portal, mobile app, or MES can post requisitions programmatically. We ship a proper __manifest__.py with pinned dependencies and target your exact Odoo series — 17.0, 18.0, or 19.0 — accounting for Community vs Enterprise differences (for example, approval-tier and advanced routing behavior) so the module fits your edition rather than assuming features you may not have.
Because this is build-to-order, delivery starts with a scoping call, not a download. After we confirm the exact states, approval hierarchy, sourcing rules, and any integration points, typical delivery is 2–4 weeks from confirmed scope: we develop against your version on an isolated staging environment, run UAT with your team, then install to production with a documented rollback path and a git repository handover. Pricing starts from $249 (indicative, single-company base scope); multi-company routing, deeper procurement/budget integrations, localization requirements, or migrating a large backlog of historical requisition data increase the quoted scope. You get a fixed quote after the scoping call — never a surprise invoice.
Wants every material need to arrive as an approved, budget-checked requisition that cleanly becomes an RFQ or purchase order — with a full audit trail of who requested what and why, instead of ad-hoc emails and spreadsheets.
Needs employee demand routed through a single queue so available stock is issued via internal transfers first and only genuine shortfalls trigger buying, cutting duplicate orders and surprise stock-outs.
Wants their team to raise material requests in Odoo in seconds — from the backend or a simple link — and to see request status without chasing procurement, while keeping their own cost-center spend visible.
Responsible for a maintainable module that respects Odoo's security model, upgrades cleanly across the 17/18/19 line, and exposes an API so requisitions can be created from external systems.
ecosire.com でライセンスを購入し、アカウント ダッシュボードから Material Stock and Purchase Requisitions モジュールの ZIP をダウンロードします。
ZIP をサーバー上の Odoo カスタム アドオン フォルダーに抽出します (または、[アプリ] > [Odoo.sh / runbot のファイルからインストール] を介してアップロードします)。
開発者モードをアクティブにし、アプリを開き、「アプリリストの更新」をクリックして、「Material Stock and Purchase Requisitions」を検索し、「インストール」を押します。
新しいメニューを開き、ECOSIRE ライセンス キーを貼り付け、外部認証情報 (Shopify、Amazon、Stripe など) を接続して保存します。
組み込みの接続テストを実行し、最初の 10 レコードを同期し、定期的な cron をスケジュールします。何か問題が発生した場合はサポートにお問い合わせください。
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| Employee material demand capture | First-class requester UI plus portal/API entry | Possible but you design and build it | Often procurement-only, limited requester view | |
| Multi-level approval matrix | Configurable by amount, department, category | Whatever you code and maintain | Fixed or shallow approval flow | |
| Stock-aware sourcing | Internal transfer if available, else RFQ/PO | You wire the stock/purchase logic yourself | Usually routes straight to purchase | |
| Row-level security | Record rules scope requester vs approver vs buyer | Depends on your implementation rigor | Varies; often coarse access | |
| Fit to your version/edition | Built for your exact 17/18/19 and edition | Yours to match and upgrade | Generic build across many versions | |
| API / external integration | XML-RPC/JSON-RPC endpoints designed in | Add it yourself | Rarely documented for this use | |
| Support & ownership | Support window + git repo handover | You own all maintenance | Vendor SLA varies, source often opaque | |
| Time to production | Typically 2–4 weeks from confirmed scope | Unpredictable, dev-capacity dependent | Install fast, fit later |
This is a build-to-order module, not an instant download. After a scoping call to confirm states, approval hierarchy, and sourcing rules, typical delivery is 2–4 weeks from confirmed scope. We develop and UAT on staging, then install to production with a rollback plan.
Pricing starts from $249 as an indicative single-company base-scope figure. After a short scoping call we send a fixed quote — no surprise invoice. Drivers such as multi-company routing, deeper budget/procurement integrations, localization, or migrating a large backlog of historical requisitions increase the quoted scope.
Every build includes a post-go-live support window for defect fixes and configuration tweaks, plus technical docs and a git repo handover so any Odoo team can maintain it. Version upgrades (for example moving from 18.0 to 19.0) and new feature work are quoted separately as change requests.
Yes. We target your exact series — 17.0, 18.0, or 19.0 — and account for Community vs Enterprise differences (such as approval-tier and advanced routing availability) so the module fits your edition rather than assuming features you may not have.
Odoo core's `purchase.requisition` is a Manager-facing tendering tool for procurement. This module adds the missing front end: employees raise material demand, it runs through a configurable multi-level approval matrix, checks stock availability, and only then becomes an internal transfer or a purchase — with row-level security so requesters see just their own requests.
Yes. We can expose requisition creation through the portal, an activity/email approval link, or the XML-RPC/JSON-RPC API so a lightweight app or website form posts requests — with `ir.model.access.csv` and record rules ensuring each user only sees what they should.
Yes. The module is API-first: an external portal, mobile app, or MES can create and query requisitions over Odoo's XML-RPC/JSON-RPC API, carrying requester, product, quantity, warehouse, and cost-center so the same approval and sourcing logic applies.
A build-to-order Odoo module that captures employee material demand, routes multi-level purchase requisition approvals, and turns approved lines into RFQs or internal stock transfers. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17, 18, or 19.