> 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/troubleshooting-and-support/configuration-fields.md).

# Configuration Fields

The key fields of the **Magento Configuration** page by section.

### General

* **Web Store Code**: unique shop identifier
* **Web Store Name**: display name
* **Active**: production release
* **Connection Status / Last Error**: last connection test

### Connection

* **Website URL**: Magento base URL without trailing `/`
* **API Base Path**: usually `/rest/all/V1`
* **Use API Integration**: OAuth mode; not recommended for production in 27.10.0.16
* **User Name / User Password**: token login
* **Consumer/Access Token fields**: OAuth secrets

### Orders

Allows Order Download, Create Doc. Immediately, Sales Order Document Type, Sales Order No. Series, Downloadable Order Status, Start From Order ID, Default Location Code, Calculate Invoice Discount, Prices Including Tax, and tax flags.

### Customers

Create Unknown Customer, Customer Template, Default Guest Customer, and Default Login Customer.

### Catalog

Allow Item Upload, Upload Item Image, Upload Simple Variants, Use Model as Configurable, Upload Bundle Items, Upload Product Category, Default Category/Attribute Set/Visibility, and Max Products Per Run.

### Inventory

Inventory Sync Mode, Upload Inventory, Upload Variant Inventory, Allow Update Magento Inventory, and Upload Negative Quantity.

{% hint style="warning" %}
A visible field does not guarantee the feature is evaluated in every process. See the "Known Limitations" page.
{% 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/troubleshooting-and-support/configuration-fields.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.
