> 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/when-fallback-methods-apply.md).

# When fallback methods are used

`use_fallback_methods_on_empty` on the [shipping settings resource](/prism/merchants/merchant-configuration-resources.md#shipping-settings) controls when a merchant's [fallback shipping methods](/prism/merchants/configuration/fallback-shipping-methods.md) are passed through to your channel.

## Turned off (the default)

Fallback methods are offered alongside whatever rates the merchant's platform returns. Shoppers see both.

Use this when the fallback methods are genuine everyday options, for example a negotiated flat rate that should always be available next to the platform's carrier rates.

## Turned on

The merchant's platform is checked first, and fallback methods are passed through only if no platform rates remain once exclusions are applied, including the free-shipping exclusion and any rule-based shipping exclusions. That makes them a safety net rather than an everyday option.

Use this when the platform's own rates should always win, and the fallback methods exist only to keep checkout working for a merchant whose platform sometimes returns nothing, for example for destinations its shipping zones do not cover.

{% hint style="info" %}
This setting only matters while platform rates are being passed through. With [`exclude_external_methods`](/prism/merchants/configuration/choosing-shipping-rates.md) turned on, applicable fallback methods already replace the platform's rates.
{% endhint %}

## Updating the setting

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

```json
{
  "use_fallback_methods_on_empty": true
}
```

## Related

* [Fallback shipping methods](/prism/merchants/configuration/fallback-shipping-methods.md) covers defining the methods themselves.
* [How Violet shipping works with the merchant's platform](/prism/merchants/configuration/shipping-and-your-platform.md) explains the overall pass-through model.


---

# 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/when-fallback-methods-apply.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.