> ## Documentation Index
> Fetch the complete documentation index at: https://shipmagic-docs.speedysquirrelhq.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Ranged Rates
> Charge a different price for each band of weight, value, or quantity
A **Range** rate charges one price for a band of values. Stack several of them and you get a price table — the classic "0–5kg costs \$8, 5–10kg costs \$12" structure.
## Setting one up
Set **Calculation parameter** to whatever the bands should be measured against — **Total weight of items**, **Total price of items**, or **Number of items**.
Three fields appear: Range Start, Range End, and Price.
**Range Start** is required. **Range End** can be left empty, which means "and above".
Click **Add rate** again and create the next band, using the **same rate name** each time.
Using the same **rate name** across bands is what makes this work. The customer sees one shipping option; ShipMagic returns only the band that matches their cart. Different names would show them several options at once.
## Covering the whole scale
Bands must not overlap, and should not leave gaps. If a cart falls into no band, that rate produces nothing.
A complete weight table looks like this:
| Range Start | Range End | Price |
| - | - | - |
| 0 | 5 | 8.00 |
| 5.01 | 10 | 12.00 |
| 10.01 | 20 | 18.00 |
| 20.01 | *(empty)* | 25.00 |
Mind the boundary. If one band ends at `5` and the next starts at `5`, a cart weighing exactly 5 is ambiguous. Start the next band just above — `5.01`
The final band with an empty **Range End** is important: without it, a cart heavier than your largest band gets no rate at all.
## Range + Incremental
When a band should have a base price *plus* a per-unit charge inside it, set **Rate Type** to **Range + Incremental**. You give the band (Range Start / End), then a base price, an incremental price, and a "per each" step.
Use it for tables like "5–10kg is \$12 plus \$1.50 for every kg over 5".
## Range + Range
**Range + Range** matches on **two parameters at once**. You set a band on the rate's main calculation parameter, then choose a second parameter and give it its own band and price.
Use it for tables that vary along two axes — for example weight *and* order value, where heavy-but-cheap and heavy-but-expensive orders should price differently.
Range + Range is the most intricate rate type in the app. If you find yourself needing three or more axes, that is usually a sign to split the logic across several rules with [priorities](/shipping-rates/basic-shipping-rate) instead.
## Examples
**Free shipping above a threshold**
```text theme={null}
Rate 1 — Standard Shipping
Calculation parameter: Total price of items
Rate Type: Range | Start: 0 | End: 100 | Price: 5
Rate 2 — Standard Shipping
Calculation parameter: Total price of items
Rate Type: Range | Start: 100.01 | End: (empty) | Price: 0
```
**Price by number of items**
```text theme={null}
Rate Type: Range | Start: 1 | End: 3 | Price: 4.95
Rate Type: Range | Start: 4 | End: 10 | Price: 7.95
Rate Type: Range | Start: 11 | End: (empty) | Price: 12.95
```
## Related
A base price plus a charge per unit.
Scale with order value instead of bands.
Bound the result of any calculation.
The full rate dialog reference.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.