Have something to say?

Tell us how we could make the product more useful to you.

New Event Status — "Completed" or "Archived"

The Problem: Currently, the Experiences app mirrors Shopify’s binary product status: Active or Draft. While this works for inventory, it fails to meet the logical lifecycle of an event. Draft implies a "work in progress" or an event that has not yet occurred. Active implies the event is currently bookable. The Gap: Once an event is over, moving it to "Draft" feels counterintuitive and creates administrative clutter, as there is no way to distinguish between an event that is finished and an event that hasn't started yet. The Proposed Solution: Introduce a third status—Completed or Archived—to represent the post-event phase. This status would serve as a "Deep Freeze," allowing users to: - Preserve all historical booking data and attendee lists. - Remove the event from the live storefront/booking calendar. - Clearly distinguish past successes from future drafts in the administrative dashboard. User Value: "Naming is pretty important, as draft implies it hasn't happened yet... we run many events that are active, but then should be marked as complete or finished when the event has happened." — Experiences customer For high-volume users like galleries and workshops, accurate naming is essential for clean reporting and team communication. It prevents the accidental deletion or "reactivation" of past events. Functional Requirements: Manual Toggle: Allow users to manually switch an event from Active to "Completed." Visual Distinction: Use a distinct color/badge (e.g., Gray or Blue) in the dashboard to separate completed events from Active (Green) and Draft (Yellow). Read-Only Data: Ensure that marking an event as "Completed" does not delete the associated customer data or sales history. Suggested Labels Option A: Completed (Most descriptive for events) Option B: Archived (Standard software terminology) Option C: Past Event

Janeen Gleeson 1 day ago

Add the ability to convert a non-e-ticketed event into an e-ticketed event and then send the tickets to previous bookings for the experience.

Sometimes we want to convert a non-e-ticketed event into a ticketed event so we can have ticket images and QR codes to scan. For example, if we forget to turn that feature on but sell bookings, at some point during or after the sales have happened, we want to convert those customers into ticketed customers. Require an action on the part of the merchant to retroactively create those tickets and then have a means of sending them to the customer.

Nathaniel Brooks 1 day ago

Independent Participant Tracking (Non-Inventory Bookings)

The Problem: Currently, all booking types in the Experiences app automatically deduct from the total product inventory. This prevents merchants from selling "Add-on" spots (like lunch guests, observers, or companions) who need to be accounted for in terms of names and dietary requirements but do not take up a seat in the core activity (e.g., a cooking class or workshop). Proposed Solution: Introduce a toggle within the Booking Type settings to "Exclude from Inventory." This would allow a merchant to: - Track Capacity for the Core Activity: Ensure the primary class/experience doesn't oversell. - Capture Add-on Data: Collect names, contact info, and dietary requirements for guests who are attending only a portion of the event (e.g., the meal). - Unlimited or Separate Scaling: Allow these guests to be booked without hitting the "Sold Out" threshold of the main event. User Scenario: "I have a cooking class with 10 spots. I want to allow those 10 students to bring a friend for the lunch portion afterward. I need to know the friends' names and allergies, but I don't want the app to stop selling class spots just because 10 friends have already signed up for lunch." Key Requirements: - Inventory Toggle: A per-booking-type setting: [ ] Reduce Product Inventory. - Data Collection: Must still trigger the "Additional Information" forms for these non-inventory guests if that form is active. - Manifest Integration: These guests should appear on the attendee manifest and exports, clearly labeled by their booking type.

pizzini-wines.myshopify.com 3 days ago

Improve Export Reporting Flexibility and Usability for Instance-Level Data

As a Merchant, I need to generate accurate, instance-level reports for single- and multi-day workshops so that I can reconcile income, report to funders, and manage financial performance efficiently. Problem: Current Shopify and Experiences reports don’t provide data at the instance level. The existing export requires significant manual manipulation and lacks the fields needed for proper reconciliation and funder reporting. Key Issues: Export only shows total order price — line item price is missing. “Starts at” and “Order created” fields are text strings combining date and time, making sorting/filtering difficult. Date range filter behavior is unclear for multi-day events. Date picker requires manual clicking through calendars, slowing large-range reporting. Requested Enhancements: 1. Add line item price (before tax/fees) to the export. 2. Allow exports based on either order created date or instance date. 3. Split “Starts at” field into separate, sortable “Start date” and “Start time” fields. 4. Split “Order created” into separate, sortable “Order date” and “Order time” fields. 5. Enable typed date entry in date range inputs instead of requiring calendar clicks. Impact: These changes would allow Merchants to build accurate, automated reports for programme, financial, and funder reporting — eliminating extensive manual data handling and improving efficiency for organizations running large event programs.

Mark About 1 month ago

Ability to add a convenience fee or other charge at checkout to an experience/event purchase fee/charge

Similar to how most ticketing platforms charge convenience fees/charges, create a setting that allows store owners to set a fee, on a per experience basis, that is charged in the Shopify checkout. Note: Making a /cart /checkout charge non-optional can be tricky because Shopify is designed to let customers edit the cart line items. If Experiences was to do this in a way that creates a non-optional charge to make the customer to pay for the main experience/event + the convenience charge, the app may need to create a new experience + charge custom SKU/product that could result in many new, temporary, Shopify products.

An Anonymous User 10 months ago

Ability to add a notice for a particular day(s) that would show up in the calendar view

As a merchant, sometimes I want to put a notice on the calendar that isn't bookable, may not even have a time, but applies to a day or series of days. For example, "No pokemon today" or "XYZ unavailable" over a span of days. This feature would be helpful for merchants who rely heavily on Experience's calendar feature. https://help.experiencesapp.com/en/articles/4770454-add-a-monthly-calendar-view-to-your-shop-to-show-all-your-experiences-in-one-place

Berry Hatfield 11 months ago

Show an experiences as "sold out" when in a Shopify collection page

It would be helpful to have an experience show as sold out in a collection grid (Shopify terminology) when sold out. This would keep the customer from having to click into the product page (PDP) just to find out it's sold out. Considerations: - This would need to only work if 100% of all time slots are sold out - Most merchants have more than one bookable time slot and the Experiences app only looks so far into the future (currently 6 months?), so it's possible something would show as sold out if there were no near-term availability but far future availability.

stitcherystudio.myshopify.com 11 months ago