Booking Engine

10 articles Marcus Cole By Marcus Cole

Booking Engine

New Setup Add Channel - ChannelRUSH Booking Engine Admin -> Settings -> Channels -> Add New Click 'Add New' from the 'Channels' section, and add the 'ChannelRUSH Booking Engine'. CRS Settings Admin -> Settings -> Channels -> ChannelRUSH CRS If the 'ChannelRUSH CRS' link does not appear in 'Admin -> Settings -> Channels', make sure the channel 'ChannelRUSH Booking Engine' is added to the property's set of channels. You can also add the ChannelRUSH CRS as a channel directly in addition to the ChannelRUSH Booking Engine. Related Article - ChannelRUSH CRS Please complete the ChannelRUSH CRS Settings, which configure how your booking enigne will operate. Use the following article for guidance: 💡 ChannelRUSH CRS ChannelRUSH CRS Domain Setup To have the booking engine load under a subdomain of your primary domain - i.e. booking.yourdomain.com, in your DNS provider config, create a subdomain of your choice (i.e. booking), and set the following record. Record Type: CNAME Host: booking (or the subdomain of your choice) Points To: reservation.services TTL: 12 Hours (or something reasonable / greater than 12 hours)

Shift4

Shift4 Support Shift4 Support - Chat, Email, Phone https://www.shift4.com/support Shift4 Status Page https://status.shift4.com/ Shift4 Knowledge Base https://shift4.zendesk.com/hc/en-us Setting Shift4 Up - Access Tokens To use Shift4 as your credit card processor with our booking engine, you need to create an 'Authorization Token' and provide it to us. Once we have the 'Authorization Token' we use it to create an 'Access Token' using our client GUID. Once this is setup, we can use your Shift4 account to process payments for your booking engine setup with ChannelRUSH.

Booking widget: embed guide

