Connecting Sales and Field Operations: Odoo × Bitrix24 API Integration

How a two-way integration turned a won deal into a fully tracked survey, sales order, installation and support lifecycle, with no re-keying between systems.

Choice2mobile Technology Ltd provides residential and business internet across Lagos. Its sales team works in Bitrix24, while surveys, sales orders, installations and customer support run in Odoo. Every customer passes through both systems: a lead is won in Bitrix24, then an engineer surveys the site, finance approves the order and collects payment, a field team installs the service, and the support desk looks after the customer afterwards.

Get In Touch

Odoo and Bitrix24 two-way API integration for telecom operations

Project Snapshot

Project Overview: At a Glance

Operational Challenges

The Operational Challenge & Bottlenecks

Before the integration, the hand-off between sales and operations depended on people copying information from one system into the other. That created several recurring problems:

Manual re-entry

Every won lead had to be retyped into Odoo as a survey ticket, and again later as a sales order and installation job.

No shared view of progress

Sales staff in Bitrix24 could not see whether a survey had been done, an order approved, or an installation finished without asking the operations team.

Payment blind spots

Confirmation that a customer had paid lived in Odoo, so sales could not reliably follow up or close the loop with the customer.

Disconnected support

Support requests logged against a customer in Bitrix24 had to be recreated in Odoo before engineers could act on them.

Architectural Integration

The Integration Solution: Bidirectional API Sync

OCE built a set of REST API endpoints in Odoo and a matching push mechanism back to Bitrix24. Bitrix24 calls Odoo when a commercial event happens (a lead is won, an order is requested, a support case is opened, an installation is closed). Odoo pushes status back to Bitrix24 whenever a ticket changes stage, a survey completes, or a payment is recorded. The integration covers four connected workflows, shown below.

Workflow	Started by	Odoo → Bitrix24	Bitrix24 → Odoo
Survey Ticket	Lead marked Won in Bitrix24	Stage updates; survey completion status	Create survey ticket
Sales Order	Bitrix24 create-order API call	Approval and payment information	Create sales order linked to the survey ticket
Installation Ticket	Odoo, after order approval and payment	Draft ticket details; stage updates	Close ticket
Support Ticket	Support ticket raised in Bitrix24	Stage updates; resolution status	Create support ticket

Core Architecture Principle

Design principle: one source of truth per stage

Bitrix24 owns the customer relationship and the commercial decision. Odoo owns survey, approval, payment, installation and support execution. Records in both systems are linked by reference, so a sales order always points back to the survey ticket it came from, and an installation ticket always points back to its sales order.

Production Dashboard Viewports

Automated Workflows in Action

Live screenshots from Odoo ERP showing automated ticket creation, line items, assignment groups, SLA targets, and complete stage audit trails.

Workflow 1: Survey Ticket

The customer journey begins the moment a sales representative wins a lead in Bitrix24.

Lead won triggers ticket creation

When a lead is marked Won in Bitrix24, it calls the Odoo API and a new survey ticket is created automatically, already assigned to the right engineering group for the area.

Stage changes flow back to Bitrix24

As the ticket moves through Draft, Open, Work In Progress, Completed, Finalized and Closed in Odoo, each stage change is pushed to Bitrix24.

Survey result is pushed on completion

When the survey is done, Odoo calls the push API and sends the completion status to Bitrix24, so the sales team knows the site is ready to quote.

Workflow 2: Sales Order

Once the survey confirms the site, the commercial order is raised from Bitrix24 and executed in Odoo.

Bitrix24 creates the order in Odoo

Bitrix24 calls the create-sales-order API, and Odoo creates the sales order with a direct reference to the original survey ticket and opportunity.

Approval and payment are pushed back

When the order is approved and payment is recorded in Odoo, Odoo calls the push API and sends the payment information to Bitrix24.

Workflow 3: Installation Ticket

Payment unlocks installation. No one needs to remember to schedule the job.

Draft installation ticket is created automatically

When the sales order is approved and paid, Odoo creates a draft installation ticket and pushes its details to Bitrix24.

Stage changes stay in sync

As the field team moves the ticket through its stages in Odoo, every update is reflected in Bitrix24.

Closing in Bitrix24 closes it in Odoo

When the installation is confirmed and closed in Bitrix24, it calls the close API and the matching ticket in Odoo is closed too.

Workflow 4: Support Ticket

After go-live, customer support follows the same connected pattern.

Support case in Bitrix24 creates an Odoo ticket

When a support ticket is created in Bitrix24, it calls the Odoo API and a support ticket is created with the customer, product and service area filled in.

Stage updates flow back

Each stage change in Odoo is pushed to Bitrix24 so account owners can see progress.

Resolution is pushed on completion

When the support work is done, Odoo calls the push API and sends the final status to Bitrix24.

Connected Pipeline

The Complete End-to-End Operational Lifecycle

Together, the four workflows form one continuous chain from first sale to ongoing support:

Lead won in Bitrix24

Survey ticket created in Odoo

Survey completed in Odoo

Status pushed to Bitrix24; sales team can quote

Order requested from Bitrix24

Sales order created in Odoo, linked to the survey

Order approved and paid in Odoo

Payment pushed to Bitrix24; draft installation ticket created and pushed

Installation progresses in Odoo

Stage updates mirrored in Bitrix24

Installation closed in Bitrix24

Ticket closed in Odoo

Support case raised in Bitrix24

Support ticket created in Odoo; progress and resolution pushed back

Outcomes

Key Business Results & Outcomes

No duplicate data entry

Survey tickets, sales orders, installation tickets and support tickets are created through the API instead of being retyped.

Real-time visibility for sales

Sales staff see survey, payment, installation and support status inside Bitrix24 without switching systems or chasing colleagues.

Payment-driven installation

Installation work starts only once an order is approved and paid, and it starts automatically.

Full traceability

Every record links back to the one before it, and every stage change is logged in Odoo’s chatter, giving a complete audit trail per customer.

Clear ownership

Each team keeps working in the system built for its job, while both systems stay consistent.

Architecture & Stack

Integration Technology & Platform Roles

Bitrix24

Role: CRM: leads, deals, customer communication, installation confirmation

Odoo

Role: ERP: survey, sales, approvals, invoicing and payment, helpdesk and field tickets

Odoo REST API Endpoints

Role: Inbound calls from Bitrix24: create survey ticket, create sales order, create support ticket, close ticket

Push API to Bitrix24

Role: Outbound updates from Odoo: stage changes, survey and support completion, payment, draft installation ticket

Matters - Documents & Activity

Understanding ReactJS

Connecting Sales and Field Operations: Odoo × Bitrix24 API Integration

Project Overview: At a Glance

Client

Industry

Region

Platforms

Scope

Delivered By