1С/BAS ↔ Odoo integration

Confirmed sales orders and counterparties from Odoo become documents in 1С/BAS, and payments, shipments and stock from 1С/BAS come back to Odoo

Sales, CRM and the pipeline live in Odoo, while accounting, tax reporting and the warehouse stay in 1С/BAS because the accountant works there. Between the two, a person re-types every confirmed order and every new client, and salespeople ask the accountant whether the client has paid. The 1С/BAS ↔ Odoo pair makes each confirmed sales order in Odoo a customer order in 1С/BAS with the right counterparty, and brings payments, shipments and stock balances from 1С/BAS back to Odoo, so the salesperson sees the state of the deal without asking. Below: what exactly moves, which scenarios we cover and which capabilities of both systems we rely on.

Request an integration System page: 1С/BAS →System page: Odoo →

What moves between the systems

Odoo → 1С/BASA sales order confirmed in Odoo becomes a customer order in 1С/BAS with the same lines, quantities and prices, and the document number is written back to the Odoo order.
Odoo → 1С/BASA new company or contact in Odoo is created in 1С/BAS as a counterparty with its tax code, address and bank details, or matched to an existing one by tax code.
1С/BAS → OdooPayments received in 1С/BAS are written to the Odoo order and invoice as paid, with the date and amount, so the salesperson sees it in the pipeline.
1С/BAS → OdooShipments made in 1С/BAS mark the Odoo order delivered with the date and the carrier's tracking number.
1С/BAS → OdooStock balances and the chosen price type from 1С/BAS are written to Odoo products on a schedule, so quotes are built from real stock and current prices.
1С/BAS → OdooOverdue receivables from 1С/BAS appear on the client card in Odoo, so the salesperson knows before calling that the previous invoice is unpaid.

What we connect

We agree on who owns what: products, prices and stock in 1С/BAS; clients, pipeline and orders in Odoo; payments and shipments in 1С/BAS. Each field has exactly one master.
We check the Odoo edition and plan: outside access must be included, and a cloud account needs a locally set password or an access key for the exchange user.
In Odoo the administrator creates a separate user for the exchange with an access key and rights only to sales, contacts and products; the key can be revoked at any time.
On the 1С/BAS side we use the open exchange interface the platform builds itself, under a separate user with rights to read balances and payments and to create orders and counterparties.
We map the catalogues and statuses: which Odoo product is which 1С/BAS item, which Odoo order stage starts the transfer, and which 1С/BAS events mean «paid» and «delivered» in Odoo.
We test on copies of both bases with a dozen orders and clients, compare with the accountant, and only then switch the exchange to the live systems.

Automation scenarios

Orders typed twice

Before the salesperson confirms the order in Odoo, then the operator types it into 1С/BAS, and once a week a line is missed.

After the confirmed order appears in 1С/BAS within minutes with the same lines, and Odoo shows the 1С/BAS document number.

«Has the client paid?»

Before salespeople message the accountant several times a day to ask about payments.

After the payment from 1С/BAS marks the Odoo order paid within minutes, and the salesperson sees it in the pipeline.

Quote built from stale stock

Before the salesperson promises delivery from stock that was sold yesterday, because Odoo shows last week's numbers.

After balances from 1С/BAS are written to Odoo products on a schedule, and the quote is built from what is really on the shelf.

Two cards for one client

Before the client exists in Odoo under one name and in 1С/BAS under another, and reconciliation at month end takes a day.

After counterparties are matched by tax code, a new client is created once, and both systems refer to the same record.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

The official BAS support portal documents its integration technologies under the title «Технології інтеграції 1С:Підприємства 8.3» — BAS is built on the 1C:Enterprise 8.3 platform.
Source: its.bas-soft.eu ↗ checked 2026-09-25
According to the same documentation, the platform automatically builds a REST interface using the OData protocol, through which outside systems can read, change, create and delete data over HTTP.
Source: its.bas-soft.eu ↗ checked 2026-09-25
Almost all Odoo data and features are reachable from outside for connecting or analysis; part of that is available over XML-RPC from a variety of programming languages.
Source: www.odoo.com ↗ checked 2026-09-25
Outside data access is only available on custom-priced plans — it isn't available on the entry-level single-app plan or on the standard plan.
Source: www.odoo.com ↗ checked 2026-09-25
Cloud (Odoo Online) accounts need a locally set password to use the outside connection, since a regular sign-in through Odoo Online's own authentication doesn't work for it.
Source: www.odoo.com ↗ checked 2026-09-25
Since version 14.0, Odoo supports access keys that can replace a password in scripts, while the account's regular sign-in stays the same.
Source: www.odoo.com ↗ checked 2026-09-25

Limits

The limits come from both systems. Odoo does not push events by itself in this setup: the exchange reads new and changed orders on a schedule of minutes, not instantly. Outside access is not included in every Odoo plan, and a cloud account needs a locally set password or an access key; we check this before anything else. Each field has one master, so a price changed by hand in Odoo is overwritten from 1С/BAS on the next pass. 1С/BAS is on the official prohibited software list: we do not take projects for state bodies, critical infrastructure or systems with state data, and with private businesses we discuss the risk openly.

How to start

Three steps from a first message to work on your project.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

Why keep 1С/BAS at all if Odoo has accounting?

Because the accountant, the tax reporting and the auditor's habits are there, and moving them is a separate project with its own risk. The pair lets sales work in Odoo today without touching the accounting; if you later move accounting to Odoo, the exchange is simply switched off.

Our Odoo is self-hosted, not the cloud version. Does it matter?

It makes things simpler: outside access is there, and no plan check is needed. We only need the exchange user with an access key and a network route from our side to your server.

What if the salesperson changes the order after it went to 1С/BAS?

Changes to an order that is not yet shipped are carried to the 1С/BAS document on the next pass. Once the order is shipped in 1С/BAS, it is locked on the Odoo side and further changes go through a new order or a return; we agree this rule at the mapping step.