A build-to-order Odoo module that turns photographed or scanned business cards into structured CRM leads and contacts using AI text recognition. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17, 18, or 19. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $299.00 USD; request a quote for a scoped proposal.

A build-to-order Odoo module that turns photographed or scanned business cards into structured CRM leads and contacts using AI text recognition. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17, 18, or 19.
Şimdi ödeme yok. Bu, ekibimize bir teklif talebi gönderir — fiyat ve sonraki adımlarla e-posta ile dönüş yapacağız.
Sales teams that run Odoo still collect leads the analog way: a stack of business cards from an expo booth, a folder of card photos on a rep's phone, a WhatsApp thread of snapshots after a conference. Someone then keys each one into crm.lead or res.partner by hand — misspelling company names, dropping VAT numbers, and letting warm contacts go cold while they sit in a data-entry backlog. Odoo core has no card-to-contact capability at all: there is no OCR pipeline, no image-to-field mapping, and the standard lead form assumes a human is typing. Even the closest off-the-shelf apps.odoo.com module tends to ship a fixed field map and a single OCR engine you cannot swap, which rarely matches a specific country's card conventions or a team's existing lead-qualification workflow.
Mobile-friendly OWL capture widget plus a QWeb upload action that stores each card image as an `ir.attachment` on a dedicated `card.scan` record
AI text-region detection and field classification into name, title, company, phone, mobile, email, website, and structured postal address
`@api.depends` compute + normalization layer that maps raw extraction onto native `res.partner` and `crm.lead` fields (phone/email format, country, state)
Automatic company resolution: creates or links the parent `res.partner` company and attaches the person as a child contact
De-duplication against existing partners and leads by email and normalized phone before any new record is written
Confidence scoring per field, with low-confidence values held for one-click human review instead of silent writes
ECOSIRE builds a made-to-order module that closes that gap end to end. We add a capture surface — a mobile-friendly OWL widget and a QWeb-rendered upload action — so a rep photographs a card and the image lands as an ir.attachment on a new record. A dedicated model (for example card.scan, extending models.Model) then calls an AI recognition service to detect the card's text regions and classify them into name, job title, company, phone, mobile, email, website, and postal address. A set of @api.depends compute methods and normalization rules map the raw extraction onto real Odoo fields, resolve or create the res.partner company, de-duplicate against existing partners by email and phone, and spin up a crm.lead (or a contact under an existing company) with the source, medium, and campaign already stamped. Low-confidence fields are flagged for a one-click human review rather than written silently, so the data your reps trust is data a person confirmed.
Everything is engineered to your instance, not bolted on. Access is governed by ir.model.access.csv plus record rules so a rep only sees their own scans while managers see the team's; automated actions (base.automation) can route a freshly created lead to the right salesperson, tag it, or trigger a follow-up activity. The module ships as a proper addon with its own __manifest__.py, versioned views, and demo data, and it exposes its create-lead path over Odoo's XML-RPC/JSON-RPC API so an existing badge scanner, event app, or kiosk can push cards in without touching the UI. We build against Community or Enterprise as your edition requires — calling out any Enterprise-only dependency up front — and target whichever of Odoo 17.0, 18.0, or 19.0 you run.
Delivery is build-to-order. After a short scoping call we confirm the exact field map, the recognition provider and language coverage, your de-duplication rules, and which teams and pipelines the leads flow into, then send a fixed quotation. Typical delivery is 2 to 4 weeks from confirmed scope, and you receive the module on a staging instance for UAT before it ever touches production. Pricing starts from $299 (indicative, single-company base scope); multi-company routing, additional card languages or scripts, integrations with an external event/badge system, and bulk migration of an existing backlog of card images all increase the quoted scope.
Reps who collect dozens of cards at expos and conferences and need each one to become a routed, deduplicated CRM lead the same day instead of a data-entry backlog.
Owners of pipeline hygiene who need consistent source/campaign tagging, no duplicate partners, and a report tying scanned cards to converted leads for event ROI.
The people responsible for the instance who want a clean addon with proper access rules, an integration path for existing badge hardware, and a supported upgrade across 17/18/19.
Teams running the event calendar who want captured contacts to land with the right medium and campaign so follow-up automation and attribution actually work.
Lisansı ecosire.com adresinden satın alın ve hesap kontrol panelinizden AI Business Card Reader for Odoo modülünün ZIP dosyasını indirin.
ZIP'i sunucudaki Odoo özel eklentiler klasörünüze çıkarın (veya Uygulamalar > Odoo.sh / runbot'taki dosyadan yükle yoluyla yükleyin).
Geliştirici Modunu etkinleştirin, Uygulamalar'ı açın, Uygulama Listesini Güncelle'ye tıklayın, AI Business Card Reader for Odoo'i arayın ve Yükle'ye basın.
Yeni menüyü açın, ECOSIRE lisans anahtarınızı yapıştırın, tüm harici kimlik bilgilerini (Shopify, Amazon, Stripe vb.) bağlayın ve kaydedin.
Yerleşik bağlantı testini çalıştırın, ilk 10 kaydınızı senkronize edin ve yinelenen cronu planlayın. Herhangi bir sorun olursa desteğe başvurun.
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| Card image to CRM lead | Full pipeline: capture, AI extract, dedupe, create lead | Possible but you build every stage yourself | Often fixed field map and one OCR engine | |
| Field mapping & normalization | Scoped to your fields, phone/country normalized via compute | Whatever your team codes and maintains | Generic map, limited configurability | |
| De-duplication | By email + normalized phone before write | Must design and test the matching logic | Basic or absent | |
| Recognition engine choice | Pluggable; cloud or self-hosted for data residency | Your integration and upkeep | Usually locked to the vendor's engine | |
| Access control | `ir.model.access.csv` + record rules per role | You define and audit the rules | Depends on the module | |
| External integration | XML-RPC/JSON-RPC endpoint for badge scanners/kiosks | Build the API surface yourself | Rarely exposed | |
| Support & ownership | Post-go-live window + full git repo handover | Self-supported unless you hire out | Vendor support tier, code often closed | |
| Odoo 17/18/19 fit | Built and tested for your exact version and edition | You port and re-test each upgrade | May lag new releases |
No. It is a build-to-order module. ECOSIRE builds it for your specific Odoo instance and field map after a scoping call, then installs and supports it. It is not an existing apps.odoo.com download.
Typical delivery is 2 to 4 weeks from confirmed scope. The timeline depends on the field map, number of card languages, de-duplication rules, and any external integrations agreed during scoping. You get a firm date with your fixed quotation.
Pricing starts from $299 as an indicative single-company base-scope figure. After a short scoping call we confirm exact requirements and send a fixed quotation. Drivers like multi-company routing, extra languages, badge-scanner integration, or migrating a backlog of card images increase the quoted scope.
We build for Odoo 17.0, 18.0, or 19.0, on Community or Enterprise. If any part of the scope depends on an Enterprise-only feature, we flag it before you commit so there are no surprises.
Every build includes a post-go-live support window for defect fixes and configuration adjustments, plus full git repo handover so you own the code. Version upgrades and enhancements beyond that window are quoted as a separate maintenance scope.
The recognition provider is a scoping decision. We can wire a cloud AI service or a self-hosted/on-prem engine depending on your data-residency needs, and card images are stored as standard Odoo attachments governed by your access rules and record rules.
Yes. The module exposes its create-lead path over Odoo's XML-RPC/JSON-RPC API, so an external badge scanner, kiosk, or event app can push cards straight into CRM without anyone using the Odoo UI. That integration is part of the scoped build.

A build-to-order 2Checkout (Verifone) payment integration for ERPNext, giving global digital-goods sellers card acceptance, 45+ local payment methods, multi-currency checkout, and reconciled invoices. ECOSIRE scopes, builds, installs, and supports it on your ERPNext v15/v16 instance.

A build-to-order 2Checkout / Verifone payment gateway for Magento 2 and Adobe Commerce: localized checkout in 12 languages, iDEAL, Giropay and regional methods, multi-currency global selling, subscription billing and tax/invoicing automation — engineered, installed and supported by ECOSIRE.

A build-to-order ERPNext application for anonymous 360-degree reviews — configurable peer, manager, report and self rater groups, weighted competency scoring, and aggregated gap-analysis and heatmap reports. ECOSIRE scopes, builds, installs and supports it on your Frappe/ERPNext v15/v16 instance.
A build-to-order Odoo module that turns photographed or scanned business cards into structured CRM leads and contacts using AI text recognition. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17, 18, or 19.