> For the complete documentation index, see [llms.txt](https://docs.violet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violet.io/prism/merchants/configuration.md).

# Configuration

Merchant configuration lets you change how Violet handles a merchant's shipping, inventory, and catalog behavior directly, without routing every change through Violet support. Each capability is exposed as a first-class REST resource under `/merchants/{merchant_id}/*`.

The guides in this section explain what each configuration capability does and how the pieces behave together. For endpoint definitions, field tables, and request examples, see the two reference pages:

* [Merchant Configuration Resources](/prism/merchants/merchant-configuration-resources.md) covers the individual REST resources.
* [Merchant Configurations](/prism/merchants/merchant-configurations.md) covers the full configuration object, including feature flags.

{% hint style="info" %}
Configuration is set per merchant and applies to that merchant across every channel they are connected to. There is no per-channel or per-app configuration, although a few settings can only be changed with a channel or admin token.
{% endhint %}

{% hint style="warning" %}
Configuration writes are rejected while the merchant is disabled or while their configuration is locked by Violet. Contact the Violet team if a merchant's configuration is locked.
{% endhint %}

## Shipping

Shipping configuration controls which shipping methods Violet passes through to your channel for a merchant's orders.

* [How Violet shipping works with the merchant's platform](/prism/merchants/configuration/shipping-and-your-platform.md) explains the layered model: Violet filters and supplements what the merchant's platform returns, and never changes the platform's own settings.
* [Choosing which shipping rates are passed through](/prism/merchants/configuration/choosing-shipping-rates.md) covers the exclusion toggles for platform rates and free shipping.
* [Fallback shipping methods](/prism/merchants/configuration/fallback-shipping-methods.md) covers the methods you define in Violet, including pricing, handles, and conditions.
* [When fallback methods are used](/prism/merchants/configuration/when-fallback-methods-apply.md) covers the toggle that holds fallback methods in reserve.

## Inventory

* [Inventory location filters](/prism/merchants/configuration/inventory-location-filters.md) covers choosing which Shopify locations count toward product stock levels. Shopify merchants only.

## Catalog

Catalog configuration controls which products sync into the catalog, and whether the ones already there can be purchased.

* [How catalog rules work](/prism/merchants/configuration/how-catalog-rules-work.md) explains the two rule types and the moment each one acts. Read this first. Catalog rules currently apply to Shopify merchants only.
* [Availability rules](/prism/merchants/configuration/availability-rules.md) covers making synced products purchasable or not.
* [Exclusion rules](/prism/merchants/configuration/exclusion-rules.md) covers stopping products from syncing in, or syncing them unpublished.
* [Offer publishing and visibility](/prism/merchants/configuration/offer-publishing-and-visibility.md) covers the automatic publishing default and the visibility override that only channels can change.


---

# 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.violet.io/prism/merchants/configuration.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.