I’m building a Webflow site for a co-ownership real estate company. The business has two main services:
Weekly Rentals: I’ve already planned the CMS for this by creating a list of weeks and adding a multi-reference field to each property to indicate which weeks are available for rent.
Weekly Sales: Here’s where I’m stuck. Each property has a unique price for every week, and there are 19 properties with 52 weeks each.
My challenge is creating a CMS structure that can handle this data efficiently while being scalable and manageable. I thought of creating a collection for “Sales Weeks” where each week links to a specific property and includes its price. However, with 19 properties and 52 weeks, that’s nearly 1,000 items in the CMS—seems cumbersome to manage.
Does anyone have suggestions for a more practical or automated way to set this up? Any tips for better structuring this data in Webflow, or tools/automations that could make this process smoother?
Thanks in advance for your help!
This is what we need. We are transfering from a wordpress to webflow.
What are you doing with the data?
Your options shift a bit depending on whether you’re only displaying one Property’s pricing at a time, or building a page that shows e.g. 100 properties.
Since the CMS doesn’t have a tabular ( spreadsheet-style ) editing mode, you’re right that it’s not well-suited to managing thousands of datapoints.
One option is to admin that data externally, e.g. AirTable and use WhaleSync to sync that data over to the CMS. That makes it much easier to enter and update.
If changes and updates are infrequent, there are more manual sync tools- PowerImporter pro, and Finsweet has a new one that could be ideal here.
That would give you a fairly ideal setup - easy admin plus easy CMS-driven designer work.
Another option;
If the data is only displayed on the individual Property page, then you might remove it from the CMS altogether. I’ve found that Google Sheets is a surprisingly good way to do this for moderate-traffic sites; you could keep the weekly pricing there in a per-property sheet and retrieve the CSV or JSON only with Google’s export URL format, which is relatively easy to process with Javascript. Some programming there though.
I’d also reconsider your data structure.
It looks like what you want is a list of weekly pricing between date X and Y, and that pricing often stays consistent for awhile.
If you’re retrieving that with a piece of JS, then you could just retrieve the changes. e.g. Week 12 = 120, Week 14 = 140. Then there’s a lot less data to admin, and you just calculate the missing weeks until the next change. Easier admin, but client side dev to expand and render that data.
Michael, thanks in advance for taking the time to try to help me.
So in terms of data, the site will have a page for rentals with al the houses then a page for the sales with all the houses, then a page per individual house both for rentals or sale path. In the sales it will have a price per week available, an the individual rental page will have a only price from XXXXX€ then if the person is interested they will get in touch with the client.
I like that idea of the google sheet, i was thinking about that myself but my programming skills are very very limited.
As a general approach, if the number of houses is relatively low, and the traffic is reasonable, I’d personally go with the Google sheet, because it’s very easy to admin. However it requires some programming to extract and present the data. It’s an excellent approach for low-budget, low-volume projects.
If the traffic is higher or the number houses is higher e.g. > 20, and/or you don’t have a dev on the team, I’d definitely go towards Airtable → sync → CMS using Whalesync or another product. There is more infrastructure to setup, and a higher monthly cost, but it’s far more robust as a solution.
Sync between the CMS and Google Sheets? I have not seen any tools that support a direct sync. You could look at Whalesync, it syncs between a lot of different services.
Otherwise automations could work but that would be a bit rough to build, because spreadsheets are so fluid in their editing approach.
Are you needing some dev help building this?
Overall it’s not a complex feature, but it’s important to choose the right path or you’ll hit a wall as the site grows.