The widget is one script served from https://be.channelrush.net/widget/v1/channelrush.js. It renders the whole booking flow (search → rooms → cart → extras → guest → payment → confirmation, plus "look up, change or cancel a booking") into a <div> on your page, inside Shadow DOM, so your site's CSS and the widget's CSS never interfere. The snippet <div data-crush-key="pk_live_xxxxxxxxxxxx" data-crush-lang="en-US" data-crush-currency="USD" style="--crush-primary:#0d47a1;"></div> <script async src="https://be.channelrush.net/widget/v1/channelrush.js" data-cookieconsent="ignore" data-ot-ignore></script> You get the key (pk_live_… / pk_test_…) from ChannelRUSH → Admin → CRS Settings → Booking Widgets. A key is bound to the domains you list there; the widget refuses to load anywhere else ("Booking widget not allowed on this site"). Attributes on the <div> Attribute Required Meaning data-crush-key yes Public key for the property. data-crush-lang no Language, e.g. en-US , de-DE . Set it to the page's own language and the widget follows it with no language selector . Leave it out and the widget starts in the property's default language and shows a selector when the property offers several. data-crush-currency no Initial currency (ISO 4217). Same rule. data-crush-mode="searchbar" no Render only the search form; on submit send the visitor to data-crush-target . See wix.md . data-crush-target with searchbar URL of the page that hosts the full widget. data-crush-room-type no A room type id: the widget books that room only , for a widget on the room's own page. See Booking on a room page . data-crush-fallback-url no Your hosted booking page; shown as a link if the widget cannot load at all (blocked script, very old browser). data-crush-layout="compact" no Force the compact layout used inside sandboxed iframes (auto-detected on Wix). style="--crush-…" no Theme variables, see theming.md . Script form (advanced) <script src="https://be.channelrush.net/widget/v1/channelrush.js" data-cookieconsent="ignore" data-ot-ignore></script> <script> ChannelRUSH.init({ key: 'pk_live_xxxxxxxxxxxx', el: '#book-here', language: 'en-US', currency: 'USD', theme: { primary: '#0d47a1' }, onEvent: (name, detail) => console.log(name, detail) }); </script> window.ChannelRUSH is the only global: init(options), destroy(el?), version. Under a strict CSP the second, inline <script> needs your own nonce/hash; prefer the declarative form. Testing against the test server To try the widget against the ChannelRUSH test environment instead of production, change only the script URL and use a test key: <div data-crush-key="pk_test_xxxxxxxxxxxx"></div> <script async src="https://testbe.channelrush.net/widget/v1/channelrush.js" data-cookieconsent="ignore" data-ot-ignore></script> The widget automatically talks to the server it was loaded from (any *.channelrush.net host over https), so the test snippet needs no extra configuration — swap the script URL back to be.channelrush.net with your pk_live_… key to go live. Test keys only work on the test server (and on localhost); bookings made there use the test card and never reach a live payment gateway. If your site sends a Content Security Policy, allowlist https://testbe.channelrush.net while testing (see csp.md). Platform guides - WordPress — Elementor, Divi, Gutenberg - Squarespace - Wix — read this one before embedding on Wix - Webflow - Static HTML / any other site Reference - csp.md — Content Security Policy directives - cookie-consent.md — Cookiebot / OneTrust - theming.md — every --crush-* variable - events.md — crush:* events, GA4 / Google Tag Manager - versioning.md — pinning, /v1/ vs /1.x.y/, browser support From your ChannelRUSH settings What the widget picks up from the property's own settings, with nothing to configure on your page: - Extras for the stay. When the property sells add-ons (airport transfer, breakfast, parking …), the guest gets an extras step between the cart and the guest details, with a photo, the price and a quantity for the whole booking or per room — for an extra priced per person, how many of the guests take it (up to the room's guests). The server prices every extra — the widget never does arithmetic. A property that sells none never sees the step. - Closed dates in the calendar. Days the property takes no check-in or check-out, and minimum stays, are greyed out in the date picker, each saying why. The widget only ever greys out a stay the booking engine would refuse anyway; when in doubt it leaves the day open and the search says what is available. Sold-out nights are struck through but can still be picked: the guest gets the results for those dates, which say which rooms are sold out. - Flexible dates. When the property switches it on, "Flexible dates? See open dates" appears under the search form and on the room list. It opens a calendar of the days a stay can start on for the nights the guest chooses — with the lowest price per night on each day, taxes and fees included, if the property shows prices — and "See rooms" lists the rooms for the dates picked. With prices on, the date picker also shows the price under each check-in day. The property may also show "Only N rooms left" when few remain; ChannelRUSH leaves that off unless the property turns it on. Prices include taxes and fees Every room price a guest sees includes the taxes and fees set up for the property in ChannelRUSH: the total for the stay, the average per night, and a note saying "Includes taxes and fees". A promo code shows as the amount saved. In the cart each room shows its full price too. The price summary lists the room rate, each fee and tax, and the total, and the total is the most prominent figure. This follows the US FTC rule on fees for lodging (16 CFR 464, in force since May 2025) and the EU and UK rules on showing the final price. If your own pages quote room prices next to the widget, include the taxes and fees there too. Deep links Any page with the widget accepts these query parameters (all optional, prefixed so they never collide with your own): Parameter Meaning crush_ad , crush_dd Arrival and departure, yyyy-MM-dd . Both present: the widget opens straight on the room list for those dates. crush_na , crush_nc Adults and children (one room). crush_promo Promo code. crush_cur , crush_lang Currency (ISO 4217) and language, e.g. EUR , de-DE . crush_rt A room type: the widget books that room only , with a "See all rooms" link for the others. crush_rp A rate plan: that rate is preselected on every room that offers it. crush_cal A month, yyyy-MM : the widget opens on the flexible-dates calendar at that month (when the property has it on; otherwise the search form). With it, crush_ad / crush_dd are the stay already picked on the calendar. crush_n With crush_cal : the number of nights the calendar prices, 1–30. ?crush_ad=2026-09-10&crush_dd=2026-09-13&crush_na=2&crush_nc=0&crush_promo=SUMMER&crush_cur=EUR&crush_lang=de-DE opens the room list for those dates. ?crush_cal=2026-10&crush_n=3&crush_na=2 opens the flexible-dates calendar on October, pricing three-night stays for two adults. ?crush_lookup=1&crush_res=HV100123 opens "Find your booking" with the reservation number filled in (this is what the confirmation email links to). "Book this room" and rate landing pages A guest who clicks "Book this room" has already chosen the room, so crush_rt focuses the booking flow on that room. Existing /book?crush_rt={roomTypeId} links do not need to change, and no new booking API is needed: - The search form names it ("Your room: Deluxe Double"). Guest selection follows the room’s capacity, counting adults and children together. If a link or saved search specifies too many guests, the widget asks the guest to correct the party size or see all rooms. - The room list shows that room alone, with its rates. Other rooms, sold-out ones included, are not listed. - The date picker uses this room’s restrictions. When flexible dates are enabled and the cart is empty, "See open dates" shows this room’s available stays. With calendar prices enabled, prices are for this room, not a different room at the property; they are not limited to a rate preselected with crush_rp. - When the room cannot be sold for the dates, the widget shows the reason when available, such as sold out, no check-in or check-out that day, or a minimum stay. Otherwise it shows a general unavailable message. - While choosing dates or viewing results in the full widget, "See all rooms" returns to the property’s room list and guest limits. The linked room is listed first when available for the party. Reloading while the room link remains in the address restores the room-focused view. crush_rp preselects that rate on every room that offers it; a rate the room does not offer leaves that room's first rate selected. Nothing is added to the cart until the guest presses Select, and after that "Add another room" offers the same room again (or every room, after "See all rooms"); Change on a cart line of another room (one already in the cart before the link) offers every room. A room id the property does not show (unknown, or switched off) books nothing alone: the widget lists every room, without an error. While the search form or the room list is showing, both parameters stay in the address through a currency or language switch, a reload and the browser's Back button; from the cart on they leave the address. Reloading there restores the cart without a URL-only room restriction. An inline data-crush-room-type remains configured after a reload, including at the cart. - A room page's button: https://www.yourhotel.com/book?crush_rt=1234 — no dates needed: the guest picks them on the booking page. A guest who already searched in this browser tab goes straight to that room's rates for those dates, with any rooms already chosen kept. - An ad for a rate: https://www.yourhotel.com/book?crush_ad=2026-10-02&crush_dd=2026-10-05&crush_rp=5678. Use https://be.channelrush.net/widget/v1/channelrush.js (recommended), or pin https://be.channelrush.net/widget/1.2.0/channelrush.js. Version 1.2.0 supports this room-specific flow. A widget pinned to 1.1.0 or older only lists the crush_rt room first among the others; update the script URL to get the new behavior. If switching a pinned script with an integrity attribute to /widget/v1/, remove that attribute; if staying pinned, use the matching hash in Versions and pinning. Booking on a room page To let guests book a room without leaving its page, put the widget on the room page and name the room with data-crush-room-type. It works as a crush_rt link does, and wins over a crush_rt in the page's address: <div data-crush-key="pk_live_xxxxxxxxxxxx" data-crush-room-type="1234"></div> <script async src="https://be.channelrush.net/widget/v1/channelrush.js" data-cookieconsent="ignore" data-ot-ignore></script> The whole booking (dates, rates, extras, guest details, payment) then happens on the room page. Use one widget per page: only the first one on a page keeps its steps in the address. A room page's search bar can name the room the same way (data-crush-mode="searchbar" with data-crush-room-type): it uses the room’s combined adult-and-child capacity and sends the room to the booking page, unless data-crush-target names one itself. Replace 1234 with the room's id from the content API, the same id used in crush_rt. Room type and rate plan ids are also listed in CRS Settings → Booking Widgets → How to use a key → Site content → Room type and rate plan ids, for room pages and booking links. Your ChannelRUSH contact can help identify the right room. A search form on another page To let guests pick dates on your home page and land on the booking page with the rooms already listed (no second click), use either: 1. The widget's own search bar — data-crush-mode="searchbar" with data-crush-target="/book" (see wix.md). It has the widget's date picker and checks the dates before leaving the page. On a room page, name the room with data-crush-room-type="1234" (or in the target: data-crush-target="/book?crush_rt=1234"). 2. Your own HTML form — any GET form whose fields carry the parameter names. Style it as you like; no script is needed on that page: <form method="get" action="/book"> <input type="date" name="crush_ad" required> <input type="date" name="crush_dd" required> <select name="crush_na"><option>1</option><option selected>2</option><option>3</option><option>4</option></select> <select name="crush_nc"><option selected>0</option><option>1</option><option>2</option></select> <input type="hidden" name="crush_rt" value="1234"> <!-- optional: on a room page --> <button>Check availability</button> </form> <input type="date"> submits yyyy-MM-dd, which is what the widget reads. A date-picker plugin that submits another format (10/02/2026) is ignored — the guest then lands on the search form instead of the room list. Empty fields are ignored. Google Hotel Ads A Google Hotel Ads or free booking link click can land on your widget page the same way. The landing URL Google opens looks like: https://www.yourhotel.com/book?crush_ad=2026-10-02&crush_dd=2026-10-05&crush_na=2&crush_nc=0 If ChannelRUSH runs your Google Hotels connection, tell your ChannelRUSH contact the booking page's address and we set it up. If you manage your own Hotel Center point-of-sale, build the URL from Google's variables: crush_ad=(CHECKINYEAR)-(CHECKINMONTH)-(CHECKINDAY)&crush_dd=(CHECKOUTYEAR)-(CHECKOUTMONTH)-(CHECKOUTDAY)&crush_na=(NUM-ADULTS)&crush_nc=(NUM-CHILDREN). Conversion goals See events.md: after a booking the page address gains crush_confirmed=1. What the widget never does - No cookies. Search criteria and the cart live in sessionStorage for the tab only; card data never leaves the payment form. - No requests to anything but the channelrush.net host it was loaded from — https://be.channelrush.net for the live snippet — plus Cloudflare Turnstile for bot checks on lookup / change / cancel and after repeated payment failures. - No changes to your page's styles or globals beyond window.ChannelRUSH. WordPress Works with any theme and page builder. Paste the snippet where the booking form should appear. Add data-cookieconsent="ignore" / data-ot-ignore to the script tag if you run Cookiebot or OneTrust (cookie-consent.md). <div data-crush-key="pk_live_xxxxxxxxxxxx" data-crush-lang="en-US" data-crush-currency="USD"></div> <script async src="https://be.channelrush.net/widget/v1/channelrush.js" data-cookieconsent="ignore" data-ot-ignore></script> Elementor 1. Edit the page with Elementor, drag an HTML widget (Basic → HTML) into the section. 2. Paste the snippet into the HTML Code box. Save. 3. Set the section/column width as you like; the widget adapts to its container (it lays out in one column under 640 px, two above, three above 960 px). Editor mode: the widget deliberately renders nothing inside the Elementor editor iframe (it checks elementorFrontend.isEditMode()), so the HTML widget looks empty while editing. Preview or view the page to see it. Elementor popups and lazy-loaded sections are fine: the script watches the page for ten seconds after load and mounts into any data-crush-key element that appears. Divi 1. Add a Code module (not Text) where you want the widget. 2. Paste the snippet into the module's Content field. Divi keeps <script> tags in Code modules. 3. Divi's Visual Builder does run scripts; if you see the widget inside the builder that is expected. If the Code module shows the snippet as text, switch the module's content editor to the code view (the </> tab). Divi's global resets (* { box-sizing }, uppercase headings, button resets) do not reach the widget: it renders in Shadow DOM. The widget uses a system font stack by default; set style="--crush-font: …" on the <div> to match your Divi font. Gutenberg (block editor) 1. Add a Custom HTML block. 2. Paste the snippet. 3. Use the block's Preview tab to see it; the editor's edit view shows the raw HTML. If your user role cannot save <script> tags (the unfiltered_html capability, common on WordPress.com and multisite), ask an administrator to paste it, or add the script tag once via a header/footer plugin (e.g. "WPCode" → Footer) and keep only the <div> in the block. One script tag serves every widget <div> on the page. Caching / optimisation plugins - Do not let WP Rocket, Autoptimize, LiteSpeed Cache or similar combine, defer-rewrite or "delay" the widget script. Add be.channelrush.net to the plugin's exclusion list. Delaying it until user interaction breaks the deep links from confirmation emails. - Do not self-host or minify the script; it is already minified and versioned. See versioning.md if you want to pin a version. Checklist - Page shows "Find a room" with the calendar and a Search button. - Choosing dates and searching lists rooms with prices in the right currency. - The browser console shows no [ChannelRUSH] errors. A message about the key or the domain means the key is not bound to this site's domain in ChannelRUSH. Squarespace Requires a Business plan or higher — Personal plans cannot run custom code (<script>) in Code Blocks or Code Injection. Code Block (recommended) 1. Edit the page, add a Code block where the booking form should appear. 2. Set the block to HTML (not Markdown) and paste: <div data-crush-key="pk_live_xxxxxxxxxxxx" data-crush-lang="en-US" data-crush-currency="USD"></div> <script async src="https://be.channelrush.net/widget/v1/channelrush.js" data-cookieconsent="ignore" data-ot-ignore></script> 3. Save. In the editor the block may render a placeholder; open the live page to check. Code Injection (site-wide script) Settings → Advanced → Code Injection → Footer: <script async src="https://be.channelrush.net/widget/v1/channelrush.js" data-cookieconsent="ignore" data-ot-ignore></script> then place only the <div data-crush-key="…"></div> in a Code Block on the booking page. Use this when you have several booking pages, or when Code Blocks strip scripts on your template. AJAX page loading Many Squarespace templates (Brine family and others) load pages with AJAX, so a script in a Code Block does not re-run when the visitor navigates to the booking page from another page. Two options: - Turn off Enable AJAX Loading (Design → Site Styles → search "AJAX"); or - keep AJAX on and load the script via Code Injection (Footer). The widget watches the page for new data-crush-key elements for ten seconds after each load and mounts into them; with AJAX navigation the footer script is already on the page, so the <div> from the Code Block is picked up as it is inserted. If the widget appears on a hard refresh but not after in-site navigation, AJAX loading is the cause. Squarespace-specific notes - Squarespace's global styles do not reach the widget (Shadow DOM), and the widget uses a system font stack by default. Set style="--crush-font: …" on the <div> to match your site's font (theming.md). - Squarespace serves your site over HTTPS; the widget requires that. - Cookie banner: Squarespace's own banner does not block scripts. If you added Cookiebot or OneTrust, see cookie-consent.md. Wix Wix does not let you add a <script> to the page itself. Its "Embed HTML" element (Add → Embed code → Embed HTML) renders your code inside a sandboxed iframe on a wixsite.com / filesusr.com origin. That has consequences for a booking flow: - The iframe has a fixed height that you set in the Wix editor; content that grows past it scrolls inside the frame. - The page URL and browser history belong to the Wix page, not to the iframe: no deep links into the booking flow, no Back button through the steps. - sessionStorage inside the frame is separate from the page's; a visitor who leaves and comes back starts over. - Your key must be bound to the iframe's origin (*.wixsite.com / *.filesusr.com shown in the browser's network tab), not only to your custom domain. The widget detects the Wix frame and switches to its compact layout automatically (internal scrolling, no URL writes). It works, but the experience is better with the recommended setup below. Recommended: search bar on Wix, booking on your own page 1. Host the full widget on a page you control — a plain HTML page on your own domain, a subdomain (book.yourhotel.com), or any non-Wix host — using the standard snippet (static-html.md). 2. On the Wix site, add an Embed HTML element with the widget in searchbar mode. Submitting the search sends the visitor to your booking page with the dates, guests, promo code, currency and language in the URL: <div data-crush-key="pk_live_xxxxxxxxxxxx" data-crush-mode="searchbar" data-crush-target="https://book.yourhotel.com/" data-crush-currency="EUR" data-crush-lang="de-DE"></div> <script async src="https://be.channelrush.net/widget/v1/channelrush.js"></script> The redirect navigates the top window (the visitor leaves the Wix page for the booking page; the frame is not stuck inside). Without data-crush-target the widget logs a warning and renders the full flow instead. Set the Embed HTML element to about 160 px high, full width for the search bar. Full widget inside the Wix frame If you must run the whole flow inside Wix: 1. Add → Embed code → Embed HTML, paste the standard snippet. 2. Size the element to the full page width and 900 px high; the widget scrolls internally when a step is taller (compact layout). 3. Bind the key to the Wix iframe origin in ChannelRUSH (open the page, check the network tab for the frame's host). 4. Accept the limitations above (no deep links, no browser Back between steps, no restore after leaving the page). Wix Velo (custom code with $w) and the "Custom element" option do not change any of this: both still isolate third-party HTML in a frame. Wix ADI / Wix Studio Same element ("Embed HTML" / "Embed a widget"), same behaviour. Webflow Custom code needs a paid Site plan (Basic or higher) or a paid Workspace when exporting. Embed element 1. Open the page in the Designer, drag an Embed element (Add → Advanced → Embed) where the booking form should appear. 2. Paste the snippet: <div data-crush-key="pk_live_xxxxxxxxxxxx" data-crush-lang="en-US" data-crush-currency="USD"></div> <script async src="https://be.channelrush.net/widget/v1/channelrush.js" data-cookieconsent="ignore" data-ot-ignore></script> 3. Publish. The Designer canvas shows a placeholder for Embed elements; the widget renders only on the published site. Page or site settings (script once, <div> anywhere) Page settings → Custom code → Before </body> tag, or Project settings → Custom code → Footer code: <script async src="https://be.channelrush.net/widget/v1/channelrush.js" data-cookieconsent="ignore" data-ot-ignore></script> Then use an Embed element containing only the <div>. Notes - Webflow's class-based styles do not reach the widget (Shadow DOM). The widget uses a system font stack by default; match your site's font with --crush-font (theming.md). - The Embed element's size is the widget's container: the widget uses container queries, so a narrow column gets the one-column layout regardless of the viewport. - Webflow's page transitions/interactions do not interfere; if you use a third-party "smooth page transition" script that swaps <body> content, the widget mounts again automatically for ten seconds after each load, and you can call ChannelRUSH.init({ key, el }) after the swap for longer-lived apps. Static HTML, custom sites, other CMSs Any page that can contain a <div> and a <script> can host the widget. <!doctype html> <html lang="en"> <head> <meta charset="utf-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> <title>Book your stay</title> </head> <body> <main style="max-width: 1100px; margin: 0 auto; padding: 24px;"> <div data-crush-key="pk_live_xxxxxxxxxxxx" data-crush-lang="en-US" data-crush-currency="USD" data-crush-fallback-url="https://reservation.services/yourhotel" style="--crush-primary:#1e3a5f; --crush-radius:8px;"></div> </main> <script async src="https://be.channelrush.net/widget/v1/channelrush.js" data-cookieconsent="ignore" data-ot-ignore></script> </body> </html> - The script can go anywhere (<head> with async, or the end of <body>); it mounts into every data-crush-key element present at DOMContentLoaded and keeps watching for ten seconds. - One script serves any number of widgets on a page (for example two properties). Only the first widget on a page writes deep-link parameters to the URL; the others run in memory. - Serve the page over HTTPS. Plain-http pages can call the HTTPS API, but sessionStorage restore and Turnstile behave better on HTTPS and some browsers warn about card forms on http pages. - Register the exact origin(s) of the page with the key: https://www.yourhotel.com and https://yourhotel.com are two origins. Sub-paths do not matter. Programmatic use (single-page apps, React, Vue, …) const instance = ChannelRUSH.init({ key: 'pk_live_…', el: document.getElementById('book'), language: 'de-DE', currency: 'EUR' }); // later, when the component unmounts: instance.destroy(); // or ChannelRUSH.destroy(el) init is idempotent per element. Everything the widget adds to the page (Shadow DOM, event listeners, the data-crush-mounted marker) is removed by destroy(). An ES module build is available at https://be.channelrush.net/widget/v1/channelrush.esm.js (import { init, destroy, version } from …); it does not define the global and does not auto-mount. Like the script build, it talks to the channelrush.net host it was imported from — import it from testbe.channelrush.net to target the test server. Also see csp.md if your server sends a Content-Security-Policy header, events.md for analytics, theming.md for colours and sizing. Theming The widget is styled entirely through CSS custom properties read from its host <div>. Set any subset inline, in your stylesheet, or through ChannelRUSH.init({ theme: { primary: '#0d47a1' } }) (keys without the --crush- prefix are prefixed for you). Values the property configured in ChannelRUSH are applied first; whatever you set on the page wins. <div data-crush-key="pk_live_…" style="--crush-primary:#1e3a5f; --crush-primary-contrast:#fff; --crush-radius:8px; --crush-font:'Inter', system-ui, sans-serif;"></div> /* or in a stylesheet */ [data-crush-key] { --crush-primary: #1e3a5f; --crush-accent: #b8860b; } Variables All twenty variables, with their defaults (from the widget's base stylesheet): Variable Default Used for --crush-font system stack ( system-ui, -apple-system, 'Segoe UI', Roboto, 'Helvetica Neue', Arial, sans-serif ) Font family of everything in the widget. The widget cannot inherit your page font through its style isolation, so set this to your site's font stack to match it. --crush-font-size 16px Base font size; every other size is relative to it ( em ). --crush-color-text #1f2328 Body text. --crush-color-muted #6b7280 Secondary text: hints, descriptions, per-night prices, "Includes taxes and fees", weekday names, policy line. --crush-color-bg transparent Background of the whole widget area. --crush-color-surface #ffffff Cards (search form, room cards, cart lines, summary, banners), inputs and secondary buttons. --crush-color-border #d0d7de Borders of cards, inputs, buttons, amenity chips, summary rows. --crush-primary #0d47a1 Primary buttons (Search, Select, Continue, Pay), selected calendar days, selected rate plan border, checkbox/radio accent, link buttons. --crush-primary-contrast #ffffff Text on primary buttons and selected days. --crush-accent #0d47a1 Prices and the reservation number. --crush-danger #b42318 Error text and borders, sold-out lines, the required-field asterisk, cancelled status. --crush-success #067647 "Only n left", applied promo code, a promo's "Save …" line, confirmed status, cancellation-done banner. --crush-radius 6px Corner radius of cards, inputs, buttons, calendar cells, images. --crush-shadow 0 1px 2px rgba(0, 0, 0, 0.08) Card shadow. --crush-gap 12px Spacing unit: grid gaps, card padding, margins (fractions/multiples derived). --crush-input-height 44px Minimum height of text inputs and selects. --crush-button-height 44px Minimum height of buttons (keep ≥ 44px for touch targets). --crush-max-width none Maximum width of the widget; the layout follows its container otherwise. --crush-image-ratio 4 / 3 Aspect ratio of room photos. --crush-focus-ring 0 0 0 3px rgba(13, 71, 161, 0.35) Focus indicator (box-shadow) on every focusable control; match it to --crush-primary . Layout The widget uses container queries, not media queries: it becomes two-column above a 640 px container and three-column (room cards) above 960 px. Put it in a narrow sidebar and it stays single-column even on a wide screen. There are no fixed heights; images use the aspect ratio above. Dark backgrounds There is no automatic dark mode. For a dark page set the surface/text/border trio, e.g. [data-crush-key] { --crush-color-bg: transparent; --crush-color-surface: #1b1f24; --crush-color-text: #e6edf3; --crush-color-muted: #9da7b3; --crush-color-border: #30363d; --crush-primary: #4c8dff; --crush-primary-contrast: #0b0f14; --crush-focus-ring: 0 0 0 3px rgba(76, 141, 255, 0.45); } Keep text/surface contrast at 4.5:1 or better; the defaults meet WCAG AA. What you cannot restyle Everything inside the widget lives in Shadow DOM: your selectors (.btn, h2, input, …) do not reach it, and its rules do not leak out. Only the variables above cross the boundary; typography is re-established inside the widget, so set --crush-font (and --crush-font-size) to match your site. Reduced-motion preferences are respected automatically. Events and analytics The widget dispatches DOM CustomEvents on its host <div> (they bubble and cross the shadow boundary, so document.addEventListener works). Each detail is built from a fixed allow-list — never guest names, emails, card data or addresses. The same events reach ChannelRUSH.init({ onEvent(name, detail) }). A hosted ChannelRUSH booking site reports the same events with the same names and fields, and pushes them to dataLayer for you: see Analytics events on your hosted booking site. Event detail When crush:search { arrival, departure, adults, children, promoCode } a search is submitted (dates are yyyy-MM-dd strings) crush:add_room { roomTypeId, ratePlanId, arrival, departure, adults, children } a room is added to the cart crush:remove_room { roomTypeId, ratePlanId, lineId } a cart line is removed (also when a sold-out line is dismissed) crush:quote { total, currency, rooms } the server priced the cart (fires again on every cart change, extra chosen, currency or language switch) crush:checkout_start { rooms, nights, currency } the guest reaches guest details — from the cart, or from the extras step when the property sells extras. It does not fire again when the guest goes back and forward crush:booking_confirmed { reservationId, rooms, nights, currency, total } the booking is confirmed crush:booking_canceled { reservationId } a booking is cancelled through "Find your booking" crush:booking_modified { reservationId } a booking's dates or guests are changed through "Find your booking" Extras have no event of their own: choosing one re-prices the cart, so it arrives as a crush:quote with the new total. crush:booking_modified carries the reservation number only — no amounts: a change can charge or refund a difference, and the booking's new total is not an e-commerce event of its own. total is the booking total in currency (number). reservationId is the property's reservation number as printed on the confirmation. Plain JavaScript <script> document.addEventListener('crush:booking_confirmed', function (e) { console.log('booked', e.detail.reservationId, e.detail.total, e.detail.currency); }); </script> Google Analytics 4 (gtag.js) <script> document.addEventListener('crush:search', function (e) { gtag('event', 'search', { search_term: e.detail.arrival + '..' + e.detail.departure, adults: e.detail.adults, children: e.detail.children }); }); document.addEventListener('crush:add_room', function (e) { gtag('event', 'add_to_cart', { items: [{ item_id: e.detail.roomTypeId, item_variant: e.detail.ratePlanId, quantity: 1 }] }); }); document.addEventListener('crush:checkout_start', function (e) { gtag('event', 'begin_checkout', { currency: e.detail.currency }); }); document.addEventListener('crush:booking_confirmed', function (e) { gtag('event', 'purchase', { transaction_id: e.detail.reservationId, value: e.detail.total, currency: e.detail.currency, items: [{ item_name: 'Hotel stay', quantity: e.detail.rooms }] }); }); document.addEventListener('crush:booking_canceled', function (e) { gtag('event', 'refund', { transaction_id: e.detail.reservationId }); }); </script> Google Tag Manager Add a Custom HTML tag, trigger All Pages (or the booking page only), that forwards the widget events into the data layer: <script> (function () { var map = { 'crush:search': 'crush_search', 'crush:add_room': 'add_to_cart', 'crush:remove_room': 'remove_from_cart', 'crush:quote': 'crush_quote', 'crush:checkout_start': 'begin_checkout', 'crush:booking_confirmed': 'purchase', 'crush:booking_canceled': 'refund', 'crush:booking_modified': 'crush_booking_modified' }; Object.keys(map).forEach(function (name) { document.addEventListener(name, function (e) { var d = e.detail || {}; var payload = { event: map[name] }; if (name === 'crush:booking_confirmed') { payload.ecommerce = { transaction_id: d.reservationId, value: d.total, currency: d.currency, items: [{ item_name: 'Hotel stay', quantity: d.rooms }] }; } else if (name === 'crush:booking_canceled') { payload.ecommerce = { transaction_id: d.reservationId }; } else { payload.crush = d; } window.dataLayer = window.dataLayer || []; window.dataLayer.push({ ecommerce: null }); window.dataLayer.push(payload); }); }); })(); </script> Then create a GA4 Event tag for purchase with a Custom Event trigger on event name purchase, reading ecommerce.transaction_id, ecommerce.value, ecommerce.currency and ecommerce.items from Data Layer Variables (or use the "Send Ecommerce data" option with Data Layer as the source). URL-based goals Prefer the crush:booking_confirmed event above: it fires once per booking and carries the reservation number and total. For tools that can only match a page address (a "destination" goal, a URL-based conversion), the widget also marks the address when a booking is confirmed: https://www.yourhotel.com/book?crush_confirmed=1 The widget changes the address in place (history.replaceState) — the page does not reload — so the tool must watch address changes on the page: - Google Tag Manager: a History Change trigger with the condition Page URL contains crush_confirmed=1. - Google Analytics 4: enhanced measurement → Page views → Page changes based on browser history events (on by default), then mark the page_view whose page_location contains crush_confirmed=1 as a key event. - A tool that only counts full page loads will not see it; use the event instead. The marker carries nothing else: no reservation number, no amount, no guest details. It is already in the address when crush:booking_confirmed fires, so a GTM trigger may also combine the two (event purchase and Page URL contains crush_confirmed=1). Situation Address Counts again? Booking confirmed …?crush_confirmed=1 (replaces the payment step's entry) — Guest presses Book another stay , or opens Manage this booking that address is replaced — one address change, the marker gone from history no Guest presses Back from the confirmation the guest-details entry, no marker no Guest reloads the confirmation page the page loads once with the marker, then the widget shows the search form and removes it yes, for a URL goal — like any thank-you page reload; crush:booking_confirmed does not fire again Back, then Forward to the confirmation the marker appears for a moment, then the search form replaces it possibly, for a history-change trigger It is not written inside a Wix embed (compact layout), in search-bar mode, or by a second widget on the same page — those never change the page address. Notes - Events fire once per action; crush:quote is the only one that repeats (every re-price). - If your consent tool gates GA, the listeners above simply forward into a dataLayer/gtag that is not sending; the widget itself is unaffected. - The confirmation email deep link (?crush_lookup=1&crush_res=…) opens the lookup step directly; no event fires until the guest acts. Cookie consent tools (Cookiebot, OneTrust, …) The widget sets no cookies and uses sessionStorage only for the visitor's current search and cart (cleared when the tab closes). It needs no consent category. Consent tools that auto-block unknown <script> tags will, however, block it until the visitor accepts "marketing" or "statistics" — which stops guests from booking. Mark the script tag as exempt: <script async src="https://be.channelrush.net/widget/v1/channelrush.js" data-cookieconsent="ignore" data-ot-ignore></script> Tool Attribute Notes Cookiebot data-cookieconsent="ignore" With "Auto blocking mode" on, every script without this attribute is held until consent. If you use manual blocking instead, leave type="text/javascript" (do not set type="text/plain" ). OneTrust data-ot-ignore Required when "Auto-Block" is enabled in the OneTrust script settings. Alternatively classify be.channelrush.net as "Strictly necessary" in the OneTrust categorisation. Usercentrics data-usercentrics="…" not needed Usercentrics only blocks scripts you explicitly configure; do not add the widget to its Smart Data Protector list. Complianz / CookieYes / WordPress plugins — These block by rewriting type on scripts you list; do not list the widget. Consent Mode (Google) — Not applicable; the widget does not use Google tags. Your GTM/gtag forwarding of crush:* events ( events.md ) follows your own consent state. Also exempt https://challenges.cloudflare.com (Cloudflare Turnstile, the bot check on the "Find your booking" step) if your tool blocks by domain: Turnstile does not set marketing cookies either. How to tell the widget was blocked The page shows an empty gap where the widget should be, and the browser console shows the widget script with type="text/plain" or the consent tool's log entry. If the script ran but the API was blocked, the widget renders a panel that names the likely cause (see csp.md). Content Security Policy If your site sends a Content-Security-Policy header (or meta tag), allow the following. Nothing else is contacted. script-src 'self' https://be.channelrush.net https://challenges.cloudflare.com; connect-src 'self' https://be.channelrush.net; img-src 'self' https://be.channelrush.net https://cr-production.appspot.com; frame-src https://challenges.cloudflare.com; Directive Why script-src https://be.channelrush.net the widget script itself ( /widget/v1/channelrush.js ) script-src https://challenges.cloudflare.com Cloudflare Turnstile (bot check). Loaded only when needed: the "Find your booking" / cancel steps, and after repeated payment failures. connect-src https://be.channelrush.net all API calls ( /v1/config , /v1/search , /v1/quote , /v1/book , /v1/bookings/… ) and the on-demand language files ( /widget/v1/i18n/de.json ) img-src https://cr-production.appspot.com https://be.channelrush.net room and property photos (CDN) frame-src https://challenges.cloudflare.com the Turnstile challenge renders in an iframe style-src: nothing is required. The widget applies its stylesheet through adoptedStyleSheets (a CSSOM API, not governed by style-src) in every browser it supports. On engines without adoptedStyleSheets it falls back to a <style> element inside its shadow root and copies the nonce from its own <script nonce="…"> tag, so a nonce-based style-src still passes. It never sets style="" attributes; theme values are CSS custom properties that you set on the <div> (your inline style, your policy — put them in a stylesheet rule instead if your policy forbids inline styles). Testing against the test server: while your embed loads the script from https://testbe.channelrush.net, use that host in script-src, connect-src, and img-src in place of (or alongside) https://be.channelrush.net — the widget talks to the host it was loaded from. form-action: not needed (the widget submits with fetch, never a form navigation). font-src: not needed (it inherits your font or uses the system stack). No 'unsafe-eval', no 'unsafe-inline' is required by the widget. The programmatic ChannelRUSH.init(...) inline snippet is your inline script and needs your nonce or hash like any other; the declarative data-crush-key form needs none. Nonce-based policies <script nonce="r4nd0m" async src="https://be.channelrush.net/widget/v1/channelrush.js"></script> The widget reuses that nonce for the two things it may add later: the Turnstile <script> tag and the fallback <style>. Diagnosing a blocked widget - Blank space, nothing rendered, console shows "Refused to load the script": script-src is missing https://be.channelrush.net, or a consent tool blocked the tag (cookie-consent.md). The widget cannot help here — its code never ran. - Panel "The booking widget is blocked by this site's Content Security Policy": the script ran, but the browser reported a securitypolicyviolation for be.channelrush.net when it tried to fetch its configuration. Add connect-src. - Panel "We can't reach the booking service right now … Site owner: …" with a Retry button: the configuration request failed without a CSP report. Usually connect-src on a browser that does not fire violation events for fetch, an ad/privacy blocker, or a real outage. The panel links to your data-crush-fallback-url when set. - "Verification is unavailable" on Find your booking: Turnstile could not load — check script-src/frame-src for challenges.cloudflare.com. Report-only first Deploy with Content-Security-Policy-Report-Only and watch the reports for be.channelrush.net / challenges.cloudflare.com before enforcing. Versions, pinning, browser support Two URLs URL Behaviour Cache https://be.channelrush.net/widget/v1/channelrush.js Rolling : always the latest 1.x release. Recommended. 1 hour, stale-while-revalidate 1 day https://be.channelrush.net/widget/1.2.0/channelrush.js Pinned : this exact release; it does not update automatically. 1 year, immutable The content components (channelrush-content.js, see the content API guide) ship in the same folders from 1.1.0, under the same rules: …/widget/v1/channelrush-content.js rolls, …/widget/1.2.0/channelrush-content.js is pinned. The rolling v1/ URL receives bug fixes and new features that keep the embed contract (attributes, ChannelRUSH.init options, event names and detail shapes, theme variables, minimum browser) unchanged. Anything that would break that contract ships as 2.0.0 under /widget/v2/, alongside v1/, and v1/ keeps receiving fixes for 12 months after v2 is released. Check that a pinned script and its version.json are available before using that version. Each folder also contains channelrush.esm.js (ES module build; channelrush-content.esm.js likewise), source maps, version.json ({ "version": "1.2.0", "integrity": "sha384-…", "contentIntegrity": "sha384-…" } — useful when reporting a problem) and i18n/*.json (language files loaded on demand from the same folder). Subresource Integrity SRI hashes are published for pinned URLs only (the table below lists the integrity value per version; it is also in each folder's version.json). The rolling v1/ file changes with every release, so an integrity attribute on it would break your embed at the next release — do not add one there. <script src="https://be.channelrush.net/widget/1.2.0/channelrush.js" integrity="sha384-ZirSvgOu1ahVEzKF7dfMX0GpJPGUz6RUeuXDplr+z8j1baJWRJ/jIeRLc8lJHHba" crossorigin="anonymous" async></script> Version Released integrity of channelrush.js (pinned URL only) integrity of channelrush-content.js 1.2.0 Available; verified 2026-10-29 sha384-ZirSvgOu1ahVEzKF7dfMX0GpJPGUz6RUeuXDplr+z8j1baJWRJ/jIeRLc8lJHHba sha384-XTkxLMVjMec53EW2lfpztFp5T8/O/lY9pbfUvoksd32URDdysnGwRi1rQmz2/08C 1.0.1 2026-10-11 sha384-ZZxOZPY/737e0PbE38yF802aG1qQBFCqDDm5jFGtsW6GjqrpaqcKWmnWe53GWsxd — 1.0.0 2026-10-10 sha384-x0SZ31kqGHnHzbRkTC8SG1jAjnWf9IZTiGPjqUoAV+d5EL7E5BrIJog2hAZkYddc — 1.0.0 is the first release. 1.0.1: an extra priced per person is chosen by the number of guests who take it (up to the room's guests), not a quantity charged for every guest. 1.1.0 adds the content components (channelrush-content.js); the booking widget works as in 1.0.1. 1.2.0: a "Book this room" link (crush_rt) books that room only — its rates, its guest limit, its own open dates, and "See all rooms" for the others — where 1.1.0 listed it first among them; and data-crush-room-type books one room on the room's own page (see booking on a room page). If you pin, put a reminder in your calendar: a pinned widget does not get security fixes automatically. Wire contract Widget 1.x always talks to API /v1/. API changes that the widget needs are additive within /v1/; a widget major bump may move to a new API version, never the reverse. Browser support (v1) Requires ES2020, Shadow DOM, adoptedStyleSheets (or the built-in <style> fallback) and CSS container queries — in practice: - Safari 16 and later (macOS and iOS) - Chrome / Edge 105 and later - Firefox 110 and later - Samsung Internet 20 and later Older browsers do not get a broken layout: the widget shows "Your browser is too old to run the booking widget" with a link to your data-crush-fallback-url (the hosted booking page) or, without one, a "please book by phone" line. Reporting a problem Include the page URL, the value from …/widget/v1/version.json (or ChannelRUSH.version in the console), the browser, and any [ChannelRUSH] console lines. Every API error carries a request id in the network response (requestId); quoting it lets support find the server-side log entry. Analytics events on your hosted booking site Your hosted ChannelRUSH booking site reports each step of a booking, so your tag manager or analytics can measure searches, carts, checkouts and bookings. They are the same events, with the same names and fields, as the embeddable booking widget — one setup covers both. Every event is sent two ways, from the page itself (document): 1. a DOM CustomEvent named crush:… that document.addEventListener (or window.addEventListener) can hear; 2. a push to window.dataLayer, already in the GA4 e-commerce shape — no forwarding tag is needed. This works on every template, including the ones that draw the booking engine in an isolated part of the page (a shadow root): scripts in Page Header cannot look inside the engine, but they do hear these events. The payloads are built from a fixed allow-list. They never contain a guest's name, e-mail, phone, address or any card data. Events DOM event dataLayer event When Fields crush:search crush_search A results page is shown for dates the guest asked for arrival , departure ( yyyy-MM-dd ), adults , children crush:add_room add_to_cart A room and rate plan were added to the cart roomTypeId , ratePlanId , arrival , departure , adults , children crush:remove_room remove_from_cart A room was removed from the cart roomTypeId , ratePlanId crush:quote crush_quote The cart or the checkout page shows the priced cart (repeats on every view) total , currency , rooms crush:checkout_start begin_checkout The guest opens the checkout page rooms , nights , currency crush:booking_confirmed purchase A booking was made reservationId , rooms , nights , currency , total crush:booking_canceled refund The guest canceled a booking reservationId crush:booking_modified crush_booking_modified The guest changed a booking reservationId total is the booking total including taxes and fees, as a number, in currency. reservationId is the reservation number printed on the confirmation. A changed booking carries no amounts: a change can charge or refund a difference, so it is not a sale of its own. What lands in dataLayer // purchase (each e-commerce push is preceded by { ecommerce: null }) { event: 'purchase', ecommerce: { transaction_id: 'R-10482', value: 480.5, currency: 'USD', items: [{ item_name: 'Hotel stay', quantity: 1 }] } } // refund { event: 'refund', ecommerce: { transaction_id: 'R-10482' } } // everything else { event: 'add_to_cart', crush: { roomTypeId: '7', ratePlanId: '10', arrival: '2026-10-01', … } } In Google Tag Manager, create a GA4 Event tag per event you want, with a Custom Event trigger on the event name (purchase, begin_checkout, …). For purchase, read ecommerce.* from Data Layer Variables or use "Send Ecommerce data" with the Data Layer as the source. Without a tag manager: <script> document.addEventListener('crush:booking_confirmed', function (e) { gtag('event', 'purchase', { transaction_id: e.detail.reservationId, value: e.detail.total, currency: e.detail.currency }); }); </script> Put either in Page Header (CRS admin → Content). Good to know - Booking, change and cancel events fire once. Reloading the confirmation page does not repeat them. If the guest's first answer was lost and the booking is confirmed on a retry, purchase may be reported for the same transaction_id again; GA4 de-duplicates on it. - crush:search fires when a results page is shown (a reload repeats it), crush:quote on every view of the cart or checkout. Use them for funnels, not for counting unique actions. - Differences from the widget: there is no promoCode on crush:search (the code is entered at checkout) and no lineId on crush:remove_room. - Looking up a booking fires nothing until the guest changes or cancels it. - If your consent tool blocks analytics, the events still fire; your tags decide what is sent.

