Direct answer: before a UK hotel group, short-term-let operator, OTA, channel manager, package seller or booking agent lets an **AI assistant or agent quote, personalise or “confirm” an inclusive overnight price** for accommodation in a destination with a **visitor levy** (tourist tax), you must already know **whether the stay is in scope**, **how the levy is calculated** (rate base, night caps, VAT treatment), **which booking cut-off dates apply**, and **that the total price shown at invitation to purchase includes the levy**. An AI that invents a room rate, omits the levy until checkout, or averages nights incorrectly is not a helpful concierge. It is a pricing and consumer-law failure waiting to land on ops.
That is the operator question Kaize is answering here. We are a UK AI product studio for travel and hospitality. This is not tax advice and not a substitute for your local-authority scheme documents. It is a **control-stack** article for product and revenue leaders: what must already be true before an agent is allowed to **quote inclusive accommodation** where a visitor levy applies. It sits beside — and does not replace — our DMCC drip-pricing / total price controls, Package Travel Regulations booking-journey changes, CRA unfair-terms notices and AI agent access-control pieces.
Primary evidence is first-party public authority material: the City of Edinburgh Council Visitor Levy scheme page (5% on paid overnight accommodation cost **before VAT**, **not** on extras such as parking, meals, drinks or transport; charged on the **first five nights**; applies to stays from **24 July 2026**, with an exemption for stays booked and paid in part or full **before 1 October 2025**); VisitScotland’s Visitor Levy business guidance under the **Visitor Levy (Scotland) Act 2024**; and the cross-cutting UK requirement that visitors must see the **total price inclusive of the visitor levy at the point of purchase** (price transparency / DMCC-aligned practice VisitScotland and Edinburgh guidance both point operators toward). We do not invent client outcomes, penalty cases, GSC lifts or GEO ranks.
Visitor levy is not the same as DMCC drip-pricing — and AI must not conflate them
**DMCC drip-pricing rules** answer: show the **total price** (mandatory fees included) when you invite someone to purchase. A **visitor levy** answers a narrower destination question: a **statutory local charge** on overnight accommodation with its own **rate base**, **night cap**, **accommodation-type scope** and **forward-booking cut-offs**. An AI that only “adds a tourist tax line somewhere” without encoding those rules still fails both stacks — and an AI that only learned “always show total price” without a levy calculator will still under- or over-quote Edinburgh stays.
For product owners the practical rule is: **inclusive-price UX** (DMCC / price marking) and **levy calculation state** (destination scheme) are separate gates. Both may be required. Neither is optional just because a generative assistant drafted a quote card.
- Do not let the agent treat “room rate × nights” as “inclusive overnight price” in a levy destination.
- Do not let the agent apply the levy to meals, parking, spa or transfer add-ons when the scheme says accommodation-only.
- Do not let the agent invent a sixth levy night when the scheme caps at five consecutive nights (Edinburgh).
- Do not let the agent ignore the 1 October 2025 / 24 July 2026 cut-off logic for Edinburgh forward bookings.
What Edinburgh’s scheme actually requires operators to encode
Edinburgh is the clearest live UK destination scheme for AI quote engines today. Per the Council’s published scheme summary: the levy is **5%** of the cost of **paid overnight accommodation**, charged **before VAT**, **not** charged on extras (parking, meals, drinks, transport), and only on the **first five nights** of a stay. It applies for stays from **24 July 2026** onward. Stays on or after that date that were **booked and paid for (in part or full) before 1 October 2025** are **not** subject to the levy. Scope includes hotels, hostels, guest houses, B&Bs, self-catering, aparthotels, many short-term lets, and other paid overnight categories listed by the Council — including providers **below the VAT threshold**.
VisitScotland’s national guidance stresses that local authorities set rate and structure, that percentage schemes apply to the **reasonable cost of accommodation only**, and that operators must **follow existing pricing regulations** so the visitor sees the **total price inclusive of the visitor levy at the point of purchase**. That is exactly where AI quote and “deal” agents break first: they optimise for a headline number, then surprise the guest with a levy at payment or arrival.
- Version-pin destination levy rules in config (Edinburgh 5% / 5-night cap / accommodation-only / cut-off dates) — not in free-text prompts the model can “creatively interpret”.
- Treat package and OTA merchant-of-record seams as first-class: who calculates the levy, who displays it, who remits it.
- If your AI sits above a channel manager, PMS or OTA, map **which system of record** owns stay dates, accommodation net, and levy liability before the agent speaks a price.
Gate 1 — Is this stay in a visitor-levy destination and in scheme scope?
Before an agent can quote, classify the property and the stay.
- Destination: Edinburgh City Council boundary today; other Scottish local authorities may adopt schemes under the Visitor Levy (Scotland) Act 2024 — do not hard-code “Scotland = 5%”.
- Accommodation type: in-scheme vs exempt (use the Council’s published lists; do not let the model invent exemptions).
- Guest type: Edinburgh notes UK and Scottish residents are included unless a specific published exemption applies — AI must not waive the levy because someone “sounds local”.
Gate 2 — Can we calculate the levy correctly for these dates?
Calculation is deterministic product logic, not generative prose. For Edinburgh-style percentage schemes: take the **accommodation-only** portion for each **liable night**, apply the rate, honour the **night cap**, and apply **forward-booking cut-offs**. VisitScotland FAQs walk mixed-date stays (levy only on nights that fall on/after the start date). An agent that averages a seven-night stay into seven levy nights, or that applies 5% to a B&B package including breakfast, is wrong even if the total “looks inclusive”.
- Block quote tools until stay nights, property location, accommodation net and booking/payment timestamps required for cut-off logic are present.
- Require a machine-readable levy outcome (amount + nights assessed + scheme version id) attached to the quote object.
- On scheme-rule miss: hard-stop inclusive confirm; open human revenue/ops case — do not let the model “estimate a tourist tax”.
Gate 3 — What AI may draft vs what it must never decide
Kaize POV (labelled): generative models are useful for **drafting** guest explanations of why a levy appears, multilingual FAQ copy and ops checklists when a scheme updates. They are the wrong component to **decide** the levy amount or to invent an inclusive price when levy state is incomplete. Wire tools so the model can propose “collect stay dates”, “flag channel-manager levy field missing”, or “queue human review for mixed-date stay” — and cannot call `publish_quote`, `confirm_rate` or `send_payment_link` while levy calculation state is red.
- Allow: explain a verified levy line using scheme-sourced wording after calculation succeeds.
- Allow: summarise which nights were assessed vs capped for a human agent.
- Deny: inventing a levy percentage; omitting levy from an “all-in” card; confirming packages that include Edinburgh nights without levy-inclusive total price.
Gate 4 — OTA / PMS / package seams
Most AI booking assistants do not own the PMS. OTAs, channel managers, corporate bookers and package builders create seams where the customer-facing “from” price drifts ahead of levy-inclusive truth. Before you ship an agent that quotes UK accommodation, write the seam contract: which system calculates the levy; whether the OTA display includes it; how scheme updates propagate; who remits to visitorlevy.scot (or the relevant platform) on the operator’s quarterly cycle.
If you cannot name that contract, the agent should stop at **“prepared for human rate confirmation”** — the same control pattern we argue for drip-pricing totals, package insolvency disclosures and border eligibility elsewhere in the journal.
Gate 5 — Evidence, monitoring and scheme-change drill
Keep documentary evidence that (1) destination scheme version and effective dates in production match published authority docs, (2) quote objects store levy amount and assessed nights, (3) invitation-to-purchase UX showed levy-inclusive totals, and (4) exemptions/cut-offs were applied from booking/payment timestamps — not from model memory. Run a tabletop: seven-night Edinburgh stay with five-night cap; stay crossing 24 July 2026; booking paid before 1 October 2025; OTA that strips levy lines; AI that adds levy to breakfast. Measure quote-error rate on levy fields — not chatbot sentiment.
FAQ
**Does this replace DMCC total-price controls?** No. DMCC / price-transparency rules still require a complete total at invitation to purchase. Visitor levy is a destination-specific component that must be **inside** that total when the scheme applies. Run both.
**Is every UK city charging a tourist tax now?** No. Scotland’s Visitor Levy (Scotland) Act 2024 enables local schemes; Edinburgh’s published scheme is the operational reference for stays from 24 July 2026. Do not let an agent invent a Manchester statutory levy or copy Edinburgh’s 5% elsewhere without a published scheme.
**Can disclosure that “AI generated this quote” cure a missing levy?** No. Labelling an AI quote does not create inclusive-price compliance or correct a wrong levy calculation.
What Kaize will (and will not) build here
Kaize builds AI product controls around how travel actually works — including hard stops when destination levy state is incomplete. We will help you map quote/confirm tools to levy calculators, night caps and inclusive-price UX. We will not invent local-authority schemes, claim a turnkey tax certification, or ship an agent that publishes “all-in” Edinburgh rates while levy calculation is unresolved. If that is the control conversation you need, start from what we build, how we think, or contact.