**Short answer:** JAS covers the core workflow this prospect describes: application, jury, accept or decline, then collect vendor fees. Before you promise two specifics, confirm them with product: true per-item accept/decline inside a single application, and fully custom fees set per vendor after acceptance. This article helps you scope those needs accurately for fairs, festivals, and Renaissance Faire–style marketplaces. Use it to qualify the prospect, not to replace a demo. --- ## 1. Confirm the overall fit JAS is built around jurying, acceptance, and booth payments. It does not include ticketing, volunteer management, or entertainment scheduling. For prospects who don't want those tools, that focus is a selling point. The standard flow maps to their process like this: 1. **Applications.** Vendors apply through a configured event. See [Creating a New Event](/help/article/creating-a-new-event) and [Configure Application Categories](/help/article/configure-application-categories). 2. **Jury.** Jurors review and score applications. See [Standard Jury Setup](/help/article/standard-jury-setup) or [Rolling Jury Setup](/help/article/rolling-jury-setup). 3. **Accept or decline.** Results go out to applicants. See [Finalizing Your Jury](/help/article/finalizing-your-jury) and [Sending Standard Jury Results](/help/article/sending-standard-jury-results). 4. **Vendor fees.** Accepted vendors complete an acceptance form and pay. See [Acceptance Form and Booth Payments](/help/article/acceptance-form-booth-payments) and [Set Up Payment Processing](/help/article/set-up-payment-processing). **Rolling jury tip:** A rolling jury reviews applications as they arrive instead of all at once after a deadline. That is often a good fit for a long season with ongoing intake. ## 2. Handle the "jury individual items" request carefully JAS juries at the **application** level. The prospect wants to say yes to some wares and no to others from the same vendor. Before promising anything, walk through these options: 1. **Category-based structure.** Set up categories by product type, such as Leatherwork, Jewelry, or Resale. Vendors then apply separately for each product line, and each application gets its own decision. Configured in Event App Categories (`/events/$eventId/app-categories`). 2. **Split applications.** JAS supports splitting applications through the Event Application Splitter (`/events/$eventId/application-splitter`). See [Managing Split Applications](/help/article/managing-split-applications) and [Split Jury Setup](/help/article/split-jury-setup). - **Requires confirmation:** whether splitting can isolate individual items for separate yes/no decisions in the way this prospect describes. 3. **Item detail in the application.** Use [Configure Artwork Requirements](/help/article/configure-artwork-requirements) and [Custom Application Requirements](/help/article/custom-application-requirements) to collect per-item images and descriptions. Jurors can then evaluate each item, even when the formal decision is made per application. **What not to say:** Don't promise a checkbox-style accept/decline per item within one application unless product confirms it. ## 3. Scope variable vendor fees This prospect has no fixed booth inventory. They lay out the leased grounds each season after acceptance, and fees depend on tent or space size. 1. Booth fees are configured in Event Booth Payment Specs (`/events/$eventId/booth-payment-specs`) and tracked in Event Booth Payment (`/events/$eventId/booth-payments`). 2. The acceptance form is a natural place to collect each vendor's space needs, such as tent dimensions and frontage. See [Acceptance Form and Booth Payments](/help/article/acceptance-form-booth-payments). 3. **Requires confirmation** before quoting: - whether payment specs can offer multiple size or price options for vendors to select, and - whether an admin can set a **custom amount per vendor** after acceptance, as an invoice-style flow. 4. Event Coupons (`/events/$eventId/coupons`) exist, but don't position coupons as a fee-adjustment method without confirming that use with product. ## 4. Set up non-art vendors Most of this marketplace is handcrafted artisan wares, which is squarely JAS territory. For the minority of vendors: 1. **Give each type its own category**, such as Food, Services (massage, tarot), and Resale. Each can then be juried, filtered, and reported on separately. See [Search and Filter Applications](/help/article/search-filter-applications). 2. **Collect type-specific requirements**, such as health permits, insurance, or a service description, through [Custom Application Requirements](/help/article/custom-application-requirements). 3. **Adjust image expectations.** A tarot reader won't submit the same portfolio as a blacksmith. Confirm how per-category image requirements can be configured before demoing this. The prospect has already said they can work around edge cases. Lead with how well the artisan majority fits, and be candid about the service vendors. ## 5. Before the demo - Get answers on the two "requires confirmation" items in sections 2 and 3. - Log the prospect's fee model and vendor mix on the lead record (`/leads/$leadId`) so onboarding inherits the context. - Any pricing or plan details must come from the current deal terms. Don't estimate. --- **Suggested follow-up articles (not yet documented):** - Configuring Variable Booth Fees by Space Size - Setting Up Food and Service Vendor Categories - Positioning JAS for Renaissance Faires and Seasonal Fairs