> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/guest-experience/upsells/how-to-set-up-an-upsell.md).

# How to set up an upsell

This guide shows you how to set up an upsell, so that guests can buy it in the Guest Portal.

{% hint style="info" %}
**Before you start**

* You need the *upsells edit* permission.
* Connect a billing account. See [Billing](https://docs.guestway.io/account-and-administration/billing.md).
* For a custom upsell, make a [service template](https://docs.guestway.io/guest-experience/service-templates.md) first, or make one in the editor.
  {% endhint %}

## Choose the type

{% stepper %}
{% step %}

### Open the upsells

Go to **Settings** → **Organization** → **Upsells**.

If you start from a guest journey, open the **Upsells** step and click **Create a new upsell**. The currency and the properties of the journey are then filled in.
{% endstep %}

{% step %}

### Pick the upsell type

Click **Add Upsell**. On **What would you like to add?**, click **Early check-in**, **Late check-out** or **Custom upsell**.

If you want to start from a ready-made custom upsell, click a template under **Or pick an existing template**, for example **Parking** or **Breakfast**. The names, the description, the category and the price are then filled in.
{% endstep %}

{% step %}

### Name the upsell

Fill in the **Internal name** and the **Guest-facing name**. If you want, add a **Guest-facing description**.

For a custom upsell, select the **Category**. If you started from a template, the category is already set.

Select the **Guest facing currency**. It must match the guest journeys that offer this upsell.
{% endstep %}

{% step %}

### Add images

Under **Guest portal images**, click **Add images**, or drag images onto the card. You can add more than one image.

To choose the image that guests see first, select it and click **Set as primary**.

If you add no images, guests see a default image.
{% endstep %}
{% endstepper %}

## Set up early check-in or late check-out

{% stepper %}
{% step %}

### Select the properties

Select the listings, multi-units or complexes where the upsell is offered.

If you see *Properties already linked*, a property already has an upsell of this type. Remove that property, or change the other upsell.
{% endstep %}

{% step %}

### Set the times and prices

Under **Pricing** → **Available times**, click **Add time range** to add a range. Drag a range to move it, or drag its edge to change its length. Type the price of each range in the row below the timeline.

For example, for early check-in: **11:00–13:00** at a higher price and **13:00–15:00** at a lower price, with the standard check-in at 15:00.

If you see *Time ranges must be connected before you can save.*, close the gap between two ranges.

For a late check-out, if guests must not buy it on the departure day itself, or only until a time, turn on **Limit same-day purchase**.
{% endstep %}

{% step %}

### Sync the charge to your PMS

If you want the charge on the guest's bill in your PMS, turn on **Sync to PMS folio**. Fill in the **VAT percentage**, and select **Sync as bill line** or **Sync as service template**.
{% endstep %}
{% endstepper %}

## Set up a custom upsell

{% stepper %}
{% step %}

### Select the service template

In the **Service template** card, select the **Default service template**. To make a new one, click **Create new template**. If a service template with that name already exists, click **Use existing** to select it.

If you have more than one PMS, or a PMS template for the service, turn on **Configure per integration**. Then select a service template for each integration.
{% endstep %}

{% step %}

### Set the price

In **Upsell pricing settings**, click **Applies the whole stay** or **Applies a specific day**.

Select the **Pricing type**, and fill in the amount.

If guests can buy more than one, turn on **Guests choose a quantity**.

If guests must not buy the service for the current day, or only until a time, for example breakfast until 09:00, turn on **Limit same-day purchase**. Then click **Allow until a time** and type the time, or click **Don't allow**.
{% endstep %}

{% step %}

### Sync the charge to your PMS

If you want the charge and the payment on the guest's bill in your PMS, turn on **Sync to PMS folio**.
{% endstep %}
{% endstepper %}

## Ask guests for extra information

This part is optional. Skip it if you need no answers from guests.

{% stepper %}
{% step %}

### Add a custom field

In the **Custom fields** card, click **+**. For a custom upsell, the card shows after you select the service template.

Pick the kind of answer, for example **Text** or **License plates**. For all kinds other than **License plates**, pick a reservation custom field, or click **Create custom field**.
{% endstep %}

{% step %}

### Write the question

In **Label guests see**, type the question, for example *What is your arrival time?*. If you leave it empty, guests see the name of the custom field.

Turn on **Mandatory** if guests must answer before they can pay.
{% endstep %}

{% step %}

### Put the fields in order

Drag the rows into the order in which guests must see them. Check the guest portal preview next to the cards.
{% endstep %}
{% endstepper %}

## Turn on the upsell

{% stepper %}
{% step %}

### Decide how requests are confirmed

Turn on **Enabled** so that guests can buy the upsell.

If your team must approve each request, turn on **Needs approval**. Then decide if **Auto-refund on decline** is on.
{% endstep %}

{% step %}

### Choose when guests can buy

In the **Purchase window** card, turn on **Before check-in**, **During stay** or both.

If only some bookings must get the upsell, click the conditions button of the period and click **Add condition**. Only bookings that match all conditions see the upsell in that period.

If sales must stop some time before arrival, add **Hours until check-in** to the conditions of **Before check-in**, for example 24 hours.
{% endstep %}

{% step %}

### Check the setup

Read the readiness alert at the top of the editor. Fix each item, and click **Re-check**.

When the alert shows **Upsell setup ready**, the setup is complete.
{% endstep %}

{% step %}

### Save the upsell

Click **Create**, or **Save** for an existing upsell. The toast *Upsell created* shows.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**Use Needs approval for early check-in only when the turnover is short.** Instant confirmation sells better. Keep **Auto-refund on decline** on, so that a declined request does not make a refund ticket.
{% endhint %}

{% hint style="success" %}
**Give the earliest time range the highest price.** A high price for 09:00–11:00 and a lower price for 13:00–15:00 sell to the guest who must arrive early and to the guest who only wants to.
{% endhint %}

## Related

* [Upsells](https://docs.guestway.io/guest-experience/upsells.md): all fields and limits
* [How to review upsell requests](https://docs.guestway.io/guest-experience/upsells/how-to-review-upsell-requests.md)
* [Guest journey](https://docs.guestway.io/guest-experience/guest-journey.md): turn on the **Upsells** step


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.guestway.io/guest-experience/upsells/how-to-set-up-an-upsell.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
