> For the complete documentation index, see [llms.txt](https://uni.fotello.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uni.fotello.co/products/add-ons.md).

# Add-ons

Add-ons help you increase order value without slowing down checkout.

Fotello supports two add-on workflows:

* **Booking add-ons** are optional upgrades you attach to services and packages.
* **Fotello add-ons** are built-in Fotello-powered upsells like Twilight and Staging.

Use this page for booking add-ons. For built-in Fotello templates, see [Fotello Add-ons](/products/fotello-add-ons.md).

### Create a new add-on

You create booking add-ons the same way you create services.

{% stepper %}
{% step %}

#### Open Add-ons

Go to **Storefront → Products → Add-ons** or use [this link](https://app.fotello.co/dashboard/products?tab=addons).

<figure><img src="/files/EQP6K8KYS1unzP1xQ9Ep" alt=""><figcaption></figcaption></figure>

Click **Add Add-on** to open the add-on form.

<figure><img src="/files/JvfQvButRH07wNsbg2HD" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Add a type, name, and description

Pick the closest match for the add-on type to keep your catalog organized. Use a clear, customer-facing name. Keep the description short and outcome-focused.
{% endstep %}

{% step %}

#### Set the duration

Add a **duration** in minutes if the add-on affects the appointment length.

If it does not require on-site time, turn on **Time does not apply**.
{% endstep %}

{% step %}

#### Upload images

Add a few strong visuals. Images help customers understand the upgrade fast.
{% endstep %}

{% step %}

#### Add pricing tiers

Add either area-based or area-independent tiers to support different pricing options.

For each tier, fill out:

* **Tier name**
* **Price**
* **Min** and **Max** range (only for area-based tiering)

{% hint style="info" %}
If you want no upper limit, leave **Max** blank.
{% endhint %}
{% endstep %}

{% step %}

#### Save

Save the add-on when you're done.
{% endstep %}
{% endstepper %}

### Show add-ons in booking

Attach the add-on as a **recommended add-on** on a [Service](/products/services.md) or [Package](/products/packages.md).

When a customer adds that product during booking, Fotello surfaces the recommended add-ons at the right moment.

### Use Fotello add-ons for platform-service upsells

If you want to sell Fotello-powered extras like Twilight, Staging, Marketing Designs, or Premium Property Website, use the built-in templates in [Fotello Add-ons](/products/fotello-add-ons.md).

To let customers buy eligible Fotello add-ons after delivery, enable [Pay as you go](/billing/pay-as-you-go.md) and send the listing from [Deliver listing](/delivering-listings/deliver-listing.md).

### Best practices

* Keep booking add-ons tightly related to the selected service or package.
* Add time only when the upgrade affects scheduling.
* Avoid too many choices. Aim for 3–5 recommended add-ons per product.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://uni.fotello.co/products/add-ons.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.