| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Project (project) • Purchase (purchase) • Surveys (survey) • Invoicing (account) • Employees (hr) |
| Lines of code | 4422 |
| Technical Name |
grev_od_tender_management |
| License | OPL-1 |
| Website | https://grevlin.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Project (project) • Purchase (purchase) • Surveys (survey) • Invoicing (account) • Employees (hr) |
| Lines of code | 4422 |
| Technical Name |
grev_od_tender_management |
| License | OPL-1 |
| Website | https://grevlin.com |
|
|
|
▣ What's Included in the Suite
|
|
⭐ Suite-Level Capabilities
|
|
▶ How It Works
|
|
📦 What's Inside — vs Buying Separately
|
|||||||||||||||||||||||||||||||||||
|
📋 Changelog
|
|
🙋 Support & Contact 30 days free support included with every purchase. Our team responds within one business day.
|
Tender Management Suite
The Tender Management Suite is the meta-installer for the complete Grevlin tender lifecycle platform. Installing this single application installs all three sub-modules and provides a unified menu, an OWL dashboard, and consolidated navigation across tender calls, vendor bids, Purchase Orders, and Project Tasks.
Overview
Included Modules
| Module | Version | Purpose |
|---|---|---|
| grev_od_tender_core | 19.0.1.0.0 | Foundation: tender calls, lots, bidding, evaluation, portal |
| grev_od_tender_purchase | 19.0.1.1.0 | PO fulfillment: one-click PO from awarded lot |
| grev_od_tender_project | 19.0.1.1.0 | Task fulfillment: task hierarchy, timesheets, milestones |
This module adds no new models. Its value is the unified installation point, integrated menu structure, and the OWL dashboard component.
Installation
Prerequisites
- Odoo 19.0 Community or Enterprise
- Standard Odoo modules: base, mail, survey, portal, purchase, purchase_stock, stock, project, hr_timesheet
Steps
- Copy all four module directories to your Odoo addons path
- Go to :menuselection:`Apps --> Update Apps List`
- Search for Tender Management
- Click :guilabel:`Install` — all three sub-modules are installed automatically
Note
If you only need the bidding engine without fulfillment, install grev_od_tender_core alone. Add the fulfillment modules later as your procurement process matures.
Quick Start
Step 1 — Create a Tender Call
- Go to :menuselection:`Tenders --> Tender Calls`
- Click :guilabel:`Create`
- Set the Reference, Title, and Bid Deadline
- Optionally attach a :guilabel:`General Survey` for vendor qualification
- Save the record (state: Draft)
Step 2 — Add Lots and Requirements
- Open the :guilabel:`Lots` tab on the tender form
- Click :guilabel:`Add a line` to create a lot
- Set :guilabel:`Fulfillment Type` to Purchase Order or Project Task
- Open the lot and add Requirement Lines (product, qty, specs, estimated price)
- Repeat for each independent package in the tender
Tip
A tender can mix fulfillment types across its lots. Lot A could generate a PO (goods) while Lot B generates a project task (services) — all within the same tender call.
Step 3 — Publish and Collect Bids
- Click :guilabel:`Publish` on the tender — vendors can now see and respond
- Vendors log in to the portal and submit their bids, including:
- Completing mandatory surveys
- Entering price, delivery date, and terms per lot line
- Monitor submissions via :menuselection:`Tenders --> Bids`
Step 4 — Evaluate and Award
- Click :guilabel:`Start Evaluation` once the deadline passes
- Open each bid and score it on technical and financial criteria
- The Final Score (50/50 weighted) ranks the bids automatically
- Click :guilabel:`Award Bid` on each lot and select the winning bid
Step 5 — Fulfill (PO or Project Task)
Depending on the lot's fulfillment type:
Purchase Order path:
- Open an awarded lot with :guilabel:`Fulfillment Type` = Purchase Order
- Click :guilabel:`Create Purchase Order`
- Confirm the PO and proceed to goods receipt
Project Task path:
- Open an awarded lot with :guilabel:`Fulfillment Type` = Project Task
- Click :guilabel:`Create Project Task`
- Assign team members, monitor timesheets, and accept deliverables via the acceptance workflow
Dashboard
Access the OWL dashboard at :menuselection:`Tenders --> Dashboard`.
The dashboard provides real-time visibility into:
- Active tenders — count of tenders in Published or Evaluation state
- Lots by status — breakdown of awarded, open, and cancelled lots
- Bids by state — submitted, evaluated, won, and lost bid counts
- Expiring soon — tenders with deadlines within the next 7 days (urgent)
- Recent tenders — quick-access list of the most recently created calls
- Quick actions — :guilabel:`New Tender` button for fast creation
The dashboard is implemented as an OWL component registered as the tender_dashboard client action.
Technical Reference
This module contributes:
- views/tender_dashboard_views.xml — OWL client action registration
- views/menu_views.xml — consolidated application menu
- static/src/js/tender_dashboard.js — OWL dashboard component
- static/src/xml/tender_dashboard.xml — QWeb template
- static/src/css/tender_dashboard.scss — component styles
The dashboard uses useService("orm") RPC calls to aggregate KPIs from the grev.tender.call, grev.tender.bid, and grev.tender.lot models.
See Also
- :doc:`../grev_od_tender_core/index` — Tender Core documentation
- :doc:`../grev_od_tender_purchase/index` — Purchase Fulfillment documentation
- :doc:`../grev_od_tender_project/index` — Project Fulfillment documentation
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module