Можно ли купить готовый коннектор Odoo-1С?

Готовый модуль может ускорить техническое подключение, но его проверяют на версиях систем, моделях данных и бизнес-процессе. Сопоставление статусов, налогов и документов требует настройки.

Какая система должна хранить номенклатуру?

Та, где каталог управляется как основной процесс. Это может быть Odoo, 1С или отдельная PIM; остальные системы получают согласованную копию.

Нужно ли синхронизировать всё в обе стороны?

Нет. Двусторонний обмен нужен там, где обе системы создают значимые события. Для большинства полей безопаснее один владелец и одностороннее распространение.

Можно ли связать системы напрямую через API?

Да. При небольшом числе потоков прямой адаптер может быть достаточен. При сложной логике отдельный интеграционный слой упрощает преобразования, повторы и наблюдаемость.

Как начать оценку проекта?

Выбрать один сквозной процесс и предоставить примеры объектов из обеих систем: карточки, заказы, товары, остатки, оплаты и статусы.

Odoo and 1C: Integrating Orders, Stock, and Accounting

Exchange map

One entity—one owner; confirmed statuses flow back

Odoo and 1C can own different parts of the process when owners, keys, events and failure-recovery rules are defined for master data and documents.

01

Odoo

CRM, quotes, orders and operational statuses within the agreed scope.

02

1C

Statutory accounting, documents, settlements and period closing for a CIS legal entity.

03

Integration

Key mapping, data transformation, delivery, retries and error logging.

04

Control

Reconcile amounts, taxes, lines, stock and payments using control examples.

The two systems do not modify the same object independently.
Repeating a message does not create a duplicate.
A partial shipment does not close the entire order.
Exchange errors are visible to the responsible person instead of remaining in a technical log.

Why companies connect Odoo and 1C

An international group may use Odoo for CRM, sales, procurement, warehousing and order management, while its CIS legal entity uses 1C for statutory accounting. The parent company still needs a unified view of orders, operations and payments.

Without integration, employees recreate business partners, item masters and documents, share payment statuses in chats and reconcile stock manually. Errors are discovered during shipment or month-end closing. The goal of data exchange is to eliminate duplicate entry and give each role a clear, verified data source. For companies with legal entities in the UAE, it is also important preparing Odoo and 1C for mandatory e-invoicing.

Do not start with the API

Odoo provides an external API for working with models and data. The 1C platform supports HTTP and web services, OData, JSON, XML, exchange plans and scheduled jobs. The technical options are sufficient; the complexity lies in the meaning of the operations.

Before choosing the transport, agree when an order is considered confirmed, which event reduces available stock, which date becomes the sales date, how currencies and units of measure are mapped, whether a posted document can be changed, and what happens during a return or partial shipment. Otherwise, the connector will quickly transfer the conflict between systems.

Assign an owner to each object

Object	Possible owner	What the second system receives
Lead and opportunity	Odoo	Qualified business partner
Counterparty	Odoo or 1C, according to the agreed rule	Stable identifier and details
Item master	Odoo, PIM or 1C	Code, name, unit and tax group
Commercial proposal	Odoo	Order basis
Customer order	Odoo	Document for execution and accounting
Implementation	1C or Odoo — depending on the warehouse system	Number, date and accounting status
Stock	Warehouse system of record	Available quantity by warehouse
Payment	1C or banking system	Payment status, amount, date and currency
Accounting entries and period closing	1C	Aggregated financial result

The allocation depends on how sales, the warehouse and accounting actually operate. The basic rule is simple: two systems must not independently create and modify the same object.

What data is typically transferred

Counterparties

Stable key, legal status, settlement currency and details. Changes to banking or tax details require approval from the responsible person.

Item master

Code, name, unit, variants, tax category, packaging and serial tracking. Different units require an explicit conversion rule.

Prices and currencies

The base price is kept separate from the price list, discount and actual line price. For international operations, the currency, exchange rate and effective date are recorded.

Orders and shipments

Odoo sends the confirmed order and receives the document number, status, shipped quantity and reason for any discrepancy.

Stock and reserves

A specific quantity type is transferred: physical, free or available after reservations, together with the warehouse and calculation timestamp.

Payments

The banking or accounting system returns the amount, date, currency and matching result for the order or invoice.

Direct connector, microservice or bus

Direct exchange or adapter

Suitable for a small number of clearly defined flows
Launches faster with stable data models
Requires control over the close version relationship between Odoo and 1C

Microservice, ESB or iPaaS

Stores mappings, transformations, retries and the log
Justified when WMS, PIM, a website, banks, marketplaces and BI are involved
Adds an operational layer and does not replace business rules

Map out your integration landscape

clients@kt.team Telegram @kt_team_it

Batch exchange or events

Flow	Reasonable approach	Why
Confirmed order	Event after confirmation	Delay affects execution
Critical payment status	Event or short interval	Changes the shipping decision
Large product catalog	Batch loading plus changes	Full real-time processing creates unnecessary load
Stock available to the manager	On an event or after a defined delay	Frequency depends on the cost of breaking a promise to the customer
Data for BI	On a schedule	For reporting, an agreed schedule is usually sufficient

Use real-time processing where a delay changes an employee's or customer's action. Batch processing is easier to control and maintain for other flows.

How to prevent document loss

Each message has a unique identifier
The recipient confirms delivery and the processing result
A temporary error triggers a limited retry
Resending does not create a second object
Each error gets a clear status and an owner
The log stores the original value, transformation and transfer time
After the system is restored, the queue continues processing
Reconciliation identifies a document that was not delivered or differs in amount

Step-by-step integration launch

01
Select process
For example: confirmed order in Odoo → document in 1C → sales transaction → payment status in Odoo.
02
Describe the data
Document the entities, owners, keys, required fields, reference data and permitted changes.
03
Prepare examples
Test a standard order, currency, discount, partial shipment, return, unknown item, duplicate and system unavailability.
04
Set up controls
Before automating the flow, configure a log, delivery statuses, a retry queue and error notifications.
05
Perform reconciliation
Compare document counts, amounts, taxes, currency, lines, stock and payments; queue discrepancies for review.
06
Open the flow
Start with one legal entity, business unit or order type, then expand the scope after stable operation.

How to accept the integration

Each object has a designated owner
Matching keys do not depend on the name
Repeating a message does not create a duplicate
Errors are visible to business users or support
Reference data remains consistent
Partial operations are recorded correctly
Amounts, taxes, currencies and lines are reconciled
Changes to posted documents are controlled
Integration user access is restricted
The log reconstructs the document's route

Integration pilot

Analyze one Odoo-1C flow

1 process

We will take a real order or another end-to-end document, define data owners, events, change rules and test cases, then choose an adequate data exchange architecture.

map of systems, entities and owners
data exchange contract and error scenarios
reconciliation and acceptance criteria

Discuss Odoo and 1C integration

Sources

Review date: 21.10.2026

Odoo 20 - External JSON-2 API
1C technologies for integration tasks

Odoo and 1C: integrating orders, products, stock, and accounting

One entity—one owner; confirmed statuses flow back

Odoo