Hospitality & travel
Booking engines are legal instruments. Every rate, resort fee, allergen menu, review score and "only 2 rooms left" nudge on your site is a regulated statement, and the DMCC and Omnibus regimes have made pricing games directly finable on both sides of the Channel.
Sub-sectors, with their real law counts
Read live from the Attachment Matrix. Counts shown for United Kingdom / England; every cell opens the full stack in the Explorer.
The price at the end, against the price at the start.
The booking flow is walked to checkout and every increment recorded: resort fees, service charges, cleaning, taxes added late. Drip pricing is now a banned practice, and the receipt is the evidence.
What the Radar watches hardest here
A worked scenario
ILLUSTRATIVEA boutique hotel group, Dubai + London, direct-booking push
Challenge. The booking engine added a "service charge" at step three, and the Dubai site’s tracking ran identically for UK visitors, pre-consent.
What the Radar did. The Radar’s UK-vantage capture caught the pre-consent tracking (PECR, T1) and the interaction test walked the booking flow to surface the late fee (DMCC drip-pricing finding).
Outcome. Headline rates corrected across both sites; consent gated by geography; evidence vaulted before either regulator or OTA partner noticed.
See your exact stack, then watch it.
Pick your sub-sector and jurisdiction in the Explorer for the verbatim law list, or start with the introductory audit and see the Radar's method on your own website.
Watchlist items describe checks the Radar runs, not legal advice about your business. Applicability depends on confirmed facts and supported scope. Scenario is illustrative, not a client reference.