Services · Ecommerce development · QR ordering marketplaces
Codeeo offers QR menu ordering website development UK operators can run as a true marketplace: many food and drink businesses selling to guests through one table code and one checkout. We build the guest ordering site, a portal for every vendor, and an operator console for commission, payouts, disputes and reviews, designed from the start to roll out across several venues and cities, and to respect rules that differ between England, Scotland, Wales and Northern Ireland.
The UK is one market for payments, consumer law and data protection, but food rules are devolved. A platform that will trade in more than one nation needs those differences built into the data model, not patched in when the first Welsh or Scottish venue signs up.
200+ companies servedFrom a first store to an ADX listed developer
What we build
Most QR ordering products were built for a single restaurant and stretched to fit everything else. A national marketplace has a different centre of gravity: the vendor, the money and the rules. Each vendor must be verified once and able to trade at several venues. Each payment must be split, taxed correctly and paid out by a regulated provider. Each venue must apply the rules of its nation and the licence it holds.
These are the parts we put at the core. Everything runs in the browser, so guests scan and order, vendors manage their business in a portal, and your head office runs the network from one console.
Every venue is tagged to England, Scotland, Wales or Northern Ireland. That drives which hygiene scheme it shows, whether calorie labelling applies to in-scope vendors, and which defaults appear in vendor terms. Adding a venue in Cardiff or Belfast then means choosing a nation, not commissioning new code. Licensed trading hours are also held per venue, so ordering closes when that site's licence says it must.
New nations go live through settings, not rebuilds.
England, Wales and Northern Ireland use the numbered Food Hygiene Rating Scheme, and display at the premises is a legal requirement in Wales and Northern Ireland. Scotland uses the Food Hygiene Information Scheme with Pass or Improvement Required. Vendor records hold the right result for each premises.
Each vendor's hygiene status is recorded in the correct format.
A vendor is verified once, with identity and bank checks through your payment provider, and can then trade at any venue you approve. Menus can be shared or varied per venue, and statements separate sales by venue so each site's commission is clear.
National vendors join once and expand easily.
Guests pay once for an order that may involve several vendors. A regulated provider's marketplace product holds and splits the funds, deducts your commission and pays vendors on your schedule. Your business never handles vendor money, which keeps it out of the FCA's regime for payment services.
Money flows correctly without you becoming a payment firm.
Charge vendors a commission, a monthly platform plan, a pitch fee or a mix, set per venue and per vendor. Plans renew automatically, failed vendor payments are retried and flagged, and changes apply from a future date so issued statements never move.
Your revenue model runs without manual invoicing.
Receipts are issued in each vendor's name, with VAT shown only where that vendor is registered, while your commission or plan is invoiced from your business. Food eaten on the premises is standard rated, and your accountant receives exports that reconcile vendor sales with payouts.
Clean VAT records on both sides of the marketplace.
In Great Britain, the Employment (Allocation of Tips) Act requires qualifying tips to reach workers in full. Tips added at checkout are allocated to the vendor whose staff served the order and passed through without deduction, with reports vendors can use for their tipping policy.
Tips handled correctly, with records to prove it.
The UK kept the platform-to-business regulation, which expects marketplaces to explain how listings are ranked and to give vendors reasons and notice before restricting them. The console records ranking rules, sends suspension notices with reasons and runs an internal complaints process for vendors.
Vendors know where they stand and why.
Guest complaints open a case for the vendor with a deadline, escalating to your team if contested, and agreed refunds are recovered from that vendor's payout. Reviews come only from completed orders and cannot be selectively hidden, in line with the fake review ban in the 2024 Act.
Fair outcomes and ratings guests can believe.
Head office sees sales, commission, refund rates, preparation times and ratings by vendor, venue, city and nation. Venue managers see their own site; vendors see only their own business. Reports export to your finance and BI tools.
One view of the whole network, with the right access for each role.
Who we build for
Shared dining has spread from London into Manchester, Birmingham, Leeds, Glasgow, Bristol and beyond: food halls in old markets and warehouses, concessions in stadiums and arenas, and leisure venues with several kitchens. The common thread is many sellers and one guest, and the businesses below feel that most. Each also answers to its own local authority for licensing and food inspection, so the platform has to hold venue-level conditions while head office keeps a national view.
You operate halls in more than one city and want one platform, one vendor contract and one set of reports. Each hall has its own vendors, hours and licence conditions, and some vendors trade in several halls. Restaurant ordering platform development UK groups need at this scale is mostly about the operator console, rollout tools and consistent settlement.
Most national projects begin with one pilot hall, then roll out.
Bowling, competitive socialising, cinemas and live music venues often host food from partner brands. Guests order from their lane, booth or seat, and each partner is paid its share. The platform separates your own outlets from partner concessions in every report. Partner brands that operate in several of your venues keep one account, one contract and a single statement split by site, which makes a national partnership far easier to administer.
You run catering across stadiums, arenas, campuses or workplaces in different parts of the country. You need pre-ordering before events, collection points, mixed in-house and concession vendors, and reporting by site for each client. One codebase serves every site, configured per contract.
We test capacity against the largest crowd you serve.
You want to sign up independent venues across the UK and charge them for ordering. That means self-serve vendor onboarding, monthly plans or commission, clear platform terms, vendor support and a growth plan city by city. We help shape the rules and build the product your team will run. The first city usually proves the onboarding flow and support load; later cities reuse the same playbook with local sales effort, not new engineering.
Your solicitor finalises the terms; we make the software enforce them.
Engagement
Codeeo does not have a UK office. Our team of 80+ works from Dubai, Riyadh and Karachi, we have delivered 200+ projects across the UAE and the US, and we are rated 4.7 from 23 Google reviews. UK clients work with us by video call for discovery, design reviews and sign-offs, with scope on shared boards and every release on a staging site you can try at your own venues. You can commission a fixed first release, retain a team for continuous development, or ask us to stabilise and extend a platform you already run. Every review ends with a written record of decisions and next steps.
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 select the stack per project. A fast mobile web front end, a server application with a relational database for orders and ledgers, and a payment provider with a marketplace product form the usual core. Infrastructure is hosted in your accounts and fully documented. Order queues protect tickets if a kitchen screen loses connection, and load tests run against your largest expected crowd before each wave.
01Web
02Commerce
03Data and cloud
04Marketing and tracking
Scope, integrations and how many nations and venues the first release covers.
The main factors are the number of venues and vendors at launch, whether vendors onboard themselves, how complex your commission and plan rules are, how many tills and kitchen systems we connect, and how many nations you trade in. After discovery we give you a written estimate and a phased plan. Running costs, including hosting, payment provider fees and support, are set out separately so you can model margins.
Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.
Get in touchPROVEN RESULTS
React
Next.js
TypeScript
Node.js
Laravel
WordPress
Shopify Plus
WooCommerce
BigCommerce
PostgreSQL
MySQL
MongoDB
AWS
Azure
Docker
GA4
Google Tag Manager
Search Console
Meta Pixel
Looker Studio