A build-to-order Odoo module that centralizes each supplier's own product catalog, price lists, and available-stock figures against your internal products. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19 database. 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 centralizes each supplier's own product catalog, price lists, and available-stock figures against your internal products. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19 database.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
Buyers and procurement teams rarely fight your own product master data — they fight the supplier's. Every vendor sends their own SKU codes, their own descriptions, their own price breaks, and their own view of what is actually in stock, and none of it matches how your products are set up in Odoo. Native Odoo captures a slim slice of this on the product.supplierinfo records reachable from the Purchase tab: a vendor, a vendor product code and name, a minimum quantity, a price, and a validity window. What it does not model is the vendor's full catalog as the vendor sees it, the vendor's live or last-imported available stock per item, richer price structures, or a clean workspace where a buyer can compare what several suppliers say about the same thing before raising a purchase order. When that context lives in spreadsheets and inboxes, buyers key the wrong code, miss a better price break, or commit to a vendor who cannot actually fulfil.
New ORM models (`models.Model`) for vendor product catalog, vendor price lines, and vendor available-stock, each foreign-keyed to `product.template`/`product.product` and `res.partner`
Extends rather than replaces native `product.supplierinfo`, so existing Purchase-tab vendor pricing keeps working alongside the richer catalog
Vendor price lines with quantity breaks, currency, unit of measure, and validity dates (date_start/date_end)
`@api.depends` compute fields that surface the current best applicable vendor price and freshest available-stock figure directly on the product form
Per-vendor available-stock tracking with a last-updated timestamp so buyers can judge how stale the figure is
Vendor product code and name mapping so a supplier's own SKU resolves to your internal product
This is a build-to-order module we design and build for your database — it is not an existing download. We extend the vendor/product relationship with new models (models.Model) that hold the vendor's own product records, their price lines, and their available-stock figures, each linked back to your product.template/product.product and to res.partner. Vendor prices are expressed as their own lines with quantity breaks, currency, unit of measure, and validity dates, and @api.depends compute fields surface the current best applicable price and the freshest known stock figure directly on the product form so a buyer sees it without hunting. We wire clean views (XML, and OWL components where an interactive comparison panel earns it), list and form layouts for the vendor catalog, and optional QWeb reports such as a per-vendor price/availability sheet. Access is governed by ir.model.access.csv plus record rules so a purchasing user sees vendor data while it stays scoped by company, and automated actions or scheduled jobs can flag expired prices or stale stock. Where you already receive vendor feeds, we expose the models over Odoo's XML-RPC/JSON-RPC API so an external sync — a CSV drop, an EDI file, or a supplier portal export — can update prices and stock on a schedule rather than by hand.
Because it is built to your scope, the module respects your realities: multi-company record rules, your currencies and units of measure, your existing supplier records, and whether you run Community or Enterprise (the core models here are Community-compatible; Enterprise-only touchpoints are only introduced when your edition and workflow call for them). We target Odoo 17.0, 18.0, or 19.0 and pin the build to your running version so the ORM APIs, view architecture, and manifest (__manifest__.py) dependencies match exactly.
Delivery is build-to-order. It starts with a short scoping call to confirm which vendor attributes matter, how prices and stock arrive, and what the buyer's daily workflow should look like; from that we produce a fixed quotation and a written scope. Typical delivery is 2-4 weeks from confirmed scope, depending on integration and data-migration depth. You get the module built, installed on a staging database for UAT, then promoted to production with a rollback plan, plus documentation and a support window. Pricing starts from $249 (indicative, single-company base scope); multi-company record rules, live vendor-feed integrations (EDI/CSV/API), deeper price-list logic, and the volume of historical vendor data to migrate increase the quoted scope.
Runs supplier relationships in Odoo and needs one place where every vendor's own catalog, price breaks, and available stock live against internal products — so buyers pick the right supplier and the right price without spreadsheets.
Raises RFQs and POs daily and wants the vendor's current best price and known availability visible on the product form, plus a way to compare suppliers before committing an order.
Owns the database and needs the new models to respect multi-company record rules, correct access rights, and version compatibility — with clean code and a git handover rather than an opaque black-box app.
Cares that promised availability reflects what vendors can actually fulfil, and wants stale prices and stock flagged automatically so planning decisions rest on current data.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Vendor Product Management 模块 ZIP。
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中(或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传)。
激活开发者模式,打开应用程序,单击更新应用程序列表,搜索 Vendor Product Management,然后按安装。
打开新菜单,粘贴您的 ECOSIRE 许可证密钥,连接任何外部凭据(Shopify、Amazon、Stripe 等),然后保存。
运行内置连接测试,同步前 10 条记录,并安排定期 cron。如果出现任何问题,请联系支持人员。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Vendor catalog depth | Full vendor-side catalog, price lines, and available stock modeled to your needs | Whatever you can spec and build in-house | Fixed feature set, take it or leave it | |
| Available-stock tracking | Per-vendor stock figure with last-updated timestamp and staleness flags | Possible but you design and maintain it | Rarely covered, or only for specific connectors | |
| Fit to your workflow | Built to your scope: your UoM, currencies, multi-company rules | Fully bespoke, at your effort and cost | Generic; you adapt your process to the app | |
| Feed / API sync | XML-RPC/JSON-RPC + scheduled imports (CSV/EDI/API) where in scope | You build the integration yourself | Only if the app ships that specific connector | |
| Version support | Pinned and tested on your Odoo 17.0/18.0/19.0 and edition | You own compatibility and upgrades | Depends on the vendor's release cadence | |
| Code ownership | Full git repo handover, documented, yours to keep | You own it, but also all the maintenance | Licensed code; limited or no ownership | |
| Support & accountability | Scoped delivery, UAT, rollback plan, post-go-live support window | Internal team carries all risk | Best-effort vendor support, variable SLAs | |
| Cost model | Fixed quote after scoping; indicative from $249 | Open-ended developer time | Low sticker price, hidden fit and support cost |
No. This is a build-to-order Odoo module that ECOSIRE designs, builds, installs, and supports specifically for your database. There is no instant download — after a scoping call we build it to your confirmed requirements and deploy it on your Odoo 17/18/19 environment.
Typical delivery is 2-4 weeks from confirmed scope. The exact timeline depends on how vendor prices and stock reach you (manual, CSV, EDI, or live API), whether multi-company rules apply, and how much historical vendor data needs migrating. We give a firm timeline in the fixed quotation after the scoping call.
Pricing starts from $249 as an indicative, single-company base-scope figure — it is not a firm price. After a short scoping call we issue a fixed written quotation. Multi-company record rules, live vendor-feed integrations, deeper price-list logic, and larger data-migration volumes increase the quoted scope.
Every build includes a post-go-live support window for defects and questions. Because we hand over the full git repository, you own the code. We also offer ongoing support and version-upgrade engagements (for example moving the module from Odoo 17 to 18 or 19) as a separate scoped arrangement.
The core models, security, and views are Community-compatible. We only introduce Enterprise-only touchpoints when your edition and workflow require them. We confirm your edition and version during scoping and pin the `__manifest__.py` and dependencies accordingly.
Yes, where that is in scope. We expose the new models over Odoo's XML-RPC/JSON-RPC API and can build scheduled imports so a CSV drop, EDI file, or supplier portal export updates prices and available stock on a schedule instead of by hand. Live integrations add to the quoted scope.
No. It extends the native vendor/product relationship rather than replacing it, so your existing `product.supplierinfo` pricing continues to work. The new catalog, price lines, and available-stock tracking sit alongside it and reference the same suppliers and products.
A build-to-order Odoo module that centralizes each supplier's own product catalog, price lists, and available-stock figures against your internal products. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19 database.