Caching and data freshness
RentalTide keeps copies of data that rarely changes, so pages load fast and the platform is not asked for the same settings thousands of times a day. Most changes show up within seconds. A few screens hold data longer on purpose, and they are listed below.
Your booking page
When you save pricing, an inventory item, location settings or branding, the booking page's copy is cleared straight away, on every server.
- A new visitor sees the change at once.
- A browser that loaded the booking page in the last minute may show its previous copy for up to 60 seconds. A reload after that shows the change.
- A booking page left open in a tab keeps the prices it loaded until it is reloaded. It does not fetch new prices by itself.
- The single-item card widget (one item's card embedded on your website) refreshes within 5 minutes.
The price on the booking page is a display value. The amount actually charged is calculated on the server when the customer pays, so a stale price on screen can never cause a wrong charge.
Check the season. A date is priced by the season that covers it, so editing your off-season changes nothing for dates inside your peak season.
In the RentalTide app
Most screens refresh when you open them and again when you come back to the tab, so another device sees a change within seconds of looking at it.
| What | How fresh |
|---|---|
| Inventory and fleet | Refreshes when you open the page or return to the tab |
| Location settings | At once on the device that saved; on another device, when the page is reopened |
| Account and staff settings | Within about a minute |
| Journey board | Every 15 seconds while the tab is open |
| Today's hub | Every 15 seconds |
| Calendar | When you open it or return to the tab |
| Home dashboard revenue chart | Shows the last figures instantly, then refreshes |
| Analytics dashboards | Up to 5 minutes (forecasts up to 15 minutes) |
| Slip waitlist | May show a list up to 5 minutes old until you reload |
| Capital eligibility | Up to 24 hours, because it is worked out from 84 days of charges |
| Logos, photos, attachments | Can stay in your browser for hours |
Walk-up prices and taxes are calculated on the server for every quote, so a tax rate you change applies to the next walk-up without waiting.
What is never cached
These are always read live:
- Bookings and payments. A booking or payment is written in the same request that makes it, so no staff member ever sees a booking go missing because of a cache.
- POS transactions. Every sale, refund and till adjustment is recorded at once.
- Ledger entries and accounting. Financial state is always read from the source of truth.
- Walk-up timing. The "left" and "back" times update in real time.
- Promo codes. A new code works on the next booking. A booking page that was already open keeps its old prices until it is reloaded.
How to force a refresh
From least to most disruptive:
1. Use the page's refresh button
Analytics, reporting, the journey board and the home dashboard have a refresh icon in the page header. It fetches the latest data for that page.
2. Navigate away and back
Reopening a page from the sidebar fetches its data again.
3. Hard-refresh the browser
A hard refresh drops everything the tab is holding and reloads it from the server.
- Mac:
Cmd + Shift + R - Windows / Linux:
Ctrl + Shift + R - iOS / Android: pull down to refresh, or close and reopen the tab
4. Log out and back in
The most thorough option. It also clears your sign-in token, which is worth trying if you think a permission change has not reached you.
Frequently asked
Will my customers see an old price after I change it?
Only if they had your booking page open before the change. A new visitor sees the new price at once; anyone else sees it after reloading the page (within a minute of your save at most). The card widget catches up within 5 minutes.
Does caching affect payment processing?
No. The charge is always calculated on the server at the moment of payment.
Can I turn caching off for my location?
No, and there is rarely a need: saving already clears the booking page's copy. If something still looks stale after a reload, contact support.
My change still has not appeared after a reload. What now?
It is not a cache issue. Check that the change saved (and, for prices, which season covers the date), then reach out to support if needed.
Summary
- Saving pricing, items, location settings or branding clears the booking page's copy at once. A browser may hold its copy for up to a minute; reload to see the change.
- The single-item card widget refreshes within 5 minutes.
- Most of the app refreshes when you open a page or return to the tab. Analytics can be up to 5 minutes old.
- Bookings, payments, POS transactions and the ledger are never cached, and the charge is always calculated on the server.

