Projects & Real EstatePractice area
International Airline Alliance, Codeshare & Interline Agreement Architecture
**Hero** International airline cooperation needs a contract architecture that connects commercial reach with operational accountability, passenger transparency and a route-specific regulatory assessment. For airlines, airline groups and aviation investors, the right structure begins with the operating model, applicable traffic rights, market constraints and the customer journey—not a one-size-fits-all template.
The starting point
Make the next decision with the commercial context in view.
A proposed airline relationship can sit on a spectrum. An **interline arrangement** may support the sale of a journey involving more than one carrier and coordinate elements such as ticketing, baggage or settlement. A **codeshare** commonly involves one carrier placing its designator on a flight operated by another carrier. The U.S. Department of Transportation describes the latter as a marketing arrangement in which an airline places its designator code on another airline’s flight and sells tickets for it.[[2]](#source-log) A broader alliance, joint venture or other commercial cooperation arrangement may introduce more extensive coordination. It may therefore require a different assessment of governance, market access, competition, regulatory authorisations, operational interfaces and customer communications. Labels alone do not decide the outcome: the detailed design, markets and jurisdictions matter.
How we help
The work around the decision.
01
If the commercial model is still being selected: map the cooperation architecture
Compare an interline, codeshare, alliance or more integrated commercial structure against the stated business case. Define the parties, routes, products, sales channels, phases and decision rights so that the commercial ambition is capable of being expressed in a coherent agreement structure.
02
If routes cross borders or involve traffic rights: build a permissions and approvals map
Identify the jurisdictions, air service agreement context, carrier designations, licences, notifications or approvals that may be relevant to the proposed services. The analysis should distinguish between a contractual plan and the permissions required for a service to be marketed or operated.
03
If partners will share economics or coordinate decisions: set commercial terms and governance boundaries
Develop provisions for scope, inventory or capacity interfaces, pricing and revenue arrangements where appropriate, payment and settlement mechanics, performance information, audit rights, governance forums, escalation and change control. The appropriate degree of coordination and information sharing requires careful competition assessment in the relevant markets.
04
If one carrier sells travel operated by another: allocate operational and safety interfaces
Clarify the operating-carrier and marketing-carrier roles, reporting pathways, service standards, operational handovers, insurance interfaces, audit and assurance concepts, and response to changes in authorisations or operating capability. The U.S. DOT’s code-share overview illustrates that, for services within its remit, safety review is considered before code-shared operations are implemented.[[2]](#source-log)
05
If customers will make one booking across carriers: design the passenger-facing journey
Review how the operator is identified in schedules, search results, advertisements, booking confirmations and travel documents; then align the agreement with responsibilities for check-in, baggage, schedule changes, disruption communications, refunds and complaints. In the United States, for example, Part 257 requires specified disclosures of the operating carrier for covered code-share services; other regimes may take a different approach.[[3]](#source-log)
06
If data, distribution or technology systems are connected: document the control framework
Assess necessary interfaces among reservation, departure-control, distribution, loyalty, settlement and customer-service systems. Define permitted data flows, security and incident-response expectations, record retention, system testing, continuity and responsibility for change management, subject to the applicable data and technology rules.
07
If the arrangement may affect competition or market access: plan the assessment and engagement path
Establish an evidence base for route overlaps, competitive constraints, customer benefits and the intended level of coordination. Consider whether merger control, competition, aviation, consumer or other reviews may be relevant before implementation, recognising that authorities apply their own tests and timetables.
08
If the relationship will evolve over time: prepare for launch, monitoring and exit
Sequence conditions precedent, approvals, implementation milestones, launch criteria, periodic review, suspension rights, termination, passenger protection during wind-down, data return or deletion, and transition support. A disciplined lifecycle design can help parties manage a change in network strategy without assuming that every consequence is contractually transferable.
Context for the decision
The facts and records that shape the route.
What is the practical difference between interline, codeshare and alliance arrangements?
The terms describe different forms and depths of cooperation, and their commercial use can overlap. At a high level, interline arrangements often facilitate multi-carrier journeys; codeshares involve a carrier’s code on another carrier’s operated flight; and alliances or joint ventures may involve broader collaboration. The agreement, its operating model and the applicable rules—not the label alone—determine the appropriate legal analysis.
Does a codeshare agreement itself create the right to operate an international route?
Generally, no. A commercial agreement is distinct from the traffic rights, operating authorities, designations and other permissions that may be necessary for an international service. The relevant position can vary with the route, the carriers and the applicable air service arrangements. The European Commission’s explanation of bilateral air service agreements is one useful reminder of that distinction.[[4]](#source-log)
When should competition or regulatory questions be considered?
At the design stage, before partners commit to customer-facing dates, coordinate commercially sensitive activity or invest heavily in systems. The degree of overlap, market concentration, scope of coordination, routes concerned and local law can all affect the analysis. No general page can determine whether a notification, authorisation or clearance is required in a particular case.
Questions, not prescriptions
What may matter.
What is the practical difference between interline, codeshare and alliance arrangements?
The terms describe different forms and depths of cooperation, and their commercial use can overlap. At a high level, interline arrangements often facilitate multi-carrier journeys; codeshares involve a carrier’s code on another carrier’s operated flight; and alliances or joint ventures may involve broader collaboration. The agreement, its operating model and the applicable rules—not the label alone—determine the appropriate legal analysis.
Does a codeshare agreement itself create the right to operate an international route?
Generally, no. A commercial agreement is distinct from the traffic rights, operating authorities, designations and other permissions that may be necessary for an international service. The relevant position can vary with the route, the carriers and the applicable air service arrangements. The European Commission’s explanation of bilateral air service agreements is one useful reminder of that distinction.[[4]](#source-log)
When should competition or regulatory questions be considered?
At the design stage, before partners commit to customer-facing dates, coordinate commercially sensitive activity or invest heavily in systems. The degree of overlap, market concentration, scope of coordination, routes concerned and local law can all affect the analysis. No general page can determine whether a notification, authorisation or clearance is required in a particular case.
What should passenger communications make clear?
They should accurately identify the operating carrier and explain practical matters that affect the journey, such as check-in, baggage, service changes, disruption support and how customers receive assistance. Mandatory wording, timing and placement differ by jurisdiction and sales channel. In the United States, the federal rules require prominent operator identification in covered schedule displays and written confirmation at purchase.[[3]](#source-log)
How can parties manage change or disruption across a multi-carrier itinerary?
The agreement can allocate coordination procedures and customer-service handoffs, but it should be tested against mandatory passenger, consumer, safety and operational rules that may apply independently of the contract. Clear escalation routes, information exchange, recordkeeping and transition arrangements are often as important as the initial commercial allocation.
Begin with context
Put the decision into focus.
For an initial conversation, share only high-level, non-confidential context about the relevant business decision, markets, parties, documents and timetable. Do not send confidential, privileged, personal or time-sensitive material through a website enquiry.Legal information only. This page provides general legal information, not legal advice. It does not address the facts of any individual matter and does not create a lawyer-client relationship. The appropriate route, framework, timing and outcome depend on the applicable law, documents and circumstances.