Where do I upload the photos of a room?

From the Dashboard open the three-dot menu, entry «Configuration», then the «Rooms» group: tap the room in the list and the «Photos» card is the first block of its page. «Manage rooms» is a different page: it is where you create rooms and change how many there are, not where you configure one.

How many photos can I upload?

Twenty per gallery, and the galleries are separate: every room type has its own twenty and the property has another twenty. The first photo is the cover. Once the limit is reached, «Add photo» accepts no new uploads until you delete one.

What saves itself on this page?

Only the photos: every upload, move or deletion goes out at once. Everything else — titles, capacity, prices, and the location on the «Property details» page — only takes effect when you tap «Save Changes» at the bottom of the page.

I cannot see the «Occupancy cap per channel» card.

It only appears if the room is on sale on the portals and the property has at least one connected channel. The cap comes down by itself when a channel rejects an occupancy higher than it accepts, but it never goes back up by itself: if you widen the capacity on the portal, the old cap stays until you remove it by hand from that row.

Is the price I type per person or for the whole room?

It is the price of the room for one night. How much extra guests weigh is decided by the «Pricing Model» card — «Linear», «Derived» or «Fixed price». With «Linear» and a single treatment active, the surcharges for adult, youth and infant sit inside that same card, not in a separate one.

Photos and Room Setup Guide

The photos, texts, capacity and prices of a room — and the photos and location of the property

The two screens this guide covers The photos The property location Titles and descriptions Details and features Amenities Selling on the portals Room prices Special cases If something is not right

The two screens this guide coversOne for the room, one for the property

The «?» button of two different screens brings you here, because the two screens share the thing that matters most: the photos. The rest splits in two.

Screen	What it covers	How you get there
Room Setup (on a hotel: Type Configuration)	The photos, titles and descriptions, capacity, portal selling and prices of one room	Dashboard > ⋮ menu > Configuration > Rooms group > tap the room in the list
Property details	The photos of the property as a whole, and its position on the map	Same Rooms group, Property details button; or Booking Engine > photo shortcuts > Property photos

«Manage rooms» is a different page. It is where you create rooms and change how many there are, not where you configure one: a room opens for configuration when you tap it in the list, not from there.

The Property details button only appears once at least one room type exists, and it does not appear at all if you manage apartments: for you the location belongs to each single room (see Special cases). The second route, through the Booking Engine, stays open to everyone.

The photosTwo separate galleries, same rules

Vezpa keeps two distinct galleries, and the difference matters: putting the front of the building into a room gallery makes it look like the room.

Gallery	What belongs here	Where it appears	Limit
Room photos the Photos card in Room Setup	The room or the apartment: the spaces, the beds, the bathroom, the view	That room page in the Booking Engine. In the app they are only visible here, in the gallery that edits them	20
Property photos at the top of Property details	The property as a whole: the front, shared spaces, the pool, the garden	The general property page in the Booking Engine	20

The limit of twenty applies to each gallery: with five room types you have five galleries of twenty, plus the property one. Once the limit is reached, Add photo stops accepting new uploads until you delete one.

Adding, ordering, removing

Tap Add photo and pick one or more images: they upload one after the other, with a bar telling you something is happening.
Drag a photo to move it: above the strip it says Drag to reorder.
To remove an image, tap the bin icon on the photo and confirm.

Photos save themselves. Every upload, every move and every deletion goes out at once: there is nothing to confirm with «Save Changes», which covers all the other fields on the page. The first photo is the cover, the one a guest sees first; delete the cover and the next photo takes its place.

These photos do not travel to the connected portals. They dress the Vezpa Booking Engine. The photos people see on Booking.com, Airbnb and the others are uploaded from the channel manager extranet, together with the rest of the listing content (descriptions, amenities): Vezpa sends availability and prices to the portals, not images.

Photos that came from a portal

When you import a property from a portal, the images already published there can land in the matching gallery. Once here they are photos like any other: you reorder and delete them the same way, the import never overwrites what was already there, and the same limit of twenty per gallery applies.

The property locationYou type the address, the point marks itself

Below the photos, in Property details, sits the Coordinates block: the Booking Engine and the channel connection need the exact point, and without it the property does not appear on the map.

Type into the «Search for the address» field: suggestions appear as you type.
Pick a suggestion: the point marks itself on the small map below.
If it does not land where you want, drag the small map: the dot stays put in the middle and it is the map that moves underneath.
For more room, tap «Pick on the map», move the map and confirm with «Use this location».

