Ürün ayrıntıları İngilizce olarak görüntülenir. Çeviriler yakında gelecek.
Kısa bilgiler
- Fiyat
- $499.00 USD
- Odoo versiyonları
- 17, 18, 19
- Kurulum süresi
- 30 dk.
- Lisans
- Bir kerelik kalıcı
- Diller
- 11 language
Tek Seferlik Satın Alma
Kaufland Marketplace Connector (DE/CEE)
A build-to-order Odoo integration that syncs your product offers, orders, stock, prices and shipments with the Kaufland.de and CEE marketplace. ECOSIRE scopes, builds, installs and supports it on your Odoo 17, 18 or 19.
$499.00USD
Şimdi ödeme yok. Bu, ekibimize bir teklif talebi gönderir — fiyat ve sonraki adımlarla e-posta ile dönüş yapacağız.
Temel Özellikler
Kaufland offer/listing publication from `product.template` and `product.product`, with price, stock, item condition and delivery-time fields mapped to the Kaufland offer schema
Scheduled order import via `ir.cron` that creates a matching `sale.order` per Kaufland order and links it through a `kaufland.order.map` record for traceability
Automatic order acknowledgment back to Kaufland within the marketplace SLA window, so new orders don't age out and hurt account health
Bidirectional, delta-based inventory sync driven by `@api.depends` computed fields and automated actions on `stock.quant` / `qty_available` — pushes only changed offers, not the whole catalog
Price sync from Odoo pricelists or list price to the corresponding Kaufland offers, with configurable rounding and min/max guard rails to prevent bad pushes
Shipment and carrier tracking upload triggered on `stock.picking` validation, transitioning the Kaufland order to shipped with the tracking number
Configurable category and attribute mapping between Odoo product attributes and Kaufland's required category tree, stored as editable records (no hard-coded mappings)
Server-side Kaufland Marketplace API client with request signing, rate-limit-aware retry/back-off, and full request/response logging for audit
Multi-storefront support for Kaufland.de plus CEE markets (e.g. CZ/SK/PL where enabled), each configured as its own `kaufland.account` with independent credentials and currency
Multi-warehouse aware stock resolution so the quantity published to Kaufland reflects your chosen source location(s), not a single hard-coded warehouse
Error surfacing on the Odoo record — failed publishes/imports raise a logged activity or exception note on the offer/order so operators see and retry them instead of silent failures
Security via `ir.model.access.csv` and record rules restricting marketplace models to a Kaufland Manager/User group; credentials stored in `ir.config_parameter`, never client-side
Optional inbound webhook controller endpoint (JSON-RPC style) for near-real-time order events where Kaufland supports push, falling back to cron polling
SKU/EAN reconciliation to match Kaufland offers to existing Odoo products and prevent duplicate product creation on import
Bu Ürün Hakkında
If you sell on Kaufland.de (or its CEE storefronts) alongside Odoo, the day-to-day reality is two disconnected systems held together by CSV exports and manual re-keying. Odoo core has no concept of a Kaufland offer, no field for a Kaufland order id, and no way to acknowledge or ship an order back to the marketplace. Sellers end up copying stock levels by hand, missing the acknowledgment window on new orders, and oversell when a warehouse quantity drops but the Kaufland offer never updates. The result is late shipments, account-health penalties, and price/stock drift across channels that Odoo was never designed to reconcile.
Neden Kaufland Marketplace Connector (DE/CEE)
Kaufland offer/listing publication from `product.template` and `product.product`, with price, stock, item condition and delivery-time fields mapped to the Kaufland offer schema
Scheduled order import via `ir.cron` that creates a matching `sale.order` per Kaufland order and links it through a `kaufland.order.map` record for traceability
Automatic order acknowledgment back to Kaufland within the marketplace SLA window, so new orders don't age out and hurt account health
Bidirectional, delta-based inventory sync driven by `@api.depends` computed fields and automated actions on `stock.quant` / `qty_available` — pushes only changed offers, not the whole catalog
Price sync from Odoo pricelists or list price to the corresponding Kaufland offers, with configurable rounding and min/max guard rails to prevent bad pushes
Shipment and carrier tracking upload triggered on `stock.picking` validation, transitioning the Kaufland order to shipped with the tracking number
ECOSIRE builds a native Kaufland connector that lives inside your Odoo database as a proper module — a real __manifest__.py, dedicated models.Model classes (for example kaufland.offer, kaufland.order.map, kaufland.account), and clean integration with product.template, stock.quant, sale.order and stock.picking. Authentication and every call to the Kaufland Marketplace API are handled server-side with proper request signing and retry/back-off, so credentials never touch the browser. Listing and offer publication push your price, stock, condition and delivery-time to Kaufland; a scheduled ir.cron job (and optional webhook endpoint via the Odoo controller layer) imports new orders, creates the matching sale.order, and sends the required acknowledgment automatically within the marketplace SLA.
Technically, the sync is bidirectional and idempotent. Inventory and price sync are driven by Odoo's ORM — @api.depends computed fields and automated actions detect changes to qty_available or list price and queue a delta push to the affected offers, so you are not blindly re-sending the whole catalog. Category and attribute mapping is modeled as configurable records (a mapping UI in standard XML/OWL views) so your Odoo product attributes translate to Kaufland's required category schema without hard-coding. When you validate a delivery, the connector uploads the shipment and carrier tracking number back to Kaufland and transitions the order state. Everything is guarded by ir.model.access.csv plus record rules so only the right users touch marketplace data, and API traffic is logged for auditability. We build against your target line — Odoo 17.0, 18.0 or 19.0 — and note Community vs Enterprise differences up front (the connector itself runs on Community; Enterprise-only touchpoints like advanced studio-built views are only used if you already run Enterprise).
Because this is build-to-order, nothing is shipped blindly. We start with a scoping call to confirm your Kaufland account setup, storefronts (DE and which CEE markets), catalog size, carrier/tracking flow and edge cases like bundles or multi-warehouse. You approve a written scope; we build on a staging copy of your Odoo, run UAT against your real (or sandbox) Kaufland credentials, then install to production with a rollback plan. Typical delivery is 2-4 weeks from confirmed scope, and you receive the full source, documentation, a training session and a post-go-live support window. You own the code and the git repository at handover — no black box, no per-order lock-in.
Ne elde edeceksin
- Installable Odoo module source code built for your exact version (17.0, 18.0 or 19.0), delivered as a versioned package
- Installation and configuration on your staging and production Odoo, including Kaufland account/credential setup and cron scheduling
- Technical documentation: model/field reference, API integration notes, mapping configuration and cron/webhook behavior
- End-user guide plus a live training session for your operations team covering offers, orders, stock and shipment flows
- UAT on a staging copy against sandbox or real Kaufland credentials, with a documented go-live and rollback plan
- Post-go-live support window for bug fixes and adjustments after production launch
- Git repository handover so you own the full source history and can maintain or extend it independently
- Category/attribute mapping configured for your live catalog as part of onboarding
Bu kimin için
German/CEE Kaufland seller on Odoo
A merchant already selling on Kaufland.de and expanding into CEE storefronts who runs operations in Odoo and needs offers, orders, stock and shipments to stay in sync automatically instead of via CSV re-keying.
E-commerce / operations manager
Owns marketplace account health and fulfillment SLAs. Needs orders acknowledged in time, tracking uploaded on shipment, and a clear view of any sync failures so nothing falls through the cracks.
Multi-channel brand scaling to marketplaces
Already sells via web/other channels in Odoo and is adding Kaufland as a new channel. Needs per-storefront configuration, price/stock guard rails and multi-warehouse-aware stock so a new channel doesn't cause overselling.
Odoo partner or in-house IT lead
Responsible for the Odoo instance and wants a properly-architected module (clean models, access rules, logging) they own via git — not a black-box connector with hidden per-order fees or unmaintainable code.
Kuruluma genel bakış
ECOSIRE'dan indirin
Lisansı ecosire.com adresinden satın alın ve hesap kontrol panelinizden Kaufland Marketplace Connector (DE/CEE) modülünün ZIP dosyasını indirin.
Odoo'ya yükle
ZIP'i sunucudaki Odoo özel eklentiler klasörünüze çıkarın (veya Uygulamalar > Odoo.sh / runbot'taki dosyadan yükle yoluyla yükleyin).
Modülü yükleyin
Geliştirici Modunu etkinleştirin, Uygulamalar'ı açın, Uygulama Listesini Güncelle'ye tıklayın, Kaufland Marketplace Connector (DE/CEE)'i arayın ve Yükle'ye basın.
Ayarları yapılandırın
Yeni menüyü açın, ECOSIRE lisans anahtarınızı yapıştırın, tüm harici kimlik bilgilerini (Shopify, Amazon, Stripe vb.) bağlayın ve kaydedin.
Doğrulayın ve yayına alın
Yerleşik bağlantı testini çalıştırın, ilk 10 kaydınızı senkronize edin ve yinelenen cronu planlayın. Herhangi bir sorun olursa desteğe başvurun.
Kaufland Marketplace Connector (DE/CEE) Nasıl Karşılaştırılır
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| Kaufland-specific fit | Built for your catalog, storefronts and fulfillment flow | Fully bespoke but you define everything from scratch | Generic feature set, may not cover your edge cases | |
| Order acknowledgment & SLA | Auto-acknowledge within marketplace window via cron/webhook | Possible, but you must design and test the SLA logic | Varies; often polling-only, SLA not guaranteed | |
| Stock & price sync | Delta-based, multi-warehouse aware, with guard rails | Whatever you build and maintain yourself | Often full-catalog push, limited guard rails | |
| Category/attribute mapping | Editable mapping records configured for your catalog | Hand-built each time you add products | Fixed mapping model, hard to bend | |
| Code ownership | Full source + git repo handed over to you | You own it (you wrote it) | Vendor-locked, often obfuscated, per-order fees | |
| Delivery & effort | 2-4 weeks from confirmed scope, we build and install | Months of internal dev + ongoing maintenance | Instant install but self-configured and self-supported | |
| Support & Odoo upgrades | Post-go-live window + optional upgrade support | Your team, or contractors you re-source each time | Tiered/paid support, upgrade timing not in your control | |
| Security & access control | Access CSV + record rules, server-side signed API calls | Depends on your team's rigor | Usually fine, but you can't inspect the internals |
Kaufland Marketplace Connector (DE/CEE) hakkında Sıkça Sorulan Sorular
+How long does delivery take?
This is a build-to-order module, not an instant download. Typical delivery is 2-4 weeks from the point where the scope is confirmed in writing after your scoping call. Larger catalogs, extra CEE storefronts, or unusual fulfillment edge cases can extend that, and we tell you the realistic timeline before you commit.
+What happens to support and updates after go-live?
Every build includes a post-go-live support window for bug fixes and adjustments. Because you receive the full source and git repository, you can maintain it yourself, or engage ECOSIRE for ongoing support and for upgrades when you move to a newer Odoo version or when Kaufland changes its API.
+Which Odoo versions and editions are supported?
We build for Odoo 17.0, 18.0 or 19.0 — you pick your target during scoping. The connector runs on Odoo Community; it does not require Enterprise. If you already run Enterprise we integrate cleanly with it, and we flag any edition-specific behavior up front.
+Do I need a Kaufland Seller / Marketplace API account?
Yes. You need an active Kaufland Seller account with Marketplace API access (client key/secret). The connector authenticates and signs requests server-side using those credentials, which are stored securely in Odoo and never exposed in the browser. We help you configure them during setup.
+How does it avoid overselling and price mistakes?
Stock sync is delta-based and multi-warehouse aware, pushing the true available quantity from your chosen source location(s) whenever it changes. Price sync includes configurable rounding and min/max guard rails so an accidental bad value in Odoo is caught before it publishes to Kaufland.
+Will it create duplicate products when importing orders?
No. Order import reconciles Kaufland offers to existing Odoo products by SKU/EAN before creating anything, and maps each Kaufland order to a `sale.order` through a dedicated mapping record, so you get traceable orders without duplicate product records.
+Can it handle multiple Kaufland storefronts (DE and CEE)?
Yes. Each storefront is configured as its own account record with independent credentials and currency, so you can run Kaufland.de alongside supported CEE markets from the same Odoo instance with per-store offer, price and stock control.
İlgili Modüller
Teklif isteyin
Kaufland Marketplace Connector (DE/CEE)
A build-to-order Odoo integration that syncs your product offers, orders, stock, prices and shipments with the Kaufland.de and CEE marketplace. ECOSIRE scopes, builds, installs and supports it on your Odoo 17, 18 or 19.
- Kaufland offer/listing publication from `product.template` and `product.product`, with price, stock, item condition and delivery-time fields mapped to the Kaufland offer schema
- Scheduled order import via `ir.cron` that creates a matching `sale.order` per Kaufland order and links it through a `kaufland.order.map` record for traceability
- Automatic order acknowledgment back to Kaufland within the marketplace SLA window, so new orders don't age out and hurt account health
- Bidirectional, delta-based inventory sync driven by `@api.depends` computed fields and automated actions on `stock.quant` / `qty_available` — pushes only changed offers, not the whole catalog