> ## Documentation Index
> Fetch the complete documentation index at: https://docs.armin.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# bol.com

> Handle bol.com customer questions as tickets with live order data, and let AI Agents cancel items or handle returns.

The bol.com integration turns the customer questions bol.com relays to your support inbox into clean tickets with the order attached, so your team (and your AI Agents) can answer bol.com buyers from the same place they handle every other channel. Replies go out as normal email.

## When to use it

Use bol.com in Chatarmin CX when:

* you sell on bol.com (Netherlands and Belgium) and buyers send you questions through bol.com
* you want those questions shown with the order number and the buyer's own words instead of raw relay emails
* you want to see the live order and its returns next to the ticket
* you want AI Agents or macros to reply to bol.com buyers the same way they reply to email, and AI Agents to cancel items or handle returns with your approval

> [!NOTE]
>
> bol.com is rolling out gradually. If you don't see **bol.com** under Integrations yet, [contact support](mailto:support@chatarmin.com) to get access.

## How it works

There are two parts, and they work independently:

1. **Customer questions arrive by email.** bol.com already emails every customer question to the support address in your bol.com account, from a relay address ending in `@partnerplatform.bol.com`. Chatarmin CX reads those emails in your connected inbox. It does not fetch messages from bol.com. It picks out the order number, bol.com's case ID, and the buyer's message, and shows the ticket as **bol.com** in the inbox. Under the hood it is still an email ticket, so your email rules, workflows, and AI Agents still apply.
2. **Order data comes from bol.com.** Once you connect your bol.com Retailer account, Chatarmin CX uses the order number from the email to load the live order from bol.com: its status, items, shipping address, and returns.

Replies are ordinary email, so the linked email channel's sending limits apply. There is no separate bol.com limit to configure.

## Set it up

You need **Admin** access in Chatarmin CX (the **Manage integrations** permission) and access to your bol.com Seller Dashboard.

**1. Create API credentials in bol.com**

In the bol.com Seller Dashboard, go to **Instellingen** → **API Instellingen** and create **Client credentials voor de Retailer API**. Copy the **Client ID** and the **Client Secret**. bol.com shows the secret only once, so keep it somewhere safe until you have connected.

**2. Connect bol.com in Chatarmin CX**

Go to [Integrations → bol.com](https://armin.cx/app/_/settings/integrations/bol_com) and click **Connect**. Paste the Client ID and Client Secret, then click **Connect**. Chatarmin CX checks the credentials with bol.com before it saves anything. If they are wrong, you see an error and nothing is saved. The connected account is named after your bol.com shop name.

**3. Check that your support inbox is connected**

Make sure the email address bol.com sends customer questions to is connected as an [email channel](https://docs.armin.cx/channels/email/intro.md) in Chatarmin CX. If your team already answers bol.com questions from that inbox, you don't need to change anything. There are no bol.com notification settings to change.

### Test it

Find a recent bol.com customer question in your inbox, or wait for the next one. It should show as **bol.com** in the ticket list, with the buyer's message on the ticket. Open it and check the bol.com order card in the sidebar: it shows the order status, items with price and offer reference, total, shipping address, and any returns. If the ticket still shows as plain **Email**, see Troubleshooting below.

## Order data in the ticket

The bol.com order card shows:

* the order status and the items with their price and offer reference
* the order total and shipping address (fields bol.com anonymises are hidden)
* a **Cancellation requested** tag when the buyer asked bol.com to cancel
* returns for the order, with their handling status and RMA ID

If the order number doesn't match an order on your connected account, the card shows an empty state. For returns, Chatarmin CX checks the newest 50 handled and the newest 50 unhandled returns on your account.

## Reply to bol.com customers

Open the ticket like any other and use **Send reply**. Your message goes out as a normal email reply through the linked inbox, and bol.com relays it to the buyer.

> [!NOTE]
>
> AI Agents can draft and send replies on bol.com tickets the same way they do on email. No separate setup is required.

## AI Agent actions

Give an [AI Agent](https://docs.armin.cx/ai-agents/skills-and-actions.md) bol.com actions when you want it to look up orders and returns, or act on them. Connect bol.com first, then enable the actions on the agent and pick which connected bol.com account it may use.

### Read actions

* **Get bol.com order**: Look up an order by number, or the order the conversation is about.
* **Get bol.com returns**: Look up one return, or the returns of an order (from the newest 50 handled and 50 unhandled returns).

### Write actions

* **Cancel bol.com order item**: Cancel one item that has not shipped yet. bol.com refunds the buyer. A shipped item goes back through a bol.com return instead.
* **Handle bol.com return**: Record how a return was handled, using one of the six results bol.com lets retailers set, for example **Return received** or **Exchange product**. **Still approved** reverses an earlier rejection.

Both write actions require [human approval](https://docs.armin.cx/ai-agents/human-in-the-loop.md) by default. A cancellation can't be undone, so keep approval on until you trust the agent's instructions.

In a customer conversation, the actions only work on the order named in the buyer's bol.com email, so an agent can't act on another buyer's order. Test runs simulate write actions instead of changing anything on bol.com.

## Disconnect or reconnect

* **Reconnect:** if bol.com rejects the saved credentials, for example because you deleted or replaced them in the Seller Dashboard, the account shows **Reconnect required**. Create new credentials in bol.com, click the account in [Integrations → bol.com](https://armin.cx/app/_/settings/integrations/bol_com), and enter the new Client Secret. The Client ID is already filled in; change it too if you created new credentials. Saving clears the warning.
* **Disconnect:** go to [Integrations → bol.com](https://armin.cx/app/_/settings/integrations/bol_com), open the account's status menu, and choose **Disconnect**. This removes the bol.com connection, so order data and AI Agent actions stop working. Your email channel and existing tickets stay. To connect again later, repeat **Set it up** above.

## Troubleshooting

| Symptom | What to check |
| - | - |
| bol.com tickets show as **Email**, not **bol.com** | Only customer questions bol.com relays from an `@partnerplatform.bol.com` address show as bol.com. Notices from `klantbericht.bol.com`, `verkopen.bol.com`, and `automail@bol.com` are account notices, not buyer messages, so they stay plain email. |
| No customer questions arrive | Check that the support email address in your bol.com account is the one connected as an email channel in Chatarmin CX. |
| No order data on the ticket | Check that the account under **Integrations → bol.com** doesn't show **Reconnect required**, and that the order belongs to the connected bol.com account. Order numbers a buyer types with dashes are not recognised. |
| A follow-up message has no order number | Follow-up emails that only name the case keep the order number from the first email of that case. If the first email never arrived in Chatarmin CX, there is no order number to carry over. |
| A return is missing from the order card | Only the newest 50 handled and newest 50 unhandled returns are checked. Look up older returns in the bol.com Seller Dashboard. |
| Replies never reach the buyer | Check that the linked email channel can send (its own connection is healthy). bol.com relays replies automatically, so there is no approved-senders step. |
| **Reconnect required** on the account | bol.com rejected the saved Client ID or Client Secret, usually because the credentials were deleted or replaced in the Seller Dashboard. Create new credentials and reconnect; see **Disconnect or reconnect** above. |
| Connecting shows an error | Check that you copied the Client ID and Client Secret of **Client credentials voor de Retailer API**, without extra spaces. Nothing is saved until bol.com accepts them. |

If none of these resolve it, [contact support](mailto:support@chatarmin.com) with the affected ticket or bol.com order number.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.