Skip to Content

Tender Project

by
Odoo

$ 261.84

v 19.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Project (project)
• Discuss (mail)
• Employees (hr)
• Surveys (survey)
Community Apps Dependencies
Lines of code 3871
Technical Name grev_od_tender_project
LicenseOPL-1
Websitehttps://grevlin.com
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Project (project)
• Discuss (mail)
• Employees (hr)
• Surveys (survey)
Community Apps Dependencies
Lines of code 3871
Technical Name grev_od_tender_project
LicenseOPL-1
Websitehttps://grevlin.com
📋

Tender → Project Tasks

Convert awarded service tender lots into managed Project Tasks — with automatic task hierarchy, timesheet logging, deliverable acceptance, and milestone-based billing.

✓  Odoo 19.0 ⚡  Community & Enterprise 💰  €179 — OPL-1 🛠  Service Fulfillment
🔒  Requires:  grev_od_tender_core must be installed first. Also requires standard Odoo project and hr_timesheet.

Tender Project extends the Tender Core with a complete service fulfillment path. When a tender lot is awarded for services — consulting, construction, IT delivery — one click creates a structured Project Task with sub-tasks per lot line, automatic project assignment, timesheet access, and a manager sign-off workflow for deliverable acceptance.

Core Features

📄

Automatic Task Hierarchy

One click creates a main task plus one sub-task per lot line. Task names, specifications, and deadlines are pre-populated from the winning bid. The project is auto-created by tender name if it doesn’t already exist, with timesheets enabled.

⏱

Timesheet Logging

Vendors and internal staff log hours directly on tender tasks using Odoo’s standard hr_timesheet. Timesheet counts are tracked per lot with smart button navigation. Transparent billing is grounded in actual logged hours.

🔒

Deliverable Acceptance Workflow

Managers formally accept or reject completed tasks with date-stamped sign-off, acceptance notes, and Chatter notifications. Accepted deliverables are clearly marked; rejections trigger re-work with full audit history.

💎

Milestone-Based Billing

Define billing milestones per task with fixed amounts or timesheet-based variable billing. Milestones progress through pending → done → invoiced states. Amounts are released only upon confirmed completion.

👥

Vendor Portal Access

The winning vendor is automatically subscribed as a follower on the project and main task. They can view task details, log timesheets, and track milestone status through the standard Odoo portal — no separate login or system required.

🔗

Full Traceability

Every task is linked to its source tender lot, tender call, and winning bid via stored relational fields. Navigate Task → Lot → Tender Call instantly with smart buttons. Contract value and vendor identity are inherited from the bid automatically.

How It Works

1

Award Lot

Evaluate bids, award the lot to the winning vendor

→
2

Create Tasks

One click creates main task + sub-tasks from lot lines

→
3

Log Work

Vendor and staff log timesheets against tasks

→
4

Accept & Bill

Manager accepts deliverables, milestones marked invoiced

Changelog

v19.0.1.1.0 — Initial Release

  • One-click project task creation from awarded tender lot (main + sub-tasks)
  • Auto-creation of Odoo project by tender name with timesheets enabled
  • Sub-tasks generated per lot line with specs, deadlines, product mapping
  • Contract value inherited from winning bid sum on project task
  • Vendor portal access: winner subscribed as follower on project & task
  • Timesheet logging integration (hr_timesheet) with per-lot count tracking
  • Deliverable acceptance workflow: accept/reject with notes & date sign-off
  • Milestone model (grev.tender.task.milestone): fixed & timesheet billing
  • Milestone state machine: pending → done → invoiced
  • Full traceability: Task → Lot → Tender Call smart buttons
🙋

Need Help?

✉  support@grevlin.com

𝕏  @GrevlinGlobal

🆕  30 days free support included

Tender Management — Project Fulfillment

Tender Project extends the Tender Core module with the Project Task fulfillment path. Once a lot with fulfillment_type = project is awarded, this module enables one-click task creation: a main task is created with one sub-task per lot requirement line, timesheets are enabled, the vendor is subscribed as a follower, and a milestone-based billing model is available for structured service delivery.

Note

Requires :doc:`../grev_od_tender_core/index` plus the standard Odoo modules project and hr_timesheet.

Overview

Key Features

  1. Automatic task hierarchy — one click creates a main task and one sub-task per lot line; names, specs, and deadlines are pre-populated from the winning bid
  2. Auto-project creation — if no project exists for the tender, one is created automatically with allow_timesheets = True
  3. Vendor portal access — the winning vendor is subscribed as a follower on the project and main task; they can view tasks and log timesheets
  4. Timesheet logging — hr_timesheet integration with per-lot timesheet count tracking via smart button
  5. Deliverable acceptance workflow — managers formally accept or reject completed tasks with date-stamped sign-off and notes
  6. Milestone-based billing — configurable milestones per task with fixed-price or timesheet-based (variable) billing
  7. Contract value tracking — total winning bid value is inherited on the main task for budget visibility

Installation

Prerequisites

Steps

  1. Go to :menuselection:`Apps --> Update Apps List`
  2. Search for Tender Management — Project Fulfillment
  3. Click :guilabel:`Install`

