Guides
Partner and coalition programmes
Partner and coalition programmes let several brands share one loyalty currency and one member account so customers can earn and redeem across unrelated merchants. Across 217 programmes profiled, 214 have known tier status and 112 run tiers, while this cluster holds 20 definitions and 14 decisions. Success hinges on coalition economics, partner governance, and a shared accrual ledger rather than any single brand's campaign calendar.
What this covers
Partner and coalition programmes are the loyalty arrangements in which two or more unrelated brands share one loyalty currency, one member account, one liability ledger, and one redemption catalogue. They include formal coalitions such as the 15 coalition programmes profiled, of which 2 run tiers, and partner networks embedded in airlines, retail, hotels, banking, and telecom. This guide excludes single-brand programmes that have one operator and do not depend on cross-partner settlement. It also excludes vendor software and agency services as standalone topics, though those choices appear when partner integration forces a build or buy decision. The cluster publishes 20 definitions and 14 decisions, with 57 curriculum modules supporting deeper study.
How the pieces fit together
The mechanism begins with a lead operator or coalition board that defines a common currency, earning rates, and redemption thresholds. Each partner signs an agreement covering its buy rate for points, its share of liability, and the transaction data it must share. A member joins through one partner but holds a single account valid across the whole network. Earning transactions post from each point of sale into a central ledger, which tracks partner-specific liability and net settlement rather than leaving each brand to manage its own points.
Redemption works only when each partner exposes inventory or rewards through a shared catalogue. The operator may run a central redemption store, or partners may redeem against each other at agreed rates. Settlement occurs on a fixed cadence, usually monthly, using the ledger to move funds between partners so the partner that issued the points does not bear the full cost of redemption at another partner. Tier status, where present, is calculated across coalition-wide qualifying activity, not within one brand. Across the 217 programmes profiled, 214 have known tier status and 112 run tiers. Among the 15 coalition programmes profiled, only 2 run tiers, which signals that most coalitions favour simple earn and burn over multi-level status.
The tier picture varies sharply by sector. Airlines run tiers in 61 of 61 profiled programmes, hotels in 18 of 18, and the single other programme runs tiers. Retail runs tiers in 25 of 46 with known status, restaurants in 2 of 22, telecom in 2 of 7, and banking in 1 of 14. Grocery shows 0 of 18 with known status running tiers, and fuel shows 0 of 12. These numbers show where multi-level status is already accepted and where a coalition is more likely to keep the programme flat while still allowing those sectors to act as earn partners.
Partner recruitment is the main growth loop. The coalition adds partners that serve different purchase occasions, such as grocery and fuel, even when those partners do not operate tiers. Data sharing and marketing permissions are governed by coalition rules, not by each brand alone. The operator manages partner onboarding, API access, and member support so the customer never has to reconcile balances across brands. Without that central operation, the single-account promise breaks and each partner retreats into its own loyalty silo.
Where programmes get this wrong
Many coalitions launch with one anchor brand and one weak partner, so the earning network is too thin to change behaviour. A customer earns at the anchor and can only redeem at the same anchor, turning the programme into a discount club rather than a coalition. Partner liability models also fail when every partner buys points at the same face value but redemption values differ, leaving one partner to subsidise redemptions at another. Without a fixed settlement cadence, the central ledger drifts and partners dispute balances each quarter.
Some programmes treat tier status as a marketing badge rather than a cross-partner qualification. They allow each partner to define its own elite threshold, so a member can be gold at one partner and base level at another inside the same coalition. Others set coalition-wide tiers but do not share qualifying activity quickly enough, causing customer service complaints. Data sharing is another recurring failure: partners withhold transaction detail to protect their customer base, which defeats the coalition's central modelling and personalisation.
Redemption breakage is often booked as operator profit without returning value to members, depressing repeat activity. Some coalitions recruit partners fastest in sectors with zero tier history, such as grocery and fuel, but fail to design an earn-only role, so those partners exit after one contract. The coalition may also operate as a separate customer-facing brand rather than an infrastructure layer, forcing members to manage two accounts and weakening the single-account promise that justified the partnership in the first place.
How to work through it
Start by defining the coalition's minimum viable network. Choose one anchor partner and two or three partners from different purchase occasions. Compare sector tier norms using the 217 profiled programmes: airlines 61 of 61 run tiers, while grocery 0 of 18 and fuel 0 of 12 do not. Use this to decide whether tiers belong in your first release.
Second, set the currency, earn rates, and liability model before recruiting partners. Decide whether the coalition will run tiers. Only 2 of 15 profiled coalitions do, so default to flat earn and burn unless cross-partner frequency clearly justifies status. Write down who owns breakage and how redemption liability transfers between partners.
Third, build the central ledger and settlement rules. Specify how often partners settle, what happens when a partner runs short of liability, and how redemption at one partner is funded by the issuing partner. Model the first six months with worst-case redemption rates so no partner is surprised by a large settlement bill.
Fourth, recruit and onboard partners with clear data sharing contracts. Evaluate platform fit against the 87 vendors profiled, of which 48 publish full or partial pricing. The vendor segments are 26 ecommerce-smb, 19 enterprise, 18 composable-api, 17 vertical-specialist, and 7 agency-services. Choose based on integration depth, not just logo count.
Fifth, pilot with a subset of partners before full launch. Run at least one settlement cycle and one cross-partner redemption test. Measure the share of members earning at more than one partner, because that is the core coalition behaviour.
Sixth, formalise governance. Write partner rules for changes to currency value, data access, tier qualification, and exit. Review the cluster's 14 argued decisions and 20 definitions to learn from prior disputes rather than repeating them.
Seventh, expand deliberately. Add a partner only when it brings a missing purchase occasion or a distinct redemption inventory. Do not add partners solely for logo count, because thin participation weakens the coalition's economics.
Finally, work through the 57 curriculum modules to deepen team understanding of coalition liability, partner economics, and governance. This path builds the shared vocabulary and decision discipline that most partner programmes lack.