Fulfillment by Kaufland

Fulfillment by Kaufland (FBK) is a service offered to sellers where Kaufland is taking over the fulfillment to the customers. Since processes in FBK are fundamentally different the Marketplace Seller API also works differently for the new fulfillment type.
Right now there are two fulfillment types:

  • fulfilled_by_merchant
  • fulfilled_by_kaufland

All endpoints are built in a way that you only receive non-FBK information and you can ignore the fulfillment type fields. At the same time this means if you want to get FBK information via API you need to explicitly request it.

Managing Inventory

In general you are not able to create, update or delete units with fulfillment_type=fulfilled_by_kaufland via API. These units can right now only be managed via Seller Portal. If you still try to manipulate a FBK unit, the server will respond with a HTTP 400 error code (Message: Parameter [fulfillment_type] is missing or has wrong value).

Yet you may receive FBK units via the API. GET /units endpoint has a filter fulfillment_type where you can explicitly request FBK units. Single FBK units can be retrieved via /units/{id_unit}. The response always includes the fulfillment type.

Furthermore it is not possible to create or update FBK units via file. If you try to update a FBK unit via file this line of the import will be skipped. The rest of the import continues as usual.

Managing Orders

In general you are not able to update or cancel orders with fulfillment_type=fulfilled_by_kaufland. If you try to operate with one FBK order, the server will respond with a HTTP 403 error code (Message: Access forbidden. The method cannot be executed for entity fulfilled by Kaufland.).

You can still retrieve details of these orders including the parameter fulfillment_type=fulfilled_by_kaufland to your GET requests. These orders can be retrieved as soon as the orders are created (order status=open) by sending GET requests to the /orders endpoint. You can also retrieve your order units directly, by sending GET requests to the /order-units endpoint.

All order-units of one order will have the same fulfillment type. At the same time fulfillment type is part of the order and order-unit model in order to make this information accessible as easy as possible. If customers buy two units of different fulfillment types at the same time this will be split up into two orders.

Managing Order Invoices

You may upload and create the invoices of your FBK orders, with the same procedure as invoice uploads for the orders fulfilled by sellers.

Managing Tickets

In general for the FBK service our Kaufland.de Customer Service handles the ticket communication with the customer when there is a problem with an FBK order. Nevertheless, there can be cases where we require your help processing a ticket e.g. the customer needs an invoice. In those cases you will be involved in a given ticket. FBK tickets in which you are involved can be received, responded to and closed. FBK tickets in which you are not involved cannot be retrieved, responded to or closed.

You may receive FBK tickets via the API. GET /tickets endpoint has a filter fulfillment_type where you can explicitly request FBK tickets with fulfillment_type=fulfilled_by_kaufland. Single FBK tickets can be retrieved via /tickets/{id_ticket}. The response always includes the fulfillment type.

You are able to respond to a FBK ticket in which we require your help using the POST /tickets/{id_ticket}/messages endpoint. You can close a ticket in which we require your help by sending a PATCH request to the /tickets/{id_ticket}/close endpoint. You cannot open tickets on FBK order-units using the POST /tickets endpoint. Opening tickets is only possible for order-units that are of fulfillment_type = fulfilled_by_merchant.

Tickets always have a 1-to-1 connection with order-units. That also means that a ticket and an order-unit which are connected do have the same fulfillment type. At the same time fulfillment type is part of the ticket and the order-unit model in order to make this information accessible as convenient as possible.

Managing Returns

You can only retrieve details for returns with fulfillment_type=fulfilled_by_kaufland. You can do so doing a GET request to /returns or /returns/{id_return} for further details, including the the appropriate filter parameter fulfillment_type=fulfilled_by_kaufland. You can not initiate a return for fulfillment_type=fulfilled_by_kaufland. If you still try to initiate it, you will get an HTTP 403 error code (Message: Access forbidden. The method cannot be executed for entity fulfilled by Kaufland.).

Managing Reports

FBK offers are not included in account-listing and account-listing-with-shop-price reports. These reports only include offers fulfilled by the seller.

As for the Sales reports, you may retrieve the report in the Sales Report new business model as of 2.7.2018, where the fulfillment type is specified in the fulfillment_type column. Older formats of the sales report, old business model until 2.7.2018 and old format in business model till 2.7.2018 include FBK orders but do not differentiate them from other orders fulfilled by sellers.

For cancellation report, it includes FBK orders but does not differentiate them from other orders fulfilled by sellers.

Managing Push Notifications

With the push notifications feature, you can get immediate notifications on certain events regardless of your fulfillment type, therefore including FBK.