> For the complete documentation index, see [llms.txt](https://developer.esw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.esw.com/customs-catalog-api/customs-catalog-api/core-concepts/brand-and-tenant-configuration.md).

# Brand and Tenant Configuration

Every product and operation in the API is scoped to a Brand, which is itself part of a Tenant. Understanding this hierarchy is essential before importing any data.

{% tabs %}
{% tab title="Brand" %}
The commercial identity of the retailer. All products, classifications, VAT rates, and duty rules are scoped to a brand. Most endpoints accept `brandCode` as a parameter or body field.
{% endtab %}

{% tab title="Tenant" %}
A parent account that can contain multiple brands. Some file-based endpoints use `tenantCode` instead of `brandCode`. Retrieve the mapping from `GET /BrandConfig/{id}` which returns both codes.
{% endtab %}
{% endtabs %}

### `BrandConfig` fields

| Field                  | Type        | Description                                                                                                      |
| ---------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------- |
| `brandCode`            | string      | Unique identifier for the brand. Used on most endpoints.                                                         |
| `tenantCode`           | string      | Parent tenant identifier. Used on file-based and admin endpoints.                                                |
| `delimiter`            | string      | CSV field delimiter for file-based imports (e.g. `,` or `\|`).                                                   |
| `regions`              | array       | List of Region codes this brand operates in. Only these regions will have duty rates populated.                  |
| `weightUnitDefault`    | Lb / Kg     | Default unit for the `weight` product field if not explicitly specified per product.                             |
| `currencyUnitDefault`  | CurrencyIso | Default currency for `unitPrice.amount` if not specified.                                                        |
| `processRawCatalogs`   | boolean     | Whether raw file catalogs are processed. If false, file uploads are rejected.                                    |
| `allowDefaultProducts` | boolean     | When true, products that fail classification receive a default HS code fallback instead of being marked invalid. |
| `avalaraEnabled`       | boolean     | If true, tax rates come from Avalara integration rather than the internal VAT engine.                            |
| `hsCodeLimit`          | string      | HS code precision level: `6`, `8`, or `10` digits.                                                               |


---

# 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://developer.esw.com/customs-catalog-api/customs-catalog-api/core-concepts/brand-and-tenant-configuration.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.