Here saving is not automatic. Photos go out on their own, the location does not: it only takes effect when you tap «Save Changes» at the bottom of the page. Leave before that and the old one stays. It is the difference that costs people their work most often, and it lives inside the same screen.

In the browser trial the map is not drawn: you type the address all the same and the location is set from the suggestion you pick. In the installed app the map is there.

Titles and descriptionsThe commercial name, one language per field

The Titles and Descriptions cards work the same way: one field for every language you sell in on the Booking Engine, labelled with the name of that language. Languages you do not use get no field at all, so the list differs from property to property.

The title is the commercial name guests read — «Sea View Room», not a code. If you leave it empty, the Booking Engine shows the room's internal name.
The description is the listing text, again one per language.
Titles and descriptions belong to the room type: editing them from one room updates every room sharing that type.

When a translation is missing, the guest reads English — not the base language. The fallback runs in this order: their own language, then English, then the base field. With English filled in and German empty, a German guest sees the English version.

«Room Name» is something else

On the setup of a single unit there is also the Basic Information card with the «Room Name» field: it is the internal code you recognise the room by in the calendar and in lists — short, eight characters at most, something like RM1 or APT1. No guest ever sees it. Open a room type and that card is not there: the internal code belongs to each room, not to the group.

Details and featuresTwo neighbouring cards with different jobs

The Details card holds the numbers that govern selling:

Field	What it is for
Max Pax	The capacity. It decides how many people the portals show a price for, so keep it equal to what the room really holds. The helper under the field reads «Maximum capacity of this accommodation» (or «of this room type»).
Dimensions (sq m)	The floor area, shown to guests.
Setup	How the beds are arranged. You pick from a list that explains every code: X is a single bed, M a double bed, and they add up (MX = a double plus a single). It does not change the price, the capacity or what the channels show: it is a reminder for you and your housekeeping staff.
Commercial Type	What you are selling in the portals' vocabulary (double room, apartment, bed in dormitory and so on). It is the type the listing is published under.

Features are a separate card

The Features card sits right below and holds six pill switches: Children, Disabled, Pets, Extra Bed, Sep. Beds, View. These are the features guests filter the search by in the Booking Engine, and that show on the room page: turn one on only if the room really has it, because a filter switched on for nothing brings bookings you cannot honour.

AmenitiesWhat the guest finds in the room and in the property

Amenities tell the guest what they'll find: in the room (TV, Wi-Fi, fridge, hairdryer, kitchen) and in the property (parking, lift, swimming pool, breakfast).

Room amenities are set in the room configuration, in the Amenities panel under the characteristics. If you work by room type, you set them on the type and they propagate to the rooms that belong to it. Property amenities are set once on the Booking Engine page and do not need repeating on every room.

The entries in our catalogue have their own icon and arrive already translated into every language of your Booking Engine. If something is missing, the Manager can add an entry of their own: you can give it an icon too, chosen from all the ones available, and the same icon can go on as many entries as you like. You write the entry in the languages you sell in. An entry without a translation still shows, in the text you wrote, so it doesn't disappear without you noticing.

The guest sees them on the Booking Engine: room amenities on the room's card, both when choosing among the available units and on the property page; property amenities above the list of accommodations.

Amenities do not go out to the connected portals. Booking.com's facilities are loaded from the channel manager extranet, together with photos and descriptions.

Selling on the portalsThe switch, and the cap for a single channel

At the bottom of the Details card sits the «Sell this room on the portals» switch, which decides whether the room is offered to the connected portals.

Turned off, the room stays bookable by you and on your Booking Engine: it is no longer offered to the connected portals.
Taking it off sale is always possible. Putting it back on sale requires a plan that includes the OTA channels: without one the switch will not turn on, and the app says so.
If the plan is what excluded it, under the switch you read «Excluded from the portals because the plan does not include the OTA channels: it goes back on sale by itself on renewal». In that case there is nothing to do: on renewal it returns on its own.

Occupancy cap per channel

Some channels accept fewer guests than you sell here. A room for three can be bookable for only two on a given portal: that portal rejects the price for the third guest every night, and the room ends up effectively unsellable for three there. The Occupancy cap per channel card is for exactly that: one row per connected channel, showing its current cap or «No cap set — sells at full capacity».

