Os detalhes do produto são exibidos em inglês. Traduções em breve.
Fatos rápidos
- Preço
- $249.00 USD
- Versões Odoo
- 17, 18, 19
- Tempo de configuração
- 30 min
- Licença
- Uma vez perpétua
- Idiomas
- 11 idiomas
Compra Única
Lead Enrichment & Data Append
A self-hosted Odoo module that enriches CRM leads with company, firmographic and social profile data derived from the email domain — with no per-credit Odoo IAP cost. ECOSIRE builds it to your provider stack, installs it, and supports it after you request a quotation.
$249.00USD
Sem pagamento agora. Isto envia um pedido de orçamento à nossa equipe — responderemos por e-mail com preços e próximos passos.
Recursos Principais
Extends `crm.lead` with a firmographic field set (legal name, employee band, industry, HQ country/city, revenue band, tech hints) via a clean `models.Model` inheritance layer, no core patching
`@api.depends('email_from')` compute derives the email domain and re-triggers enrichment candidates when the address changes, while append fields stay manually editable
`ir.cron` scheduled action auto-enriches newly created leads in configurable batch sizes with rate-limit throttling and exponential back-off
Post-commit execution so the lead saves instantly and the salesperson never waits on a third-party API round-trip
Pluggable provider architecture: an abstract adapter interface with one concrete implementation per source (REST vendor, WHOIS/domain, internal CSV/MMDB, or your existing data contract)
Per-domain response caching so 40 contacts at one company consume a single lookup, cutting API cost and honoring vendor rate limits
Manual per-record server action on the lead form for on-demand enrichment plus a bulk list-view action to re-enrich historical leads without re-import
Companion audit model logs every enrichment attempt (provider, timestamp, status, raw payload hash) for traceability and safe re-runs
Access controlled by `ir.model.access.csv` and record rules so enriched fields respect existing CRM team/salesperson visibility
Social profile append (LinkedIn, X, Facebook company URLs) stored as validated URL fields for click-through from the lead form
Configurable field-mapping settings (via `res.config.settings`) so you decide which provider attributes write to which Odoo fields and whether to overwrite or fill-only
Enriched attributes are queryable over XML-RPC/JSON-RPC for external sync and available to QWeb reports, pivot views, and kanban grouping
No Odoo IAP credits and no Enterprise-only dependency — runs identically on Community and Enterprise, fully self-hosted
Graceful degradation: partial data is written when a provider returns incomplete results, and failed lookups are flagged for retry rather than silently dropped
Sobre este Produto
Sales teams lose hours retyping company names, sizes, industries and LinkedIn URLs that a lead's email domain already implies. Odoo's native crm.lead captures whatever the web form or import gives you and stops there — the built-in "Enrich Company" and "Autocomplete" features route through Odoo IAP, which bills per credit, locks the data source to Odoo's partner, and leaves nothing in your control when credits run dry. For a high-volume B2B pipeline that quickly becomes an unpredictable line item, and it can't be pointed at the enrichment provider you already pay for. That is exactly the gap this build-to-order module fills.
Por Que Escolher Lead Enrichment & Data Append
Extends `crm.lead` with a firmographic field set (legal name, employee band, industry, HQ country/city, revenue band, tech hints) via a clean `models.Model` inheritance layer, no core patching
`@api.depends('email_from')` compute derives the email domain and re-triggers enrichment candidates when the address changes, while append fields stay manually editable
`ir.cron` scheduled action auto-enriches newly created leads in configurable batch sizes with rate-limit throttling and exponential back-off
Post-commit execution so the lead saves instantly and the salesperson never waits on a third-party API round-trip
Pluggable provider architecture: an abstract adapter interface with one concrete implementation per source (REST vendor, WHOIS/domain, internal CSV/MMDB, or your existing data contract)
Per-domain response caching so 40 contacts at one company consume a single lookup, cutting API cost and honoring vendor rate limits
ECOSIRE builds a self-hosted enrichment engine that extends crm.lead (and optionally res.partner) with a structured firmographic layer: parsed email domain, legal company name, employee-count band, industry/NAICS-style classification, HQ country and city, revenue band, technology hints, and social handles (LinkedIn, X, Facebook). New fields are declared on a proper models.Model inheritance layer with @api.depends('email_from') compute triggers so a domain change re-derives what it can, while append-only fields stay editable. Every write is scoped by ir.model.access.csv plus record rules so enriched data respects your existing CRM visibility, and all enrichment activity is logged to a companion model for audit and re-run.
Technically, the append logic is provider-pluggable. We implement a thin adapter interface — a Python abstract layer with one concrete adapter per source (Clearbit-style REST, self-hosted domain-WHOIS, your existing data vendor, or an internal MMDB/CSV) — so you are never welded to one vendor's pricing. An ir.cron automated action sweeps freshly created leads on a schedule and enriches them in batches with rate-limit and back-off handling; a manual server action lets a rep enrich one record on demand from the form view; and a bulk action on the list view re-enriches historical leads without re-importing. Calls are resilient by design: cached per domain (so 40 leads at acme.com cost one lookup), retried on transient failure, and never block the salesperson — enrichment runs post-commit, so the lead saves instantly and fills in seconds later.
Because it exposes clean fields on crm.lead, everything downstream just works: filter and group your pipeline kanban by employee band or industry, drive routing/assignment rules off firmographics, feed QWeb reports and Odoo dashboards, and query the enriched attributes over the standard XML-RPC/JSON-RPC API for your data warehouse. It targets Odoo 17.0, 18.0 and 19.0 and works on both Community and Enterprise — no Enterprise-only dependency, and no reliance on the paid IAP autocomplete.
Delivery is build-to-order: nothing here is an instant apps.odoo.com download. After a short scoping call we confirm your Odoo version, edition, hosting, and which enrichment provider(s) you want wired in, then build against that exact target. Typical delivery is 2–4 weeks from confirmed scope. You get the installable source, UAT on a staging copy of your database, a documented rollback path, and a post-go-live support window — and you own the Git repository at handover.
O que você ganha
- Installable Odoo module source (full `__manifest__.py`, models, views, security, cron and adapter code) built for your exact Odoo 17.0/18.0/19.0 version and edition
- Installation and configuration on your environment, including provider credentials, cron cadence, and field-mapping setup
- Technical documentation covering the data model, adapter interface, and how to add a new enrichment provider later
- End-user guide plus a live training session for your sales/ops team on manual, bulk, and automatic enrichment
- UAT on a staging copy of your database with a documented, tested rollback plan before production go-live
- Post-go-live support window for defect fixes and configuration adjustments
- Handover of the complete Git repository with commit history so you own and can extend the code
- Data-mapping worksheet documenting exactly which provider fields populate which `crm.lead` fields and the overwrite/fill-only rules agreed during scoping
Para quem é isso
B2B Sales Operations Lead
Runs pipeline hygiene for a high-volume inbound team and is tired of unpredictable Odoo IAP credit bills. Wants clean firmographics on every lead so routing, scoring and territory rules fire automatically — without a per-lookup meter running.
CRM / Odoo Administrator
Owns the Odoo instance and needs enrichment that installs cleanly, respects `ir.model.access.csv` and record rules, and can be pointed at a provider the company already contracts. Values the pluggable adapter so vendor changes don't mean a rebuild.
Demand Generation / Marketing Manager
Imports lists and captures web-form leads that arrive with little more than an email. Needs employee band, industry and social profiles appended so segmentation, nurture routing and lookalike targeting actually work inside Odoo.
Revenue Operations / Data Analyst
Pulls CRM data into a warehouse over XML-RPC/JSON-RPC and needs consistent, structured firmographic attributes on `crm.lead` — plus an audit log of what was enriched, by which provider, and when.
Visão geral da instalação
Baixe do ECOSIRE
Compre a licença em ecosire.com e baixe o ZIP do módulo Lead Enrichment & Data Append no painel da sua conta.
Carregar para Odoo
Extraia o ZIP em sua pasta de complementos personalizados do Odoo no servidor (ou faça upload via Aplicativos > Instalar do arquivo em Odoo.sh/runbot).
Instale o módulo
Ative o modo de desenvolvedor, abra Aplicativos, clique em Atualizar lista de aplicativos, procure por Lead Enrichment & Data Append e pressione Instalar.
Definir configurações
Abra o novo menu, cole sua chave de licença ECOSIRE, conecte quaisquer credenciais externas (Shopify, Amazon, Stripe, etc.) e salve.
Verifique e entre no ar
Execute o teste de conexão integrado, sincronize seus primeiros 10 registros e agende o cron recorrente. Entre em contato com o suporte se algo falhar.
Como Lead Enrichment & Data Append se compara
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| Cost model | One-time build; you pay your provider directly, no Odoo per-credit fee | Unpredictable dev cost; still need a data source | Often subscription plus data credits on top | |
| Provider flexibility | Pluggable adapter — swap or add vendors without a rebuild | Whatever the developer hard-codes | Usually tied to the vendor's own API | |
| Auto-enrich on creation | `ir.cron` batch sweep plus post-commit, throttled and cached | Possible but you design the batching yourself | Varies; often manual-only or partial | |
| Bulk historical enrichment | List-view bulk action, no re-import, audit-logged | Extra scope to build | Sometimes, often extra tier | |
| Data ownership & hosting | Self-hosted, you own the Git repo and the data | You own it, if it's documented | Data flows through vendor cloud | |
| Security model | `ir.model.access.csv` + record rules, scoped to your CRM visibility | Depends on developer discipline | Generic, may over-expose fields | |
| Odoo version support | Built for your exact 17.0 / 18.0 / 19.0, Community or Enterprise | Whatever is scoped | Depends on listing maintenance | |
| Support & upgrades | Post-go-live window + optional version-upgrade path | Ad hoc, depends on the developer's availability | Vendor support tiers, variable |
Perguntas frequentes sobre Lead Enrichment & Data Append
+How long does delivery take?
This is a build-to-order module, not an instant download. Typical delivery is 2–4 weeks from confirmed scope — the exact timeline depends on your Odoo version/edition, how many enrichment providers you want wired in, and any custom field mapping. We confirm dates in writing after the scoping call.
+Do I still need Odoo IAP credits?
No. The whole point is to avoid per-credit IAP billing. The module is self-hosted and calls the enrichment provider(s) you choose under your own contract, or a domain/WHOIS-based source that has no per-lookup fee. You control the data source and the cost model.
+Which enrichment providers can it use?
The engine is built around a pluggable adapter interface, so we can wire in a REST vendor (Clearbit-style), a WHOIS/domain source, an internal CSV/MMDB dataset, or your existing data contract. We confirm the provider(s) during scoping and can add more later without rebuilding the module.
+How does support and updates work after go-live?
Every build ships with a post-go-live support window for defect fixes and configuration tweaks. Because you receive the full Git repository, you can extend it yourself, or engage ECOSIRE for version upgrades (for example 18.0 → 19.0) and new provider adapters as a follow-on.
+Does it work on Odoo Community, or only Enterprise?
Both. It targets Odoo 17.0, 18.0 and 19.0 and has no Enterprise-only dependency and no reliance on the paid IAP autocomplete — it runs identically on Community and Enterprise, fully self-hosted.
+Will auto-enrichment slow down the sales team?
No. Enrichment runs on an `ir.cron` sweep and post-commit for new leads, so records save instantly and fill in seconds later. Per-domain caching means many contacts at the same company cost a single lookup, and failed calls are flagged for retry rather than blocking a save.
+Can I enrich the leads already sitting in my database?
Yes. Alongside auto-enrichment on creation, we ship a bulk list-view action so you can select and re-enrich historical leads in batches — no re-import required. The audit log records every attempt so re-runs are safe and traceable.
Módulos Relacionados
Solicitar orçamento
Lead Enrichment & Data Append
A self-hosted Odoo module that enriches CRM leads with company, firmographic and social profile data derived from the email domain — with no per-credit Odoo IAP cost. ECOSIRE builds it to your provider stack, installs it, and supports it after you request a quotation.
- Extends `crm.lead` with a firmographic field set (legal name, employee band, industry, HQ country/city, revenue band, tech hints) via a clean `models.Model` inheritance layer, no core patching
- `@api.depends('email_from')` compute derives the email domain and re-triggers enrichment candidates when the address changes, while append fields stay manually editable
- `ir.cron` scheduled action auto-enriches newly created leads in configurable batch sizes with rate-limit throttling and exponential back-off
- Post-commit execution so the lead saves instantly and the salesperson never waits on a third-party API round-trip