> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orriven.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Exhibition overview

> Run the trade-show side of an event: exhibitors, booths, booth types and orderable services. An optional module, off by default.

The Exhibition module brings the **company** into your event. Registration handles people — one person, one ticket. A trade show adds a second kind of participant: a company that confirms its attendance, brings a staff roster, occupies booths and orders services. Exhibition mode models exactly that.

It is an **optional module, off by default**. Every event starts without it; enabling it is a per-event decision.

## Enable it

Click **Exhibition** in the event navigation. While the module is off, the entry leads to an enable page describing what it adds. Click **Enable Exhibition** — the module's four pages join the event's navigation, and nothing else about the event changes.

## The cast

<CardGroup cols={2}>
  <Card title="Exhibitors" icon="building-2" href="/en/exhibition/exhibitors">
    The company participant: one company in this event, with contacts, a staff roster, a badge code, and a confirmation lifecycle.
  </Card>

  <Card title="Booth types" icon="layout-template" href="/en/exhibition/booth-types">
    The catalog, set up once: "3×3 standard", "6×6 island" — a name, description and specification that booths reference.
  </Card>

  <Card title="Booths" icon="store" href="/en/exhibition/booths">
    The inventory and the daily allocation task: real units with a hall, a number and an occupant. Two booths of the same type are not interchangeable.
  </Card>

  <Card title="Services & materials" icon="plug" href="/en/exhibition/services">
    What exhibitors order for their booths — power drops, furniture, lead scanners — and the orders recorded against each item.
  </Card>
</CardGroup>

## Suggested setup order

<Steps>
  <Step title="Enable the module">
    From the **Exhibition** entry in the event navigation.
  </Step>

  <Step title="Define booth types">
    The catalog first: a [booth type](/en/exhibition/booth-types) describes what a booth is, then the units under it are the actual inventory.
  </Step>

  <Step title="Name your halls as venues">
    A booth's hall is a **venue** from [Program & venue](/en/program/venues) — booths and the agenda speak of the same places, so "Hall A" exists once.
  </Step>

  <Step title="Add the booths">
    Create each [booth](/en/exhibition/booths) with its hall, number and type.
  </Step>

  <Step title="Create service items">
    Publish the [services & materials](/en/exhibition/services) exhibitors can order.
  </Step>

  <Step title="Add exhibitors and allocate">
    Add each [exhibitor](/en/exhibition/exhibitors), link a badge code for its staff, assign booths, and record service orders as they come in.
  </Step>
</Steps>

## How it connects to the rest of the event

* **Exhibitor staff are ordinary attendees.** A staff member registers like any guest — typically through the exhibitor's dedicated **badge code** — and is then attached to the company. There is no second identity.
* **Badge quotas are redemption codes.** An exhibitor's staff allotment is a code from [Offers & redemptions](/en/ticketing/offers) linked to the exhibitor; its use limit is the quota. See [Exhibitors](/en/exhibition/exhibitors).
* **Halls are venues**, shared with the [program layer](/en/program/venues).
* **Automations can react to exhibition moments** — an exhibitor being confirmed, a booth being assigned — with the company's contact email as the recipient. See [Automations](/en/marketing/automations).

## Rules to know

* **Everything here is organizer-driven today.** There is no exhibitor self-service portal yet — companies don't log in; your team records confirmations, allocations and orders from the console.
* **Everything is free today.** Booth types and service items carry no prices; publishing them is a catalog decision. Pricing arrives later on the same definitions.
* **Nothing important is deleted.** Exhibitors, booths, booth types and service items archive or cancel rather than delete, so history and references stay intact.