I am writing this in our South London production space, looking at two stacked cases of the same SKU. One is going to a hospitality wholesaler tomorrow. The other is going to a DTC fulfilment partner. Same liquid, same bottle, two completely different demand curves over the next three months.

The cause is the 2026 FIFA World Cup. Access Hospitality forecasts UK pub spend will rise more than 150% compared with Euro 2024, and Talking Retail pencils in £2.9bn of retail spend over the tournament period. Startups.co.uk reporting on the same forecast adds the operational note that matters most: venues are already bracing for capacity strain.

For us, and for the small drinks brands we build planning tools for, that is a bottling-cycle problem, not a bartender problem. Which is the real story underneath the World Cup forecasts, and the one almost no one is writing about.


The format choice is a human-attention choice

There is a long-running argument that bottled ready-to-drink cocktails dilute the craft of bartending. From the maker side of this, I think the framing is wrong. The format is doing something different.

During a demand surge, a venue's binding constraint is not liquid. It is bartender attention. The cocktail that takes 90 seconds to build when the bar is quiet still takes 90 seconds during a World Cup match-day rush. Multiply that by three hundred orders and you get a queue, then a walked customer, then a manager getting nervous about table turnover.

A bottled RTD format collapses the build time. It does not replace the bartender's skill. It frees the bartender to do the work the surge actually demands: reading the room, recognising the regulars, calling the order accurately when the kitchen is also slammed, defusing the table that is about to become a problem. Those are the human jobs that do not get done if your bartender is making the same Negroni for the seventh time that hour.

I want to be careful here, though. This argument only works for the right drink at the right occasion. A bottled Old Fashioned format-shifted to a craft cocktail bar on a quiet Tuesday is a category error. The maker-vs-machine framing is not "automate everything". It is "automate the bits that absorb attention you need elsewhere".

The bottling-cycle problem

Here is what changes for the producer. You have one bottling line. You have a production lead-time measured in weeks because every batch ages before it gets filled. You have a trade demand curve that says "we want 4x normal volume for six weeks starting June 14", and a retail demand curve that says "we want 2x normal volume for ten weeks starting June 1, peaking in match-week windows".

The two curves do not align. Trade demand is concentrated and predictable in shape, tracking the match schedule. Retail demand is broader and more sensitive to weather, marketing, and what people are watching at home. The bottling-cycle problem is allocating finite production capacity across these two curves with a planning horizon that is longer than either channel's lead time.

This is the layer most small drinks businesses solve in their head, on the back of a napkin, the week before they need to commit to the next batch. It works until it does not. The year it does not work, you either stock out of the retail channel during a match week, or you over-commit to retail and disappoint your trade account just when their match-day order matters most.

What demand-spike planning actually looks like

The Drinks Business reporting on tournament-period stock-outs from prior years documents the pattern well. Smaller producers consistently under-forecast the retail surge in week 1 of the tournament and over-forecast the trade demand in week 4 once group-stage attrition kicks in. The aggregate is a mismatch between what was bottled and what got pulled through.

The tooling we build for this is not sophisticated forecasting. It is the connecting tissue between three things that already exist as data inside the business: the trade order book (what has been committed), the DTC weekly sales velocity (what is actually moving), and the bottling lead-time per SKU (how many weeks before a new batch can be in either channel). When those three are on one weekly snapshot, the conversation about what to bottle next stops being a guess.

ChannelDemand signalPlanning horizonCommon failure mode
Trade (on-trade hospitality)Tournament fixtures, venue PO cadence4 to 6 weeksOver-committing to fixed dates that get walked back if the home team is out by Week 3
Retail (DTC plus grocery)Weather, social, weekday and weekend split2 to 3 weeksUnder-forecasting the kitchen-table multiplier when people watch at home
Production (bottling line)Batch ageing, fill capacity6 to 10 weeksChoosing the wrong split between channels two months before either curve is observable

That third row is the one that bites hardest. Production lead-time is longer than either channel's planning horizon, so you are committing to a split before you know what the actual curves look like. Honestly, fair enough. Most small drinks businesses are operating without the data layer that would let them revise that split as new information lands.

Where Absolution Labs comes in

This is where Absolution Labs comes in. We bring the planning layer to small drinks brands that already know their channels and already understand their bottling rhythm. The tooling pulls the trade order book, the DTC weekly velocity, and the production calendar into one weekly snapshot, surfaces the deviation between planned and observed by Week 2 of any demand event, and lets the owner revise the next bottling decision with two weeks of real signal instead of pre-event guesses.

What the tooling does not do is replace the production judgement. The owner still decides what to bottle and when. The tooling makes the decision visible against the real curves, which is what the World Cup surge will reward and the brands without that layer will lose to.

The honest version of the maker-vs-machine question, from where I sit, is not whether automation belongs in a craft business. It is which parts of the work absorb attention that should be doing something else, and what you give back to the human side when you take those parts off the load. The bottled RTD format is a maker-vs-machine answer for the bar floor. The planning layer is the same answer for the bottling line behind it.

Frequently asked questions

Will the 2026 World Cup really lift UK pub spend by 150% versus Euro 2024?

Yes, that is the Access Hospitality forecast reported through industry trade press in spring 2026. The drivers are the larger 48-team format, North American time zones spreading matches across the UK working day, and pent-up summer hospitality demand. Talking Retail layers on a £2.9bn retail spend forecast over the same window.

Why do small drinks brands stock out during tournament weeks?

Production lead-time is longer than either trade or retail planning horizons. The split between channels gets committed weeks before the actual demand curves are observable, so brands either over-commit to trade (and lose retail) or under-forecast retail (and disappoint kitchen-table demand). The fix is a planning layer that surfaces deviation early enough to revise the next bottling decision.

Does a bottled RTD format compromise the craft of cocktail-making?

Only if you format-shift the wrong drink to the wrong context. For high-volume, time-pressured moments, match-day pub service, summer festival service, RTD format collapses build time so the bartender can do the human work the room actually needs. For a quiet bar where the cocktail build is the experience, the case is different.

What data does a small drinks brand need for demand-spike planning?

Three rolling weekly views are usually enough: the trade order book (committed POs), the DTC sales velocity (what is actually moving in retail), and the production calendar (when the next batch can hit either channel). On one snapshot, the owner can revise the next bottling decision before the deviation gets locked in.