Cousins Food & Beverage Management for UK Pubs

Last updated: 12 April 2026

Most pub operators think food and beverage management is just inventory tracking. It’s not. The real cost of poor F&B control isn’t the software subscription—it’s the 3-5% of revenue disappearing through waste, portion creep, and stock discrepancies that nobody notices until a Friday stock count goes sideways. When I was evaluating systems for Teal Farm Pub in Washington, Tyne & Wear, the deciding factor wasn’t the demo. It was whether the software could handle a Saturday night with kitchen tickets printing, bar tabs running, and three staff hitting the system simultaneously without losing a single transaction. Cousins is built for exactly this scenario. This guide covers what the software actually does, whether it solves real problems for wet-led and food-led pubs, integration reality, and the training overhead most operators don’t budget for.

What Is Cousins F&B Management?

Cousins is a dedicated food and beverage tracking system designed for hospitality venues. It sits on top of your existing EPOS till and creates a separate inventory and costing layer. Rather than relying on your till system to track stock, Cousins uses barcode scanning, recipe management, and real-time portion control to monitor food and drink at a granular level.

Think of it this way: your EPOS tells you how many pounds you made. Cousins tells you why—or why you didn’t make as much as expected. It tracks usage against theoretical consumption and flags where the gap is largest.

The core modules are:

• Inventory management: Barcode-driven stock receives, par levels, and stock takes. Works offline and syncs when connection returns.
• Recipe costing: Ingredient-level tracking so you know the exact cost of every dish and drink combination served.
• Waste tracking: Logged damage, spillage, and unsellable stock—critical for identifying theft vs. poor handling.
• Variance reporting: Compares theoretical usage (based on sales mix) to actual stock consumed. Highlights suspicious gaps.
• Purchasing integration: Links to supplier data to track invoice accuracy and spot price creep.

For a pub operator, the practical benefit is simple: you’ll know within 48 hours if your pour cost is drifting, if portion sizes are inconsistent, or if stock is disappearing faster than sales justify. Without this layer, most pubs don’t spot these problems until month-end P&L review—by which time the damage is done.

How Cousins Works with Your EPOS System

Here’s where most implementations trip up: Cousins doesn’t replace your EPOS. It works alongside it. And that integration has to be configured correctly.

At Teal Farm Pub, managing 17 staff across front of house and kitchen simultaneously, we run sales through our EPOS till. Cousins sits on a separate terminal (usually in the back office or kitchen) and pulls transaction data from the EPOS via API connection. The kitchen display screens print tickets, and Cousins tracks which items were prepared against theoretical consumption.

The integration path typically looks like this:

1. EPOS records sale (burger, pint of lager, vodka soda)
2. Transaction data syncs to Cousins via secure API
3. Cousins compares actual usage to recipe ingredient requirements
4. Variance report flags discrepancies
5. You investigate and adjust portion control or training

The critical piece most operators miss: you need accurate recipe data entered into Cousins before any of this works. If your burger recipe is set to 180g of mince but your kitchen is actually using 200g, Cousins will track that 200g as variance—which is correct, but it won’t fix itself. You have to adjust the recipe or train the kitchen.

Your pub IT solutions guide covers EPOS integration strategy in detail, but for Cousins specifically, ensure your provider handles:

• Real-time or near-real-time transaction feed (not batch uploads that run overnight)
• API stability during peak trading—it can’t crash when you’re doing £2,000+ per hour in sales
• Fallback mode if the internet drops (does Cousins continue working locally?)
• Data encryption between EPOS and Cousins systems

Real-World Setup & Integration Reality

Setup typically takes 4-6 weeks from contract to full operational system. Here’s the timeline most operators don’t budget for:

Week 1-2: Configuration

Your Cousins partner (usually a reseller or the vendor direct) configures the API bridge to your EPOS. They set up your venue structure (bar, kitchen, cellar), cost centres, and user accounts. Sounds straightforward. In reality, this is where 70% of integration issues emerge. Your EPOS configuration might have product codes set up in a way Cousins doesn’t expect. Menu items might be grouped differently. Stock transfers between areas might not map cleanly.

Week 2-4: Recipe & Inventory Build

You (or a Cousins consultant at your cost) enter every recipe, every ingredient, every portion size. You set par levels for every product. You conduct an opening inventory count (physically count every bottle, every portion, every ingredient). This is the unglamorous bit—it takes 2-3 days for even a small 80-120 cover food-led pub. For a large venue doing substantial volume, it’s a full week.