Issue a booking-widget key

Create a public key for a property's booking widget, bind it to the websites that may use it, and keep the embed snippet shown after creation. Before you start - Select the correct property. Issuing keys requires both Booking Engine / CRS - Settings and Channel Settings - Login Info permissions. Ask your organization administrator if you cannot use the controls. - Save the property's CRS settings and create a booking profile first. The profile needs a language for the widget to operate. Check its languages, currencies and booking-flow options before assigning it. - Obtain the website origins from your site builder. An origin is the scheme and hostname, plus a port when used—not the full booking-page address. - Decide whether this is a live website or a controlled test. A test key does not create a reservation sandbox. A test booking can reduce inventory and trigger configured PMS and email delivery. Use a test property and coordinate the test environment before making bookings. Create Key submits the form and issues the key. Typing in the fields only changes the form and its preview. Cancel or Back to Keys leaves without submitting this key request; neither undoes an earlier creation. Open the issuance form 1. Open Admin → Settings - CRS for your property. 2. Select BE & CRS. 3. Find Widgets under Booking Engine Settings. 4. Click Add New in the Widgets section. The page title is Issue a New Key. Check the property name above the fields. If you are already on Booking Widgets, click Issue a New Key instead. Enter the key settings Key issuance fields: Name, Booking Profile, Allowed Origins and the unchecked Test key option, with its reservation-side-effect warning. The demo form has one booking profile, Main. The grey example name and website address are placeholders, not entered values. 1. Enter a Name that identifies where the key will be used, such as Main website or Staging website. 2. Choose the Booking Profile for this website. When only one profile exists, its name appears without a visible dropdown. 3. Enter each Allowed Origins value on its own line. Use the examples below to distinguish the root domain, subdomains and local development addresses. 4. Leave Test key (pk_test_) unchecked for a live key, or check it only for your agreed test setup. 5. Review This key will serve and every origin before submitting. 6. Click Create Key once. Do not leave the result page until you have copied the key and snippet. If the request times out or the result is unclear, follow Creation did not return a clear result below before clicking Create Key again. Choose the allowed origins For a widget embedded at https://www.example.com/book, enter: https://www.example.com If both the root domain and www host serve the widget, enter both: https://example.com https://www.example.com Use a wildcard only when the widget must work across subdomains you control: https://*.example.com That wildcard covers www.example.com, booking.example.com and deeper subdomains. It does not cover https://example.com; add the root domain separately when needed. Prefer exact hosts when you do not need broad subdomain access. For local development, include the actual port: http://localhost:3000 - Use HTTPS for public websites. HTTP is supported for local loopback addresses such as localhost, not ordinary public hosts. - Do not include /book, other paths, query strings, fragments or a username/password in the origin. - Scheme and port must match the website's actual origin. Do not add :443 when the browser's origin omits it. - Leading/trailing whitespace, trailing slashes and duplicate lines do not create additional allowed websites. - At least one origin is required. Review every line yourself; an issued key is not proof that every configured origin works. Choose live or test mode Unchecked — live key (pk_live_): use for the live booking website. Ordinary live-property bookings follow the property's payment and reservation settings. Checked — test key (pk_test_): accepts only the ChannelRUSH test card, with no live-card charge. It still creates a reservation and can affect inventory, PMS delivery and emails. A test key against the production widget server is restricted to localhost/loopback origins, which must also be in Allowed Origins. Allowlisting a public staging hostname does not make a test key work there against production. For a public staging site, coordinate the ChannelRUSH test environment and follow the embed guide's test-server instructions. The generated snippet points to the production widget script even when you select a test key. Do not assume checking Test key changes the script host. Use the script and key issued for your agreed environment; a key is not automatically available on a different server. Review the profile and preview The This key will serve panel shows profile languages, currencies and cancellation settings above a snippet with a masked placeholder key. This is a preview before issuance, not a usable key or a completed booking check. This key will serve summarizes the selected profile's Languages, Currencies and Cancel in widget setting. Edit profiles opens the profile area in CRS Settings. Changes to a shared profile affect its other websites, widgets and CRS connections too. The profile provides the widget's languages, content, currencies, checkout fields and cancellation options. Rooms, rates, policies and the card gateway come from CRS settings. The snippet you will get shows the embed structure and live/test prefix. Its dots are placeholders. The displayed language and currency come from property defaults; choosing another profile does not automatically refresh those snippet values to that profile's preferences. Have your site builder check the final snippet's language and currency against the selected profile. The embed guide explains these attributes and language/currency selectors. Why are keys public? explains why the key is visible in website source. Treat it as a public identifier, not a password. Allowed origins deter copying the widget onto another website; they are not strong authentication for software outside a browser. Check the result and preserve the snippet After successful creation, ChannelRUSH returns to Booking Widgets and shows Your new widget key, marked Shown once. 1. Use Copy beside the full Key, and paste it into your site's configuration or handoff document. 2. Use Copy beside Embed snippet - paste it where the booking widget should appear. 3. Check that both pasted values are complete before refreshing, navigating away, changing property or editing another key. 4. Check the new entry under Keys against the intended name, allowed origins and live/test type. 5. Give the snippet to your site builder and follow the booking widget embed guide for installation on your platform. If Copy does not work, select and copy the displayed text manually while the result is still open. Do not refresh to repair the clipboard. The full key cannot be displayed again through the key list. Later visits show a masked value. A new key starts enabled, but Enabled does not mean the property is ready to accept bookings. Issuing a key does not enable CRS settings, supply missing profile languages, load inventory, validate the payment setup or install the widget on your site. After installation, open the actual allowed website and check that the widget loads for the intended property with the expected languages and currencies. A Last Used timestamp alone is not proof of successful loading or a completed booking. Arrange any checkout test separately, with the correct property and environment. Field reference Field or control What it does Requirements and defaults Name Identifies the website or purpose in the key list. Required; maximum 100 characters. Initially blank. Leading/trailing spaces are removed. A descriptive name helps distinguish separately issued keys. Booking Profile Assigns one of this property's profiles to the key. The first available profile is selected initially. One profile appears as text; several profiles offer a dropdown. Create the intended profile before issuance if it is absent. Allowed Origins Lists the website origins from which the widget may be used. Initially blank; at least one required. One scheme://host[:port] per line. See the origin examples and wildcard limits above. Test key (pk_test_) Creates a test rather than a live key. Unchecked initially. Test-card and server-origin restrictions apply; reservation side effects remain possible. This key will serve Summarizes the selected profile. Read-only languages, currencies and cancellation information. It is not a readiness or delivery check. The snippet you will get Previews the embed and key prefix. Not a real key. Review the final script host, language and currency before installation. Create Key Submits the settings and issues a separate key. Click once. Repeating a successful request can create another key. Cancel / Back to Keys Returns to Booking Widgets without submitting the current form. Does not revoke an already-issued key. Rate limit tier and theme overrides are configured after issuance using Edit on the key, not on this form. New keys use the Standard tier and no key-level theme overrides. Common problems The form is disabled or saving is refused You need both permissions listed under Before you start. A demonstration login may show the form while refusing changes. Ask your organization administrator to confirm access for the correct property; do not use another property's key as a workaround. “Choose a booking profile for the key” or no profile is available Create or select a profile under CRS Settings → BE & CRS → Booking Profiles, then reopen the issuance form. Check the profile's languages before continuing. If an existing profile is still missing, contact support with the property and profile name. “Save the CRS Settings before issuing a widget key” The property needs saved CRS settings. Have an authorized administrator complete that setup before issuing the key. Creating a key does not substitute for booking-engine setup. The name or origins are rejected For “Name is required (100 characters max).”, enter a nonblank name within the limit. For “At least one allowed origin is required.”, add a website origin. For “is not a valid origin (scheme://host[:port], no path)”, remove paths and other URL extras and check the scheme/host. Review the entire form and all origin lines before submitting again. If correctly formatted values are still refused, contact support with the exact error and intended origins. Creation did not return a clear result The key may already have been saved. Open Booking Widgets for the same property and inspect Keys before repeating the request. Compare the name, type, origins and creation time. Do not assume an error or lost connection means no key was issued. If you cannot identify the result, contact support with the property, key name, action time/time zone and error text. Do not repeatedly create keys to test whether the page is responding. The full key is gone Check the snippet already saved by you or your site builder. The masked key in the list cannot replace the full key. If no copy exists, an authorized administrator must arrange revocation and replacement, then update every affected website or integration. Revocation is irreversible and can interrupt existing users of the key. Confirm where it is used before proceeding. The widget is not allowed on the website Check the actual website origin against Allowed Origins, including HTTPS, root versus www, and any port. Check live/test mode and the script's server. For Wix, embedded frames or consent/CSP problems, use the relevant platform section of the embed guide. Do not add broad wildcard access merely to suppress an unexplained error. The key exists but the property is unavailable Check that the key is enabled and not revoked, CRS settings are enabled, and its booking profile still exists with a language. If those checks do not resolve the problem, contact support with the property, key name or masked identifier, website URL and error text. Do not send passwords, payment details or guest information. Related - Set up a booking profile - Booking widget: embed guide

