Services · Mobile app development · QR menu apps
Codeeo handles QR code menu development London restaurants, pubs, food halls and hotel bars can run as their own product. Guests scan at the table, read the menu in their language, order, split the bill and pay from their phone, while your kitchen and floor staff see every ticket in one place. It matters in a city where a West End table may turn three times before curtain up and a Square Mile lunch crowd has forty minutes, not ninety.
We build for operators who want the menu, the guest data and the payment flow under their own name rather than rented from a marketplace. Our team works with London clients remotely, with discovery, design reviews and demos held by video call, so a restaurant QR menu development London project fits around your service hours rather than pulling managers off the floor.
200+ companies servedFrom a first store to an ADX listed developer
What the system can include
A London menu has to work for a theatre couple with a hard stop at seven, a table of eight colleagues on one company card, a tourist who reads Italian better than English and a regular who just wants the usual. The pieces below can run as a web menu that opens straight from the QR code, with no download, and as a fuller app for loyalty and repeat ordering. We pick the order of build from your trading pattern: a Soho bar and a Canary Wharf canteen rarely need the same first release. Every screen is designed against WCAG 2.2 so guests using screen readers or larger text can order without asking for help, which also supports your duties under the Equality Act 2010.
Guests enter their show time when they scan, and the menu highlights dishes the kitchen can deliver within the window, holds dessert until a set point and sends the bill before the interval rush. Useful for Covent Garden, Shaftesbury Avenue and South Bank rooms where the whole floor empties at once.
Fewer guests asking for the bill in a panic at a quarter to curtain.
Dish names, descriptions and allergen notes translated and reviewed for the languages your visitors actually read, with whichever language the guest's phone already uses opening first. Translations sit in the admin so a new special appears in every version the moment your manager publishes it.
Visitors order with confidence instead of pointing at photos.
Pay by item, split evenly or let one guest settle on a company card, with Apple Pay, Google Pay and contactless card payments through your chosen processor. Each guest gets a receipt by email, and VAT receipts can be generated for business diners claiming expenses.
Large tables pay in minutes rather than queuing at one card machine.
Once a business reaches 250 or more employees, the England calorie labelling rules cover its online and QR menus as well as printed ones. We show kcal per portion beside each item at the point of choice and include the required daily intake statement, fed from your recipe data rather than typed by hand.
Calorie information stays accurate when recipes change.
Guests filter by the 14 regulated allergens and see written allergen information for every dish, while the menu prompts them to speak to staff about their needs. That follows the Food Standards Agency's best practice of written information backed by a conversation.
Allergy questions start informed and end with a staff check.
Any service charge is shown plainly before the guest pays, along with whether it is optional, and tips can be added on screen. Reporting splits tips and service charges by shift so you can pass them to staff in line with the Employment (Allocation of Tips) Act 2023 and your written policy.
Guests know what they are paying and staff know what they are owed.
Office workers order from their desk, choose a collection slot and pick up without queuing, which suits sites near Liverpool Street, Bank or Canary Wharf where the midday peak is short and intense. Slots close automatically when the kitchen reaches capacity.
The lunch peak spreads across slots the kitchen can handle.
When the kitchen runs out of the lamb or the bar loses a keg, staff mark it unavailable from a tablet and it disappears from every table's menu at once. Guests never order something the pass cannot send, and servers stop walking back to tables with bad news during a packed Saturday service in Soho or Islington.
Fewer apologies and fewer refunds on items that ran out.
Orders flow into the till and kitchen screens you already run, through the provider's API where one is available, so a QR order looks like any other ticket to the pass. We confirm what your POS supports during discovery before promising any connection.
No re-keying orders between phone, till and kitchen.
Groups with sites in Shoreditch, Clapham and Marylebone manage one master menu with local prices, local specials and local stock levels, and can switch a dish off at one site when it sells out.
Head office sets the standard and each site keeps its own detail.
Who this is for
The right first release depends on what slows your service down today. A West End dining room loses money when tables cannot pay fast enough; a food hall loses it when guests give up queuing at three counters; a City canteen loses it at twelve thirty. Here are the starting points we see most often in London, and what we would build first for each. If none of them fits exactly, discovery is where we work out what your version looks like.
Some clients come to us after a free QR tool they outgrew; others are replacing printed menus that cost a reprint every time a price changes. Either way, the aim is the same: a menu your managers can edit in minutes and guests can use without instructions.
Your covers arrive together, eat against the clock and want to leave at the same moment. A timed menu, early bill prompts and pay at table do most of the work here. We design the flow so a server can still take over any table, because a QR menu should speed up hospitality rather than remove it. Theatreland rooms usually see the benefit in the first busy week.
Start with pay at table; it gives the fastest result.
Places like Borough Market and the converted food halls across the city put several kitchens around shared seating. One QR code per table, one basket across vendors and one payment, with each kitchen seeing only its own tickets and the operator receiving a settlement report per trader. Guests stop walking between counters, and traders stop losing sales to the queue next door.
Vendor payouts and reporting are scoped before design.
Pubs need fast rounds at the bar and table service in the garden. Guests order drinks and food from the table, with prompts that hand age checks to staff before alcohol is served, as your premises licence conditions require. Each pub keeps its own specials while the group manages pricing, brand and reporting centrally.
Age checks stay with your staff, not the app.
International guests want a menu in their own language and the option to charge food to the room. We build the language layer, connect to your property system where it offers an API and keep the design consistent with the hotel's brand so the menu feels like part of the stay. Non-residents pay by card in the usual way.
Room charging depends on your property system's integration options.
How we work together
Most London operators start with a fixed scope first release covering one site or one service style, then keep improving it on a monthly retainer as more venues join. Groups with a long programme, such as a loyalty app across many sites, sometimes take a dedicated team instead. For digital menu development London groups ask about, cost depends on the number of sites, the POS and payment integrations, how many languages you need, whether you want a native app as well as the web menu, and how much reporting head office expects. Each of these is listed in the scope so you can see what moves the budget.
A defined build with a deadline
We agree what the product has to do, write it down with a price and a date, and build exactly that. Changes are priced before they are made, not discovered on the invoice.
A product that keeps evolving
Named engineers who work your hours, join your standups and stay on the codebase. You direct the backlog; we own the quality of what ships.
Something live that needs looking after
A monthly block of hours for improvements, fixes and the small requests that otherwise wait months. Unused hours carry for a quarter.
Technology
We choose the stack around your POS, your payment provider and the people who will maintain the menu after launch. Most London builds pair a quick browser menu with cloud hosting in British or European regions, adding native or cross platform apps only once loyalty calls for them.
01Mobile
02Data and cloud
03Marketing and tracking
It depends on integrations more than on the menu itself.
A single site with a straightforward POS and one payment provider moves faster than a group connecting several tills, a property system and a loyalty scheme. After discovery we write the scope, the release order and the dates down before design starts, so you know when each London site goes live. Soft launch timing is planned around your quieter sessions, not around our calendar.
Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.
Get in touchPROVEN RESULTS
Swift
Kotlin
Flutter
React Native
PostgreSQL
MySQL
MongoDB
AWS
Azure
Docker
GA4
Google Tag Manager
Search Console
Meta Pixel
Looker Studio