> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integration-guide/workflows/intelligent-routing/routing-strategies/volume-based-routing.md).

# Volume-Based Routing

{% embed url="<https://youtu.be/xpU3zmyD4b8>" %}

Volume-Based Routing distributes payments across processors using fixed percentages. It is useful when you want predictable traffic allocation without writing conditional rules.

## When To Use It

Use Volume-Based Routing to:

* Gradually move traffic to a new processor.
* Keep multiple processors active.
* Meet a planned traffic allocation.
* Run a simple production rollout before switching to a dynamic strategy.

## Setup

1. Go to `Workflow` > `Routing`.
2. Click `Setup` for Volume-Based Routing.
3. Add a name and description for the routing configuration.
4. Select the processors and configure the required percentage split.
5. Choose whether to only save the configuration or save and activate it for payments.
6. Review the active and previously configured routing algorithms on the [Hyperswitch Dashboard](https://app.hyperswitch.io/routing).

## Notes

The configured percentages apply only to processors that are eligible for the payment. If the selected processor is not eligible, Hyperswitch uses [Default Fallback Routing](/integration-guide/workflows/intelligent-routing/routing-strategies/default-fallback-routing.md).


---

# 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://docs.hyperswitch.io/integration-guide/workflows/intelligent-routing/routing-strategies/volume-based-routing.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.