Manage booking-widget keys

Review the public keys for your property's booking widget, change their website origins and settings, or retire a key without losing track of the sites that use it. Before you start - Select the correct property. Saving and revoking keys requires both Booking Engine / CRS - Settings and Channel Settings - Login Info permissions. Ask your organization administrator if controls are unavailable. - Identify every website and content integration using the key. A change applies to every consumer of that key, not only the page you are viewing. Coordinate changes with your website builder. - Check the assigned booking profile. It must belong to this property and have at least one language. Its languages, currencies and booking-flow options affect what guests can use. - Treat Test as a key type, not proof of a reservation sandbox. Do not make a booking merely to check a key: reservations can affect inventory and configured delivery. Coordinate any booking test separately. Against production, Test keys work only from localhost/loopback origins. Adding a public website to Allowed Origins does not make a Test key work there. Use a Live key for a public production website or a site builder's server. Widget keys are public identifiers embedded in websites, not account passwords. Allowed origins restrict browser use; they are not a substitute for the booking service's security controls. Never put an account password or private API credential in the widget snippet. Open the key list 1. Select the property in the application header. 2. Open Admin → CRS Settings. 3. Find Widgets and click its Edit link. 4. On Booking Widgets, find the key under Keys. Use its name, masked key and Type together to distinguish live and test entries. If the list says No widget keys have been issued for this property yet, check the selected property. Use Issue a New Key and follow Issue a booking-widget key when a new key is needed. The full key and its usable embed snippet are shown only after issuance. The shortened value in this list cannot be expanded into the original key. Editing an existing key does not issue a new one. Edit a key Save submits the expanded key's form. Opening Edit or typing into its fields does not save changes. Each key has its own form. 1. Click Edit on the key you intend to change. The form opens below the list; scroll down if needed. 2. Update Name so you can identify the site or integration. 3. Review Booking Profile before changing it. Reassigning the key changes the profile used by every site and content integration using that key; it does not edit the profile itself. 4. Update Allowed Origins, keeping every website origin that must continue working. Removing an origin can stop browser requests from that site. 5. Review Rate Limit Tier and any Theme Overrides. Use the field reference below. 6. Click Save in that key's form. 7. Check the save confirmation, then reopen Booking Widgets and the same key. Confirm the saved name, origins, profile, tier and theme values. A save confirmation means the key settings were saved in ChannelRUSH. It does not prove that the website has loaded the widget successfully or that a booking was accepted. Existing cached configuration may delay the effect of edits; reload the website when checking the result. To discard unsaved changes, leave or reload the page without pressing Save. Closing the expanded form is not a server-side undo. If you have already saved a wrong value, restore the intended value and save again after checking its impact on the other sites using the key. Set allowed website origins An origin is scheme://host[:port], not a full page URL. Enter one per line, for example: https://www.example-hotel.com https://example-hotel.com - https://www.example-hotel.com/book is not an origin: remove /book. - www.example-hotel.com is incomplete: include https://. - The www and non-www hosts are separate origins. Include both if visitors use both. - https://*.example-hotel.com permits subdomains, including deeper subdomains, but not the bare https://example-hotel.com host. Add the bare host separately when required. - Include a port when it is part of the site's browser origin, such as http://localhost:3000 for local development. Use HTTPS for public websites; HTTP is accepted only for loopback development hosts. - Do not include paths, query strings, fragments or usernames/passwords. Blank lines and duplicate origins are removed when saving. A completely blank list is not valid. Allowed Origins field on the Booking Widgets editor, showing one website origin per line and the required format Example from the demo property. Enter your own website origins; do not copy these domains. Ask your site builder for the origin the browser actually sends, especially for embedded frames or preview sites. Do not remove working origins to troubleshoot an unrelated booking problem. Change or remove theme overrides Enter one override per line using the widget's variable name without --crush-: primary=#1a4d8f primary-contrast=#ffffff accent=#e0a100 font=Inter radius=8px The prefix is also accepted. Names are case-insensitive and saved in lowercase. If a name appears more than once, the last value wins. To remove an override, delete its line and click Save. To remove all overrides saved on this key, clear Theme Overrides and save. Reload the website to check the appearance. Your website can supply its own styling too, so removing a key's overrides does not guarantee the website will use every default colour or font. Use the supported variables in the booking widget guide. An accepted name/value line does not prove that the widget recognizes the name or that the browser accepts the CSS value. Replace a lost key or move to a new one The existing full key cannot be recovered from the masked list. For a planned replacement, coordinate the cutover rather than revoking the old key first. 1. Identify every website and content integration using the old key. 2. Click Issue a New Key and follow the issuance guide. Choose the intended live/test type, profile and origins. 3. Copy the new key and snippet when shown. Give the website builder the replacement needed by each consumer. 4. Before switching consumers, open the new key's Edit form, review its Rate Limit Tier, recreate any required Theme Overrides, and Save. These settings are not copied from the old key: a new key starts with Standard tier and no theme overrides. 5. Have the builder replace the old key wherever it is used, including content API integrations. 6. Confirm that the affected sites load with the replacement and that their expected content and booking search work. A loaded widget alone does not verify the payment or reservation-delivery flow. 7. Revoke the old key only after the planned cutover checks pass. If the objective is to stop use immediately rather than preserve continuity, revocation deliberately interrupts those consumers. Coordinate that decision with the people responsible for the affected sites. Revoke a key Revocation cannot be undone on this page. Every site and content integration still using the key will lose access. Revocation does not cancel existing reservations or issue refunds. 1. Locate the correct property, name, masked key and Type. 2. Click that key's Edit link. 3. Click Revoke in its form. 4. Read the confirmation. Cancel it if the key or scope is wrong; confirm only when the affected consumers should stop using it. 5. After the page returns, check that the row says Revoked and shows its timestamp. Its Edit link is no longer available. Revoke does not save other pending edits in the form. A revoked key remains in the list as history. It cannot be re-enabled here; issue a new key if service must be restored. Do not assume revocation takes effect at every consumer immediately: cached key information can delay enforcement. Check the affected website or content integration separately. If the response to Revoke is unclear, reload the list and inspect the row before taking another action. Escalate an ambiguous result rather than replacing or revoking additional keys. Check the result on the website After an ordinary edit or planned replacement: 1. Reopen the key in ChannelRUSH and confirm the intended saved settings. 2. Open or reload the actual website URL that uses it—not only the site builder's editor. 3. Check that the widget loads and uses the intended language, currency and appearance. If it reads site content, check that content too. 4. If booking search is part of your approved check, confirm the expected rooms and dates can be searched. Stop before submitting a booking unless that test is separately coordinated. Enabled describes the key's stored status. It does not establish that the property's booking setup is complete, that an origin is correct, or that its profile can supply the required content. Last Used is not evidence of a successful booking or even a successful authorized request. Field reference Key list Column What it tells you Key Shortened public identifier. It distinguishes entries but is not the complete key to paste into a website. Name The saved identifying name. Allowed Origins Website origins configured for browser use of this key. Profile The assigned booking profile's name. A dash means the current profile name could not be resolved; investigate the assignment rather than assuming a default. Tier The saved booking-attempt rate-limit tier. Type Test or Live . This is fixed when the key is issued and cannot be converted in this editor. Status Revoked , Enabled or Disabled . Revoked takes precedence. Revoked keys include a timestamp and have no Edit link. There is no enable/disable switch on this page. Last Used An approximate recorded key-lookup time, not a complete request log. Rejected requests can update it. A dash means no timestamp is stored, not proof that the key has never been attempted. Created When the key was issued. Edit Opens the form for a non-revoked key below the list. Created, Last Used and the revocation timestamp use your account's time zone. Edit form An existing key's form starts with its saved values; opening it does not reset settings to defaults. Field Values, requirements and effect Name Required, up to 100 characters. Leading and trailing spaces are removed. Use an identifiable site/integration name. Booking Profile Choose an existing profile for this property. It must have a language configured for the widget to operate. A missing assignment should be corrected explicitly; do not rely on the dropdown merely displaying a choice. Rate Limit Tier Trial , Standard or High . Controls the key's booking-attempt allowance, not the number of rooms or completed reservations. Standard is the normal tier for newly issued keys. Ask support before increasing it to address unexplained traffic. Other abuse limits still apply. Allowed Origins At least one valid origin, one per line. Keep all required sites. See the examples and wildcard rules above. Theme Overrides Optional name=value lines. Names may contain letters a–z , digits and hyphens; the optional --crush- prefix is removed. Each supplied value must be nonempty and at most 200 characters, with no ; , } or url( . Blank entire field removes this key's saved overrides. Save Saves this key's editable settings. It does not rotate the key, change its Test/Live type or replace snippets installed on websites. Revoke Permanently disables this key after confirmation. It is a separate action from Save and does not apply unsaved form edits. How to use a key: the two tabs - Booking widget explains the booking flow and shows a placeholder snippet. Use the full snippet preserved at issuance; the placeholder is not a working key. The booking widget guide covers installation, platform-specific instructions, themes, links and analytics. - Site content explains how the same key can serve property content to a website or site builder. Its content API guide gives request details. The expandable Room type and rate plan ids, for room pages and booking links section provides IDs for links. A listed ID does not guarantee availability for particular dates. - These keys are public. Why are keys public? explains why a website-visible identifier and origin checks do not provide password-style secrecy. Use the Content API guide with your developer before changing an integration. Revoking a shared key affects these content requests as well as its booking widget. Common problems Symptom Likely cause and safe next action Save/Revoke is unavailable or permission is refused Check that you have both required permissions for the selected property. Ask your organization administrator; do not switch to another property to work around the restriction. Name is required (100 characters max). Enter a nonblank name within the limit and review the other fields before saving again. At least one allowed origin is required. Restore the required website origins. A blank list is not a way to disable the key. An origin is rejected as invalid Use scheme://host[:port] without a path. Check HTTPS, spelling and port with the website builder. A theme line must be in the form name=value , or its name/value is not allowed Correct the line using the field reference. A theme-format error can return you to the page without retaining your edits: reopen the correct key and recheck all fields. Validation failed but the row appears changed Some failed submissions can redisplay the attempted values. Leave/reopen the page to check what is stored before assuming the edit succeeded or retrying. The widget says it is not allowed on this site Compare the actual website origin with the saved list, including www , scheme, port and any iframe origin. Check the key type and status; involve the builder if these match. Do not broaden origins indiscriminately. Enabled , but the widget still cannot load Check its profile assignment and profile languages, the installed key and origin, then the property's booking setup. Use the embedding guide for script/CSP problems. Escalate with the error rather than issuing repeated replacement keys. Theme changes do not appear Confirm they were saved, use a supported variable name and reload the website. Have the builder check website-supplied styling and caching before repeating the change. The key was not found or has been revoked. Reload the list and confirm property/key/status. Another operator may have changed it; revoked entries cannot be edited back into service. Key is Disabled This screen has no enable switch. Ask your administrator or support to investigate before replacing it. Full key or snippet was lost The list cannot reveal it. Follow the planned replacement workflow and coordinate every consumer's cutover. For unresolved problems, give support the property, key Name and masked identifier, affected website URL, action time and time zone, and exact error. Do not send account passwords, payment details or guest data. Related - Issue a booking-widget key - Set up a booking profile - Booking widget: embed guide