The card only appears if the room is on sale on the portals and the property has at least one connected channel: with no channels there is nothing to cap and the card is not drawn at all. Each channel has its own cap, independent of the others, and the Booking Engine is never affected: there the room keeps selling at full capacity.

The cap comes down by itself, but it never goes back up by itself. If you send a channel more guests than it accepts, the channel rejects and Vezpa learns the limit on the first rejection: that is the expected behaviour, not a bug. The other way round nothing happens, and nothing can happen: if tomorrow you widen the capacity on the portal extranet, no rejection will ever arrive and the old cap stays where it is until you remove it yourself, from that same row. The way back is always this one: first raise the capacity on the portal, then remove the cap here.

The cap limits what Vezpa sends; it is never a promise about what the channel will accept. It does not go below the room's minimum occupancy, and that floor declares itself at two different moments.

On saving. If you type a cap lower than the minimum occupancy, the save goes through but the value written is that minimum: an orange notice says which channel, what you asked for and what was saved in its place, and the channel's row shows the real number straight away.

When it is the channel declaring a cap below that minimum. Vezpa keeps the minimum, and from then on, on that channel, it has no occupancy left to offer that the channel has accepted: the price ladder it sends shrinks to the single rung of the minimum occupancy, which is the very value that channel refused, and every later update sends that one again. How the portal behaves from there — whether it takes the room off sale or leaves it at the price it already had — is the portal's own decision, and Vezpa does not see it: the only certain answer is in its extranet. A notification then reaches the Manager and the Assistant — the check on channel rejections runs at night, so it shows up on the first useful pass — naming the room, the channel, how many guests that channel accepts and from how many it sells here, and giving the two ways out: raise the capacity in the portal extranet up to that minimum, or lower the room's minimum occupancy (with the Linear price model it is the «Adults included in the rate» field, in the Adults block). Vezpa takes neither road: it does not close the channel's availability and it does not lower the minimum for you.

This is a different thing from the different capacity notice in the channels guide: that one is automatic and read-only, this one is a limit you set.

Room pricesWhere you set the base price and the per-guest surcharges

Further down, below the photos and the descriptions, you find the Pricing Model card: it says how the price grows as guests are added, and the example under the selector shows it on a rate of 100.

Linear — every guest beyond those already included adds a fixed amount that you choose.
Derived — every guest adds a percentage of the base price.
Fixed price — the price covers the whole capacity, with no per-person surcharge.

With Linear and a single treatment active — the case of apartments and holiday homes, but also of a B&B selling breakfast only — the surcharges for adult, youth and infant sit inside the Pricing Model card, not in a separate one: they were the only answer to «where do I set the price for more people?» and they used to live in a card named after meals, which anyone not serving food reasonably treats as somebody else's business. With more than one treatment active they go back to their own card, next to the price of each treatment.

If the example shows the same price for every number of guests, the adult surcharge is zero and the price does not change with people. For an apartment that is often what you want; if it should grow, fill in the Adult field.

The two age thresholds, and where the line falls

Beside the per-guest surcharges, in the «Youths» and «Infants» blocks, two fields say who those surcharges apply to: «Max youth age» and «Max infant age», in years. They are the numbers Vezpa classifies a child by once it knows their age, and they sit on the room: two room types in the same property can hold different ones, and each prices with its own.

The number you write is included. With «Max youth age» at 10, a guest aged 10 is still youth; they count among «Adults» from 11 up. The same holds for «Max infant age»: at 2, infant up to the second birthday and youth from three. Both labels promise an inclusive maximum, and from 26 September 2026 the calculation does exactly that: if you needed a threshold one year lower, lower the number by one.

With «Max youth age» at 0 this room has no children bracket at all: everybody sleeping in it counts among «Adults». The age selector a booker sees — in the app and on the Booking Engine — disappears only when none of the rooms in play has a children bracket: it reaches the highest threshold among those rooms, because the party is chosen before the room, and each room type then prices with its own. In play are the rooms the search can offer: on the Booking Engine, the ones the site shows — so a room kept off the Booking Engine does not count there.

Fixed price: the third model

Besides Linear and Derived you can choose Fixed price — «Full capacity included, no per-person charges». The price you put on the Rates calendar covers the whole room up to its maximum capacity: Adults and Youths are included and there is no per-guest price to fill in. Infants stay outside and are counted separately.

