Roadmap

What is coming, and what is deliberately not. Nothing here has a date attached — priorities move when customers tell us they should.

If something on this page is blocking you, say so. That is how things move up.

Money

Card on file with scheduled card holds. A renter saves a card, which enables charging on file for damages and the security deposit card-hold flow — auto-authorize a day or two before the event, release or capture afterwards.

Premium payouts to exhibitors electronically. Paying an individual out is a different Stripe product from the card rails the rest of the product runs on. Today premiums are a tally, a donate-back option, a record, and a check-list CSV.

Stripe Terminal tap at the gate, reusing the existing reader registry. The payment method is already recorded; the tap flow is not.

Fairground

Judge accounts as their own role. Judges use staff logins today. A dedicated role, plus per-judge queue assignment so a judge sees only their own entries.

Catalog PDF import. Extracting a published department PDF into the catalog automatically, plus a preloaded template library of common departments.

AI menu extraction for food vendors — a photo or PDF of a menu turned into the item list the vendor confirms. The paste format is already the target shape.

Vendor placement on the grounds map, and a public version of the map for attendees. It is admin-only today.

Sponsor logo roll-up for the program — one assembled export of every logo at each level, sized for print.

Entry money on the books. Entry fees are held on the entry rather than in the payments ledger. Unifying them is planned.

Communication

SMS to patrons. The plumbing exists for portal login codes; patron SMS does not yet.

Email delivery status. The email log records what was sent. Delivery-status enrichment from the mail provider would tell you what arrived.

Platform

A public REST API. See API.

Permit approvals. The government portal is live and read-only — a reviewer sees the list of flagged events but cannot record a decision in it. Per-permit approve / deny / needs-info, against a permit type and with a linked document, is planned.

Department-scoped permissions. So the food-vendor volunteer sees only vendors and the entries superintendent sees only their department, without granting whole-account access.

A fair website tier. A bundled website we set up and you edit in-house, with ticketing, schedule, and calendar baked in.

Deliberately not planned

Merging portal logins with staff logins. Renters, vendors, and exhibitors are separate systems from staff users on purpose. Merging them makes tenancy and permissions harder to reason about and is the kind of thing that leaks data across accounts.

Editing the activity log. It is an audit trail. If it were editable it would not be one.

Requesting something

Tell us what you are trying to do and what makes it hard today. That is more useful than a specification — it leaves room for a better answer than either of us has thought of.