> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vidimo.app/llms.txt
> Use this file to discover all available pages before exploring further.
# Pricing
> Set a base nightly rate, price whole date ranges with seasons, and adjust individual nights.
export const AppLink = ({to, children}) => {children};
Pricing is set per **room type**, not per room — every Double shares one price
and one calendar, the same way availability is counted. Manage it from the
property's **Pricing** settings.
Pricing lives under property settings, which are role-gated: only Managers and
other users with settings access can change prices. See
[Roles & permissions](/team/roles-and-permissions).
Changes sync to your connected channels, so a price you set here is the price
your guests are quoted — on your own booking page and on the channels you have
connected.
## Set the base rate
Each room type has a **Base / night**. This is what a night costs when nothing
more specific applies, and it is the starting point for everything below.
A room type with no base rate and no season covering a night cannot be sold that
night — there is no price to charge.
## Price a stretch with seasons
A **season** is a rule: *"1 June to 31 August costs €200 a night, minimum three
nights."* It covers a date range rather than a list of nights, so changing a
whole summer is one edit instead of ninety.
Add one under **Seasons**:
| Field | What it does |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------ |
| **Season** | A name for you, like "Summer 2027". |
| **First night** / **Last night** | The range the rule covers. Both nights are included. |
| **Price / night** | The nightly rate. Leave blank to keep the base rate and use the season only for its other rules. |
| **Min stay** | The shortest stay allowed on these nights. |
| **Per guest under** | Taken off the nightly price for each guest below the room type's capacity. Applies to direct bookings. |
| **Short stay under** / **Surcharge** | Adds the surcharge to stays shorter than that many nights. Applies to direct bookings. |
| **Priority** | Which season wins where two overlap — see below. |
### When seasons overlap
Seasons are allowed to overlap, and the one with the **highest priority** wins
for the nights they share. That is what lets you lay a short, expensive rule on
top of a long, cheap one:
* *Shoulder season*, 1 April to 31 October, €120, priority `0`
* *Peak week*, 10 to 17 August, €260, priority `10`
Every night in that range prices at €120 except 10–17 August, which prices at
€260. Shrinking or deleting the peak-week season leaves the shoulder rule
covering those nights again — nothing is stranded.
To price the whole year, use one long season at a low priority rather than
editing nights one by one. Anything more specific can sit on top of it.
## Apply a change to a range
**Apply to a range** writes one set of values across every night between two
dates in a single step — useful for a one-off stretch that is not worth a
season, like closing a fortnight for renovation.
Pick the first and last night, set a price and minimum stay, or tick **Close the
range** to stop those nights selling. Fields you leave blank are not touched, so
this narrows a range rather than overwriting values you set deliberately
elsewhere.
## Adjust individual nights
**Edit individual nights** opens a per-night list for the next 60 nights. It is
collapsed by default and shows how many of those nights you have customised, so
you can see at a glance whether anything one-off is in play.
Use it for a single night that does not follow any rule. Each night offers:
| Setting | What it means |
| ------------------------------ | ------------------------------------------------------------------------------------ |
| **Price / night** | Overrides that night only. Leave blank to fall back to the season, or the base rate. |
| **Minimum stay** | The shortest stay that may touch this night. |
| **Min stay — arriving** | Applies only to a stay that *starts* this night. |
| **Min stay — passing through** | Applies to any stay *covering* this night, whenever it started. |
| **Maximum stay** | The longest stay that may start this night. |
| **No check-in** | Guests may stay through this night, but not start here. |
| **No check-out** | Guests may not check out the next morning. |
| **Closed** | The night is not sellable at all. |
A per-night value always beats a season, and a season always beats the base
rate. So a night you edit here stays as you set it even if a season later
covers it.
The two arriving/passing-through minimums are the pair worth care. A
Saturday-arrival rule is **Min stay — arriving** on Saturdays only: it stops a
guest *starting* a stay midweek without affecting guests already staying.
## To take rooms off sale
Pricing controls what a night costs and how it may be sold. To hold a room out
of inventory entirely — an owner stay, maintenance, a manual close — use
[Blocked dates](/properties/blocked-dates) instead.