German and EU sellers on Kaufland.de Marketplace typically run their catalog, stock, and finances in ERPNext but manage Kaufland in a separate seller portal. That gap means someone re-keys every incoming Kaufland order into a Sales Order, watches for oversells when the same SKU is listed on multiple channels, exports tracking numbers by hand to release payment, and rebuilds the marketplace settlement in a spreadsheet before it can be reconciled against bank payouts. ERPNext core has no native Kaufland integration, and the Kaufland Marketplace Product API (Shop API) uses request signing and its own product/order/unit data model that ERPNext cannot talk to out of the box. That is where a native ERPNext build is worth doing rather than living in the portal.

ECOSIRE builds a proper Frappe app — installed on your bench, not a hosted middleware — that treats Kaufland as a first-class sales channel inside ERPNext. We add DocTypes such as Kaufland Settings (single, for API credentials and store defaults), Kaufland Channel, Kaufland Listing, and Kaufland Order Log, plus a mapping layer between your ERPNext Items and Kaufland EANs/units. A dedicated API client handles Kaufland's HMAC request signing and pagination, so credentials live in ERPNext and never in a spreadsheet. Incoming orders are pulled on a schedule and converted to ERPNext Sales Orders (and, where you want it, Sales Invoices and Delivery Notes) with the buyer, shipping address, marketplace fees, and Kaufland order id preserved for audit.

Technically, the connector is wired into ERPNext the way an ERPNext developer expects. hooks.py doc_events fire on Delivery Note / Shipment submit to write tracking numbers and carrier back to Kaufland automatically; scheduler_events (cron/hourly) drive order polling, inventory push, and settlement fetch as enqueued background jobs so nothing blocks the desk. Inventory and price sync are two-way: ERPNext Bin quantity and Item Price changes propagate to Kaufland listings, and we can apply channel-specific pricing rules so your Kaufland price isn't your default selling price. Whitelisted methods (@frappe.whitelist()) expose manual "sync now" actions, and client scripts add the buttons and status indicators on the relevant forms. Access is controlled with a dedicated Role and Role Profile so warehouse and finance staff only see what they should, and every API exchange is logged for troubleshooting.

Because this is build-to-order, you are not downloading a generic plugin and hoping it fits. We scope your exact channel setup — single or multiple Kaufland storefronts, ERPNext version (v15 or v16), warehouse and tax configuration, and how you want orders, shipping, and VAT to land — then build against your instance. You receive the full source of your version of the app, we install and configure it on a staging bench first, run UAT with your real SKUs, and only then cut over to production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope, and you own the code afterward.