If your opening inventory is wrong by 10%, everything downstream will be off. I’ve seen pubs spend two weeks chasing “variance” that was actually just an inaccurate opening count.

Week 3-5: Testing & Training

You run Cousins in parallel with your existing system. Don’t cut over immediately. Run both for 2+ weeks. Compare variance reports to your actual P&L and cash position. If Cousins says you should be £50 down on lager but your till says you’re up £200, something’s misconfigured. Find it now, not after you’ve made business decisions based on wrong data.

Training happens here too—kitchen staff learn to confirm prep, front of house logs waste, someone does daily stock movements. Most operators severely underestimate this phase. Staff will resist change. They’ll forget to scan barcodes. They’ll enter wrong quantities. You’ll need to be hands-on for 3 weeks minimum.

Week 5-6: Go-Live & Monitoring

Cut over to Cousins as your primary system. Run daily variance reports. Investigate anything outside normal tolerance (typically 2-3% variance is acceptable; anything above 5% needs explanation). Adjust recipes or training based on what you find.

The real problem most pubs face is that this entire process requires your active involvement, not just during setup but for the first 6 months of operation. If you treat it like a software install—order it, let someone set it up, then ignore it—you’ll get poor data quality and zero ROI. You’ll see the subscription cost but not the benefit.

Is It Worth It for Wet-Led vs Food-Led Pubs?

This is the honest question most vendors won’t answer. Cousins ROI depends entirely on your business model.

Food-Led Pubs (40%+ revenue from food)

Cousins makes strong sense here. Your food cost percentage directly impacts profit. If food is 30-35% of revenue and you’re losing even 2% to waste, portion creep, or poor stock management, that’s thousands per month. A typical food-led pub doing £5,000/week in food sales with a 2% variance problem is leaving £400+ per week on the table. Cousins costs £150-300/month. Recovering half that variance pays for itself in month one.

Additionally, FIFO management in pub kitchens becomes automatic—Cousins tracks which stock rotates when, flagging old items before they spoil. In a busy kitchen, this alone prevents significant waste.

Wet-Led Pubs (70%+ revenue from drink, minimal food)

This is where honest assessment matters. If you’re doing 90% wet sales with a small carvery or limited menu, Cousins delivers less ROI. Why? Because your pour cost variance is typically lower than food cost variance. A well-trained bar staff and basic optic or measure control keeps pour cost tight. A 1% variance on £10,000 weekly drink revenue is £100—less than Cousins costs.

However, if you’re doing wet sales with premium spirits, craft beers, or complex mixed drinks, variance compounds quickly. A high-value pour cost issue hides better in drink sales than in food.

For wet-led pubs, I’d honestly recommend investing in cellar management integration first—tracking kegs, cask rotation, wastage on draught lines, and CO2 stock. That often delivers better ROI than tracking individual drinks at the pour.

Mixed Model (50/50 wet and food)

Cousins works well here, particularly if kitchen output is inconsistent or staff turnover is high. The variance data gives you concrete evidence of where to focus training and process improvement.

Training & Staff Adoption Timeline

Here’s what nobody tells you upfront: Cousins is only as good as your staff’s discipline in using it. And staff will resist.

In the first two weeks after go-live, expect accuracy to be 60-70%. Staff will forget to scan barcodes. They’ll enter transactions hours after they occur. Kitchen will skip the waste log. Front of house won’t confirm portion sizes. This is normal—not a sign the software is broken.

By week 3-4, assuming you’re actively supervising and correcting, accuracy climbs to 80-85%. By week 6-8, you should hit 90%+. But this requires your daily involvement in early weeks, spot-checking entries and retraining staff on weak areas.

For pub onboarding training, the Cousins module typically runs 2-3 hours per person. However, real adoption takes ongoing reinforcement. Most hospitality staff respond better to peer-led training than formal instruction—get your strongest kitchen or bar person trained first, then have them teach others. It sticks better.

One practical detail: make entering data part of the shift handover process, not an afterthought. Assign someone (usually a senior team member) 15 minutes at the end of their shift to review and confirm transactions in Cousins. This becomes routine. If you don’t build it into the rota, it won’t happen consistently.

Common Objections & Honest Answers

“We’ve got F&B control working fine already without a system like this”