Check your booking engine before going live

Use Booking Engine Summary to review a property's booking setup, investigate readiness findings and check how its fees, taxes and policies affect an example stay. This is a configuration review, not a launch certificate. A green headline, Live, or Nothing to fix does not prove that a guest can complete a booking for particular dates, that a payment succeeds, or that a confirmation email arrives. Read the individual findings and check your actual guest-facing booking path before launch. Before you start - Sign in and select the correct property. Confirm its name at the top of the summary. This page reviews one property, not your whole organization. - You need access to that property. To make corrections, you also need the relevant editing permission: Booking Engine / CRS - Settings for CRS configuration, or Content for property content and photos. Ask your administrator if a linked editor is read-only or refuses a save. - Know which hosted sites, widgets and CRS connections you intend to use. A property serving CRS connections alone does not necessarily need a hosted booking site or widget. The summary itself has no Save, date filter or booking-submission control. Opening or reloading it recalculates the summary; it does not change rates or submit a reservation. Its links open other screens. Changes made and saved on those screens can affect guests and shared connections. Open and review the summary 1. Open the property's Admin page. 2. Find CRS, Booking Engine, Content. 3. Select CRS Settings. 4. Select BE Settings Summary beside the property name. The summary opens in a new tab. 5. Confirm the property name on Booking Engine Summary. 6. Read every item beneath the headline, starting with those marked ✕. 7. Follow the relevant Fix in … link to inspect the configuration that needs attention. The link navigates to an editor; it does not repair anything automatically. After inspecting or saving in an editor, use your browser's Back button or reopen BE Settings Summary to return. 8. Review What's set, Where guests book, Rooms and rate plans, and What a guest pays using the reference below. Edit settings returns to CRS Settings. Content summary opens a more detailed content review. If a finding concerns an inactive account and has no correction link, contact your administrator or ChannelRUSH support. Understand the readiness message - ✕ / to fix: a configuration problem identified as blocking bookings, either generally or for an affected room or language. - ! / to review: something to check, such as incomplete content, missing photos, an unused plan or an ended promotion. - Nothing to fix: none of the implemented configuration checks returned a finding. This is not a live availability or checkout test. Counts refer to findings. One finding can group several missing fields. Read the affected room, language or connection named in the message rather than treating the headline as an exhaustive assessment. In particular, Guests can book, but not every room is not proof that another room is currently available. Booking Engine Summary readiness panel showing a missing-logo review finding and its Fix in Content - Photos link An existing demo property's review finding. Following the link opens the photo configuration; it does not upload or change a logo. When shown, Last booking and in the last 30 days describe recorded booking-engine reservations. The window concerns reservation creation, not arrival dates. These are not counts of paid or completed stays, and historical bookings do not validate today's configuration. No bookings yet is not an error by itself. Check the result after corrections 1. Save an intended correction in its own editor, with the appropriate permission. Review that editor's confirmation or validation messages before continuing. 2. Return using your browser's Back button, or reopen BE Settings Summary for the same property. 3. Reload the page. 4. Check the individual finding and the relevant detailed setting. Do not rely only on the headline or a lower finding count. 5. Check each intended guest-facing site or widget using representative dates, occupancy and languages. Review available rooms, policies and the displayed total without submitting a real reservation merely to inspect setup. A cleared finding confirms only that the summary's check no longer detects that configuration issue. Payment processing, email delivery, reservation delivery and a complete booking require their own controlled verification. Do not turn on live processing or create a real booking solely to clear a warning. Field reference: What's set Section headings link to the corresponding area of CRS Settings. General Field What to check Property The configured property type and whether pets are allowed. Currency The property's pricing currency. It is also used by the example stay; guest currency choices are shown under Booking profiles. Time zone The saved property time zone. Not set needs attention where policies use local deadlines. Bookable The configured advance-booking window, expressed as days ahead. It is not a count of dates with inventory. If it unexpectedly shows zero, review the setting rather than concluding future bookings are impossible. Location Saved latitude, longitude and postcode. Missing values are identified in the text. Card payments The configured gateway and any required settings the check finds missing. Passthrough means cards are collected without authorization or charging by that gateway mode; the property handles charging. A configured gateway is not evidence of a successful charge. Guest emails The configured sending route and a summary reply address. A property mail provider may be configured, or ChannelRUSH's no-reply sender may be used. The address used for an actual booking can depend on its language and delivery circumstances. This line does not confirm email delivery. Rooms & Rates Field What to check Room types Enabled rooms out of all configured rooms, plus the count with an enabled rate-plan mapping. Here bookable concerns that setup, not date-specific inventory, restrictions or checkout success. Rate plans Enabled plan names. None on means no plan is enabled. Booking policies Policies referenced by rate plans or date-specific overrides. + calendar dates indicates calendar use. This is not a quote for a selected stay. Add-ons Add-ons that pass the summary's sellable/pricing checks, followed by profiles configured to offer add-ons. Offered in no booking profile needs attention if you intend to sell them. Daily-price checks inspect a limited upcoming period, not every future stay. Promotions Enabled promotions grouped as live, upcoming or ended, with coupon-code availability where applicable. A live count does not confirm that a particular booking qualifies. Venues The number of enabled venues, or None when no venues are configured. An add-on counted as for sale is not guaranteed to be offered for every room or date. Review its mapping, availability and assigned booking profile when the guest-facing result differs. Booking Engine Field What to check Channel Whether the booking-engine channel is connected and whether it is handling reservations. Connected, reservation handling off is distinct from a disconnected channel. Check this even when the headline looks ready. Hosted sites Live and test-mode configuration counts. A site is counted live here when its mapping is enabled and channel reservation handling is on. This does not test its domain, content or checkout. Widget keys Non-revoked live/test keys that are enabled and have allowed sites, plus keys classed as not usable. Also check the assigned profile and its languages; a live count alone does not validate them. Booking profiles Configured profile names. Profiles are shared by the connections assigned to them. Date picker The configured default stay length. If stated, rooms can have different dates. This is separate from the advance-booking window. Content Each content profile has Complete or a clickable gap count. These checks cover selected property, plan and room text, amenities and applicable terms—not every content field. Complete does not mean photos and logos are complete; read Photos and the findings separately. Photos reports property photos and logo presence from the shared photo-source profile. No content yet means there is no content profile for that photo summary. Use Content summary for the detailed content workflow and review every language you offer. Field reference: Where guests book This section appears when the property has a booking-engine channel, hosted sites or non-revoked widget keys. Not every property has every table. Hosted sites Column Meaning Site The hosted address. Selecting it opens the site in another tab, not its settings editor. Language The content profile associated with that site mapping. Multiple language rows can use the same address. Theme The assigned presentation theme. (retired) flags a disabled theme. Shows Website, Booking engine, or Website and booking engine. A website-only row is not evidence of an available booking flow. Profile The assigned booking profile, or None . Bookings Live or Test mode , based on the site mapping and reservation-handling configuration. Neither label is a completed booking test. No hosted sites is expected for some widget-only or CRS-only setups. It is a gap only if you intended to offer a hosted site. Booking profiles Column Meaning Profile Profile name; select it to open that profile's editor. Review its shared assignments before saving changes. Languages Languages/content profiles configured on the profile. Hosted sites also have their own language mapping above. Currencies Default currency and any additional choices, possibly every supported currency. Online changes Change and cancel, Change only, Cancel only, or Neither. This is a configured feature choice, not a promise that a particular existing reservation is eligible. Add-ons Offered or Not offered . Individual add-ons still need suitable setup and availability. Terms Must be accepted or Not asked at booking. Used by Counts of assigned sites, non-revoked widget keys and, when present, CRS partners. Assigned does not mean currently live or usable. Widget keys When present, the table shows Name, masked Key, Type, Status and Last used. - Type distinguishes Live from Test. - Status is Off, No allowed sites, or On for N sites. The last state confirms configured allowed origins, not that a widget is installed or working on all of them. - Last used is a recorded date or Never, not proof of a completed reservation. - Revoked keys are excluded. The masked value is for identification; it is not the full key to embed. The summary does not issue, enable or revoke keys. Use the appropriate widget settings workflow for changes, and never send full keys to support in a screenshot. Field reference: Rooms and rate plans Only enabled room types appear as rows, and only enabled plans have plan columns. A Switched off: note lists disabled rooms or plans where applicable. Column or mark Meaning Room type Configured room name. Can't be booked flags a missing enabled plan mapping. Max guests Configured maximum occupancy. A dash means unset, not zero guests. Rate-plan columns: ✓ The room is mapped to the enabled plan. The accessible label is Sold . It does not establish a rate or availability on guest dates. Rate-plan columns: – No mapping to that plan; the accessible label is Not sold . Photos Mapped room-photo count from the photo-source profile. Zero means no counted room photos. Language columns: ✓ No checked text gaps for that room/profile. Language columns: ! N A gap count. Point to the mark to inspect the missing-field description. Edit Opens the selected room's editor. On a narrow screen, scroll the table horizontally to see the remaining languages and Edit links. No room type is switched on means there are no enabled room rows; it does not mean the table is still loading. Field reference: What a guest pays Policies The policy text summarizes deposit and cancellation terms. Where several policies are used, read the policy and associated rate-plan names. Calendar overrides and booking conditions can change which policy applies to an actual stay. Do not treat an online-cancellation sentence as a guarantee that a particular reservation can be cancelled or refunded. Check that reservation's applicable policy and self-service eligibility before promising a guest an outcome. Fees The table includes both enabled and disabled fees. Column Meaning Fee Name; select it to open the fee editor. Amount Flat currency amount or percentage. Charged The basis: per booking, per room, per room per night, per guest, or per guest per night. Rooms All rooms, named selected rooms, or None chosen . Own tax A fee-specific tax percentage that replaces ordinary percentage tax on that fee. A dash means no override; 0% explicitly applies zero own tax. Status On or Off . Off fees remain listed but do not contribute to the example. No fees means no fee rows are configured. For a listed fee, its status and room scope determine whether it applies; being present in the table is not enough. Percentage fees use applicable room-rate amounts, not the add-on total. Per-guest charging bases require flat amounts rather than percentage fees. Taxes Column Meaning Tax Name; select it to open the tax editor. Amount Flat amount or percentage. Applies to For percentage taxes: room rates, add-ons and/or fees. Nothing means none of those categories is selected. A flat tax is described as applying to each booking. Rooms All rooms, selected room names, or None chosen . Status Off , On , or On, included in the price . Included taxes are shown within the price, not added again. The paragraph beneath the table groups enabled taxes as added on top or already included. It also flags chosen-room scope. Use individual rows when comparing a specific room; the combined percentage is not automatically applicable to every booking component. Example stay This is an illustration, not a live quote or reservation. It uses two adults, two nights at 100 per night and a generic add-on at 25, all in the property's currency. The generic add-on can appear even when you do not sell an add-on at that price. The example uses a room with an enabled plan mapping when one exists, its first configured plan mapping, and an arrival 30 days ahead. It does not search real rates or availability. Its policy calculation can therefore differ from another plan or arrival date. A displayed example also does not prove the selected plan is currently sold to guests. Example stay showing room and add-on amounts, fees, taxes, total and due at booking in a demo property The demo property's illustrative calculation. These are not recommended prices or tax settings for your property. Row What it establishes Room The fixed illustrative room amount. Add-on The fixed generic add-on amount. Fees Applicable enabled fees for the illustrative stay and selected room. Taxes Added taxes for that example. Included taxes are not added again, so this can be zero even when included-tax rows exist. Total The resulting illustrative total after applicable charges. Due at booking The policy-calculated amount due for the example. This is not an authorized or collected payment. Use the example to spot unexpected charge or policy behavior, then verify your intended room, plan, dates and guest total in the actual booking flow. Do not change taxes or policies merely to make the example match a different stay. Common problems Symptom Likely explanation and safe next step When to escalate The booking engine isn't set up for this property yet. No CRS settings were found. Confirm the property, then use Open settings to begin its setup. Opening settings can initialize the property's CRS setup. Return to the summary afterward. The property should already be configured, or you cannot access setup. The headline looks ready but a room cannot be booked The headline is not a date/occupancy search. Read every finding, the room's enabled plan mappings, the Channel line and the actual guest-facing result. Configuration appears correct but the intended room, dates or language still fail. A site is Live , but its page or checkout does not work Live describes configuration flags. Check Shows , Profile , language and the intended address; perform a normal guest search without submitting a reservation. The address fails or the expected offer remains missing. A widget is counted live but does not work Enabled status and allowed sites do not establish a valid profile, correct embedding or reservation handling. Check those separately in the widget/profile settings. Those checks do not explain the failure. Do not share the full key. Content is Complete , but a photo/logo warning remains Text-gap and photo checks are separate. Use Fix in Content - Photos or Content summary for the affected item. The correct mapped asset remains absent after reloading. A saved correction is not reflected The summary is a loaded snapshot. Confirm the editor accepted the save, return to the same property and reload. The accepted saved value and refreshed summary disagree. Avoid repeated unrelated edits. A correction link is visible but saving is unavailable Viewing the summary does not grant editing permission. Ask your administrator to check the relevant permission. The required permission is present but the editor still refuses the action. Example tax, fee or deposit differs from your expectation Check enabled status, room scope, included versus added tax, own-tax overrides and the selected policy/date assumptions. The example remains inconsistent with the applicable saved settings. The summary fails to load Stop the review and record the property, page, error text and action time with time zone. Do not change payment settings or retry a charge to test this page. Contact support with that context. For support, include the property, relevant room/plan or site, affected dates and language, expected result, observed message and action time/time zone. Do not include passwords, gateway credentials, full widget keys, card details or guest personal information. Related - Set up a booking profile - Check property content readiness with Content Summary - ChannelRUSH CRS

