# Configure Demand-Based Pricing (/how-to/activities/configure-demand-based-pricing)



Use this guide when you want your pricing to respond automatically to how much of your equipment is booked. Equipment Utilization modifiers fire based on real-time demand — they don't require you to predict which dates will be busy.

How Utilization Is Measured [#how-utilization-is-measured]

When a customer is quoting a booking, Resytech looks at the booking's time window and calculates the percentage of your equipment that's already booked during that window.

* For **Equipment Rental** activities, this is the percentage of your fleet that's in use (e.g., if you have 10 jet skis and 8 are booked, utilization is 80%).
* For **Tour** activities, this is the percentage of seats sold (e.g., 15 of 20 seats booked = 75%).

For **multi-day bookings**, the system uses the worst-case (most-booked) point across the booking window. A 3-day booking that overlaps even one peak day will see a high utilization number.

The signal is detected automatically based on the activity type — you don't need to choose which kind of utilization to measure.

Surge: Charge More When Busy [#surge-charge-more-when-busy]

This is the most common use case — automatically raise prices when most of your equipment is already booked.

1. Go to **Activities > \[Activity Name] > Settings > Pricing**.
2. Click **Add Modifier**.
3. Set **Modifier Type** to **Equipment Utilization**.
4. For **Fire When Equipment Utilization Is**, choose **At or above**.
5. Enter the **Threshold** (e.g., `80` to fire when 80% of equipment is booked).
6. Set **Method** to **Percentage** and enter a positive amount (e.g., `20` for +20%).
7. Optionally name the modifier (e.g., "High Demand Surge").
8. Click **Add Modifier**, then **Save Changes**.

Once a customer's chosen time slot crosses the threshold, the surcharge applies automatically.

Discount: Charge Less When Slow [#discount-charge-less-when-slow]

Encourage bookings during quiet periods by lowering the price when utilization is low.

1. Same steps as above, but choose **At or below** for the comparator.
2. Enter a low threshold (e.g., `30`).
3. Set **Method** to **Percentage** and enter a negative amount (e.g., `-15` for a 15% discount), or use a **Flat Amount** discount.

This is useful for weekday off-peak hours, shoulder seasons, or any time you want to fill empty inventory.

Tiered Pricing [#tiered-pricing]

Stack multiple Equipment Utilization modifiers to create pricing tiers. Each modifier is evaluated and applied in order, so the adjustments compound.

**Example:** A boat rental with 10% surge starting at 80% and an additional 20% surge starting at 95%.

1. Create a first modifier with threshold `80`, comparator **At or above**, Percentage `+10`.
2. Create a second modifier with threshold `95`, comparator **At or above**, Percentage `+20`.

A customer booking when 8 of 10 boats are out pays the base + 10%. When 9.5 of 10 are out (95% utilization), they pay base × 1.10 × 1.20 = +32% total.

Combining With Other Conditions [#combining-with-other-conditions]

Equipment Utilization modifiers can be combined with **Time Range** and **Duration** filters on the same modifier — for example, "+20% when utilization is ≥80% AND the booking is in the evening."

To layer with other modifier types (Date, Day of Week, etc.), create separate modifier rows. All matching modifiers stack in order.

When Demand-Based Pricing Doesn't Fire [#when-demand-based-pricing-doesnt-fire]

A few cases where the modifier intentionally does not apply:

* **Calendar estimate pages.** The "from $X" price shown on calendar views doesn't apply utilization-based modifiers because the calendar shows what's possible, not the live demand-adjusted quote. Customers see the demand-adjusted price once they pick a specific time slot.
* **Dynamic-duration hourly bookings.** Activities configured for ad-hoc hourly durations don't have a fixed inventory window in the same way scheduled slots do, so utilization-based modifiers don't fire on that path.
* **Activities with no equipment configured.** The modifier needs equipment to measure utilization against.

Tips [#tips]

* Pair surge modifiers with a **Price Modifier Minimum** floor on the activity if you also have discount modifiers — that prevents the floor from being violated by deep discounts.
* Use the modifier **Name** field to make tiered configurations easy to manage (e.g., "Surge T1 ≥80%", "Surge T2 ≥95%").
* Watch utilization-driven pricing for a few weeks before going aggressive — what looks like "high demand" historically may not justify a big surcharge if customers walk away.
* For a comprehensive overview of all pricing options, see [Pricing & Modifiers](/docs/activities/pricing).
