One promo, thirty legal regimes

No. A single promotion cannot legally run unchanged across alcohol markets, because trade-inducement and price-promotion rules are set per jurisdiction, not per brand. A loyalty reward that is routine in one country is a criminal offence in the next: Ireland bans loyalty points on alcohol outright, Scotland floors the price by law, and US federal rules treat many retailer incentives as illegal inducement. An engine that assumes one rulebook forces a fork at every border.

Why can't one promotion run everywhere?

Because the thing you are configuring — an incentive that nudges a retailer or shopper toward your product — is exactly what alcohol regulators write rules about, and they write them locally. A generic promo engine treats earn 100 points per case as neutral arithmetic. The law treats it as an inducement to trade, and the definition of a permitted inducement, a permitted discount, and a permitted disclosure changes at every border.

Three live examples set the range. In Ireland, the Public Health (Alcohol) Act 2018 bars loyalty-card points from being awarded on, or redeemed against, alcohol at all — a rule in force since 11 January 2021. In Scotland, minimum unit pricing sets a statutory price floor — 65 pence per unit as of September 2024, up from 50 pence — so any discount that would push the shelf price below the floor is unlawful, however your promo maths resolves. In the United States, the federal tied-house rules in 27 CFR Part 6, in force in some form since the Federal Alcohol Administration Act of 1935, make it unlawful for a producer to furnish a retailer money, services or other things of value to induce purchases — a fair description of a good deal of trade-promo mechanics.

What actually differs between markets?

Everything a promo engine stores as a parameter is, somewhere, a legal constraint: who may be rewarded, what the reward can be, how large it can get, how long it can last, and what must be disclosed. The same record that reads reward = 5% rebate, duration = 7 days, mechanic = points is compliant in one market, a licensing breach in the second, and a criminal matter in the third.

Look at what that does to the data model. duration is not a free integer — in Ireland a price promotion lasting three days or less is prohibited, so the field needs a per-market minimum, not only a maximum. reward type is not a free enum — points are fine in most markets and illegal in one. A suite that ships with a single global schema has already made the wrong assumption before you write a line of configuration.

Why does the packaged loyalty suite make this worse?

Packaged loyalty and trade-promo suites are built around a global earning model: define tiers, points, rebates and gamification once, then roll them out everywhere. That is the pitch, and it is also the trap. The moment a market's legal constraint doesn't fit the global schema, the constraint becomes custom code — a per-country fork of the rules engine, living outside the product's upgrade path.

Even the largest operators signal this carefully. The world's largest brewer describes its loyalty and gamification features as running, in its own words,

in full compliance with data protection and local legislation.

That clause is doing real work. Local legislation is the quiet admission that the global mechanic has to be bent, market by market, to stay legal — and someone has to build and maintain each bend. In a packaged suite bought off the shelf, that someone is you, in a fork you now own forever.

What does forking per market actually cost?

The expensive fork is never the first one; it is the thirtieth, and every upgrade after it. Each per-country rules fork is a place where the vendor's next release can silently break your compliance, where a regulator's amendment arrives as a code change rather than a config change, and where the one engineer who understood the Irish loyalty carve-out has since moved on. This is the same mechanism that makes every OpCo rollout restart from zero: not genuinely new requirements, but the same requirements re-encoded in a slightly different branch each time.

There is a financial tail as well. Promotions are already the least-governed line in the P&L — a large share lose money outright even when they are perfectly legal — and a compliance fork adds a second failure mode on top: a promotion that is both unprofitable and unlawful. And because loyalty points sit on the balance sheet as a liability, a market where points must be voided or blocked is not a harmless config edge case; it is a number your finance team has to carry and explain.

The way out is to stop treating jurisdictions as forks and start treating them as configuration: keep the promo definition global, but move the rules of what may be rewarded, capped, timed and disclosed into per-market legal-constraint templates that bind onto one shared engine. A regulator's change then becomes a template edit rather than a release, and a new market inherits a compliant default instead of a blank branch. That is a deliberate platform architecture decision, and it has to be made before the second market goes live, not after the tenth.

Alcohol regulators are moving in one direction — more markets pricing by the unit, more limits on what a purchase can earn, more disclosure demanded at the point of promotion — and each move lands first as legal text, not as a product feature. The teams that will absorb the next decade of these changes cheaply are the ones whose promo logic already reads its limits from a per-market template instead of a per-market branch. The rulebooks will keep diverging; the only open question is whether your engine was built to expect it.