> 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/sell-on-marketplaces/mirakl-marketplaces/how-to-set-up-a-but-channel.md).

# How to set up a But channel

But is a French online store specializing in furniture, home decor, and interior equipment. They offer a wide range of affordable products, including high-tech items and household appliances.

In this article, you'll learn how to set up a But channel to create and manage listings on But.

***

### Before you start

**You'll need**

* A Mirakl SSO account
* A project in Channable with your imported products

**Good to know**

* But requires all listing descriptions to include important information related to the delivery of the product (e.g. shipping time, delivery method). Without this information, But will reject your listing.

{% stepper %}
{% step %}

### Create a But channel

{% tabs %}
{% tab title="Modern version" %}

1. In Channable, go to **All projects**.
2. Select **\[your project]**.
3. Go to **Channels**.
   {% endtab %}

{% tab title="Legacy version" %}

1. In Channable, go to **Projects > \[your project] > Channels**.
   {% endtab %}
   {% endtabs %}

2. Click **+ Create channel**.

3. In the search bar, enter “But” and select **But**.

4. Set your channel settings:
   1. For **Name**, give your channel a descriptive name.
   2. For **Unique ID per item**, select the field containing your product IDs. This is often `id`.
   3. For **Language**, select the language your product data is in.
   4. For **Use master rule group**, select a master rule group if you have one.

5. Click **Save**.
   {% endstep %}

{% step %}

### Categorize your items

Categorize your items to match But's taxonomy and appear in the right place.

1. Go to the **Categories** step.
2. Choose your categorization method:
   1. **Generate from field:** Select a category field, such as `product_type` or `category`.
   2. **+ Add category rule:** Add text-based conditions to assign categories in bulk.
   3. **Copy from channel:** Reuse categories from another channel.
3. Click **Save**.
   {% endstep %}

{% step %}

### Create rules to fill data gaps

Use rules to prepare product data for But. Create project fields for missing data. Then populate them with rules. You can also adjust existing fields for But's requirements.

* **Rule templates:** Use common rules, then adapt them to your needs.
* **Rules setup:** Filter, modify, or enrich data for marketplace requirements.
  {% endstep %}

{% step %}

### Map shared attributes

Link project fields to attributes that apply across your But catalog.

1. Go to the **Build** step.
2. Map attributes marked **Required by marketplace**.
   1. Click the dropdown and select the project field containing the data.

{% hint style="info" %}
Some attributes support custom or supported values. These values apply to every item.
{% endhint %}
{% endstep %}

{% step %}

### Map category attributes

Category attributes apply to products in specific categories.

1. In the **Build** step, click the **Attributes per category** tab.
2. Select a category from the list.
3. Map attributes marked **Required by marketplace**.
   1. Click the dropdown and select the project field containing the data.
4. Click **Save**.

<details>

<summary><strong>Adding multiple attribute values in Mirakl</strong></summary>

Separate multiple attribute values with a pipe symbol (`|`). This helps Mirakl detect and process each value.

</details>

**Indicate whether an item is a single item or a parent/child variant**

Map the following attributes for parent and child items:

* For **SellerProductId**, map the field containing the parent ID.
* For **SellerArticleId**, map the field containing variant item IDs.

For single products without variants, enter the same value for **SellerArticleId** and **SellerProductId**.
{% endstep %}

{% step %}

### Additional requirements for But

The following requirements are specific to But.

#### Shared attributes — Item section

* Shipping class (logistic class): Enter the logistic class of your product to determine shipping costs.
* Lead time to ship: Indicate shipping time in days (time until package is handed to shipping).
* Eco-contributions: If operating in France, add eco-contributions to your offers. See the list of [available EPR categories](/list-advertise/sell-on-marketplaces/mirakl-marketplaces/setting-up-mirakl-eco-contributions.md).
* Price excl. VAT: Indicate the VAT; set the value to "20".
* Private Copy Tax: For applicable blank media items, specify the 'copie-privée' levy amount in euros.
* Warranty list: Indicate the legal guarantee of 2 years (use "2-years" with a dash).

