Every restaurant comes to us with a real problem — not a shopping list of features. Pick the one that sounds like you. We'll show you what good looks like and what the platform does about it.
We've worked with independents turning over £4k a week and chains turning over £40m a year. The jobs they hire us to do sort into four buckets — grow revenue, cut costs, scale without the wheels coming off, and run full-service dine-in alongside everything else.
Four levers most operators could be pulling harder — and most of them don't need a price rise.
The problem. Sales have plateaued. Aggregator orders are flat. You don't know which lever to pull — marketing? Loyalty? Menu changes? New channels?
What good looks like. A measurable 10–20% lift over 12 months from reactivating dormant customers, surfacing your best items, running meal deals that don't cannibalise margin, and pushing app orders where the basket size is 15–25% bigger than web. No guesswork — you can see what each lever did.
How Andromeda helps. Customer database with segmentation, automated win-back campaigns, deal engine with per-channel rules, cross-sells at checkout, branded app with push notifications, and the reporting to tell you which of these is actually working for your customers.
See the full guide on growing your sales →The problem. Uber Eats and Deliveroo bring volume, but they also own your customer, take a big slice of every order, and compete with you inside their own app. On a £20 order you keep roughly £14. Scale that across a year and it's the single biggest leak in your business.
What good looks like. Most of your repeat customers ordering through your own branded site and app. You keep the margin, you own the data, you decide what happens next. Aggregators still run — for discovery — but they're not the whole game any more.
How Andromeda helps. Your own branded ordering site, native iOS + Android app, loyalty that only works on your direct channel, automated incentives to shift repeat aggregator customers across, and per-channel pricing so Uber users pay a little more than your direct customers. All plugged straight into the same POS and kitchen.
See the full guide on building your own direct customers →The problem. You're taking the same margin on a peak-hour delivery order as a quiet Tuesday collection. Aggregator customers are paying the same as your direct customers — so the aggregator wins twice. Deal pricing was set two years ago and nobody's re-checked it.
What good looks like. Prices tuned by channel (direct, Uber, Deliveroo, Just Eat), by occasion (collection vs delivery), and by service window. Deals that drive basket size without giving away margin. Price changes rolled out cleanly to every channel in minutes, not days.
How Andromeda helps. Per-channel price uplifts so aggregator users cover aggregator commission. Tiered deal engine with minimum-spend logic. Scheduled price changes. Chain-wide overrides with local flex. Clear reporting on margin per item per channel.
See the full guide on optimising pricing →The problem. Your Uber Eats menu has stale photos. Items are out of stock on Deliveroo but live on Just Eat. Modifiers are inconsistent across platforms. Every menu change means logging into three dashboards and remembering what you did on each.
What good looks like. One menu, in one place, pushed automatically to every aggregator with the right photos, the right modifiers, the right prices per channel. Items go out of stock everywhere the moment your POS flags them. New items launch on all three platforms at once.
How Andromeda helps. Direct integrations with Uber Eats, Deliveroo, Just Eat, Bolt, Wolt and Deliverect. Single menu editor. Per-channel overrides. Real-time availability sync on Deliveroo. Auto-pause on aggregators when the kitchen gets overwhelmed.
See the full guide on improving aggregator listings →Three areas where most restaurants bleed money quietly — and where better tooling pays for itself in weeks, not years.
The problem. Orders are out the door at 42 minutes when the target is 35. Customers complain. Refund requests climb. Your drivers are running late pickups and cold drops, and you don't know whether the problem is the kitchen, the dispatch, or the driver pool.
What good looks like. Average out-the-door under target for 90% of orders. Clear visibility into where time is being lost — kitchen make-time, rack-time, or drive-time. Auto-dispatch that books a third-party courier before the kitchen gets swamped, without a human touching the screen.
How Andromeda helps. Flight Deck kitchen display with make-time tracking. Auto-scheduling that measures live throughput and queue depth. Uber Direct and Stuart integrations for on-demand couriers. A driver app with turn-by-turn and GPS back to the store. And the reporting to show exactly where the minutes are going.
See the full guide on improving delivery times →The problem. Food cost is creeping — 31%, 32%, 33%. You can't tell whether it's wastage, theft, portioning, or supplier price drift. Every menu change risks tipping a loss-making item into your top seller.
What good looks like. A known ideal food cost per item, measured actual food cost against it daily, and a variance report that points you at the 3 items causing 70% of the problem. Recipe-level portion control. Stock counts that reconcile without a calculator.
How Andromeda helps. Rameses PCA (Product Cost Analysis) with item-level ideal vs actual. Recipe management with sub-recipes. Wastage recording at the till. Stock receive, transfer and count workflows. Food cost percentage reporting that you can actually act on.
Deep guide in build — in the meantime, see Reporting.
The problem. You're over-rota'd at 3pm on Tuesdays and under-rota'd at 8pm on Fridays. Overtime creeps. New starters take two weeks to be useful on a till. Payroll reconciliation is a Sunday-night job you dread.
What good looks like. Rotas matched to forecast demand per half-hour. Clock-in at the till, not on paper. Labour-cost percentage visible live alongside sales. Payroll data exported cleanly, not rebuilt from clocking timesheets.
How Andromeda helps. Staff scheduling driven by historic sales per interval. Clock-in/out at the POS with biometric or PIN. Labour-cost percentage on the live dashboard. Scheduled-vs-actual reporting. Payroll export ready for your accountant.
Deep guide in build — in the meantime, see Reporting.
The operational and legal stuff that stops being optional the moment you open a second site or start prepping food for customers with allergies.
The problem. Two sites is fine. Five sites is chaos. Menus drift apart. Pricing inconsistencies creep in. Promotions launch on Tuesday in one shop and Thursday in another. Consolidated reporting is built by hand in Excel every Monday morning.
What good looks like. A master menu you control centrally, with clean local overrides for sites that genuinely differ. Group-wide reporting that rolls up to one number and drills down to one line item. A franchisee app so area managers can see their patch on their phone. New sites live in a week, not a month.
How Andromeda helps. Central menu management with knock-in/knock-out for local items. Mission Control app for owners, franchisees and area managers. Group reporting with exception alerts. Lab-store sandbox. Phased rollout with a dedicated implementation team. And Papa Johns UK runs 400+ sites on this.
See the full guide on managing multiple shops →The problem. The legal framing is murkier than most operators realise. Natasha's Law specifically covers pre-packed for direct sale (PPDS) — sandwiches wrapped on site for a grab-and-go display, for example. Food prepared to order in a restaurant kitchen falls under FIC 2014 allergen rules instead. Either way, you are legally required to make accurate allergen information available to the customer before they order.
What good looks like. Allergen data attached to every menu item at the recipe level, not pinned to a fridge door. Surfaced clearly to the customer on the ordering site, app and kiosk. Flagged on kitchen tickets. Updated once, appearing everywhere. And a defensible paper trail if something ever goes wrong.
How Andromeda helps. The 14 allergens are first-class data in the menu editor. They render on the customer-facing menu, on the kiosk, on the branded app, and on the kitchen ticket. Menu exports can be audited. Suppliers' allergen changes propagate cleanly through the recipe tree. Compliance stops being a quarterly panic.
See the full guide on allergens and Natasha's Law →The problem. Businesses with 250 or more employees in England are required to display calorie information on their menus under the Calorie Labelling (Out of Home Sector) Regulations 2022 — at the point of choice, in both in-store and online ordering. For chains and large groups this is already a legal obligation; for growing independents it becomes one the day you cross the threshold.
What good looks like. Calorie values attached to menu items at the recipe level so changes propagate. Displayed clearly next to the item, at the point the customer decides — on the ordering site, app, kiosk, and printed menu. One source of truth across every channel.
How Andromeda helps. Calorie fields on every menu item, rendered automatically in the customer-facing site, kiosk and app. Recipe-level changes flow down to every variant. Easy export for external verification. Ready on day one — so when you cross the 250-employee threshold, you're not scrambling.
Deep guide in build — in the meantime see Menu control.
For operators with a dining room, a pub garden, or a bar — let guests scan, order and pay from their phone with no app and no queue at the bar.
The problem. Not enough hands on a Friday night. A beer garden too far from the bar. A pub lunch that needs to turn in 45 minutes but the order-at-the-bar queue is eating ten of them. You don't need another server — you need the guest to be able to order without one.
What good looks like. A QR on every table. Guests scan, browse your menu on their phone, order and pay in one flow — the ticket goes straight to the right kitchen station, the table gets closed automatically when the final payment lands. No app download, no account, no server in the loop.
How Andromeda helps. Customer-led QR order & pay running on the same POS, same menu, same Stripe rails as the rest of the platform.
See the full pillar on QR order & pay →"We came for the online ordering. We stayed because the platform paid for itself three times over — once on commission saved, once on delivery times, once on labour."
A 30-minute demo is usually enough to show you how we'd tackle your specific problem. No slide deck. Just a working platform on your menu.
Book a demo