Kaufland
Purpose
Kaufland Marketplace becomes a sales channel. Among the marketplaces Kaufland is the strictest case: selling happens against an EAN that already exists in the catalogue — creating items on demand is not possible.
Scope
- Prices and stock work normally.
- Orders and fulfilment as with any channel.
- Every request is signed (HMAC-SHA256 over method, address, body and timestamp).
- Two settings per channel: storefront and unit id.
Interplay
The channel is a sales channel in the sense of Channels — not a special path beside the document. Items, prices and stock come from the product catalogue and stock; incoming orders become regular sales orders and travel through warehouse, shipping and invoicing like any other order. Credentials live as an integration under Integrations in the encrypted store. Flows and mappings at the system boundary — which field goes where, when a sync runs — belong to OctiConnect; conditions and waiting times remain the business of automations.
Limits
- No catalogue push. A Kaufland offer requires a catalogue item. The channel reports this openly
so the framework does not even try — otherwise errors would appear that look like outages and are in truth configuration.
- The client id is not a signature and therefore lives in the integration next to the signing
key, not in the channel configuration: that one goes out over the API to anyone with read permission.
- The real run is still outstanding. What is verified is that we ask correctly and read the
answer correctly — not that Kaufland accepts the request. A real seller account is missing.