There's a lot of noise right now about restaurant tech. POS integrations, invoice automation platforms, all-in-one tools that promise to connect everything. Every hospitality software company wants to sit between your till and your accounting software.

Most of it misses the point.

The point isn't connecting systems. The point is knowing which dishes make you money and which ones don't. And that requires something most independent cafes still don't have: accurate, current recipe costs.

The POS Data Illusion

Your POS is excellent at one thing: telling you what sold.

You sold 47 flat whites, 23 avocado toasts, 15 bacon rolls, and 8 slices of banana bread yesterday. You took £1,240. The POS can tell you that Tuesday is your best day for food, that flat whites outsell lattes 3:1, and that banana bread sells better when it's by the till.

This is useful data. But it answers the wrong question.

The question isn't "what sold the most?" The question is "what made the most profit?" Those are not the same question, and the difference between them is where most cafes leak money.

Your best-selling dish might be your least profitable. Your slowest seller might be your highest margin item. Without recipe costs, you genuinely can't tell. You're making decisions based on revenue, not profit, and that's like driving using only your speedometer while ignoring the fuel gauge.

What Recipe Costing Actually Shows You

When you know the cost of every ingredient in every dish, the picture changes completely.

That avocado toast you sell 23 of every day? It costs £2.10 to make and you sell it for £7.50. That's a 72% GP. Good.

That bacon roll you sell 15 of? The streaky bacon went up 12% last month. It now costs £1.85 to make and you sell it for £4.50. That's a 59% GP. You're making less per roll than you were 6 weeks ago and you didn't notice because the POS just shows you the same £4.50 sale price.

That banana bread? You bake it in-house. The recipe uses 4 bananas, 200g butter, 300g sugar, 2 eggs, and 250g flour. Total ingredient cost for a loaf is £1.60. You cut 8 slices and sell each at £3.50. That's a 94% GP and your most profitable item by a distance. But it's your slowest seller because it's tucked at the end of the counter.

These aren't hypothetical examples. This is exactly the kind of insight that changes where you put things on your menu, how you price them, and what you promote. And none of it comes from your POS alone.

The Integration Trap

There's a growing trend in hospitality tech: platforms that promise to integrate your POS with your accounting, your inventory, your ordering, and your kitchen display -- all for one monthly fee.

The pitch is compelling. One system, everything connected, data flowing everywhere.

But here's what I've noticed after 17 years of running cafes: the operators I know don't need everything connected. They need to know their food costs. They need to know which dishes are profitable. They need their invoice prices to update automatically so their costs stay current.

That's it. That's the problem that actually moves the needle.

Connecting your POS to your accounting software is useful for reconciliation. But it doesn't tell you your GP per dish. Connecting your ordering system to your inventory is useful for stock control. But it doesn't tell you whether that new sourdough loaf is worth the premium flour.

The integration story sounds impressive. The costing story is what actually changes your margins.

Why Costs Go Stale (And Why That Matters)

The biggest problem with recipe costing isn't setting it up. It's keeping it current.

You build a recipe in a spreadsheet. Flour costs £1.20/kg. Butter is £3.50 for 500g. You calculate your costs, set your prices, and move on.

Three months later, flour is £1.35/kg and butter is £4.10. Your recipe spreadsheet still says £1.20 and £3.50. Your menu prices haven't changed. Your actual margins have dropped by 3-4 percentage points, but you won't find out until you do a stocktake or wonder why cash feels tighter than it should.

This is the silent margin killer for independent cafes. Not waste, not theft, not overstaffing -- stale cost data that makes you think you're more profitable than you are.

The solution is connecting your invoices to your recipes. When a supplier invoice comes in with new prices, those prices should flow through to every recipe that uses those ingredients, automatically. No spreadsheet updates. No manual checks.

This is what AI invoice processing does when it's connected to recipe costing. The invoice is the trigger, the recipe cost is the output, and the gap between "supplier changed their prices" and "I can see the impact on my menu" shrinks from weeks to minutes.

POS + Costing: What the Combination Unlocks

When you connect POS sales data to accurate recipe costs, you get something neither system provides alone: menu profitability.

This is what menu engineering is built on. Every dish on your menu falls into one of four categories:

Stars -- High sales, high profit. Promote these. Protect these. They're your business.
Puzzles -- Low sales, high profit. These make you good money per sale but don't sell enough. Reposition them on the menu, rename them, feature them on your specials board.
Plough horses -- High sales, low profit. Customers love them but they barely contribute to your bottom line. Can you reduce the portion slightly? Swap an expensive ingredient? Increase the price by 50p?
Dogs -- Low sales, low profit. Why are these on your menu? Every slot on your menu is real estate. Dogs are taking space that a star or puzzle could occupy.

You can't do this analysis with POS data alone because you don't know the cost side. You can't do it with recipe costing alone because you don't know the sales side. You need both, and you need them connected.

This is exactly what MenuBrik does -- it takes your CostingBrik recipe data and your POS sales data and shows you the profitability matrix across your entire menu. No spreadsheet gymnastics. No guesswork.

Where to Start If You Have Nothing

If you're currently running a POS and a spreadsheet (or worse, no cost tracking at all), here's a practical starting point:

Week 1: Cost your top 10 sellers. Use your POS to identify your 10 best-selling items. Work out the ingredient cost for each. You don't need software for this -- a pen and your latest invoices will do. Calculate the GP% for each dish.

Week 2: Find the surprises. There will be at least one item in your top 10 where the margin is worse than you assumed. There will be at least one item outside your top 10 with a brilliant margin that you're not promoting.

Week 3: Make one change. Adjust one price. Move one item on your menu. Feature one high-margin dish on your specials board. See what happens.

Week 4: Decide if you want this automated. If the exercise was valuable but you don't want to do it manually every month, that's the point where recipe costing software earns its subscription cost.

The starting price for tools that do this properly is around £39/month. If the exercise in weeks 1-3 found you even one mispriced dish, the tool pays for itself.

The Honest Take

I built Brikly's CostingBrik and MenuBrik because this was my exact problem running Hunters Cake Company. I had a POS. I had sales data. I had spreadsheets with recipe costs that were 4 months out of date. I was making pricing decisions based on gut feel and stale numbers.

When I finally connected current invoice prices to recipes to POS sales data, I found two things:

My Victoria sponge -- our best seller -- had a worse margin than I thought because butter and eggs had crept up over 6 months.
A savoury scone that barely sold was one of the most profitable items on the board. It just needed a better position and a better name.

Neither insight came from the POS. Neither came from the invoices. It came from connecting the two through accurate, current recipe costs.

That's the gap. Not more integrations, not more automation, not more dashboards. Just: what does each dish cost to make today, and is that cost reflected in what you charge?

If you can answer that question accurately for every item on your menu, you're ahead of most independent cafes in the country. If you can't, your POS data is telling you half the story.

Start with CostingBrik →

Ed O'Brien has run Hunters Cake Company for 17 years across cafés in Witney, Burford, and a bakery in Carterton, Oxfordshire. He's building Brikly - modular tools that give independent café owners the same data the big chains have, without the big chain price tag.