Public Tender Monitoring & Bid Management, Belgium ready — BOAMP and TED monitoring, mandatory bid language (Dutch, French), foreign bidders' right of access, and buyer listing below the threshold, where no notice is published.
Overview
Public Tender Monitoring — BOAMP and TED
An SME does not lose public contracts at the bid opening. It loses them earlier, by answering tenders it never had a chance of winning — because price counted for sixty percent, or because a required certification was held by no one. This module does that sorting before you spend three days on it.
Also searched as: Odoo tender monitoring, public procurement bid software, BOAMP TED tracking, tender pipeline, public tender go/no-go, DC4 subcontracting form.
Two sources, one record per notice. BOAMP for France, TED for the European Union. Each notice enters once and only once: the key is the original reference. A subsequent collection updates what belongs to the buyer — the subject, the deadline, the procedure — without ever overwriting what belongs to you: the stage, the decision, the criteria, the conditions.
A calibrated filter, not a keyword. Three expressions sort the notices: what falls within your line of business, what must be discarded outright, and what can be delivered remotely. Exclusion takes precedence over business fit — a project-management (maîtrise d'œuvre) assignment that mentions an “information system” is discarded, not kept. Outside the départements where you operate, a notice is kept only if its subject can be delivered remotely. On TED, where selection is based on CPV codes, the exclusion works in French and Dutch.
All three are set in the settings. The shipped values are tuned on real tenders from the business software sector; replace them with your own before the first collection. An invalid expression is rejected on entry, with the error message: it cannot bring down the nightly watch. And as soon as you redefine your trade, the shipped exclusion list is dropped rather than imposed on you — it excludes roofing, plumbing and civil engineering, which may well be your trade.
Also configurable: departments, date horizon, CPV codes and TED countries, price threshold, and the monitoring recipient.
Price is the first judge. The module stores the notice's weighted scoring grid — label, type, weight as a percentage — and discards any tender where price weighs more than your threshold. Forty percent by default, adjustable. As long as the weighting is unknown, the notice is not discarded: it is flagged as such.
Eligibility requirements, and who meets them. Certification, local presence, minimum revenue, three years of references, insurance: each requirement is either met by you or covered by a declared subcontractor. A requirement that nobody covers turns the assessment into a No-go, with the reason stated in writing.
What the bid structure owes to third parties. The share you perform yourself is calculated. At zero, an alert reminds you that subcontracting the entirety of a contract is prohibited. If all covered requirements are covered by the same partner, the module says so: if that partner withdraws, the bid no longer stands. It flags, it does not block — the decision to bid remains yours.
Monitoring that does not harass you. The scheduled action schedules one activity per new notice, only once, never twice, even if you have closed the first one. Nothing is sent externally: no automatic email to any buyer.
Competitive intelligence. Award results feed statistics by buyer and by niche: who wins, and with how many bids received. This is what surfaces under-competed niches.
Responding in Belgium
The language of the bid comes before the criteria. Depending on the buyer's region, a bid written in the other language is not marked down: it is rejected without review and without appeal. Each notice therefore carries its mandatory language — Dutch, French, German, bidder's choice, or not specified. Not specified is not a neutral value: it is an admission that the tender specifications have not been read, and the module then refuses to move the notice to drafting. The rule lives in the model, not the screen: an import, a server action or an XML-RPC call runs into it just as a button does. The language is inferred from the buyer's country and region when a rule allows it — and an inferred value is flagged as such, never confused with a value actually read.
Who checks which document. For each eligibility condition, a column states who checks it: the contracting authority, the bidder, or the subcontractor. This is what separates a domestic bidder, for whom the authority queries the registers itself and who provides nothing, from a foreign bidder who must produce the equivalents from their own country — certificate of social contributions compliance (attestation de vigilance), tax compliance, company registration extract, criminal record. A condition that must be produced but is not, or whose document is older than the configured validity period, prevents moving to submission. This is exactly where foreign bids get rejected, before the offer is even read.
Contractor accreditation (agréation) applies only to construction works. Found on an IT, consulting or training lot, it is marked as not applicable: it does not switch any notice to No-go and does not prevent any submission. The module recognizes works contracts based on a pattern you configure, and you can correct it notice by notice.
Vendor listing — the half of the market that goes through no notice. Below a certain amount, a buyer can order after consulting a few suppliers, without publishing anything. No tender monitoring will ever see those contracts: there is nothing to detect, only someone to meet. The module therefore opens a second object, separate from notices: the listed prospect — the buyer, the person met, the date of first contact, the follow-up, the expected amount, and its own cycle “to contact, contacted, listed, consulted, no follow-up”. A listing closed as no follow-up only returns to the pipeline through an explicit reopening.
These three rules rely on configurable values, not constants: the region → language mapping, the languages in which you produce a bid, the validity period of a document, the listing threshold. The publisher asserts no statutory article: these are working benchmarks, and the tender's special specifications prevail.
What the module does not do
It does not download tender documents and does not extract weightings from a PDF: that is the job of the “Public Procurement — tender document (DCE) analysis” module, kept separate on purpose. It drafts no bid document. It uploads nothing to a procurement platform. It does not create buyer contacts on its own: a daily watch that creates hundreds of partners makes the address book unusable. It does not translate your bid and does not know whether you can write it in Dutch: it asks you to declare it. It detects no contract below the publication threshold — by design, there is nothing to detect — and solicits no one on your behalf. Its industry filter cannot be adapted to your sector from the interface, and it does not keep the notices the filter discarded during collection.
Both scheduled actions are shipped inactive: an installation does not query two public APIs without you asking it to.
Specifications
| Price | €199 excl. VAT |
|---|---|
| License | OPL-1 |
| Odoo series | 19.0: published on the Odoo Apps Store; 20.0: published on the Odoo Apps Store |
| Version | 1.1.0 |
| Edition | Odoo Community / on-premise |
| Technical name | marches_publics |
| Domain | Municipalities and public sector |
Price excluding VAT as displayed on the Odoo Apps Store; purchase and installation are done on the Store or through your Omnifloo instance.