Configure a hosted booking website

Connect a property's content and booking profile to a website address, then choose its booking mode, theme and appearance. A hosted mapping is one website/domain-and-language configuration under Websites. It is not a booking-widget key. Different language rows can use the same website address while selecting different content profiles. Before you start - Select the correct property. You need Booking Engine / CRS - Settings permission to save these settings. Ask your administrator if editing is disabled or saving is refused. - Have the property's content profile and booking profile ready. Content supplies the website's information and language; the booking profile supplies currencies, modify/cancel settings and checkout options. See Set up a booking profile when those shared settings need changing. - Decide whether you need a hosted subdomain, a custom hostname or a property page on an existing organization website. Arrange custom-domain DNS and HTTPS with your website administrator and ChannelRUSH support before directing guests there. Saving this form does not provision them. - For guest bookings, the property's Booking Engine channel and underlying booking setup must also be ready. Enabled for Reservations = Yes is not a complete readiness check. Fields are saved only when you submit Save or Save & Refresh. Selecting a theme, changing a color or opening a preview does not save this form. Saving an existing mapping can change the website guests use; it is not a private draft. Enabled for Reservations = No does not hide the website. Open the right website mapping 1. Select the property in ChannelRUSH. 2. Open Admin, then CRS Settings in CRS, Booking Engine, Content. 3. Select the BE & CRS tab. 4. Find Websites. 5. Choose Edit beside the address and language you want to change, or Add New for a new mapping. You are now on Edit Hosted Mapping. An existing mapping shows its content language above Property Information; a new one shows New Mapping. Check the address as well as the language when several rows exist. Set the content, address and booking profile 1. Select the property's content profile in Content Mapping. 2. Choose Enabled for Reservations. Use No while you are deliberately preventing normal guest reservations, but do not treat it as an unpublish or private-preview setting. 3. Choose Booking Engine Mode: - Booking Engine Only: the booking workflow without the full website pages. - Booking Engine + Website: website pages and the booking workflow. - Website Only: website pages without the booking workflow. 4. Choose Domain Type. 5. Enter Domain in the format for that type: - reservation.services: enter only your subdomain label, for example myhotel, to use myhotel.reservation.services. - reservierungsdienste.de: enter only the subdomain label, for example myhotel. - Custom: enter the complete hostname, for example booking.example.com. 6. Leave Language Override blank to use the content profile's language/culture. If you need a regional variant of that same language, enter a valid culture tag such as en-GB for English content. This does not translate content into another language. 7. Select Booking Profile. Do not include https://, a path or a slash in Domain. New mappings begin with an automatically generated address label; replace it with the intended label before saving. Do not clear the address as a way to disable bookings. Property Information showing content, reservation enablement, mode, domain type and language override Property Information on an existing demo mapping. These screenshots use the narrow-screen layout so the field values remain readable. From the booking profile summarizes the saved profile's default currency, additional currencies and modify/cancel mode. all means all additional currencies; none means none. This is a summary, not a second set of currency controls. A new form can display a proposed profile in the dropdown while the summary still says No profile selected. Choose the intended profile and check the summary again after saving and reopening. Use Edit profiles for profile changes. Those changes can affect other websites, widget keys and CRS connections sharing that profile. Selecting another profile on this mapping changes which shared settings this website uses; it does not duplicate the profile. Hosted website languages still come from the website's own content mappings. Property pages on an organization website A theme marked [MS] is for a multisite/organization website. Use it only with a compatible organization website already configured. The saved multisite theme exposes DomainPropertyId. This is the property's address segment, for example myhotel in group.reservation.services/myhotel. Enter the segment only, without slashes, and coordinate it with the organization website's address. A missing segment produces a warning. When changing between ordinary and multisite themes, use Save & Refresh to reload the chosen theme before configuring its additional fields. Switching between these themes can change or remove the property address segment. After Save & Refresh, verify the complete address; do not assume the previous segment was removed. If the address retains an unexpected property path or the website no longer opens correctly, stop and ask support before making further changes. Do not switch themes casually on an established organization site. Choose the theme and its options 1. Open Theme Viewer if you want to compare available designs. It opens separately; viewing a design does not select or save it on the mapping. 2. Choose Theme on the mapping editor. 3. If you changed the theme, open the arrow beside Save and select Save & Refresh. 4. Review the options now shown under Theme Options. 5. Choose the options for that theme. Save & Refresh saves the whole mapping, not just the theme. Check the address, content, booking profile and reservation-enabled state before using it. Theme-specific controls belong to the theme loaded when the page opened; changing the Theme dropdown alone does not rebuild them. Themes expose different choices. Some, such as the observed Aldine setup, have no extra option dropdowns. Roamers exposes: Field What it changes Choices Stock Whether the template may use its stock photos in supported sections. Template stock photos or Own photos only . Supply your own suitable photos before removing the template stock photos. RoomList Room-list presentation. Grid on phones, list on desktop , Grid , List . RoomDetail Room-detail photo presentation. Photo gallery or Photo banner . Roamers multisite theme options showing Stock, RoomList and RoomDetail An existing Roamers multisite mapping. Its extra options are not shown for every theme. Other themes can expose Home, Header, Footer, Nav, RoomList, RoomDetail, Color, Scheme, Style, Banner or Block. These select variants supplied by that theme; they are not free-text CSS or page-content editors. Use the choices actually offered and check the resulting pages. The reference below explains their roles. Keep Theme - Reservation at its existing value unless support has confirmed a different choice for your setup. The form offers Default and Skylark, but selecting a name alone is not proof of a different working checkout layout. Adjust the Brand Brand controls optional colors, shapes and fonts. These overrides can remain when you change themes, so review them with the new theme rather than assuming it resets them. 1. Enter any required colors in the text boxes beside the swatches. Use six hexadecimal digits, optionally preceded by #, such as #1f5f8b. 2. Choose the desired corners, button styling and fonts. 3. For an existing saved mapping, open Preview these values to inspect the unsaved Brand values and the currently displayed theme options. 4. Review any readability warnings. 5. Save only when the mapping and appearance are ready to apply. Optional Brand color fields with blank text boxes retaining default colors Blank color text boxes mean no override. The white swatch beside a blank box is not a saved white color. The preview uses the loaded website address and theme. It does not preview unsaved Domain, Theme, Booking Engine Mode or Booking Profile changes. A new, unsaved mapping has no Brand preview link; save and reopen it before using that preview. A preview is not a booking sandbox. Use it to inspect appearance, not to place a reservation as a visual check. Inspect the ordinary website address after saving; a preview link can continue showing its own overrides. Clear an override or reset the Brand - Clear a color's text box or select Template default to remove that particular override when you save. - Reset to template clears the unsaved Brand fields together. It does not reset the theme, theme-specific dropdowns, content, address or booking profile. Save is still required. - Cancel leaves without submitting these form changes. It does not reverse a previous successful save. For a standalone property website, blank Brand fields use the template's defaults. For a property on an organization website, blank property fields can inherit the organization's Brand instead. After clearing multisite overrides, check the ordinary saved website: the Brand preview can differ from that inherited result. Color readability Named colors such as red, three-digit values such as #fff, CSS expressions and transparency values are not accepted. Invalid Brand input stops the save. An explicit Text color must remain readable against explicit Page background and Panels and cards colors. Insufficient contrast between those values blocks saving. Other palette warnings can mean a color will be adjusted or ignored by the selected theme. Dark themes retain their own text/background/panel/border palette; some light-theme background choices are also rejected for readability. Check the rendered appearance rather than assuming every saved color will be applied unchanged. Choose website features - Cookie Notice requests the supported theme's cookie notice. It can be absent after the visitor has acknowledged it. Its presence does not establish legal or consent-management compliance. - Page - Contact and Page - Rooms enable those website pages in website modes. In Booking Engine Only, the controls are disabled and the pages are not enabled; the saved ticks are retained for a later switch back to a website mode. - Newsletter is a stored option, not confirmation of a working signup form, mailing-list connection or email delivery. Leave it unchanged unless support has confirmed its use in your website setup. Save and check the result 1. Review the entire mapping, including Enabled for Reservations, the address and the booking profile. 2. Choose Save to save and return to CRS Settings, or use the arrow beside it and choose Save & Refresh to save and reopen this mapping. 3. Read the confirmation and any warnings. If validation errors are shown, correct the identified fields before submitting again. 4. Under BE & CRS → Websites, confirm the intended address, content/language, theme, mode and Enabled state on the row. 5. Reopen Edit and confirm the saved settings, including the booking-profile summary and any theme-specific fields. 6. Open [open website] for that row and check the ordinary website address, content language, expected pages and appearance. Check both a desktop and a narrow screen when changing a theme. 7. Review BE Settings Summary for booking-setup issues before directing guests to the site. See Check your booking engine before going live. A saved confirmation establishes that ChannelRUSH saved the settings. It does not prove custom DNS or HTTPS is ready, inventory is sellable, payment processing works, a reservation was accepted or a confirmation was delivered. Website settings can be cached; do not repeatedly save because an already-open website still looks unchanged. Reopen the ordinary address and verify the saved settings before escalating. Field reference Site and booking settings Field Default or accepted values What to check Content Mapping Required; choose a content profile belonging to this property. New mappings start unselected. Select the intended language's content. The profile's text is not automatically translated by Language Override. Enabled for Reservations Yes / No ; new mapping defaults to Yes . Controls reservation enablement, not website privacy. The Booking Engine channel also needs reservation handling enabled. Booking Engine Mode Booking Engine Only / Booking Engine + Website / Website Only ; default Booking Engine + Website . Use a booking-capable mode when guests must book; full website pages require a website mode. Domain Generated label on a new form; leading/trailing spaces are removed and stored text is lowercase. Use a subdomain label for the two hosted suffixes, or a complete hostname for Custom. No slashes or URL scheme. Domain Type reservation.services / reservierungsdienste.de / Custom ; default reservation.services . Must match how the address is configured. Custom requires separate DNS/HTTPS arrangements. DomainPropertyId Shown for a saved multisite theme; trimmed and lowercased. The property path segment, without slashes. Required for a usable multisite property address even if only a warning is shown. Language Override Optional; blank uses the selected content profile's culture. Use a valid regional culture tag for the same language, such as en-GB . Booking Profile Required; select an existing property profile. Defines shared currencies, modify/cancel and checkout options. A proposed dropdown selection is not proof of a saved association. From the booking profile Read-only summary. Reopen after saving a changed selection to verify the assigned profile's values. Theme New mappings select Bootstrap 5 where available. Available themes depend on your organization/setup. A saved retired theme can remain visible on its existing mapping without being offered for new mappings. [MS] needs compatible organization-website setup. Theme - Reservation Default / Skylark in the observed form; new mapping defaults to Default . Retain the existing choice unless support confirms the alternative for your setup. Theme-specific variant fields Only fields supplied by the saved theme appear. Each dropdown accepts its listed values; the first/default variant is used when no valid saved variant exists. Not every theme provides the same variants or uses the same names for them. Field Role Home Home-page layout variant. Header Header arrangement. Footer Footer arrangement. Nav Navigation placement or style, such as top navigation versus sidebar. RoomList How rooms are listed, such as grid, rows or a responsive combination. RoomDetail Room-detail layout or photo presentation. Color A theme-supplied color palette; distinct from individual Brand color overrides. Scheme Light or dark theme scheme where offered. Recheck Brand contrast and ignored overrides when changing it. Style A theme-supplied visual style variant. Banner Banner presentation, such as a photo versus breadcrumb treatment. Block Breeze Block's decorative block pattern: Circle block , Diamond block , or Sun block . Stock Roamers' template-stock-photo setting, described above. Brand fields All Brand fields are optional. Blank or Template default removes the property override on save; organization-website inheritance can still apply. Field What it changes / accepted values Accent (buttons, links) Main accent color, in six-digit hexadecimal form. Text on the accent Foreground text on accent-colored surfaces. Check contrast with Accent. Text Main text color where supported by the theme. Page background Page background color where supported. Panels and cards Panel/card surface color where supported. Lines and borders Border and divider color where supported. Corners Template default , Square , Subtle , Soft , Round . Button shape Template default , Square , Soft , Pill . Button text Template default , As written , Uppercase . Heading weight Template default , Regular , Bold . Body font Template default or one of the supplied fonts; controls body text. Heading font Template default or one of the supplied fonts; controls headings. The font list includes Alegreya, Alegreya Sans, Barlow Semi Condensed, Cal Sans, Golos Text, Heebo, Inter, Jost, Libre Franklin, Manrope, Marcellus, Montserrat, Old Standard TT, Open Sans, Overpass, Playfair Display, Poppins, Public Sans and Yeseva One. Choose from the list rather than entering an external font URL. New mappings start with Cookie Notice, Newsletter, Page - Contact and Page - Rooms unchecked. Existing mappings retain their saved choices. Common problems The form cannot be saved - A booking profile is required. Select a property booking profile. If none exists, create one through Edit profiles and return to the mapping. - Content Mapping is missing. Select an existing content profile belonging to the current property. - The Domain cannot contain any slashes or The Domain Property Id cannot contain any slashes. Remove the scheme and path; keep the hostname/subdomain and optional property segment in their separate fields. - This Domain Type and Domain are already in use by another property and are unavailable. Confirm the address and property. Do not change another property's mapping to obtain the address; ask support to investigate ownership/setup. - The selected content profile is already mapped for this Domain Type / Domain / Domain Property ID / Language Override combo… Return to Websites and edit the existing matching row rather than creating a duplicate. - The Language override must be for the same language as the selected content profile. Use a regional culture of that language or clear the override. Select a different content profile when you need different-language content. - A Brand field or contrast is refused. Correct that field, use an allowed choice, or clear the override. Review the rest of the pending form before saving again. The saved website does not look as expected Confirm that you edited the correct address/language row. Reopen it to check the saved theme and options. Use the ordinary [open website] link, not an old preview URL. Review palette warnings and organization-level Brand inheritance. If the difference remains, give support the property, website URL, mapping language, changed field, action time/time zone and a non-sensitive screenshot. Theme-specific fields or DomainPropertyId are missing They depend on the loaded theme. After intentionally choosing and saving a theme with Save & Refresh, check the reloaded form. A multisite setup also needs the organization's compatible website; ask your administrator or support if the intended theme is unavailable. Do not change an established live site's theme merely to reveal a field. The website opens, but guests cannot book Check Enabled for Reservations, Booking Engine Mode, the property's Booking Engine channel and BE Settings Summary. Website visibility is not proof of bookable inventory or a working checkout. Do not repeatedly enable or save settings without identifying the failing step. Escalate with the property, ordinary website URL, affected stay dates and displayed error; do not send payment details or guest information. A save times out or returns an unexpected error The outcome may be uncertain. Reopen the existing mapping and inspect its values before retrying. For a new mapping, check Websites for the new row before using Add New again. If you cannot establish what was saved, ask support with the property, mapping/address, action time/time zone and error text. Do not create a duplicate mapping as a recovery step. Related - Set up a booking profile - Check your booking engine before going live

