> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/magento-2-api-connector/magento2_en_us/whats-new.md).

# What's New

Here you can find the most important updates to the standard connector in an easy-to-understand format. Current documentation status: **App Version 27.10.0.16**.

{% updates format="full" %}
{% update date="2026-07-13" %}

## Safely Process Product Options in Orders

* Selected Magento options remain visible directly below the associated item in the BC Sales Order.
* Option quantities are tracked separately from shipment and invoice quantities. This means pure information lines no longer block posting.
* Existing option lines are automatically repaired during updates without losing their business quantity.
  {% endupdate %}

{% update date="2026-07-12" %}

## Download Orders More Selectively and Diagnose More Easily

* Individual Magento orders can be loaded into the Sales Order Dashboard by their visible order number.
* Missing product options can be reloaded for an existing Sales Order without duplicating existing lines.
* Payment, shipping, and posting setups are validated more robustly; error messages lead more directly to the affected shop configuration.
  {% endupdate %}

{% update date="2026-06-15" %}

## Safe Migration Check After Shop Migrations

* The migration check compares payment methods, shipping methods, taxes, attributes, websites, Store Views, and customer groups against the currently connected Magento system.
* Changed or new server values can then be selectively remapped; existing BC targets are preserved.
* Product names are fully transferred during upload, provided they are maintained in the designated shop text.
  {% endupdate %}

{% update date="2026-05-01" %}

## More Control Over Catalog and Product Download

* Product options can be rebuilt from Magento attributes or selectively reloaded for individual items.
* Duplicate Magento attributes can be cleaned up without losing existing item assignments.
* The product download works resumably in batches and shows success, errors, or intentionally skipped products in a dedicated log.
  {% endupdate %}

{% update date="2026-04-28" %}

## Guided Setup, Mapping Hub, and MSI

* A Setup Wizard guides you through eight steps from connection to operational readiness.
* The Mapping Hub shows open mappings as clear tiles and supports Auto-Map as well as controlled creation of missing BC master data.
* Inventory can be linked per Magento MSI source to BC locations.
* Store Views support language-specific product and category texts.
  {% endupdate %}

{% update date="2026-02-20" %}

## Manage Categories Conveniently via Drag and Drop

* Categories can be sorted and rearranged in a tree view.
* Changes are initially marked and only saved after confirmation.
* Search, inline editing, and visible change counters simplify daily catalog maintenance.
  {% endupdate %}
  {% endupdates %}

{% hint style="info" %}
This page describes the standard scope. Custom extensions are documented only in the respective project documentation.
{% endhint %}


---

# 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://docs.solutioo.de/magento-2-api-connector/magento2_en_us/whats-new.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.
