Built-in view settings
Most storefront settings are site-wide and live under Settings → Storefront. A handful configure exactly one screen, and those live with that screen instead: open Storefront → Website, select a built-in view, and expand the Settings block below its sections.
The rule is worth keeping in mind when you go looking for something: if a setting shapes one view and nothing else, it is on that view. If it shapes the whole site, it is in Settings.
Each card in the block saves on its own — change one, save it, and the rest keep their current values. The block only appears if your role can read settings, and saving needs permission to change them.
Which views have settings
Section titled “Which views have settings”| View | Settings |
|---|---|
| Properties | Card display, catalog layout, search filters, pagination, search ranking |
| Property detail | Which sections appear, detail-page pricing |
| Checkout | Phone requirement, referrer options, priority countries |
| Blog | Post display |
| Booking | Page texts |
| Offer | Page texts |
Home, Wishlist, Blog post and Contact have no settings — they are pure content surfaces, and the Settings block does not appear on them. The Offer view has no content sections at all, so its Settings block opens expanded: there, the settings are the page.
Properties
Section titled “Properties”The search-results screen. Five cards:
Search Result Card Display — what each property card shows (guests, bedrooms, bathrooms, living space, distances) and how its location reads: hidden, place name only, breadcrumb only, or name plus breadcrumb. Hidden fields are not sent to the storefront at all, so this applies to every property card on your site, including gallery and search sections on your own pages.
Two pricing choices sit here too:
- Properties Page Pricing —
Summaryshows a nightly rate on each card,Nonehides prices entirely. - Lead Price Aggregation — whether that rate is the average (“Ø X per night”) or the cheapest seasonal rate (“from X / night”). This one reaches further than the card: it also drives map markers, the detail-page summary and SEO data, and it decides what the price filter and price sorting compare against.
Catalog Layout — with only a few properties, the full search UI (filters, map, sorting, pagination) is out of proportion. The simple layout drops it, and also changes the default navigation menu.
Search Filters — the distance thresholds offered in the filter drawer, in meters (empty = 500 / 1000 / 2000 / 5000 / 10000; up to 20 values, deduplicated and sorted on save), and the upper bound of the price slider (0 = 500 €).
Search Result Pagination — numbered pages with a total count, or lightweight Previous/Next. Turning the total off saves a database round-trip on large catalogs. Also sets how many properties appear per page, which drives the grid, the map markers and the pagination together.
Search Ranking — tunes the baseline quality score behind the “recommended” sort: relative weights for completeness, popularity and recency (0–1), a popularity cap, a recency horizon in days, and per-tag boosts added on top. Featured listings always sort first regardless. The rating weight is inert until reviews ship.
Property detail
Section titled “Property detail”One card, Property Detail Page, controlling which sections a listing page shows:
- Show cancellation policy — the policy card, when a policy is assigned to the listing.
- Show security deposit — the refundable deposit notice. On by default, because Reynt never collects the deposit and it appears in no price breakdown — see Discounts and fees.
- Show location map — the map and the location card around it.
Plus Detail Page Pricing: None hides seasonal prices, Summary shows the
average nightly rate, Detailed shows the full seasonal breakdown.
Checkout
Section titled “Checkout”Checkout — whether a phone number is required to book. Turn it off if you never call guests: the field stays on the form marked optional, and one less required field means fewer abandoned checkouts. This applies to your own website too, since bookings there go through the same API.
Referrer Options — the choices in the checkout’s “How did you hear about us?” select, per language. Leave the list empty and the field disappears.
Priority Countries — which countries sit at the top of the country dropdown in the booking form.
Post Display — whether the published date appears on blog cards and post detail. Turning it off hides the date but keeps it settable on a post to control sort order; structured data (JSON-LD) is unaffected either way.
Booking and Offer
Section titled “Booking and Offer”Both carry Page texts: per-language overrides of the storefront’s own wording on that page. Anything left blank keeps the built-in text, so you only fill in what you want to say differently.
Fields are grouped by what they belong to — general, status messages, stay
details, guest information, property information, invoice and price, offer
options, actions and dialogs, status screens, notices, and errors. Some texts
accept placeholders, listed under the field; texts with a singular and a plural
form take both, separated by a vertical bar (|).
The Offer view is the one to look at first: it has no content sections, so these texts are the entire page a guest sees when you send an offer.