Direct answer: under regulation 10 of the Package Travel and Linked Travel Arrangements Regulations 2018, the prices in a package travel contract **must not be increased** once the contract is concluded unless the contract expressly allows it, limits increases to **direct consequences** of changes in passenger-carriage fuel/power costs, third-party taxes/fees (including tourist, landing, embarkation/disembarkation fees), or relevant exchange rates, also gives the traveller a corresponding **price-reduction** right when those costs fall, and states **how revisions are calculated**. Even then, regulation 10(3) allows a price increase only if the organiser notifies the traveller **clearly and comprehensibly**, with a **justification and a calculation**, on a **durable medium**, **at the latest 20 days before the start of the package**. Where the increase exceeds **8%** of the total package price, regulation 10(4) pulls in regulation 11(4)–(11): without undue delay the organiser must offer accept / terminate-without-fee / substitute-package choices on a durable medium, with a reasonable response window, a second notice if the traveller is silent, and refund timing if the contract ends. An AI pricing, “fare update”, or WhatsApp billing agent that posts a higher balance **without** those contract rights, calculation objects, durable-medium notice, and 8% choice path is not clever revenue recovery. It is a PTR price-alteration control failure.
That is the operator question Kaize is answering here. We are a UK AI product studio for travel and hospitality. This is **not legal advice** and not a substitute for the live SI text, DBT/BEIS business guidance, your package conditions, insolvency cover, ATOL advice where flights sit in the basket, or counsel. It is a **control-stack** article: what must already be true in the booking and messaging state machine before AI is allowed to notify or collect a package price increase. It sits beside — and does not replace — our PTR Reg 12–14 termination and refund gates (**before AI cancels**), our PTR Reg 15 alternative-arrangements gate (**before AI rebooks mid-trip**), our PTR insolvency-cover naming gate (**before sale completion**), and our 2026 booking-journey redesign note (**before 6 April 2027**). This article is narrower: **Regulations 10–11 price-revision capability must be encoded before AI may raise a booked package fare**.
Why pricing agents keep colliding with Regulations 10–11
Most organisers already have a human yield or ops desk that knows “price variation” clauses are narrow. The 2026 failure mode is a **generative fare or collections agent** that can read a supplier surcharge, invent a traveller-facing delta, email a new balance, and mark the booking overdue — **without** proving that the concluded contract allows an increase, that the delta maps only to the three permitted cost classes, that a calculation and justification exist as structured objects on a durable medium, that notice is ≥20 days before start, and that a rise above 8% opens the regulation 11 choice path rather than a silent balance chase. Official business guidance restates the same: reserved rights, corresponding reductions, durable-medium notice with justification no less than 20 days before start, and >8% treated as a significant change that triggers the regulation 11 options.
Three statutory facts teams must encode before any auto-fare-hike or “balance due” tool is armed on concluded packages:
- **No increase by default** — regulation 10(2): after conclusion, prices must not rise unless the contract expressly allows it, limits the causes to fuel/power for carriage, third-party taxes/fees, or relevant FX, gives a matching reduction right, and states the calculation method.
- **Durable-medium justification + calculation + 20-day clock** — regulation 10(3): every permitted increase (any size) needs clear, comprehensible notice with justification and calculation on a durable medium, at latest 20 days before the package starts.
- **Above 8% is a regulation 11 event** — regulation 10(4) + 11(4)–(11): the traveller must be able to accept, terminate without a termination fee, or take a substitute package; silence triggers a second notice; termination without substitute brings refunds within 14 days (and regulation 16(2)–(10) where paragraph (8) applies).
Map the duty before the model speaks
Regulation 10 is not a prompt tip to “explain the surcharge politely”. Your pricing agent needs structured fields for: package vs non-package classification; whether the concluded contract contains an express price-variation clause; which of the three permitted cost drivers fired; the numeric calculation (inputs, formula, admin expenses if any for reductions); durable-medium delivery channel; days until package start; whether the proposed increase exceeds 8% of the total package price; and the regulation 11 choice objects (accept / terminate / substitute + deadlines) when it does. Those fields must be **sourced from contract and finance systems**, not invented in chat. A model that “summarises” a supplier invoice into a traveller balance without those objects is inventing a price revision the statute does not allow.
The six gates before AI may notify or apply a package fare increase
Gate 1 — Confirm a concluded package contract and an express variation right
Before any generative turn offers “your holiday price has increased”, classify the booking as a package travel contract under the 2018 Regulations and load the signed/confirmed terms. Gate 1 fails if the assistant treats every hotel+flight basket and every component sale the same, or if it assumes a price-variation clause exists because “we always surcharge fuel”.
Gate 2 — Map the delta only to fuel/power, third-party taxes/fees, or relevant FX
Regulation 10(2)(b) is a closed list for increases. Build a cost-driver object from finance and supplier feeds. Gate 2 fails if the model can still raise the fare for yield recovery, “market adjustment”, supplier margin, optional extras the traveller did not buy, or a vague “operational costs” bucket.
Gate 3 — Calculation and justification exist as durable-medium payloads before notify
Regulation 10(3) requires clear, comprehensible notice with justification and calculation on a durable medium. Generate those artefacts (PDF, email body archived as durable medium, or equivalent) **before** the messaging tool arms. Gate 3 fails if the agent can WhatsApp “pay £180 more” while the calculation is still a spreadsheet note in ops, or if justification is a one-line model paraphrase with no numbers.
Gate 4 — Enforce the 20-day-before-start notice ceiling
Irrespective of size, the increase may only be made if notice is given at latest 20 days before the package starts. Gate 4 fails if a model can still push a fare hike inside that window, or if “start of the package” is guessed from marketing copy instead of the confirmed itinerary start.
Gate 5 — If the rise exceeds 8%, open the regulation 11 choice path — do not only chase payment
Regulation 10(4) is explicit: >8% engages regulation 11(4)–(11). The traveller must receive, without undue delay, the proposed change and price impact, a reasonable decision period, consequences of silence, and any substitute package offered. They may accept or terminate without a termination fee; substitute and price-reduction rules apply; a second notice is required before the organiser may terminate for non-response; refunds follow the 14-day clock where the contract ends without a substitute. Gate 5 fails if the agent treats every hike as a collections task and never exposes accept/terminate/substitute controls.
Gate 6 — Symmetric reduction rights and adjacent PTR/ATOL/CCR gates stay armed
Where the contract gives a reduction right when the same costs fall, regulation 10(5) allows limited admin expense deduction with proof on request — encode the mirror path so AI is not a one-way fare ratchet. Price revision does not replace Reg 12–14 termination/refund controls, Reg 15 alternative arrangements before AI rebooks, insolvency-cover naming before sale completion, CCR 2013 pre-contract information on distance sales, ATOL Certificate controls before first payment, or the prepare-vs-human-confirm rule for high-impact money movements. Gate 6 fails if teams treat a fuel table as the only checklist.
What this is not
- Not a rewrite of PTR Reg 12–14 termination and refund — that article is **cancellation/termination money movement**; this one is **post-conclusion price alteration** under Regs 10–11.
- Not PTR Reg 15 alternative arrangements before AI rebooks — mid-trip performance alternatives; complementary when a significant change path is taken, not the fare-hike calculation gate.
- Not PTR insolvency cover naming — pre-sale protection naming; still required at sale time, separate from later price revision.
- Not the 2026 PTR amendment journey redesign — 6 April 2027 LTA/package boundary changes; Regs 10–11 price rules remain the live control for concluded packages today.
- Not DMCC drip-pricing quote controls — pre-purchase total-price presentation; this article is post-booking statutory price revision.
Operator checklist before go-live
- Booking classifier marks concluded package travel contracts before any AI fare-increase tool is offered.
- Contract store exposes express price-variation flag, permitted cost drivers, calculation method, and reduction-right flag as structured fields; nulls block notify.
- Finance feed maps proposed deltas only to fuel/power for carriage, third-party taxes/fees, or relevant FX; other causes hard-fail.
- Justification + calculation artefacts are generated and archived as durable medium before messaging APIs arm.
- Package-start date enforces the 20-day notice ceiling; inside the window, increase tools stay disabled.
- Percentage check vs total package price: ≤8% stays on Reg 10 notify path; >8% requires Reg 11 accept/terminate/substitute UI and second-notice logic.
- Collections/CRM agents cannot create a “balance due” from a blocked or incomplete price-revision object.
- Human confirm remains mandatory when cost-driver mapping, 8% banding, or contract variation rights are ambiguous; model may prepare, not silently raise the fare.
- Change control: no new AI pricing or guest-billing channel without repeating Gates 1–6; adjacent PTR/ATOL/CCR gates stay armed.
How Kaize frames the build
Kaize designs travel and hospitality AI so **control planes sit in front of models**. PTR Regulations 10–11 price-revision readiness is one of those gates: the notify-and-collect path does not call “send fare increase” until contract rights, permitted cost drivers, calculation/justification artefacts, 20-day timing, and — where needed — regulation 11 choice objects are live on the session — just as we refuse package sale completion until insolvency cover is named, refuse AI cancellation until Reg 12–14 refund timing is encoded, or refuse first payment on ATOL product until certificate controls pass. If you want that control stack designed around your package conditions, CRS and finance stack, discuss a project or see what we build and how travel companies should control AI agents.
Sources for operators to read next: PTR 2018 regulation 10 — alteration of the price; regulation 11 — alteration of other package travel contract terms; DBT/BEIS Package Travel Regulations 2018 guidance for businesses (PDF); Citizens Advice — cancelling a package holiday (price increase section); PTR 2018 contents. Always verify against the consolidated text, your package conditions and your counsel — this page is an operator control framing, not advice.