Kaufland Odoo Integration: Connect Kaufland to Odoo ERP
How to connect Kaufland to Odoo: options, Odoo API vs module, syncing Odoo inventory to Kaufland units, orders to sales orders, tracking, returns and pitfalls.
- Written by
- Md AshikSenior Software Engineer, Artisan Dojo
- Published
- Reading time
- 8 min read
Quick summary30-second read
- Kaufland connects to Odoo through an Apps Store connector, a multichannel tool, or a custom module built on the Kaufland Seller API.
- Odoo Online does not support custom or Apps Store modules, so integrations there must run externally through the Odoo API.
- Odoo 19 adds a JSON-2 API, and XML-RPC and JSON-RPC are scheduled for removal in Odoo 22.
- Send Odoo's free quantity, which excludes reserved stock, for the shipping warehouse, minus a buffer for other channels.
- Import each Kaufland order unit as its own sales order line and confirm shipping per order unit with tracking numbers.
To connect Kaufland to Odoo, you sync Odoo products, stock and prices to Kaufland units through the Kaufland Seller API, import Kaufland orders as Odoo sales orders, and send tracking numbers back when the delivery order is validated. You can do this with a third-party connector from the Odoo Apps Store, a multichannel tool in between, or a custom Odoo module. Whichever you choose, Odoo stays the source of truth and every Kaufland order unit is tracked by its own ID.
Our general Kaufland ERP guide covers the Kaufland side: EAN matching, units, storefronts and order units. This post goes deeper into the Odoo side: which models the data lands in, how Odoo inventory feeds Kaufland stock, and where Odoo projects usually go wrong.
What are the options for a Kaufland Odoo integration?
There are three realistic routes:
- A connector from the Odoo Apps Store. Several third-party vendors list Kaufland connector modules, each built for specific Odoo versions. Read each listing for what is not covered: at least one states it does not transfer product titles, descriptions or images, or handle Fulfillment by Kaufland.
- A middleware or multichannel tool. The tool talks to Kaufland, and you connect it to Odoo. This fits if you already sell on several marketplaces through one tool, but someone still has to map Odoo items, stock and orders to it.
- A custom Odoo module or service. Built against the Kaufland Seller API and your own Odoo setup. This makes sense when you have bundles, several warehouses, per-storefront pricing rules, or a connector that keeps failing. We compare the trade-offs in custom integration vs. connector.
One hard constraint: Odoo's own documentation states that Odoo Online is incompatible with custom modules or modules from the Odoo Apps Store. On Odoo Online, the integration has to run outside Odoo and use the Odoo API. On Odoo.sh or self-hosted Odoo, Community or Enterprise, you can install a module.
How does the integration talk to Odoo?
- Inside Odoo, as a module. The code runs in the Odoo server, uses the ORM directly, and schedules work with Odoo's scheduled actions. It needs hosting that allows custom modules and must be upgraded with each Odoo version.
- Outside Odoo, through the Odoo API. A separate service reads and writes Odoo records remotely. Odoo 19 added a new External JSON-2 API at
/json/2/<model>/<method>, authenticated with an API key sent as a bearer token. Odoo's documentation says the older XML-RPC and JSON-RPC endpoints are deprecated and scheduled for removal in Odoo 22 (fall 2028) and Odoo Online 21.1 (winter 2027).
Also from the Odoo docs: API keys cannot last longer than three months, so plan for rotation, and on Odoo Online the external API is only available on Custom pricing plans. On older Odoo versions you will still use XML-RPC or JSON-RPC, so keep the client code in one place and switch to JSON-2 when you upgrade.
Which data moves between Kaufland and Odoo?
| Kaufland concept | Odoo model and field | Direction |
|---|---|---|
| Product (matched by EAN) | product.product, barcode field (variants of a product.template) | Odoo → Kaufland |
| Unit (offer) per storefront | Mapping record linking product.product to id_offer and storefront | Odoo → Kaufland |
Unit amount (stock) | Quantities from Odoo Inventory, e.g. free_qty per warehouse | Odoo → Kaufland |
Unit listing_price | A pricelist per storefront (product.pricelist), in the storefront currency | Odoo → Kaufland |
| Order | sale.order, Kaufland order ID in client_order_ref or a custom field | Kaufland → Odoo |
| Order unit | sale.order.line, with the order unit ID stored on the line | Kaufland → Odoo |
| Buyer, billing and shipping address | res.partner (customer plus delivery address) | Kaufland → Odoo |
| Shipping confirmation | stock.picking (delivery order): carrier_id and carrier_tracking_ref | Odoo → Kaufland |
| Cancellation | Cancelled sale.order.line quantity or cancelled order | Both |
| Return unit | Return picking plus credit note (account.move) | Kaufland → Odoo |
A few Kaufland API details shape this mapping:
- Prices are integers in cents.
listing_priceis sent in the storefront's currency (the docs name CZK, EUR and PLN), and order amounts come back in cents too. Convert and round in one place. id_offerlinks storefronts. Units on different storefronts that share anid_offerkeep warehouse and quantity in sync, but not price, shipping group or handling time. That fits Odoo well: one stock figure per product, one pricelist per storefront.id_offercannot be changed without deleting and recreating the unit. Pick a stable value, such as the Odoo internal reference.
How do you sync Odoo inventory to Kaufland stock?
Stock is where overselling starts. In Odoo inventory, product.product exposes several quantities: qty_available (on hand), virtual_available (forecasted), incoming_qty and free_qty (on hand minus what is already reserved). For a marketplace offer, free_qty is usually the right starting point, because stock reserved for an open delivery order is not really available to sell.
Then decide:
- Which warehouses count. Odoo can compute quantities per warehouse or location. If Kaufland orders ship from one warehouse, send only that warehouse's stock. On Kaufland, each unit is tied to a warehouse (
id_warehouse, or your default). - How big the buffer is. If the same stock also sells on Amazon, eBay or your own shop, subtract a safety buffer so a sale elsewhere does not oversell Kaufland before the next sync.
- How kits are counted. For products sold as kits through a bill of materials, the sellable quantity depends on the components. Calculate it before sending.
- What triggers an update. Send changes when stock moves, not only on a timer, and run a full reconciliation on a schedule to catch drift.
Kaufland caps amount at 99,999, and the bulk endpoint (POST /units/bulk) accepts up to 150 units per request, returning a separate result for each unit. A bulk call can succeed while single units fail, so read those results.
Top tip
Import Kaufland orders into Odoo quickly and confirm them, so Odoo reserves the stock. Until an order exists in Odoo, the stock you send to Amazon, eBay and Kaufland still counts those items as free.
How to connect Kaufland to Odoo, step by step
Step 1: Check your Odoo hosting and version
Odoo Online, Odoo.sh or self-hosted, and which version, decides whether you can install a module and which Odoo API you can use.
Step 2: Get Kaufland API credentials
Create a client key and secret key in the Kaufland seller portal. Every request to https://sellerapi.kaufland.com/v2/ is signed with a SHA-256 HMAC and needs a timestamp within five minutes of Kaufland's server time. Test against the Seller API Playground, since "try it out" in the live docs changes real marketplace data.
Step 3: Clean up barcodes in Odoo
Every variant you want to sell needs a valid, unique EAN in the barcode field of product.product. Products that already exist in Kaufland's catalog match by EAN. For new products, you upload product data by EAN and check /product-data/status/{ean} until it reports SUCCESS or FAIL.
Step 4: Map storefronts and sync units
Call /info/storefront to see which storefronts your account can use. For each, define the Odoo pricelist, currency, warehouse, shipping group and handling time. Store Kaufland unit IDs per product and storefront in a mapping table, then create units and push stock and prices, logging every rejection.
Step 5: Import orders as sales orders
Fetch order units with status need_to_be_sent and group them by id_order. Units move from open to need_to_be_sent about 15 minutes after creation; addresses are not available before that. Create one sale.order per Kaufland order, one line per order unit, and confirm it so Odoo creates the delivery order.
Step 6: Send shipping confirmations
When the delivery order is validated, send PATCH /order-units/{id_order_unit}/send with the carrier code and tracking numbers for each order unit. Map Odoo carriers to Kaufland carrier codes explicitly.
Step 7: Handle cancellations and returns
Cancel order units you cannot ship with PATCH /order-units/{id}/cancel and a reason such as NoInventory, and cancel the matching Odoo lines. For returns, process each return unit (accept, reject, repair or clarify) and create the return picking and credit note in Odoo.
Should you use push notifications or polling?
Kaufland offers push notifications, with subscriptions created per storefront through /subscriptions, for events such as new orders and new order units. The notification does not contain the changed data, so you still call the API to fetch it. Kaufland retries failed deliveries at increasing intervals for about 12 hours, then disables the subscription, and events missed while it is disabled are lost.
So use both: notifications to react fast, and a scheduled poll (an Odoo scheduled action, or a job in your external service) to catch anything missed.
The rate limit is 111 requests per seller per second across all endpoints, with HTTP 429 when exceeded. Use bulk calls for full reconciliations and back off on 429.
Common mistakes in Kaufland Odoo integrations
- Sending on-hand stock.
qty_availableignores reservations. Using it oversells items that are already promised to other orders. - No unique key on orders. Without the Kaufland order unit ID stored on the line, a retry creates duplicate sales orders.
- Treating the order as one unit. Kaufland ships, cancels and returns per order unit. An Odoo flow that only knows "order shipped" breaks on partial shipments.
- Mixing currencies. Sending a EUR price to a PLN or CZK storefront, or forgetting the cents conversion, produces prices that are off by a factor of 100 or by the exchange rate.
- Ignoring per-unit errors. Bulk responses report each unit separately. If nobody reads them, products silently stay offline.
Our marketplace ERP integration checklist covers more checks for go-live.
Does the same approach work with other ERPs?
Yes. The Kaufland side stays the same: units by EAN, stock and prices per storefront, orders split into order units. Only the ERP side changes. German sellers often run JTL-Wawi, Xentral, SelectLine, plentymarkets (PlentyONE) or Microsoft Dynamics 365 Business Central. Whatever marketplace features or add-ons your ERP offers, check what they actually cover for Kaufland, especially multi-storefront pricing, per-unit cancellations and returns, before deciding to build. Our marketplace ERP integration service covers these setups too.
FAQ
Does Odoo have a built-in Kaufland connector?
Odoo's documentation covers marketplace connectors such as Amazon, but not Kaufland. Kaufland connections come from third-party Apps Store modules, middleware, or custom development.
Can I connect Kaufland to Odoo Online?
Not with a module. Odoo Online does not support custom modules or Apps Store modules. You need an external service that uses the Odoo API, which on Odoo Online requires a Custom pricing plan.
Which Odoo stock quantity should I send to Kaufland?
Usually free_qty for the warehouse that ships Kaufland orders, minus a safety buffer if the same stock sells on other channels.
Do I need webhooks, or is polling enough?
Polling alone works. Push notifications make order import faster, but you still need a scheduled poll, because notifications missed during long downtime are lost.
Need help connecting Kaufland to Odoo?
We build and maintain Kaufland integrations for Odoo and other ERPs, including stock logic across Amazon, eBay and your own shop. See our Kaufland API integration service, or describe your Odoo setup below and you will get a reply from the engineer who would build it.