> 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/changelog/2026/april.md).

# April

{% updates format="full" %}
{% update date="2026-04-23" tags="new" %}

## Creatives: New Brand Kit

### What's new?

We’ve launched the Brand Kit in **Creatives**, a central place at company level in Channable to manage your brand’s visual identity. Instead of manually entering hex codes or searching through folders every time you create an image, you can now upload and store your specific colors, fonts, and images in one place. These assets are automatically pinned as shortcuts in the Image Editor for easy access.

#### Benefits of using the brand kit:

* **Eliminate manual errors:** Your exact brand colors are now saved and ready to use, ensuring 100% compliance with brand guidelines.
* **Time saving:** Brand-approved fonts and images are now prioritized at the top of selection lists, removing the need to re-add assets.
* **Unified workflow:** Manage your assets globally in Creatives or add new brand elements directly from the Image Editor.

### How to access the Brand Kit:

1. Go to **\[your company] > Creatives**.
2. Go to the **Brand kit** tab. Here you can manage your library of images, colors, and fonts using the **Add** buttons in each section.

<figure><img src="/files/OBOeKtzrIFVjhZO2ZmSq" alt=""><figcaption></figcaption></figure>

OR in the Image Editor:

1. Colors: Access your palette directly from the color picker.
2. Images: View brand-specific assets at the top of the image selector.
3. Fonts: Select your preferred brand fonts from the top of the dropdown list or upload custom ones instantly.
   {% endupdate %}

{% update date="2026-04-14" tags="improvement" %}

## New project fields now appear immediately in feeds

### What's new?

New project fields now appear in your feed as soon as you create them.

Previously, new project fields only became available in the feed after the next import run. In larger projects, that delay could take time and cause features like **Feed Quality** and **Rules** to fail if they referenced fields that already existed as project fields.

#### Immediate project field availability includes:

* **No wait for the next import:** New project fields appear in the feed right away.
* **Fewer broken setups:** Your project no longer depends on a completed import before using a new field.
* **Better feature compatibility:** Features like **Feed Quality** and **Rules** can reference new fields immediately in most cases.

{% hint style="info" %}
There are still a few minor edge cases for nested fields and for fields whose values come from an import. In those cases, an import run may still be needed before everything behaves as expected.
{% endhint %}
{% endupdate %}

{% update date="2026-04-08" tags="info" %}

## AliExpress channels can no longer be created

As of April 8, 2026, you can no longer set up an **AliExpress** channel in Channable to list your items on AliExpress. Affected customers have been contacted by our team.

#### **Why was AliExpress deprecated?**

We decided to discontinue support for AliExpress due to high maintenance cost outweighing its usage.

This change allows us to allocate resources towards enhancing features, boosting support for more popular channels, and developing integrations for the platforms you want to see from us that we don't yet support.
{% endupdate %}

{% update date="2026-04-01" tags="new" %}

## Shopify Markets importer now supports metaobjects

### What’s new?

Importing Shopify Markets metaobjects is now supported in Channable. You can now import metaobjects through the Shopify Markets import method.

For example, instead of adding separate metafields for washing temperature and care guidelines to every silk scarf, you can create one **Silk Care** metaobject and link it to all relevant products.

If you later add more care information, you only need to update the metaobject once. All linked products and variants then reflect that change automatically.

#### Shopify Markets metaobjects support includes:

* **Reusable structured data:** Group related custom data in one metaobject instead of creating separate metafields for each value.
* **Metaobject references:** Import metaobjects linked through metafields at both product and variant level.
* **Translated fields:** Import translated metaobject field values, just like translated metafields.
* **Easier maintenance:** Update one metaobject in Shopify and all linked items stay aligned.
* **More flexible product data:** Add complex custom data like care instructions, materials, ingredient sets, or warranty details.

<figure><img src="/files/CSSTMWSe46LOz4W36bOA" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/TmuGfa6kIlSm7miYgtdb" alt="" width="375"><figcaption></figcaption></figure>
{% endupdate %}
{% endupdates %}


---

# 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/changelog/2026/april.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.