Review booking-engine setup across your organization

Use Org Booking Engine Summary to identify missing booking-engine configuration and content across the properties you can access in an organization. This is a setup review, not a booking-performance report. Setup complete does not prove that a website can accept bookings, that payments work, or that confirmation emails are delivered. Before you start - Select a property in the organization you want to review. Its name below the report title identifies the starting context, not the report's entire property scope. - Organization administrators see eligible properties within their authorized organization scope. Other users see their assigned eligible properties. Inactive properties and properties without a CRS or booking-engine channel are excluded. - You can read the summary without permission to edit booking-engine settings. Correcting a finding requires access to the relevant property and editing screen. Open and review the summary 1. Open Reports. 2. Under Overview, select Org Booking Engine Summary. 3. Check the selected property below Org - Booking Engine Summary. 4. Find the property you want to review in the report. 5. Read its setup badge and any Missing: line. 6. Review Enabled, Payments, any E-mail row, and the fee, tax and example-charge details. 7. Review each website/language section and the room findings beneath it. 8. Record the property, website/language, room and exact missing item before opening an editing screen. The report loads when you open it. There is no date range, Search button, Save button, CSV download or Excel view on this page. Use your browser's Find command to locate a property or a particular missing-item label in a long report. New window opens a separate tab containing the same report without the main navigation. The original report stays open. The separate view does not show another New window control. Read the property summary A property's badge has one of these meanings: - Booking engine not set up: the summary did not find booking-engine settings for that property. Detailed configuration is not shown. - 1 item missing / N items missing: one or more of the report's property, website-content or room checks found a gap. - Setup complete: those checks found no gaps. This is not a complete go-live test. The count is the number of findings displayed across the property's sections, not necessarily the number of distinct corrections. A room or shared content profile can appear under more than one website or language, repeating the same finding. Property configuration and example charge in the organization booking-engine summary Configuration portion of a demo property. Website and room sections continue below it. What the badge does not check Review the details even when the badge says Setup complete. The missing-item count does not include a disabled booking engine or failed payment/email setup. It also does not establish that websites, booking-profile languages or enabled rooms exist. A website/language section appears only when its linked content can be loaded. Missing sections are not a clean bill of health. The report does not verify available dates, sellable rates, checkout, payment authorization, email receipt or channel delivery. Review website and room findings Below each property's configuration, the report groups content by website address and booking-profile language. The same room can appear several times because each website/language is checked separately. Within each section: - Missing: below the website identifies missing property content for that section. - Room headings identify enabled booking-engine room types. - Missing: below a room identifies missing configuration or content for that room in this section. - Complete means that room passed this report's checks for this section. It does not establish bookable rates or availability. Website and room content findings, including missing descriptions and missing room mappings An existing demo website section with property-content and room-content gaps. No configuration was changed for this example. Follow up without losing the property's context Some report shortcuts currently lead to an unavailable page or the wrong settings screen. Use the main navigation as the reliable starting point for corrections: 1. Return to the normal application tab if you opened New window. 2. Select the property named in the finding. 3. Open Admin → Settings - CRS. 4. Confirm the property name on CRS Settings. 5. Choose the section relevant to the finding: - Rooms & Rates: room types, rate plans, fees, taxes and General Settings. - Content: choose the relevant content-profile/language tab for property text. - Content - Photos: photo mappings. - BE & Channels: websites and booking profiles. 6. Use the relevant setup guide before changing configuration. Save changes on that editing screen, not in this report. For room configuration, the Settings link beside a room points to that room's editor. Check its property and room name before editing. The Settings link at the top of the property section is different: it can return to the main settings page with That channel isn't set up for this property. That message from this shortcut is not proof that the booking engine is absent. Content, Photo Mappings and Photo File Manager shortcuts in the report can lead to Error - 404 - Page Not Found. Use the sections above instead; do not create replacement content merely because a shortcut failed. For the file library, use Admin → Home, then Photo File Manager under CRS, Booking Engine, Content. The website-address link opens the configured address in another tab. The presence of the link does not establish that the site is reachable or ready to sell. Check the result After authorized changes have been saved on the appropriate editing screen: 1. Reopen Reports → Overview → Org Booking Engine Summary, or reload the report tab. 2. Find the same property and website/language section. 3. Check whether the specific Missing: item disappeared and whether the displayed configuration now matches the saved settings. 4. Review other website/language sections that use the same content or room configuration. A changed finding confirms only what the refreshed report displays. Review the relevant website and booking workflow separately before treating the property as ready to sell. The report has no last-checked timestamp and does not submit a booking, send inventory, charge a card or resend an email. Field reference Property configuration and charges Field What it shows How to interpret it Property name The property owning the section. Use this name when selecting the property for follow-up. Missing: Latitude / Longitude A coordinate has not been supplied. A supplied coordinate passes this presence check; its location is not validated here. Missing: Postal Code Postal code is empty. The report does not validate the postal code against an address. Enabled The stored booking-engine/CRS enabled setting, Yes or No . Read it separately from the setup badge. Payments Credit-card processor name and Setup: Yes/No . This is a stored-configuration check, not a payment test. Passthrough can show Yes without proving online card charging. E-mail Mail provider and Setup: Yes/No , when shown. SMTP does not produce this row. A blank provider can appear as . Setup: No . Neither a missing row nor Yes proves delivery. Fees Stored fee amounts, names, calculation types and any Tax Override percentage. None means no fee entries. This list does not show enabled state or room applicability. A listed fee is not necessarily charged for every booking. Taxes Flat amounts, then percentage taxes with their selected bases: room rates , amenities , fees . None means no tax entries. The list does not identify disabled or included taxes, or room-specific applicability. Inspect the actual tax settings for those details. Total tax Separate sums of percentage rates on room rates, fees and amenities. These are percentages, not tax amounts. Flat taxes are not included in the sums. 0.00% for a base does not mean no flat tax or fee can apply. The row is absent when there are no tax entries. Example charge An illustrative calculation for 1 room, 2 people, 2 nights, $100 per night room rate, $25 amenities . The next lines show room rates, fees, amenities, subtotal, taxes and total. This is not a quote or a charge. The example does not select a real room or rate plan, so it does not demonstrate room-specific fees or taxes. It does not use a customer-selected stay date. The fee/tax lists and percentage sums can include entries that do not apply in the example, so they are not a recipe for manually reproducing its total. The report displays dollar signs without a currency code. Do not use those symbols as confirmation of a property's configured selling currency or as a currency conversion. Website content findings Finding Meaning Follow-up Hotel Description - Short Short property description is empty for the linked content. Review the matching profile in Content . Hotel Description - Long Long property description is empty. Review the matching profile in Content . Amenities The property's content amenities list has no entries. Review the content amenities list for that profile. This is not a check of every channel-specific amenity setting. Room findings Finding Meaning Follow-up Max Occupancy Maximum occupancy is unset. Review the room's configuration. A stored zero is not treated as missing by this check. Rate Plan Mappings. Unbookable. The room has no rate-plan mappings. Review its mapped rate plans. Having a mapping does not itself establish active rates or availability. All Content / Mapping This content profile has no room-content entry linked to the booking-engine room. Review the correct profile and room mapping before creating or replacing content. The room's Content shortcut is absent in this case. Photo Mappings The linked room-content entry has no photo mappings. Review the room's photo assignments. Existing mappings are not checked for image quality or reachability here. Room Description The linked room description is empty. Review the room text in the relevant profile/language. Amenities The room-content amenities list has no entries. Review the room's content amenities. Room Bed Description The bed-description text is empty. Review the descriptive text; a separate numeric bed count does not clear this check. Disabled booking-engine rooms are omitted. The report checks for missing content, not translation quality, legal completeness or whether wording is suitable for a particular channel. Common problems A property is missing, or the report has no property sections The property may be inactive, outside the selected property's organization, outside your assignments, or without a CRS/booking-engine channel. Confirm the organization and property with your administrator. The report can show no sections even without the No eligible properties are available for this summary. message. If the property should qualify, contact support with the organization, property name/ID and report URL. Do not interpret an absent section as successful setup. Setup complete appears beside an email or payment setup problem The badge counts content/configuration gaps, not every readiness condition. Inspect Enabled, Payments and E-mail separately. Ask your administrator to review the relevant settings; do not change payment credentials or send test messages merely to clear the badge. Escalate if stored settings and the report disagree after reload. A website, language or room is absent Check the website's booking profile and linked languages/content. Only enabled rooms are shown within loaded website/language sections. A missing section can hide checks rather than indicate that they passed. Ask your administrator or support to confirm the expected mapping before adding duplicates. A shortcut fails or opens the wrong page Use Admin → Settings - CRS for the selected property as described above. Do not repeat setup or create a new channel in response to a failed report shortcut. If the normal navigation also fails, send support the property, link label, destination URL and error text. A finding remains after a save Reload the report, then confirm the property, content profile/language and room edited. The same gap may appear under several websites. If the correct saved value is present but the report still flags it, send support the exact finding and the relevant property/profile/room. Do not send passwords, payment details or guest data. Related guides - Check your booking engine before going live - Check property content readiness with Content Summary

Customize your property's booking-engine wording

