> 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/choosing-shipping-rates.md).

# Choosing which shipping rates are passed through

Two settings on the [shipping settings resource](/prism/merchants/merchant-configuration-resources.md#shipping-settings) control which of the merchant's platform rates are passed through to your channel. Both are off by default, and both depend on the merchant having [fallback methods](/prism/merchants/configuration/fallback-shipping-methods.md) defined.

## Exclude external rates

`exclude_external_methods` replaces the platform's rates with the merchant's [fallback methods](/prism/merchants/configuration/fallback-shipping-methods.md). When at least one fallback method applies to the cart, every platform rate is dropped and only the applicable fallback methods reach your channel. When no fallback method applies, because none are defined or none match the cart's destination, amount, weight, or offers, the setting has no effect and the platform's rates pass through as usual.

Use this when the merchant's platform rates should never apply to orders placed through your channel, for example when you have negotiated flat-rate shipping with the merchant and represent it as fallback methods.

{% hint style="warning" %}
`exclude_external_methods` only removes platform rates when a fallback method applies to the cart. If your fallback methods' conditions don't cover a destination, order amount, or weight, shoppers in that case see the platform's rates, including ones you meant to exclude. Make sure at least one fallback method covers every destination you sell to.
{% endhint %}

## Exclude free shipping

`exclude_external_free_shipping` stops the platform's free rates (any rate priced at `0`) from being passed through. Paid platform rates still pass. The setting only takes effect for merchants with at least one fallback method defined; for a merchant with none, free platform rates still pass through.

Typical use: the merchant is running a free-shipping promotion on their own platform that should not apply to orders placed through your channel.

## Updating the settings

Both settings live on the shipping settings resource and support partial updates, so you can change one without touching the other:

```
PATCH /merchants/{merchant_id}/shipping-settings
Content-Type: application/merge-patch+json
```

```json
{
  "exclude_external_free_shipping": true
}
```

Field definitions and the read endpoint are in [Merchant Configuration Resources](/prism/merchants/merchant-configuration-resources.md#shipping-settings).

## Related

* [How Violet shipping works with the merchant's platform](/prism/merchants/configuration/shipping-and-your-platform.md) explains where these rates come from in the first place.
* [Fallback shipping methods](/prism/merchants/configuration/fallback-shipping-methods.md) covers the methods that remain when external rates are excluded.


---

# 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/choosing-shipping-rates.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.