Fair comment. If you’re doing month-end stock counts, variance is within 2%, and food cost is stable, you might not need Cousins. But—and this is critical—you have no visibility into where the variance occurs. Is it theft? Portion creep? Supplier invoice errors? Waste in prep? Without daily variance tracking, you’re flying blind. You might feel in control only because you’re not measuring carefully enough.

I’d challenge this with a simple test: do a three-week manual variance calculation. Track every food sale, estimate portions, compare to actual stock movement. Most operators find a 3-5% gap they didn’t know existed. That’s where Cousins delivers value—visibility, not just cost savings.

“It’s too expensive for a small pub”

Cousins typically costs £150-300/month depending on transaction volume and features. For a venue doing £15,000+ weekly revenue, that’s 1% or less of turnover. The question isn’t whether you can afford it—it’s whether you’ll use it actively. If you’re just going to look at reports quarterly, it won’t pay for itself. If you’re using it to make weekly adjustments to portion sizes, purchasing, or training, it will.

A better question: what’s your current pour cost and food cost? If either is trending upward without obvious reason, Cousins likely pays for itself within 2-3 months. If both are stable and tight, it might not be worth the overhead.

“Too complicated for staff to learn quickly”

The interface is actually less complex than most modern EPOS systems. Barcode scanning, portion logging, and waste entry are simple tasks. The complication isn’t the software—it’s changing habit. Staff have been trained one way. Cousins asks them to do things differently. That friction is real, but it’s behavioural, not technical.

The best implementation strategy is to phase it in: start with one high-variance area (say, spirit pours or burger portions). Get that working smoothly over 2-3 weeks. Then add another area. Most operators try to go live with everything at once and get overwhelmed.

“What happens when the internet goes down?”

Critical question, and it depends on your setup. If Cousins works purely cloud-based without local fallback, you’ll lose data entry during an outage. Most modern implementations include an offline mode—you can enter transactions locally, and they sync when connection returns. Confirm this with your provider before signing. For a pub, even 2 hours of network outage during an evening service is unacceptable.

“I don’t want to be locked into a long contract”

Reasonable. Most Cousins implementations are offered on 12-month or 24-month terms. Some resellers offer month-to-month but at a higher per-month rate. Before committing, negotiate a 90-day trial or pilot at one venue (if you run multiple sites). Use that period to prove ROI. If variance data shows £300+/month savings, you’ll happily extend. If it shows nothing, you’ve only lost 3 months fees.

“Will it integrate with my existing accounting software?”

Depends. Cousins connects to most EPOS systems via API. Integration with accounting software (Xero, QuickBooks, FreshBooks) is less standardised. Most implementations export variance data and cost reports manually into your accounting system, or via CSV integration if your accountant’s software supports it. Ask your reseller specifically: “Can variance reports feed directly into our P&L?” If the answer is “it usually requires manual entry,” budget extra time or consider a data integration service like Zapier.

“Is it worth it for a wet-led only pub with no food?”

Honestly? No, not usually. The variance you’re likely to find in a wet-only operation is 1-2% maximum, which doesn’t justify the software cost and overhead. Your money is better spent on cellar management (keg rotation, wastage tracking) or improving staff training on pouring consistency. If you sell a lot of premium spirits with complex mixing, that calculation changes—but a typical wet-led local? Invest in better stock control practices first. Cousins for wet-led makes sense once you’re above £25,000+ weekly revenue and variance is a clear problem.

The Real Cost of Cousins Is Training Time, Not the Subscription

Most operators focus on the monthly fee and miss the actual cost: the 4-6 weeks of your time and staff time to implement properly. If you value your time at £20/hour and you spend 60 hours on setup and initial supervision, that’s £1,200 in hidden cost. Add staff training time (2-3 hours per person × 5-8 staff), and you’re looking at another £300-500. The software subscription is the cheap part.

This is worth doing if the ROI case is solid. For a food-led pub with 3-5% variance problems, Cousins pays for itself in 2-3 months. For a tight operation with minor variance, you’re paying for peace of mind and data you might not act on.

Understanding your actual cost position is essential before committing. Use our pub profit margin calculator to establish your baseline costs, then assess whether Cousins variance data would meaningfully change how you operate. That’s the real decision.

For more information, visit pub profit margin calculator.

For more information, visit pub drink pricing calculator.

For more information, visit pub staffing cost calculator.