Selling on Kaufland Global Marketplace (formerly real.de) means living in the Seller Portal: downloading order files, re-keying them as sales orders, uploading offer updates when prices change, and pasting tracking numbers back one at a time. Every one of those hops is a place where a sale gets keyed twice, an item oversells because the Business Central inventory number never reached the marketplace, or a month-end close stalls because Kaufland's commission and payout statements never became journal entries. Dynamics 365 Business Central handles the sales order, the item ledger and the general ledger well — it simply has no idea Kaufland exists. There is no standard connector, no marketplace status vocabulary in the sales document lifecycle, and nowhere to park a marketplace order id, a unit id or a fulfilment deadline.

ECOSIRE builds a dedicated AL extension that closes that gap inside Business Central rather than beside it. The extension ships a Kaufland Setup page holding your client key and endpoint configuration, a staging table for raw marketplace payloads, and codeunits that talk to the Kaufland Seller API over HTTPS using HttpClient with the signed-request pattern the API requires. Incoming orders land in staging first, are mapped through configurable item/offer, shipping-method and payment-method mapping tables, and are then created as Business Central sales orders with the marketplace order number, unit ids and buyer address written to table extensions on Sales Header and Sales Line. Nothing is created blind: unmapped SKUs, unknown shipping profiles and address failures stop on an error log page you can retry from, so a bad payload never silently posts.

Synchronisation runs both ways on Job Queue Entries you control. Stock changes are picked up through event subscribers on item ledger posting and on price setup tables, queued as deltas, and pushed to Kaufland as offer updates on the cadence you set — per minute for fast movers, hourly for the long tail. Posted sales shipment and warehouse shipment triggers push fulfilment confirmations with carrier and tracking number back to the marketplace, so the buyer sees dispatch without anyone touching the portal. Settlement documents are imported and reconciled: commission, fulfilment and payout lines are matched to their originating orders and posted as configurable general journal lines against the accounts, dimensions and journal templates your controller specifies, so the Kaufland payout on your bank statement reconciles to a real ledger balance instead of a spreadsheet.

The extension is written for current Business Central release waves and runs on SaaS online and on-premises. It is delivered as a per-tenant extension, or packaged to AppSource technical requirements under your own publisher account if you want that. It ships its own permission sets so marketplace operators get the Kaufland pages without general ledger rights, exposes marketplace order and settlement data through API pages (REST API v2.0 / OData v4) for Power BI, Power Automate and Dataverse, and emits Application Insights telemetry so a failed API call surfaces in the same diagnostics as the rest of your Business Central environment.

This is a build-to-order product, not an AppSource download — nothing installs until we have talked. We start with a short scoping call to confirm your Business Central version and deployment model, your Kaufland seller account and marketplace scope, the item and category mapping you need, and how settlement postings should hit your chart of accounts. You get a fixed scope and quotation before any development starts. Typical delivery is one working week from confirmed scope: we build against your version, install and configure in a sandbox, run UAT with your team on staging, then deploy to production with a rollback plan. You receive the source code, the git repository, technical and user documentation, a training session and a post-go-live support window.