> 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/item-card-and-simple-products.md).

# Item Card and Simple Products

The BC Item Card is extended with Magento fields and direct actions for product, inventory, and images.

### What Must Be Correct Before Upload

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Identity</strong></td><td>Item number, unique Magento SKU, and product type.</td></tr><tr><td><strong>Shop Presentation</strong></td><td>Name, description, visibility, status, and websites.</td></tr><tr><td><strong>Classification</strong></td><td>Attribute set, categories, attributes, and tax class.</td></tr><tr><td><strong>Sales</strong></td><td>Price, weight, unit of measure, and inventory strategy.</td></tr><tr><td><strong>Media &#x26; SEO</strong></td><td>Images, URL key, meta title, keywords, and description.</td></tr></tbody></table>

### Creating a Simple Product

{% stepper %}
{% step %}
**Check item and SKU**

Use a permanently unique SKU; do not change it lightly after go-live.
{% endstep %}

{% step %}
**Activate Magento Product**

Set product type to **simple**, assign attribute set, visibility, and status.
{% endstep %}

{% step %}
**Maintain commercial data**

Verify price, tax group, weight, and required texts.
{% endstep %}

{% step %}
**Assign category and images**

Check at least the intended shop category and the desired default image.
{% endstep %}

{% step %}
**Run Product Upload**

After success, verify Magento Product ID, Synced At, and Status Reason.
{% endstep %}

{% step %}
**Review the result in the shop**

Compare name, status, websites, visibility, price, tax class, category, media, and inventory.
{% endstep %}
{% endstepper %}

### New or Existing Product?

{% columns %}
{% column width="50%" %}
**Without Magento Product ID**

The connector creates a new Magento product and then stores its ID.
{% endcolumn %}

{% column width="50%" %}
**With Magento Product ID**

The existing Magento record is updated. Verify SKU and assignment with extra care beforehand.
{% endcolumn %}
{% endcolumns %}

{% hint style="danger" %}
An incorrect Magento Product ID can update the wrong shop item. When in doubt, compare ID, SKU, and target product in Magento before uploading again.
{% 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/master-data-management/item-card-and-simple-products.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.
