Direct answer: before 6 April 2027, UK travel companies should treat Package Travel Regulations 2026 as a booking-journey redesign, not a legal footnote. The Amendment Regulations abolish linked travel arrangements, pull former Type A combinations into the full package definition, and add a statutory 14-day supplier refund clock. If your website, app or desk can sell two travel services in one visit — even under separate payments — you may become an organiser for contracts entered on or after that date. Map every multi-service path, decide deliberately whether you want to be an organiser or redesign the path so you are not, then wire pre-contractual information, insolvency evidence and supplier refunds into the booking system of record.
That is the operator question Kaize is answering here. We are a UK AI product studio for travel and hospitality. We do not give legal advice, and this page is not a substitute for counsel, ATOL advice or insolvency cover. It is the systems view: the customer journey and the reservation file decide whether the new package definition bites — not a policy PDF stored in a shared drive.
The primary text is short and public. The Package Travel and Linked Travel Arrangements (Amendment) Regulations 2026 (SI 2026/455) amend the 2018 Regulations, come into force on 6 April 2027, and do not apply to package travel contracts or linked travel arrangements entered into before that date. The Explanatory Memorandum published with the instrument states the policy plainly: absorb linked travel arrangement Type A into the definition of a package, remove Type B entirely, and clarify organiser rights of refund and redress against suppliers.
What actually changes on 6 April 2027
Three design facts matter for anyone who ships a booking path.
- Former Type A LTAs become packages. Where travel services are provided under separate contracts with individual providers, a package is formed if a single trader facilitated, on one visit to or contact with their point of sale, the separate selection of and separate payment for each travel service. That is the Explanatory Note language, not a marketing paraphrase.
- The LTA category is revoked. Regulation 26 and the LTA information schedules fall away. There is no “lighter” LTA shelf left for the old Type A pattern.
- Suppliers face a statutory refund deadline. New regulation 29A requires a refund to the organiser within 14 days of cancellation or the date the travel service was due to be performed, whichever comes first. Regulation 29B puts the organiser’s right of redress on a clearer statutory footing.
Industry commentary from firms such as Fox Williams and Weightmans is useful for discovery, not as a rewrite target. Their working examples match the statute: airlines selling hotel or car hire in the same visit; booking platforms with separate tabs for flight, stay and experience; hotels selling accommodation plus a local experience in one session. Those are booking-path facts. They are not optional product features.
This page does not re-argue when an AI agent may change a booking under UK GDPR and ATOL — that question already lives on when travel AI changes a booking. The 2026 reforms are about which sales combinations become packages in the first place.
The systems problem is the booking path, not the brochure
Most operators will “prepare for PTR 2026” by asking counsel for a memo and asking marketing to update terms. Both are necessary. Neither redesigns the path.
A package under the expanded definition is created by facilitation in a single visit or contact — website session, app flow, phone call, retail desk. If your stack can cross-sell a second travel service before that visit ends, the law will look at what the traveller could do in that visit, not at whether your CMS labelled the second service “optional add-on”.
That is why this is a product and operations problem Kaize cares about. The same discipline we argue for when connecting booking systems and CRM applies here: name the system of record, refuse a second file, and do not let a CRM stage or a chatbot transcript pretend to be the package contract.
- Inventory, components sold, prices paid, passenger names on documents, and the package classification for that sale belong in the booking system.
- Pre-contractual information and the package travel contract content have to be generated from that record, not from a marketing CMS snapshot.
- Insolvency protection evidence and ATOL documentation (where ATOL applies) have to match what was sold. A CRM “won” stage is not that evidence.
- Supplier refund clocks under regulation 29A need a dated cancellation or non-performance event on the supplier side of the booking file — not an inbox thread that says “chased refund”.
If those four jobs live in four tools with no named winner, April 2027 will not invent a fifth tool that makes them honest. It will only raise the cost of being wrong.
Map every multi-service path before you rewrite terms
Write the paths in operator language. For each channel — website, app, call centre, trade desk, WhatsApp, AI-assisted sales — answer:
- Can the traveller select two or more travel services in one visit or contact?
- Can they pay separately for each while still inside that visit?
- Who is the trader facilitating that selection — you, a white-label partner, or a supplier widget embedded on your domain?
- If yes to the first two, do you intend to be the organiser for that combination from 6 April 2027, or will you redesign the path so the combination cannot complete in one visit?
Those answers are binary on purpose. “We’ll see how many people buy both” is not a control. Either the path can create a package under the expanded definition, or it cannot. Softening the CTA copy does not change facilitation.
Kennedys’ insurance-facing note on the reforms makes the same operational point in different clothes: reassessment of scope risk means mapping booking pathways, ancillary sales and digital journeys — because structure and sequencing engage the framework, not the product label alone. Use that as confirmation of the work, not as a claim Kaize has audited your estate.
If you will be an organiser: what the booking file must carry
Becoming an organiser is a commercial decision with systems consequences. From the first in-scope contract on or after 6 April 2027, the booking system has to support the jobs the 2018 Regulations already put on organisers for packages — now applied to combinations that used to sit in the LTA Type A bucket.
- Classification on the sale. Persist whether this booking is a package under the expanded definition, which components form it, and which trader is the organiser. Do not infer it later from a marketing tag.
- Pre-contractual information. The information duties travel with the package. The fields shown before the traveller is bound have to come from the live product and price record, not from a stale landing page.
- Package travel contract content. Dates, transport, accommodation, other services, total price, organiser identity and insolvency entity need a single source. Divergence between confirmation PDF and reservation row is the same failure mode we already describe for ATOL confirmations on the GDPR/ATOL controls page.
- Insolvency protection. If you are newly in scope, cover is not a website footer. It is an operating constraint on whether you may take the booking. ATOL, where it applies to flight-inclusive packages, remains a separate CAA regime — do not treat PTR wording as a substitute for ATOL compliance advice.
- Supplier refund and redress. Regulation 29A’s 14-day clock needs timestamps: when the service was cancelled or due, when the organiser claimed, when funds returned. That is a booking and payables event model, not a spreadsheet chase list.
Kaize’s public stance on build versus buy fits here: buy the booking and insolvency machinery you do not want to recreate; build the journey controls and event joins no off-the-shelf “PTR checkbox” will own for your specific stack.
If you will not be an organiser: redesign the path on purpose
The alternative is deliberate separation. If you do not want two travel services sold in one visit, the product has to enforce that — not the privacy policy.
- End the session after the first travel service confirmation before a second service can be selected, with a clear break the traveller understands.
- Move cross-sells to a later, separate contact that is not the same visit — recognising that Type B’s old 24-hour facilitation pattern is removed, not “made safer”.
- Remove embedded second-service checkout from the first-service confirmation page if that embed is what creates facilitation.
- Stop AI or rules engines from completing a second travel service inside the same session unless an identified human owner has accepted organiser obligations for that path. How agents should be controlled on booking systems is a separate article — how travel companies should control AI agents — and this page should not steal it. The PTR point is narrower: an unsupervised cross-sell that completes two services in one visit is a package-formation risk, not a clever conversion tactic.
Separation has a commercial cost. Pretending you have separated while the second checkout still sits on the confirmation page has a regulatory cost. Pick one.
What not to do
- Do not wait for “final guidance” as an excuse to leave multi-service checkout unchanged. The SI is made; commencement is dated; Government has said it will reissue guidance ahead of force — that does not move 6 April 2027.
- Do not treat updated website terms as proof the journey complies. Terms do not override facilitation on the path.
- Do not store package classification only in CRM or a compliance folder. The reservation that operations, refunds and dispute handling use has to know.
- Do not invent a “light package” product mode that is neither package nor separated sale. The LTA middle shelf is being removed.
- Do not assume AI-assisted bundling is outside scope because a model suggested the second service. The trader facilitating the point of sale remains the design focus under the amended definition.
- Do not claim Kaize — or any vendor — has already made your booking paths PTR-2026 compliant. Public work on kaize.co.uk/work describes operating joins for specific clients; it is not a certification of this reform.
Kaize’s recommended sequence
The wider map of where software and AI belong in travel operations sits on AI for travel: a practical guide. For PTR 2026 specifically, we recommend a boring sequence:
- Inventory every multi-service booking path by channel, including partner widgets and AI-assisted flows.
- For each path, decide: organiser from 6 April 2027, or deliberate separation. Write the owner’s name next to the decision.
- For organiser paths: add classification, pre-contractual and contract fields, insolvency gate, and supplier refund events to the booking system of record. Point CRM at that record; do not duplicate it.
- For separation paths: change the product so the second service cannot complete in the same visit. Then re-test with a fresh session, not with a walkthrough that skips the second checkout.
- Align supplier contracts with regulation 29A’s 14-day refund expectation before you need to use it on a failed departure.
- Keep irreversible package sales human-checked until the new classification and documents are boring in production — the same production discipline as what usually breaks when travel AI leaves the demo.
Start with the single highest-volume path that already sells two travel services in one visit. Fix that path’s classification and documents before you commission a platform rebuild. If you want a structured look at where that journey work should sit on the stack you already run, start with a Kaize Opportunity Review. That is a scoping conversation, not proof that PTR 2026 readiness has already been delivered on your estate.
This is not legal advice. Check current legislation, CAA ATOL requirements where relevant, insolvency arrangements and counsel against your actual booking paths.
Frequently asked questions
When do Package Travel Regulations 2026 take effect?
The Amendment Regulations (SI 2026/455) come into force on 6 April 2027. They do not apply to package travel contracts or linked travel arrangements entered into before that date.
What happens to linked travel arrangements?
The LTA category is removed. Former Type A combinations — separate contracts facilitated in a single visit or contact with separate selection and payment — are absorbed into the package definition. Type B is removed entirely.
Do hotels and airlines become package organisers?
They can, if their point of sale lets a traveller book two or more travel services in one visit. Whether that is true for a given business depends on the live journey, not on the sector label. Get legal and ATOL advice on your paths.
What is the new supplier refund rule?
Under new regulation 29A, suppliers must refund organisers within 14 days of cancellation or the date the travel service was due to be performed, whichever comes first. Organisers also get a clarified statutory right of redress under regulation 29B.
Is updating terms and conditions enough?
No. Classification follows facilitation on the booking path. Terms, supplier contracts, insolvency cover and the reservation file all have to align with what the traveller can actually complete in one visit.
Where should package classification live in the stack?
In the booking system of record, with identifiers shared to CRM. Do not keep a second package file in the CRM or a compliance spreadsheet that can drift from the confirmation the customer received.