Designing CMS for Tours collection

Design help CMS
1

Hello Webflow Community,
I’m working on a project that involves managing multiple tours each with different days offering. I need to track the capacity for each specific date in case it’s full. I’m seeking advice on the best way to design this.

Current Approach:

  • I have set up a multi-reference ‘Tours Schedule’ (with fields Duration, Capacity, and Date) in my ‘Tours’ Collection.

  • Each Tour can take multiple dates each with different capacity.

For example I have a tour to a historic place, I would create ‘Tours Schedule’ records for each day it’s offered, and then link them in ‘Tours’.

Concerns:

  • I want to offer a certain tour throughout the year, but in my current approach I would need 365 record for each tour, which seems inefficient.

Possible solution:

  • I’m considering using a JSON field for dates, this way I could delete the ‘Tours Schedule’ Collection and add a ‘Dates’ JSON field. However, I’m not sure if this approach is reliable in webflow.

I would greatly appreciate any insights.

2

You’re building an administrative nightmare if you go that route.

The CMS does not have the capabilities needed to support an application. No querying or batch operations of any kind. No two-way relations. No user-specific data support. No opportunity to define indices, keys, JSON fields. No transactional integrity.

You’ll be much better off integrating a tour booking system, and the administration alone is worth it for your client. Not to mention billing support, scheduling and inventory support, customer data security, and so much more.

2 Likes