If you also offer breakfast or board, each treatment has its own «Amount per room (not per person)»: it is added once to the daily rate, not once per guest. On the connected portals every plan starts flat, at its own price.

The fields start at zero: switching to Fixed price does not change the prices you are already selling until you set them yourself.

Maximum capacity

The maximum capacity is the largest number of guests the room can take, and it counts Adults and Youths. Infants and very small children are extra: they take no place. This is the number that decides how many people the portals show a price for, so keep it equal to what the room really holds.

In the room setup the field is called Max Pax and the helper below reads «Maximum capacity of this accommodation» (or «of this room type»).

A price field is never left empty

Emptying a price field no longer sets it to zero: saving stops and the field stays highlighted with «Required field». If the price really is zero, write 0.

When changing a surcharge asks for confirmation

Per-guest surcharges are not stored day by day: the engine reads them again on every calculation, so changing one changes the price of every day already on the calendar, and starts the push towards the connected channels. That is why, when the change touches days that already carry a price, saving stops and shows how many days, over which period, which treatments and which channels are involved. Nothing is written until you confirm.

In the RMS page there is an option also called Fixed price — in the app help «Fixed Price (Max Pax)». It is not this pricing model: that one only decides that the price is always computed on the maximum number of guests. See the RMS guide.

Special casesWhat happens to some people, not to everyone

Are you setting up a room type or a single room?

The title at the top says it: Type Configuration or Room Setup. On a room type the page lists the rooms that belong to it and warns that changes will be applied to all of them; the «Room Name» field disappears, because the internal code belongs to the single room. Titles, descriptions, capacity and prices belong to the type in both cases.

If you manage apartments

Every room has an address of its own, so the location does not live on the property but inside each room's setup, in the Coordinates card. On «Property details» the location block and the save button are not there at all, and a note in their place says so: for you that page is only the property gallery.

The cards fold away

The page is long and not everybody uses all of it: tapping the title of a card closes it, and the app remembers which ones you closed even after you leave. A closed card is not a card turned off: its values stay exactly as they are.

At the bottom, Integrations

The last card is called Integrations and changes with the country of the property: it holds the codes and credentials that local reporting asks for per room. If your country requires none, the card stays nearly empty, and that is normal.

The registration code is not asked for here

The identification code of the room (in Italy the CIN, elsewhere its local equivalent) goes into the Booking Engine settings: that is where it is needed, because the public page is what has to print it, and there it blocks the publication of that one room instead of holding up the whole setup.

If something is not rightThe most frequent doubts, with the short answer

I changed the location and it did not save. Photos save themselves, the location does not: it needs «Save Changes» at the bottom of the page.
I uploaded photos and nothing changed on Booking.com. Portal photos are managed from the channel manager extranet: Vezpa sends availability and prices, not images.
The «Add photo» button does nothing. You are at twenty, the limit of that gallery: delete an image to free a slot.
I cannot find «Property details». It appears in the Rooms group only once at least one room type exists, and it does not appear to those who manage apartments. The second route is the Booking Engine, entry Property photos.
I cannot find the occupancy cap card. It exists only if the room is on sale on the portals and the property has at least one connected channel.
A channel lowered the number of guests by itself. That is the cap learning from a rejection. To raise it again: first the capacity on the portal extranet, then remove the cap from that channel's row.
I saved a cap and the row shows a higher number. The cap does not go below the room's minimum occupancy: the orange notice says what was saved in its place. To reach the number you wanted, lower the room's minimum occupancy first.
I got a notification about a channel cap and the minimum occupancy. That channel accepts fewer guests than the room's minimum occupancy, so the only price Vezpa can still send it is the one for the occupancy it refused. Look in the portal extranet to see how the room stands there: that part Vezpa does not know. To bring the two numbers back together there are two roads: raise the capacity in the portal extranet, or lower the room's minimum occupancy. Vezpa picks neither on its own.
I cannot put the room back on sale on the portals. It needs a plan that includes the OTA channels. If the line under the switch talks about the plan, it returns on sale by itself on renewal.
Saving stopped and asked me to confirm. You changed a surcharge that touches days already priced: the dialog says how many they are and which channels are involved. Nothing is written until you confirm.
A foreign guest is reading the text in English. The translation into their language is empty: the fallback is their language, then English, then the base field.