#### Title Requirements

* Maximum number of characters: 100
* Title structure: Product type, function, style, color, material, dimensions
* Brand name exclusion: Do not include the brand name in the title (the trademark field is automatically placed before the title on the site).
* Dimensions: Specify units (e.g., H.10 cm). Do not use acronyms. Example: Ø
* No commercial terms: Do not display terms like "Exclusive", "New", "Top seller", etc.
* Special characters: Do not include special characters (e.g., Greek letters).
* No leading dash: Do not start the title with a dash.

#### Image Requirements

* First visual: Must be on a white background, detoured (cut out).
* Positioning: From the front or a ¾ angle.
* Number of visuals: Up to 6 visuals showcasing different angles (background photo, diagram, accessories, details, etc.).
* Recommended formats: 2000×2000 pixels, 3000×3000 pixels.

#### Description Requirements

{% hint style="warning" %}
**Important:** The Description attribute is mandatory. It must include information about shipping time, delivery method, and any other carrier-delivery details. Without this information, But will reject your listing.
{% endhint %}

* Character limit: Max 8,000 characters.
* No external links: Avoid links or references to external sites or shops.
* Use HTML for enhancement: HTML can be used to enrich descriptions (HTML is blocked on Mirakl by default; contact your account manager to enable it).
  {% endstep %}

{% step %}

### Check the quality of your setup

The **Quality** step provides feedback before activation. It highlights mandatory and optional errors in your product data.

Resolve mandatory errors first.

**Actions**

* **View items:** View products with a specific issue.
* **View in build:** Open the **Build** step to map missing information.
* **Set categories:** Open the **Categories** step to categorize products.
* **Show source:** For ID fields, open the **Settings** step.
  {% endstep %}

{% step %}

### Preview before activating

The **Preview** step shows attributes mapped in the **Build** step. Use it to review product data and potential errors.

**Filtering**

* **Filter by error:** Use the **All** dropdown to show products with errors.
* **Filter by category:** Use the **All categories** dropdown to show a category.
  {% endstep %}

{% step %}

### Connect to But

Connect your channel to your Mirakl SSO account before sending listings.

{% hint style="success" %}
Linking your account does not change existing listings. Listings change only after activation.
{% endhint %}

1. In **\[your But channel]**, go to **Settings**.
2. At **Linked seller account**, click **Select seller account**.
3. Select an existing seller account, or click **+ Add a new connection**.
4. If adding a seller account:
   1. At **Connect with**, click **But** to select it.
   2. For **Label**, give your connection a descriptive name, such as “But FR”.
   3. For **Shop ID**, paste the Shop ID for the platform where you list.
   4. Click **Connect with But**.

You will be redirected to Mirakl to log in and verify your connection. Confirm any permissions. You will then return to Channable.

5. Click **Create** to finalize your connection.
   {% endstep %}

{% step %}

### Activate and run your channel

1. Select the **Settings** step in **\[your But channel]**.
2. Click **Activate API**.
3. Click **Save**.
4. Click **Run now** to send your product listings to But.
   {% endstep %}

{% step %}

### Review and fix listing errors

After you run your channel, But provides feedback about missing listing data.

Go to the **Result** step and click the **Feedback** tab.

#### Resolve errors

1. In **Description**, click on the error name. This shows an overview of products with that error.
2. In **ID**, click the ID number and scroll to the red error callout. Hover over it for more information.
3. If the error is a mapping error, click **View in build**. This opens the attribute to map or remap.
4. For information about the attribute and accepted values, hover over the attribute help icon.
5. Resolve the error, then click **Run now** to resend your listings.
   {% endstep %}
   {% endstepper %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpcenter.channable.com/list-advertise/sell-on-marketplaces/mirakl-marketplaces/how-to-set-up-a-but-channel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
