> 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/master-data-management/images-and-related-items.md).

# Images and Related Items

The connector transfers main/additional images and product relationships such as related, up-sell, or cross-sell.

### Images

1. Attach an image to the item.
2. Verify role, sort order, and label.
3. Upload the product first with a unique identifier.
4. Run Image Upload.
5. Verify the media gallery in Magento.

### Related Items

1. Maintain the relationship type and target product in BC.
2. Upload both products.
3. Run Pending Related Items.
4. Verify the product detail and cart.

{% hint style="warning" %}
If the Magento ID/SKU of a source or target product is missing, media or relationships cannot be created reliably.
{% endhint %}

Process large image volumes in controlled batches and check for stale relationships when deleting items.


---

# 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/master-data-management/images-and-related-items.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.