Tip

Installing grev_od_tender_management installs this module automatically as part of the full suite.

Configuration

Project Settings

No additional project configuration is required. The module automatically sets allow_timesheets = True on any project it creates. If you want to use an existing project, ensure timesheets are enabled on it before running task creation.

Usage

Creating Project Tasks from an Awarded Lot

  1. Go to :menuselection:`Tenders --> Tender Lots`

  2. Open a lot in Awarded state with :guilabel:`Fulfillment Type` set to Project Task

  3. Click :guilabel:`Create Project Task` in the action area

    The system will:

    • Validate the lot is awarded and in project fulfillment mode
    • Find or create a project named after the tender call (per company)
    • Create a main task: {tender_name} — {lot_name}
    • Create one sub-task per lot requirement line, linked to the main task, with specifications as task description and delivery_date as sub-task deadline
    • Set the main task deadline from the earliest delivery date across the winning bid lines
    • Set contract_value from the sum of winning bid line subtotals
    • Subscribe the winning vendor as a follower on the project and main task
    • Post a Chatter message with the sub-task count

  4. The main task form opens automatically; review and assign

Warning

Only one active (non-cancelled) parent task is permitted per lot. To re-create a task, first cancel the existing main task via the project.

Managing Sub-Tasks

Each sub-task corresponds to one requirement line in the lot:

  • The sub-task name comes from the lot line name or product display name
  • The sub-task description carries the lot line specifications
  • The deadline matches the winning bid line's delivery_date for that line
  • Sub-tasks are visible in the project's Kanban and list views with the parent task filter

Timesheet Logging

All tender tasks have timesheets enabled automatically. To log time:

  1. Open the task from :menuselection:`Project --> Tasks`
  2. Click :guilabel:`Log Time` (or open the :guilabel:`Timesheets` tab)
  3. Enter the date, duration, and description
  4. Save

Vendors log timesheets through the portal after being subscribed as followers. The per-lot timesheet count is visible via the :guilabel:`Timesheets` smart button on the tender lot form.

Accepting Deliverables

When a task is marked done by the vendor:

  1. Open the task in :menuselection:`Project --> Tasks`
  2. Review the deliverable against the lot specifications
  3. Click :guilabel:`Accept Deliverable` to approve:
    • acceptance_state is set to accepted
    • accepted_by_id records the approving user
    • acceptance_date is set to today
    • A Chatter message is posted
  4. Or click :guilabel:`Reject Deliverable` to send back for rework:
    • acceptance_state is set to rejected
    • The vendor receives a Chatter notification
    • Accepted-by and acceptance date are cleared

Tip

Add detailed :guilabel:`Acceptance Notes` to document what was reviewed and why a rejection was issued. These notes form part of the audit trail.

Milestone-Based Billing

Milestones allow structured billing aligned to delivery stages:

  1. Open a tender task from :menuselection:`Project --> Tasks`
  2. Click the :guilabel:`Milestones` smart button (visible when the task is a tender task)
  3. Click :guilabel:`Create` to add a milestone:
    • Name — milestone description (e.g. "Phase 1 Delivery")
    • Billing Type — Milestone (fixed amount) or Timesheet (variable, based on logged hours)
    • Amount — monetary amount released upon completion
    • Due Date — expected completion date
  4. To progress a milestone:

Technical Reference

Extended Models

grev.tender.lot (extended)

Added fields:

  • task_ids — One2many to project.task
  • task_count — computed; excludes sub-tasks (parent_id = False)
  • timesheet_count — computed sum of all timesheet lines on lot tasks

Added methods:

  • action_create_project_task() — creates main + sub-tasks
  • action_view_tasks() — opens filtered task list (top-level only)
  • action_view_timesheets() — opens account.analytic.line for lot tasks

project.task (extended)

Added traceability fields:

  • tender_lot_id — Many2one to grev.tender.lot (ondelete='restrict')
  • tender_id — related to grev.tender.call via lot (stored, indexed)
  • tender_bid_id — Many2one to grev.tender.bid
  • is_tender_task — computed boolean (stored, indexed)
  • tender_vendor_id — related to bid.partner_id (stored)

Added contract and acceptance fields:

  • contract_value — Monetary; total from winning bid subtotals
  • acceptance_state — pending | accepted | rejected
  • accepted_by_id, acceptance_date, acceptance_notes
  • milestone_ids — One2many to grev.tender.task.milestone
  • milestone_count, milestone_done_count — computed integers

New Models

grev.tender.task.milestone

Milestone-based billing record; inherits mail.thread.

Key fields:

  • task_id — Many2one to project.task (cascade delete)
  • billing_type — milestone (fixed) or timesheet (variable)
  • amount — Monetary; amount released on completion
  • due_date, completion_date — scheduling
  • state — pending | done | invoiced

Field Reference

Field Model Type Description
acceptance_state project.task Selection Deliverable sign-off status
contract_value project.task Monetary Sum of winning bid line subtotals
milestone_count project.task Integer (computed) Total milestones for this task
timesheet_count grev.tender.lot Integer (computed) Total timesheet entries across lot tasks

See Also

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

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.