Elbuz exchanges data with Odoo via the Odoo API, without files: catalog, warehouse stock and orders come into Elbuz; prices, new products and supplier links from price lists go back to Odoo.
When you need this:
- You run inventory and accounting in Odoo — products with variants, photos, attributes and per-warehouse stock land in Elbuz.
- You price from supplier price lists — only changed prices go to Odoo.
- You purchase in Odoo — the product’s “Purchase” tab shows price-list suppliers with their codes, prices and lead times.
- Odoo orders belong in the shared queue — each becomes a “Customer order” document.
Where to start: create an API key in Odoo.
What the Odoo connection does
- Brings products into the catalog — name, SKU, barcode, price, weight, descriptions, category; each variant as a separate card.
- Groups variants into a family and turns colors, sizes and other variant axes into option attributes.
- Fetches photos together with the Odoo website gallery, even if Odoo images require sign-in.
- Mirrors warehouses — stock of every product in every Odoo warehouse.
- Receives sales orders and adds Odoo vendors to your contacts.
- Exports to Odoo prices, new products with photo and category, optionally descriptions, SEO and main data, and supplier links.
What flows in each direction:
- Request or action
- Note
What you need from Odoo: URL and API key
Elbuz connects to Odoo on behalf of an Odoo user with that user’s API key. You need three values:
- Odoo URL — as in the browser, for example
https://company.odoo.com. If the server hosts several databases, add the database name to the URL:https://erp.company.com/?db=main. On Odoo Online the database is taken from the URL automatically. - API key — created in Odoo and pasted into the “Odoo API key” field.
- User login — only for Odoo 18 and older. Odoo 19 and newer work with the key alone, so leave the field empty.
You don’t need to specify the Odoo version: Elbuz detects whether the server supports the new Odoo 19+ protocol and falls back to the old one for Odoo 14–18.
Where to get the API key: step by step
| Where | What to do |
|---|---|
| Odoo | Avatar in the top-right corner → My Preferences → Security tab → “API Keys” block → Create API Key |
| Same place | Confirm your password, enter a description (for example “Elbuz”) and an expiry period |
| Same place | Copy the key — Odoo shows it only once |
| Elbuz | “Odoo” template → “Connection” card → URL, key (and login for Odoo 18 and older) → “Save” → “Test connection” |
1
Security tab2
Create API Key button- Security tab of the Change My Preferences dialog (avatar → My Preferences).
- Create API Key creates a key; Odoo shows it only once. Above — an existing key "elbuz" with the RPC scope and expiry date.
In Odoo 20 a key lives no longer than three months. When it expires, import and export stop with the “Invalid apikey” error. Set yourself a reminder: create a new key and enter it in both templates before the old one expires.
Create a separate Odoo user, for example “Elbuz”, with rights to sales, inventory and purchasing. That way you see which changes the integration made, and you can revoke access without touching any real person’s account.
In cloud Odoo Online, the external API is available only on the Custom plan. On the One App Free and Standard plans, Odoo won’t accept the requests. Odoo on your own server or on Odoo.sh has no such limit.
Odoo must be reachable from the internet. Elbuz runs in the cloud and doesn’t access internal networks: an Odoo server visible only inside your office network won’t connect.
How to connect
- Create a template of type “Odoo” and, in the “Connection” card, enter the URL, the API key and, for Odoo 18 and older, the login.
- Save the template and click “Test connection” — it checks the saved URL and key. If Odoo replies with your company name, the key is accepted.
- In the “Select data to import” card, keep only the checkboxes you need (what they turn on), save and run.
What to import from Odoo: template checkboxes
You decide what to take: the Odoo template shows only the checkboxes the connection actually supports. Clear a checkbox and the run skips that part.
| Checkbox | What arrives |
|---|---|
| Products | product and variant cards (fields) |
| Categories | product category: the Odoo website category, or the internal Odoo category if there is no website; works together with “Products” |
| Attributes | variant axes as option attributes, plus other attributes; together with “Products” (variants) |
| Photo | main photo and Odoo website gallery; together with “Products” (photos) |
| Warehouses | Odoo warehouses and product stock in each; without “Products” it updates stock of cards already imported (warehouses) |
| Orders | sales orders as “Customer order” documents (orders) |
| Import Odoo vendors as contacts | vendors in the “Supplier” group (vendors) |
1
Products2
Warehouses3
Import vendors as contacts- Products — loads products with their variants.
- Warehouses — mirrors the Odoo warehouses and brings stock per warehouse.
- Import Odoo vendors as contacts — creates vendors as contacts in the Supplier group.
Order within a run: vendors → products → warehouses → orders. Warehouses come after products because stock is written into existing cards.
Speed and volumes
The connection reads and writes in batches: pages of 500 products, photos in several parallel requests, prices in batches of 500 per request. Measured on November 11, 2026, with Odoo 20 on the same computer as Elbuz (no network latency):
| Operation | Volume | Time |
|---|---|---|
| catalog import with photos | 3,049 products, 3,039 photos | 8 s |
| full import into the Elbuz catalog | 3,054 products and 24 orders | 37 s; repeat run — 23 s |
| export of all prices | 3,000 products | 22 s |
| daily price export | 3,000 products, 100 changed | 0.8 s |
On your Odoo, timing depends on its server and plan, but the proportions hold: there’s no need to export the whole price list every time, Elbuz filters out unchanged prices itself. The “Stop” button in the log breaks off the catalog and order import after the current page.
What goes into the product card
Each Odoo product variant becomes a separate Elbuz card. An Odoo product without variants is one card.
| Odoo data | Elbuz card field |
|---|---|
| name (for a variant — with attributes, for example “Desk (White, Steel)”) | Name |
| Internal Reference | SKU |
| barcode | Barcode (digits only) |
| variant sales price | Price |
| quantity on hand (with the Inventory app) | Quantity; negative becomes zero |
| weight | Weight |
| sales description | Short description |
| Odoo website description, SEO title and description | Full description, meta title, meta description |
| active and the “Sales” checkbox | Status: disabled if the product can’t be sold |
Each card gets a permanent key — the product ID in Odoo. Elbuz uses it to recognize the product on every later run, even if the name or SKU changed in Odoo. So two different Odoo products with the same name stay two cards and aren’t merged into one.
A product that an export from Elbuz created in Odoo is recognized on import as your existing card, so no second card appears.
What a repeat run does with your edits
A run brings back into the card what is in Odoo now: name, SKU, barcode, price, stock, status, descriptions. An empty Odoo field doesn’t erase your value. Products that the Elbuz export created in Odoo are skipped by the import: Elbuz keeps their price and stock. To lock the price, use “Fixed Price” in the card (import overview).
Photos and attributes are loaded only when the card is created. A run doesn’t update them on an existing card: change a photo in Odoo and it won’t change in Elbuz.
A product deleted or archived in Odoo stays as it was in Elbuz: the run takes only existing products and disables nothing. You can find Odoo cards in the “Products” window by the “Source: code” column (odoo).
Variants, attributes and photos
Variants of one Odoo product are grouped into a product family: they all share the same “Variant family name” — the Odoo product name. On the website, shoppers switch between them with color and size buttons, each with its own price, photo and stock.
- Variant axes (color, size, leg material…) arrive as option attributes — they are what switches the variants.
- Odoo attributes without variants arrive as regular attributes; multiple values are separated by semicolons.
- Two different Odoo products with variants and the same name get a family name ending with the Odoo product template ID, for example “T-shirt #101”, so their variants don’t mix.
1
Color option2
Legs option- Color — the first option of the family member, with its value.
- Legs — the second option of the family member, with its value.
Without the “Attributes” checkbox, variants still become separate cards of one family, but with no option attributes. Then the website switcher won’t appear until you mark the variant attributes manually.
Product photos
Odoo images open only after signing in to Odoo, so a link to them is useless to Elbuz. Instead, the connection fetches the file itself via the API, puts it in your Elbuz storage and writes its own link into the card.
- Main photo — the variant photo, or the product photo if the variant has none.
- Gallery — extra photos from the Odoo website (eCommerce app): variant photos first, then product photos.
- One photo — one file. A photo shared by five variants is uploaded once; a repeat run with no changes downloads nothing.
Stock by warehouse
The “Warehouses” checkbox makes Elbuz mirror the Odoo warehouses: each Odoo warehouse becomes an Elbuz warehouse with the same name, holding the same stock as in Odoo. Odoo is the main system for stock.
- A new Odoo warehouse appears in Elbuz automatically on the next run.
- Each stock change is written to the warehouse movement log as a sync, with no documents. A repeat run with no changes in Odoo writes nothing.
- The card’s total stock is the sum across all Odoo warehouses.
1
Odoo warehouse2
Odoo warehouse- One of the three warehouses mirrored from Odoo, shown next to the store's own warehouses.
- Another mirrored Odoo warehouse; each Odoo warehouse becomes a separate warehouse in the list.
Without the Inventory app, Odoo has neither warehouses nor quantities: the run log shows an error for warehouses, and products are imported without stock.
Don’t record stock movements with Elbuz documents in mirrored warehouses: the next run restores the stock from Odoo. The connection doesn’t touch your own Elbuz warehouses or their documents.
Sales orders and vendors
Each Odoo sales order becomes a “Customer order” in Elbuz with the Odoo number (e.g. S00042). A repeat run updates the existing order instead of adding a second one: status (unless you changed it manually), payment, delivery, and empty contacts and address. Lines and total aren’t overwritten: change the order contents in Odoo and Elbuz keeps the old ones.
| In Odoo | In the Elbuz document |
|---|---|
| product line | document line linked to the card; price includes the line’s tax and discount |
| delivery line | delivery amount (not a product line) |
| order sections and notes | not transferred |
| customer | name, email, phone |
| delivery address | city, country, postal code, address; if there is no separate one, the customer’s address is used |
| note and customer reference | document comment |
| order state and invoice status | order and payment status — for status mapping |
The document total equals the Odoo order total including tax. The first run takes all sales orders, including quotations (drafts) and canceled ones — their state shows in the status; later runs take only orders changed since the previous run. Orders changed in the last second of the previous run arrive once more and are simply updated.
Odoo vendors in your contacts
The “Import Odoo vendors as contacts” checkbox adds Odoo vendors to Elbuz in the “Supplier” group: name, email, phones, website, tax ID, country, city, address, postal code and comment.
- A vendor is an Odoo partner with the vendor flag (it appears with the Purchase or Accounting apps). Without it, vendors are those listed in the products’ purchase prices.
- Contact persons inside a company don’t become separate vendors.
- The contact is matched by name. If it already exists, the run doesn’t change it: your edits in the contact card are preserved.
What to export to Odoo
The export is a separate “Odoo” template in the “Data export” window, with the same URL and key. What to send is set by the checkboxes in the “What to export” card:
| Checkbox | What it does in Odoo |
|---|---|
| Products | updates the price of linked products — only those whose price changed (variant prices) |
| Publish new products | creates products that don’t exist in Odoo yet: name, price, SKU, barcode, weight, short description |
| Categories | assigns a category to a new product, creating it in Odoo by path |
| Photo | sends the main photo to a new product |
| Supplier links | fills in the “Purchase” tab (details); on by default |
| Descriptions & SEO | for linked products, sends the short description to the sales description and the full one to the product description on the Odoo website, plus the SEO title and meta description; off by default |
| Main data (name, SKU, barcode, weight) | updates these fields of linked products; the name only for products without variants, since variants share it with the template; off by default |
An empty field in Elbuz doesn’t erase the value in Odoo, and only changed fields are sent. Without the Website app, Odoo has no place for the full description, so only the short one is sent.
1
Products2
Publish new products3
Supplier links4
Descriptions & SEO- Products — exports product prices and data to Odoo.
- Publish new products — newly created products are published right away.
- Supplier links — exports the links between products and suppliers.
- Descriptions & SEO — exports descriptions and SEO fields.
A product is linked if it came in by import from the same Odoo database or was already created by this export. Such a product isn’t created again, and a product from another Odoo database isn’t treated as linked. Odoo has no separate “Only export new data” checkbox: Elbuz compares prices with Odoo itself and sends only the changed ones.
Variant prices
In Odoo 20 each variant has its own price, and Elbuz writes it. In Odoo 18 and older the price belongs to the product template; a variant differs only by the attribute surcharge. There Elbuz writes the template base price if your variants without a surcharge cost the same; otherwise it skips that template, and the log shows the count.
- Stock isn’t written to Odoo. Odoo manages inventory itself, and Elbuz takes stock from it.
- Photo and category are sent only to new products; existing Odoo products keep theirs.
- A duplicate barcode in one of the new products doesn’t stop the rest: Odoo rejects only that product, and the reason appears in the log.
Supplier links in the “Purchase” tab
Elbuz knows which suppliers carry each catalog product — from linked price lists. The “Supplier links” checkbox transfers this to Odoo, into the standard “Purchase” tab of the product form: one product gets as many lines as it has suppliers.
| “Purchase” line in Odoo | Source |
|---|---|
| Vendor | the price list’s supplier; if missing in Odoo, it is created as a vendor company |
| Vendor product code and name | SKU and product name in the price list |
| Price and currency | the price list price in the supplier’s currency, if that currency is active in Odoo; otherwise in your base currency, if that one is active; otherwise converted at the Elbuz rate into the Odoo company currency. If none applies, the line isn’t written and the error goes to the log |
| Lead time | number of days from the price list’s delivery time |
1
Purchase tab2
Vendor lines- Purchase tab of the Odoo product form.
- Vendors from Elbuz price lists: price in their currency or converted, delivery lead time.
- No changes — no write. A line that already matches isn’t rewritten; changed lines are updated in batches of 500.
- A link removed in Elbuz disappears in Odoo too — but only for your suppliers, that is, those with a price list in Elbuz, and only for products included in this export.
- Lines of vendors set up only in Odoo aren’t touched. Your buyers can keep their own vendors there alongside.
The contact name in Elbuz and the partner name in Odoo must match. Otherwise Odoo gets a second company with the name from Elbuz, and the links go to it.
Scenarios
Inventory and accounting in Odoo, sales and price lists in Elbuz
Scheduled import: “Products”, “Attributes”, “Warehouses”. Export: “Products” (prices) and “Supplier links”. Stock comes from Odoo, prices go to Odoo from price lists.
Buyers work in Odoo
Export with only the “Supplier links” checkbox. Each product’s “Purchase” tab shows current suppliers, their prices and lead times.
Moving from Odoo to Elbuz
One import with all checkboxes, including vendors and orders. Photos, variant families, categories and sales history move along with the products.
Odoo orders in the shared queue
A separate import template with only the “Orders” checkbox, on a schedule: Odoo orders sit next to website and marketplace orders.
New products from price lists straight to Odoo
Export with “Publish new products”, “Categories” and “Photo”: a product that appears in the Elbuz catalog is created in Odoo with a photo and a place in the category tree.
What to do when Odoo won’t connect
| What you see | Why | What to do |
|---|---|---|
| “Invalid apikey” | the key has expired, was revoked or wasn’t copied in full | create a new key in Odoo (how) and enter it in both templates |
| “Odoo < 19: login is required” | Odoo 18 or older works with a login and key | fill in the “User login” field |
| “login or API key rejected” | the login isn’t the user who owns the key, or the database is wrong | check the login; specify the database in the URL with ?db= |
| “blocked: private or reserved address” | Odoo is on a local network, not reachable from the internet | make Odoo reachable from the internet by domain name |
| “Odoo: API error - stock.warehouse” | Odoo has no Inventory app | install the app or clear the “Warehouses” checkbox |
| “Odoo: export error product.supplierinfo” | the Odoo user who owns the key has no rights to purchase prices | grant them purchasing rights or clear the “Supplier links” checkbox; the “Purchase” tab appears in the product form with the Purchase app |
| products without photos | the “Photo” checkbox was turned on after the first run | photos reach only new cards; add photos to existing ones in Elbuz, or delete the cards and run again |
FAQ
Can I export orders from Elbuz to Odoo?
No. Orders go only from Odoo to Elbuz (sales orders).
Does Elbuz update stock in Odoo?
No. Odoo is the main system for inventory; Elbuz only mirrors its stock (stock by warehouse).
Which Odoo versions are supported?
Odoo 14–20: Community, Enterprise, Odoo.sh and Odoo Online on the Custom plan; tested on Odoo 18 and 20. Odoo 18 and older also need a login (what you need).
I deleted a product in Odoo — why is it still in Elbuz?
A run takes only existing products and disables nothing. Disable or delete the extra card in the “Products” window (repeat run).
Can I connect several Odoo databases?
Yes, one template per database. Cards from different databases don’t get mixed up: the product key includes the database identifier.
Are product attributes exported to Odoo?
No. The export sends the price, and for new products — name, SKU, barcode, weight, description, category and photo (what to export).
A product is in several Odoo website categories — where does it go?
To the deepest one. Other website categories aren’t transferred (checkboxes).
Where to find it and who has access
- Menu
- Directories → Operations → Data import (from Odoo) and Data export (to Odoo)
- Template
- new template → type “Odoo”; one template — one Odoo database
- Access right
- the “Import” and “Export” windows in “Group permissions”
- Prepare
- Odoo URL, API key; for Odoo 18 and older, also the login
1
Odoo URL2
User login3
Odoo API key4
Test connection- Odoo URL — the address of your Odoo, for example a company subdomain on odoo.com; for a specific database add ?db=name.
- User login — needed only for Odoo 18 and older; leave it empty for newer versions.
- Odoo API key — created in Odoo under My Preferences, Security tab.
- Test connection — checks the address and key before the first import.
How import templates work in general — data import overview.
Related topics
- To understand how an import template handles any source — Importing data into the catalog.
- If Odoo variants should switch by color and size on the website — Product families.
- If prices from Elbuz should go to Odoo on a schedule — Export templates.
- If you don’t have supplier links yet — Connecting and importing a price list.
