> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/list-advertise/bol/list-items-on-bol/how-to-configure-fbb-lvb-and-fbr-for-bol/how-do-i-set-my-delivery-code-for-bol.md).

# Set a delivery code for bol items

Learn how to tell bol how quickly you deliver your products, for all items at once or per item.

The delivery code (leverbelofte) is the delivery promise bol shows to customers, such as "ordered before 18:00, delivered tomorrow".

You set it with the **Delivery code** attribute in the **Build** step of your bol channel. Items that use FBR or the fulfillment auto switch need a valid delivery code, or bol can't update them.

| Your situation                                                                            | Use                                    | See                                                                                 |
| ----------------------------------------------------------------------------------------- | -------------------------------------- | ----------------------------------------------------------------------------------- |
| All items have the same delivery time                                                     | A supported value, such as `24uurs-18` | [Use one code for all items](#use-one-code-for-all-items)                           |
| Delivery times differ per day of the week, and you've set them in your bol seller account | `MijnLeverbelofte`                     | [Use your bol delivery settings](#use-your-bol-delivery-settings-mijnleverbelofte)  |
| Delivery times differ per item                                                            | A project field filled with a rule     | [Use different codes for different items](#use-different-codes-for-different-items) |

### Use one code for all items <a href="#use-one-code-for-all-items" id="use-one-code-for-all-items"></a>

1. In **\[your bol channel]**, go to the **Build** step.
2. For **Delivery code**, click **Supported values**.
3. Select the code that matches your delivery time, such as `24uurs-18`.
4. Click **Save**.

### Use your bol delivery settings (MijnLeverbelofte) <a href="#use-your-bol-delivery-settings-mijnleverbelofte" id="use-your-bol-delivery-settings-mijnleverbelofte"></a>

With MijnLeverbelofte, bol uses the delivery times you set per day of the week in your bol seller account. Bol picks the right promise based on when the customer orders. This is the only way to offer next-day delivery on weekends, which bol's standard codes don't support.

1. In your bol seller account, set your delivery times per day.
2. In **\[your bol channel]**, go to the **Build** step.
3. For **Delivery code**, click **Supported values** and select `MijnLeverbelofte`.
4. Click **Save**.

The value is case-sensitive, so select it from the list rather than typing it. After you change it, bol can take up to 24 hours to show the new delivery promise.

### Use different codes for different items <a href="#use-different-codes-for-different-items" id="use-different-codes-for-different-items"></a>

If your import already has a field with bol delivery codes, skip to step 4. Make sure its values exactly match bol's codes.

1. Go to **Setup** > **Project fields**, click **+ Add project field**, and create a field such as `bol_delivery_code`.
2. In **\[your bol channel]**, go to the **Rules** step and create a rule that fills the field.
3. Go to the **Build** step. For **Delivery code**, select your delivery code field.
4. Click **Save**.

{% hint style="info" %}

#### Example rule: Delivery code per supplier

Promise slower delivery for items that ship from an external supplier.

**IF** `supplier` `is equal to` `external`

**THEN** `set value` of `bol_delivery_code` to `2-3d`

**ELSE** `set value` of `bol_delivery_code` to `24uurs-18`
{% endhint %}

{% hint style="info" %}

#### Example rule: Delivery code per day of week

Promise a longer delivery time on weekends, using a [date condition](https://helpcenter.channable.com/manage-improve-product-data/rules-bulk-edit-and-enrich/how-to-use-conditions-if-in-rules/rule-conditions-dates).

**IF** `today` `is on` `Saturday` or `Sunday`

**THEN** `set value` of `bol_delivery_code` to `2-3d`

**ELSE** `set value` of `bol_delivery_code` to `24uurs-18`
{% endhint %}

{% hint style="info" %}

#### Example rule: Delivery code from stock

Use the fast promise only when you have stock, and a slower one when you need to reorder.

**IF** `stock` `is greater than` `0`

**THEN** `set value` of `bol_delivery_code` to `24uurs-18`

**ELSE** `set value` of `bol_delivery_code` to `2-3d`
{% endhint %}

The code only changes when your channel runs, so check that your project schedule runs often enough for the switch to happen on time.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpcenter.channable.com/list-advertise/bol/list-items-on-bol/how-to-configure-fbb-lvb-and-fbr-for-bol/how-do-i-set-my-delivery-code-for-bol.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
