Prozorro Connector

What it does

Ukrainian businesses participating in public procurement read the Prozorro feed manually every morning, copy interesting tender numbers into a spreadsheet, and lose hours every week. Prozorro Connector moves that workflow into Odoo: define your subscription once (CPV codes, keywords, region, value range, status), and the cron pulls the public feed hourly, persists only matches, emails an alert, and optionally creates a CRM lead per match.

Odoo 19 LGPL-3 Free No external dependencies Community & Enterprise

Key features

1 Subscription rules with five filter dimensions

Each subscription combines CPV codes (DK021:2015), one or more keywords (contains, regex, or negate), regions (mapped to Ukrainian oblasts and cities of special status), a value range, target statuses (active.tendering, complete, cancelled, etc.), and selected procurement methods. A tender matches only when every active filter on the subscription accepts it.

A built-in form-view warning fires if a subscription has neither CPV codes nor keywords - so a misconfigured subscription that would match the entire feed never goes live by accident.

2 Filter-at-sync: only matched tenders persist

The cron walks the Prozorro feed page by page (default 20 pages per run, configurable). For each tender, the matcher evaluates every active subscription. Only tenders that match at least one subscription are stored - the rest are dropped immediately, so the database stays small even on a busy feed.

A daily retention cron drops matched tenders 60 days after their tender_period_end unless they were converted to a CRM lead. The retention window is configurable from Settings.

3 Settings page: schedule, live status, force stop

One screen controls everything: sync schedule (off by default, configurable to any cron interval), API endpoint, pages per run, retention days, and whether to auto-create CRM leads from matches.

A live status block shows whether a sync is currently running, the timestamp of the last successful run, and the last error message if any. A Manager-only Force stop button appears only if a sync has been "running" for more than 60 minutes - clearing stale flags without an Odoo restart.

4 Test wizard: paste a UUID, get a per-filter verdict

Want to know whether your subscription would match a specific tender? Open the tender on prozorro.gov.ua, copy its UUID, paste it into the Test wizard. The wizard fetches the live tender from the API and prints a per-filter verdict: which filters accepted it, which rejected it, and the final overall match. No more guessing whether your CPV list was too narrow or your keyword regex was too strict.

5 CRM leads created automatically (with audit trail)

Per-subscription opt-in: enable Auto-create CRM lead and every match for that subscription becomes a crm.lead linked back to the source tender. Leads are always created with type='lead' (never Opportunity) so they go through your normal manual triage. The lead's chatter shows the originating subscription and the tender UUID for traceability.

6 Email alert per match with deep-link

On every successful sync that produces at least one match, the subscribed users receive a per-tender alert email with a teal NEW MATCH badge, the tender header (name, value, deadline), the tender items collapsed inside a <details> block so the inbox preview stays clean, and a one-click "View in Odoo" button deep-linking into the tender form.

Technical details

• Targets: Odoo 19 Community and Enterprise. The module depends only on base, mail, and crm.
• License: LGPL-3, free.
• Security: all menus and operational records restricted to base.group_user; settings and force-stop restricted to base.group_system. No public HTTP endpoints exposed by this module.
• HTTP client: Python stdlib urllib.request only. No requests dependency, no third-party HTTP library required at install time.
• Storage: seven new tables (subscription, keyword, tender, classification, region, procurement method, status, sync cursor) - all small, all retention-bounded.
• Cron resilience: stale `is_running` self-heal after 60 min, postcommit-deferred reschedule writes (no `lock_for_update` UserError), isolated chatter cursor (cron rollback never erases the audit trail).
• Test coverage: 20 unit and integration tests covering subscription matching, feed sync with mocked HTTP, lead-creation gating, and cursor lifecycle.

Support

Source code, issues, and feature requests: github.com/RteamAgency/rteam-prozorro

Built and maintained by Rteam, an Odoo Enterprise consulting agency. rteam.agency