Returns
Introduction
The Returns resource inside the Retailer API allows you to manage all return related activities that are concerned with the physical aspects of customer returns. It provides detailed information on returns that are registered by a customer or customer service and allows you to process returns or to create a return on behalf of the customer. Within the return-related data, you can find feedback that was provided by you or one of our warehouses in the case of Logistics Via bol.
Return structure
A return request is identified by a returnId
. A single return can contain one or more return item(s) related to one or more order id(s). The return items are identified by a rma-id
. Actions that you perform on the API are always on a specific item within a return. This means that you will always provide feedback on the rma-id level, and not on return-id. If you create a new return, the API will automatically create a return-id and an rma-id for you.
Create a return
Create a return: creates a return for a customer.
Creating a return allows you to create a return on behalf of the customer. You can create a return up to 90 days after the shipping date, if the customer sent the product to you without registering it. With this endpoint, you can therefore create a new return and credit the customer if the return was properly received. By creating a return, it will also become visible for the customer itself.
In order to create a return, you need to supply the order-item-id that you will find on the package, the amount of quantity that has been returned by the customer, and the way you want to handle this return. In case you want to handle items differently, you can create 1 or more return requests. Please be aware that you can never create more returns than the amount the customer originally ordered.
When creating a return, the customer will receive feedback through email.
Get returns
Get returns: returns a list of handled or unhandled returns.
The retrieve returns endpoint retrieves a list of returns for the retailer, that are registered by either the customer or customer service. You can also create your own returns which are visible through this endpoint.
The get returns endpoints allow you to filter on handled
returns (true
or false
). Handled returns are returns that are already handled by you. Unhandled returns are returns that still require an action from your side.
In addition to handled
, you can use the fulfilmentMethod
parameter to either filter on FBB (LvB) returns or FBR returns. Once feedback is received on a specific return item, it will be processed and change the return status to HANDLED.
Get a return by return id
Get a return by return id: returns the details of one single return.
The Get a return by return id call allows you to retrieve all the details of a single return. A single return can contain 1 or more return items that are identified by a return ID.
Handle a return by rma id
Handle a return by rma id: handles a return created by the customer.
You can use this endpoint to handle a return that was received from the sender. Be advised that handling a return is always per single return item using an rma-id
. As a partner you can specify how the state of the return must be registered and depending on the handling result supplied the customer will receive his/her money back. This action will eventually lead to one or more processing results, which are closely related to the supplied handling result and can be one of the following values:
-
ACCEPTED
: the return is accepted -
REJECTED
: the return is rejected -
CANCELLED
: the return is cancelled
This endpoint allows you to update the handlingResult of a return multiple times per rma-id .
|
To change the processing result of a return from REJECTED
to ACCEPTED
, set the handlingResult
to STILL_APPROVED
.
Return handling results
The table below shows all possible return handling result values. Retailers can only use the ones that are marked to be used by "bol and retailer", while the other results are read-only from the retailer’s standpoint.
Handling result | Is used by | Meaning | Processing result | Refunded through bol? | ||
---|---|---|---|---|---|---|
|
bol and retailer |
Return is received as expected and approved. |
|
Yes |
||
|
bol and retailer |
In consultation with the customer, the product will be exchanged or replaced. |
|
No |
||
|
bol and retailer |
Return did not met the expectation/condition. |
|
No |
||
|
bol and retailer |
You will take the lead in repairing the product for the customer. |
|
No |
||
|
bol and retailer |
Customer is allowed to keep the product. |
|
No |
||
|
bol and retailer |
In consultation with the customer, the return is still approved after an initial rejection. With this handling result, you can still refund the customer.
|
|
Yes |
||
|
bol |
Customer is allowed to keep the product with no costs. |
|
Yes |
||
|
bol |
Somewhere on its way back to the seller the return item was lost |
|
Yes |
||
|
bol |
The time between registering a return and sending it back took more than 14 days. The return is therefore cancelled. |
|
No |
||
|
bol |
Feedback with more quantity than ordered was supplied. |
|
No |
||
|
bol |
The return was reported lost but was still received. |
|
No |
||
|
bol |
The customer decided to cancel his/her return |
|
No |
||
|
The transporter failed to create a shipping label. The return is therefore cancelled. |
|
No |
|||
|
bol |
Suspicions of fraud by customer. Return will be assessed by our Logistics Service Team within two weeks, after which the item will either be accepted or rejected (in case of fraud). |
Initially none, and the final processing result depending on the outcome of the investigation could any of |
This depends on the outcome of the investigation, at which point the handling result will change to one of the following:
|
||
|
bol |
The error indicates a failure in retrieving something, possibly due to logistical or technical issues. The accompanying message suggests that a return item could not be collected. |
|
No |