Change the standard labels and messages shown on your property's hosted booking websites, or remove a property-specific change to use inherited wording again. Before you start - Select the correct property. You need Booking Engine / CRS - Settings permission to save. If the form is disabled or saving is refused, ask your organization administrator to check your access. - Know which website and language you want to change. This page edits shared booking-engine labels and messages, not property descriptions, room descriptions or booking policies. - A change belongs to the property and language, not to one website, theme or booking profile. The property's applicable hosted websites can therefore use the same wording. This guide does not describe widget or OTA text customization. - Coordinate with anyone else editing this property. Open a fresh form before starting; saving an old open form can replace another person's intervening changes, including fields you did not intentionally edit. There is no autosave. Save submits the whole wording form, including edited rows hidden by a filter. These are guest-facing settings, not a private draft. Cancel leaves without submitting your current changes; it does not undo an earlier save. Open the wording editor 1. Select the property in the application property selector. 2. Open Admin → Settings - BE. 3. In CRS Settings, use the BE & Channels tab. 4. Find Websites. 5. Select Wording. 6. Confirm the selected property and the Booking Engine - Wording heading before editing. You can also open Admin → Settings - CRS, then select BE & Channels → Websites → Wording. Find and change a label or message 1. Enter a key or phrase in Filter by key or text. For example, Postal finds postal-code labels. 2. Locate the correct row in the Text column. Similar labels can serve different forms: AddressPostalCode and CreditCardPostalCode are separate texts. 3. Find the language column you want to change. 4. Read the standard wording above its box. Gray wording inside an empty box is inherited organization wording, not a saved property value. 5. Enter your replacement in that language's box. For example, enter ZIP Code for an English postal-code label if that suits your guests. 6. Keep every placeholder, such as {0} or {1}, exactly as written in the standard text. You can move a placeholder within the sentence, but do not remove it, renumber it or add formatting inside its braces. 7. Review the other language columns and any other edits you made. Clear the search and turn off Only texts with a wording of their own if you need to inspect all rows before saving. 8. Click Save at the top or bottom of the form. 9. Check the returned page for a success or validation message, then follow Check the result below. Use plain text, up to 2,000 characters per box. HTML and literal < or > characters are not accepted. Leading and trailing whitespace is removed, and pasted line breaks are converted to spaces. Use the filters without losing track of edits - Filter by key or text searches keys, standard text and entered property wording across the displayed languages. Matching is case-insensitive. Gray inherited organization wording is not included in this search. - Only texts with a wording of their own keeps rows with a nonblank property entry in at least one language. A row can remain visible even when the language you are checking is blank. Inherited organization wording alone does not qualify. - Both filters apply together. If nothing appears, clear the search and turn off the checkbox before concluding that a text is unavailable. - Filters change the displayed rows, not the scope of Save. Hidden edits are still submitted. - If you change a wording box while filtering, change the search or toggle the checkbox to refresh the visible selection. Typing in a wording box does not rerun the filters by itself. Remove a property override 1. Find the row and language you want to restore. 2. Delete the contents of that language's box, leaving it empty. 3. Review any other pending changes, including hidden rows. 4. Click Save. 5. Reopen the editor and confirm the property box is empty. 6. Check the affected hosted website in the same language after its wording refreshes. An empty saved box means use inherited wording, not “show a blank label.” On the property's own website, an organization override takes precedence over standard text. Clearing the property box therefore does not necessarily restore the standard text printed above it. Spaces alone also count as empty. The page previews inheritance from the property's organization. If the property appears on an organization website belonging to a different organization, that website can use its own organization's fallback. Check the actual destination website rather than treating the gray placeholder as proof of every website's output. Check the result 1. After Save, read the message on the returned editor. If validation names a key and language, correct that box before submitting again. 2. Reopen Wording for the same property. Confirm the saved replacement remains in the correct language box, or that a cleared override is empty. This checks the saved configuration, not what a guest has already loaded. 3. Return to CRS Settings → BE & Channels → Websites and open the relevant website address. 4. Select the affected language and visit the page that uses the label or message. Do not complete a booking or change a reservation merely to test wording. 5. Reload that page when checking for the new text. A browser page already open does not update its wording automatically. Hosted sites refresh saved wording through periodic checks. The editor displays a 15-minute refresh notice, but saving does not immediately refresh every website or guarantee a deadline if a refresh fails. If the editor retains the correct value but the website still shows old wording, check the property, website, language and exact text key before saving again. Contact Support if the discrepancy persists. The editor contains a shared text catalogue. A listed text is not proof that your particular theme or screen displays it. Changing wording also does not enable the feature described by that wording. Field reference Control or value Meaning and use Filter by key or text Narrows visible rows by a case-insensitive phrase in a key, standard text or entered property text. It does not save or limit which edits are submitted. Only texts with a wording of their own Narrows rows to those with a nonblank property entry in any displayed language. It combines with the text filter. Text The stable key identifying the label or message, such as AddressPostalCode . Use the key to distinguish similar phrases and when contacting Support. Language headings The languages used by the property's website booking profiles. English variants share en-US , German variants share de-DE , and Spanish variants share es-ES ; a profile using es-MX can therefore appear here as es-ES . With no configured website languages, the editor falls back to en-US . This page does not add languages. Standard text above a box The global wording for that language. A dash means no standard text was loaded for that key/language; it does not mean the guest will see a dash. Text inside a box The property's own replacement for that key and language. Blank uses fallback. Each language is edited separately; entering English wording does not translate it into other languages. Gray placeholder inside an empty box Organization wording inherited by this property when available. It is not a property override. The text above the box still shows the global standard. {0} , {1} and similar placeholders Positions where the site inserts values. Preserve their exact spelling. Named placeholders, unmatched braces and formats such as {0:N2} are not supported. Validation compares against the language's standard text, or English when that standard text is missing. Save Submits the entire form, validates changed wording and returns to this property's editor after saving. The top and bottom controls do the same thing. Cancel Returns to CRS Settings without submitting the current form. It does not reverse saved changes. For language setup, review the website's assigned booking profile under Booking Profiles. Changes to a shared profile can affect multiple websites; do not change its languages solely to make a column appear without reviewing those uses. Common problems Save reports a wording validation error The message identifies the text key and language. Remove < or >, shorten an overlong entry, or restore the required numeric placeholders as indicated. One rejected entry prevents the wording changes in that submission from being applied. Your posted values remain available for correction. If a language has no standard text above its box, placeholder validation can use English. If the required placeholders are unclear, ask Support rather than guessing a replacement. Save fails without a wording validation message A general processing or database failure is different from validation. Some changes may already have been saved before a later failure. Reopen the editor and compare the affected boxes before retrying; do not assume the whole submission rolled back. If you cannot establish what saved, stop and contact Support. A text or language is missing Clear the search and turn off Only texts with a wording of their own. Check the website's booking-profile languages. If the text still is not in the shared catalogue, send Support the website address, language and the phrase or screen you want to change. This form cannot create a new text key. Clearing a box does not restore the standard phrase An organization override can now be taking effect. Check the gray placeholder and the actual website's organization context. If the inherited wording is not appropriate, coordinate the organization wording change with its administrator or enter an intentional property replacement. The website still shows the old phrase First verify that the replacement is saved for the correct property and language. Then confirm the website and screen use that key, and reload after the wording refresh. Do not repeatedly save unchanged values to force a refresh. If it remains wrong, provide Support with the property, website address, language, text key, expected and displayed wording, save time/time zone and any error message. Do not send passwords, payment details or guest information.

Customize your organization's booking-engine wording

Set shared labels and messages for your organization's hosted booking websites, while allowing individual properties to keep their own wording. Before you start - Confirm the organization you are signed in to. This editor changes organization wording, not only the property shown in the property selector. Selecting another property does not switch the organization whose wording you edit. - You need Booking Engine / CRS - Settings permission to save. If controls are disabled or saving is refused, ask your organization administrator to check your access. Demonstration accounts cannot save these settings. - Know which website, language and text you want to change. This is the shared label-and-message catalogue, not property descriptions, room descriptions or booking-policy content. - Coordinate with other editors and start from a freshly opened form. Saving an old form can replace another person's intervening changes, including fields you did not intentionally edit. There is no autosave. Save submits the whole wording form, including edited rows hidden by filters. Saved wording is guest-facing configuration, not a private draft. Cancel leaves without submitting your current edits; it does not undo an earlier save. Open organization wording 1. Open Admin → Home. 2. In the CRS, Booking Engine, Content section, select Booking Engine Organization Settings. 3. Confirm the organization name on CRS Org Settings. 4. Open the Websites tab if it is not already selected. 5. In the Websites section, select Wording. 6. Confirm the heading Booking Engine Organization - Wording before editing. If Booking Engine Organization Settings is not available, ask your administrator to confirm your organization's booking-engine setup and access. Do not substitute a different organization's property to find the editor. Understand which wording wins Wording is chosen separately for each text key and language: 1. On a property's page, a saved property override takes precedence. 2. Otherwise, the applicable organization override is used. 3. If neither exists, the standard text is used. On the organization's own pages, there is no property override. A property's own hosted website uses its owning organization's fallback. When a property appears on another organization's hosted website, that website's organization supplies the fallback instead. Your organization entry is shared wherever that organization supplies the wording; it is not limited to one domain, theme or booking profile. A property-specific entry can therefore keep a property from adopting your new organization phrase. Use the property wording guide when you need an exception for one property. Find and change a label or message 1. Enter a key or phrase in Filter by key or text. For example, Postal finds postal-code labels. 2. Identify the intended row in Text. AddressPostalCode and CreditCardPostalCode are different texts, even if their displayed phrases are similar. 3. Find the language column you want to change. 4. Read the standard wording above its box. 5. Enter your replacement in that language's box. For example, ZIP Code could replace an English postal-code label. 6. Preserve every placeholder, such as {0} or {1}, exactly as written. You can move a placeholder within the sentence, but do not remove it, renumber it or change its spelling or brace contents. 7. Review your other edits and language columns. Clear the search and turn off Only texts with a wording of their own if you need to see all rows. 8. Click Save at the top or bottom of the form. 9. Read the returned message and follow Check the result below. Use plain text, up to 2,000 characters per box. HTML and literal less-than or greater-than signs are not accepted. Leading and trailing whitespace is removed; pasted line breaks become spaces. Organization wording filtered to AddressPostalCode, with standard text and empty English, German and Spanish override boxes The demo editor shows the standard phrase above each empty organization box. Filtering does not change any wording. The refresh notice is explained under Check the result. Find existing overrides - Filter by key or text matches keys, standard text and entered organization wording across the displayed language columns. Matching is case-insensitive. - Only texts with a wording of their own keeps rows with a nonblank organization entry in at least one displayed language. A row can qualify even when the language you are checking is blank. - Both filters apply together. Clear the search and turn off the checkbox before concluding that a text is missing. - The checkbox considers current inputs, including unsaved entries, when filtering runs. Typing in a wording box does not rerun the filters by itself; change the search or toggle the checkbox to refresh the selection. - Hidden rows remain part of Save. Filters are not a way to save only one row or language. Remove organization wording 1. Find the text key and language you want to restore. 2. Empty that language's box. 3. Review all other pending edits, including hidden rows. 4. Click Save. 5. Reopen organization Wording and confirm that box is empty. 6. Check the affected website and language after its wording refreshes. An empty saved organization box means no organization override, not “display a blank label.” Spaces alone also count as empty. Clearing this entry does not remove a property's own wording; that property override still takes precedence. Without a property override, removing the organization entry restores the standard text where available. Clearing a replacement does not recover an older organization phrase. To restore an earlier custom phrase, enter that phrase again and save. Check the result 1. After Save, read the success or validation message on the returned editor. 2. Reopen Wording from the same organization's settings. Confirm that your replacement remains in the correct language box, or that a cleared box is empty. This checks saved configuration, not a guest's already-open page. 3. Return through Organization Settings to Websites and open the intended website address. For a property's own website, use that property's website address instead. 4. Select the affected language and visit a page that uses the text. Check both an organization page and an affected property page when your change is intended for both. 5. Reload the page when checking for updated wording. Do not complete a booking, send a form or modify a reservation merely to test text. The editor displays a 15-minute refresh notice. Hosted sites check for wording changes periodically as they serve requests; Save does not immediately refresh every site or guarantee a deadline if a refresh fails. An already-open guest page does not update automatically. If the saved value is correct but the site differs, check the website's organization, any property override, the language and the exact text key before saving again. A catalogue entry does not establish that every theme or screen displays that text. Changing wording does not enable the feature described by it. Field reference Control or value Meaning and use Filter by key or text Narrows displayed rows by a key, standard phrase or current organization entry. It neither saves nor limits the submitted edits. Only texts with a wording of their own Shows rows with a nonblank organization input in at least one displayed language. It combines with the text filter. Text The key identifying the label or message, such as AddressPostalCode . Use it to distinguish similar phrases and when contacting Support. You cannot add new keys here. Language headings, such as en-US , de-DE and es-ES Shared translation-language columns derived from your organization's booking-profile languages. Regional choices can share a canonical column: the demonstrated es-MX profile language appears as es-ES in this editor. With no configured profile languages, the editor offers English. This does not add a language to a website. Standard wording above a box The standard text for that key and language, not a preview of your organization's replacement. A dash means no standard phrase is loaded for that cell. Do not assume a dash guarantees English guest-facing fallback. Wording box Your organization replacement for that key and language. Maximum 2,000 characters; plain text only. Organization boxes do not preview a property's separate override. Empty wording box No organization override. Standard text applies unless a higher-priority property override supplies the text. Empty does not hide the label. Placeholders such as {0} Values supplied when the message is displayed. Preserve their exact spelling and all required numbers; do not enter your own values in place of them. Save Validates and submits the entire form. The top and bottom buttons perform the same action. Cancel Returns to organization settings without submitting current edits. It cannot reverse saved changes. Organization Settings Returns to the organization's settings page; it is navigation, not Save. Common problems Save names a key and language in a validation error Correct the named box: remove less-than or greater-than signs, shorten an overlong entry, or restore the required numeric placeholders. A message such as plain text only, < and > are not allowed or keep the placeholders ... of the original text identifies the rule to fix. One validation refusal prevents the wording changes in that submission from being applied. Posted values remain on the page for correction. If the standard phrase is missing for a language, placeholder validation can use English; ask Support if the expected placeholders are unclear rather than guessing. Save fails without a wording validation message A general processing failure is different from validation. Some changes may have saved before a later failure. Reopen the editor and compare the affected boxes before repeating the submission. If you cannot establish what saved, stop and contact Support rather than assuming the whole save was rolled back. A language or text is missing Clear the search and turn off Only texts with a wording of their own. Check the organization's booking-profile languages and the editor's language headings. Regional language choices can share a column. If the text or expected column is still unavailable, give Support the website, language and phrase or screen you need to change. Do not change unrelated profile languages to manufacture a column. A property keeps its old phrase A property override can take precedence over the organization entry. Inspect that property's wording for the same key and language. Coordinate any removal with its administrator; changing organization wording alone does not erase property exceptions. If no property override explains it, check which organization hosts the actual website and contact Support if the discrepancy remains. Clearing a box does not restore the expected wording Confirm that the empty box was saved for the correct organization and language. A property override or a different hosting organization's fallback may still apply. If you wanted an older custom phrase rather than the standard text, re-enter that phrase intentionally. Escalate if the actual website context does not explain the result. The website still shows old wording Confirm the saved value, exact key, language and website scope. Reload the affected page after the normal wording refresh; repeatedly saving unchanged values is not a refresh control. If the discrepancy persists, send Support the organization, affected property if applicable, website address, language, key, expected and displayed wording, save time/time zone and error text. Do not send passwords, payment details or guest information. Related - Customize your property's booking-engine wording