> 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/readme.md). # Welcome to Vendor Space Vendor Space is the all-in-one platform for event organizers to manage vendors, booths, sponsors, and payments — without the spreadsheet chaos. Whether you're running a craft market, food festival, trade show, or community fair, Vendor Space gives you the tools to manage your entire vendor operation from one place. ## What you can do with Vendor Space * **Manage vendors** — Add, import, and track vendors across all your events * **Collect payments** — Send payment links and collect booth fees directly through Stripe * **Build custom forms** — Create application and registration forms for your events * **Track your pipeline** — See exactly where every vendor is in the booking process * **Manage booths** — Assign vendors to booths and track availability * **Coordinate sponsors** — Organize sponsorship tiers, track payments, and manage deliverables * **Communicate** — Message vendors and send automated reminders * **Check in vendors** — Track arrivals and setup on event day ## How this guide is organized * **Getting Started** — Create your account, connect Stripe, and set up your first event * **Events** — Everything about creating and managing events * **Vendors** — Adding, importing, and tracking vendors * **Payments** — Collecting payments and managing transactions * **Forms** — Building custom forms and managing submissions * **Sponsors** — Managing sponsorship packages * **Booths** — Booth inventory and assignments * **Communication** — Messaging, reminders, and campaigns * **Vendor Portal** — How your vendors interact with Vendor Space * **Operations** — Tasks, check-in, documents, and analytics * **Settings** — Account settings, team, and billing --- # 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://vendorspace.gitbook.io/docs/readme.md?ask=&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.