> For the complete documentation index, see [llms.txt](https://docs.commercelayer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.commercelayer.io/core-api-reference/2026-05/merchants.md).

# Merchants

The merchant object and the allowed CRUD operations on the related resource endpoint

A merchant is the fiscal representative selling in one or more [markets](https://docs.commercelayer.io/core-api-reference/2026-05/markets.md) and/or [stores](https://docs.commercelayer.io/core-api-reference/2026-05/stores.md). It represents the legal entity — with its own billing address — responsible for the transactions taking place in the markets it owns.

## Merchants and markets

Each market must be associated with exactly one merchant, but the same merchant can own multiple markets. An organization can also have more than one merchant — for example, if you operate multiple brands or legal entities under the same Commerce Layer organization, each with its own tax registration and billing details.

{% hint style="info" %}
A store inherits its merchant from the associated market by default, but you can optionally assign it a different one — for example, if a specific retail location is fiscally represented by a distinct legal entity.
{% endhint %}

## Billing address and tax calculation

A merchant must be associated with a billing [address](https://docs.commercelayer.io/core-api-reference/2026-05/addresses.md) at creation time. Tax calculators use this address — together with the order's shipping address — to determine the applicable tax rate, so getting it right during setup directly affects tax computation for every order placed in the merchant's markets.


---

# 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.commercelayer.io/core-api-reference/2026-05/merchants.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.
