Integration with 1C, Odoo, the SalesDrive CRM and a Dotykacka POS brings your catalog, orders and sales into Elbuz without manual re-entry. Each system connects with its own template in “Data import”.
When you need this:
- Your accounting runs in 1C — the catalog, prices and stock come from exchange files.
- Your company works in Odoo — products, warehouses and orders flow into Elbuz, and prices and new products go back.
- Orders come in through SalesDrive or a POS — sales land in your documents.
Where to start: choose your system in the table and open its article.
What the connections do
- 1C — catalog, prices and stock from CommerceML 2 files; back — as a CommerceML file.
- Odoo — two-way exchange via the Odoo API.
- SalesDrive — orders by webhook, catalog and stock from YML.
- Dotykacka — POS receipts into your records, products to the POS.
Which system to connect and what flows where
| System | When to choose it | Into Elbuz | Back | What you need |
|---|---|---|---|---|
| 1C (CommerceML) | accounting in 1C with a CommerceML 2 export | products, groups, specifications, photos, prices and stock | catalog and prices — as a CommerceML file | import.xml and offers.xml or links to them |
| Odoo | your company's ERP is Odoo | products with variants and photos, stock for each warehouse, sales orders, suppliers | prices, new products with photo and category, supplier links | Odoo address and API key; for Odoo 18 and older — also a login |
| SalesDrive | orders come in through the SalesDrive CRM | orders — as sales documents; catalog and stock | YML feed — with the “CRM SalesDrive” template in “Data export” | link to the YML export, account subdomain, API key |
| Dotykacka | an offline outlet with a Dotykacka POS | paid receipts, customers | categories and products to the POS | cloud ID and API refresh token |
How to connect
- Template. “Data import” → “Add” → “CommerceML2 (1C)”, “Odoo”, “CRM SalesDrive” or “dotykacka.pl (POS)”. One template is one Odoo database.
- Access. Specify the files or links, key or token — the system's article says exactly what. Run it manually and check the result.
- Schedule. Put the template on a schedule. For the reverse direction, create one more template in “Data export”.
Scenarios
- 1C as the source of truth. The template picks up import.xml and offers.xml by links on a schedule; a repeat exchange updates the same cards by
Ид. - Odoo plus supplier price lists. The catalog and warehouse stock come from Odoo, and Elbuz exports supplier links from price lists back to Odoo.
- Orders from SalesDrive. The webhook delivers an order right after it's created, and the API key fills in the history.
- Store and POS. Each Dotykacka receipt becomes three documents: a stock write-off, a cash receipt and a sale.
FAQ
Can I export data from Elbuz to 1C?
Yes: a separate export template builds a CommerceML file that 1C accepts with its standard exchange processing (send the catalog to 1C).
Why does Odoo need two templates?
The import template pulls data from Odoo, and the export template sends it back; both work with the same API key.
Will the 1C exchange delete products that aren't in the file?
Only if you turn on the deletion checkbox — it requires a separate permission (exchange with 1C).
What happens to a POS product that isn't in the catalog?
It becomes a card in a service category (Dotykacka POS).
Where are the marketplaces?
In the articles Ukrainian marketplaces, Kazakhstan marketplaces, European marketplaces and US marketplaces.
Where it is and who has access
- Menu
- Directories → Operations → Data import → “Add” → system type
- Other entry points
- Directories → Operations → Data export — to 1C, Odoo, SalesDrive and the POS
- Access right
- the “Import” window in “Group permissions”
- Prepare
- exchange files, an API key or a system token — each system needs its own
Related topics
- If orders from SalesDrive or the POS arrive with errors — Orders via API.
- To understand how edits in the card are protected — Catalog via API.
- If you sell on European marketplaces — European marketplaces.
