> For the complete documentation index, see [llms.txt](https://vendorspace.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendorspace.gitbook.io/docs/booths/creating-booths.md).

# Creating booths

Booths represent the physical spaces at your event where vendors set up. Vendor Space lets you create and manage every booth so you have a clear picture of your event layout and availability.

## How to Create Booths

1. Navigate to the **event** you want to manage.
2. Go to the **Booth Management** section.
3. Click the **Add Booth** button.
4. Fill in the booth details and click **Save**.

## Booth Fields

When creating a booth, you will provide the following information:

| Field            | Description                                                                                               |
| ---------------- | --------------------------------------------------------------------------------------------------------- |
| **Booth Number** | A unique identifier for the booth within this event (for example, "A1", "B12", "101").                    |
| **Label**        | An optional friendly name or description (for example, "Corner Booth by Entrance", "Large Island Booth"). |
| **Product**      | The booth product type linked to this booth, which determines its pricing and features.                   |

### Booth Numbers

Every booth must have a unique number within its event. This is how you and your vendors identify specific booths. You can use any numbering scheme that works for your venue:

* Sequential numbers: 1, 2, 3, 4...
* Lettered rows: A1, A2, B1, B2...
* Zone-based: North-101, South-205...

> **Tip:** Choose a numbering scheme that matches your venue's floor plan. If vendors can easily find their booth using the number, setup day goes much more smoothly.

## Creating Multiple Booths

If your event has many booths, you can add them one at a time using the Add Booth button. Enter each booth's number, optional label, and linked product, then save and repeat.

> **Tip:** Set up all your booths before you start assigning vendors. Having the complete layout ready gives you a clear view of total inventory and helps you make better assignment decisions.

## Linking Booths to Products

Each booth can be linked to a booth product. The product defines the booth's type, pricing, and any included features. For example, you might have products like:

* "Standard 10x10 Booth" at $300
* "Premium Corner Booth" at $500
* "Double Booth" at $550

Linking a booth to a product ensures that vendors are charged the correct amount and that you can report on revenue by booth type.

## What's Next

After creating your booths, you can:

* [Assign vendors to booths](/docs/booths/assigning-vendors-to-booths.md) as they are confirmed.
* [Track booth statuses](/docs/booths/booth-statuses.md) to monitor availability at a glance.


---

# 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://vendorspace.gitbook.io/docs/booths/creating-booths.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.
