Services · Ecommerce development · QR ordering marketplaces

Ordering marketplaces that let London guests buy from every kitchen with one scan.

Our QR menu ordering website development London work is for venues where many businesses sell to the same seat: food halls, covered markets, office campus dining floors, hotel complexes and arenas. Guests scan, browse every kitchen, pay in one checkout and track each ticket. Behind that, the platform verifies traders, takes your commission, pays each business through a regulated provider and keeps refunds, disputes and reviews on the record.

London venues are crowded, international and expensive to run. A shared ordering site has to cope with Friday night volumes, menus that tourists can read, pricing that meets national consumer law and settlement that a dozen independent kitchens will accept without arguing over every line.

Built for
Food hall landlords, market operators, workplace catering managers, hotel and leisure groups and founders building a multi-venue ordering service anywhere in Greater London.
Typical timeline
We agree the first venue, the payment set-up and the trader rules in video discovery sessions, then date each phase in writing once its scope is approved.
What you own
Your platform's source code and documentation, the guest site, the trader portal, the full order and payout history, and the payment provider account opened in your company's name.
Rated
4.7 / 5 from 23 Google reviews

200+ companies servedFrom a first store to an ADX listed developer

Modon
Majid Al Futtaim
HP
Belkin
Dulsco Group
OneClickDrive
Hanayen
HMS
Clocksprings
Ghezlan

Inside the platform

What a shared ordering site needs to handle London trade.

The difference between a QR menu and a marketplace is what happens after the guest taps pay. A marketplace has to know which business sold each item, who carries the VAT, what commission applies, when that business is paid, and who answers if the order goes wrong. In London those questions arrive at volume: a busy hall can have hundreds of open orders across a dozen kitchens on a Saturday evening.

Below is what we typically build. Each feature lives on the web: the guest site that opens from the code on the table, a trader portal for each kitchen, and your operator console. No download is involved for anyone.

Explain your project
  • Verified trader accounts

    Before a business can sell, the portal checks its identity and bank details through your payment provider, records its Companies House or sole trader status and its VAT registration, and stores its food hygiene rating from the local authority. Expiring documents trigger reminders to the trader and to your team.

    Only checked businesses can take guests' money on your site.

  • Menus in several languages

    Guests in Covent Garden or on the South Bank often read menus in a language other than English. Traders write their menu once, and you can add reviewed translations for the languages your footfall needs, with allergen labels kept identical across every version. The guest picks a language once and the choice holds for the whole visit.

    Visitors order with confidence, and fewer questions reach the counter.

  • Calorie display for larger traders

    In England, businesses with 250 or more employees must show calories on menus, including online ones. A national chain trading in your hall falls under that rule even if your other kitchens do not, so the menu builder lets each trader mark itself in scope and enforces calorie fields where it is.

    Chain traders stay compliant without slowing the independents.

  • VAT that follows the seller

    Food eaten on the premises is standard rated, and in most marketplace set-ups each trader is the seller of its own food while your business sells a service to the trader. The platform issues receipts in the trader's name, invoices commission from you, and exports both to your accountant's preferred format.

    Each business's VAT records reconcile with its payouts.

  • Commission tiers and pitch fees

    Set different commission rates for anchor tenants and new kitchens, add a fixed weekly pitch charge, or offer a lower rate on weekday lunch. Rules are versioned, so a change from next month never alters a statement already issued.

    Your commercial terms are applied exactly as agreed.

  • Trader performance reports

    Each kitchen sees its own sales by hour, average preparation time, refund rate and rating trend, while your console compares every trader across the hall. Those numbers make lease renewals, pitch moves and menu advice a conversation based on evidence instead of opinion.

    Better decisions about which kitchens stay, move or grow.

  • Payouts through a regulated provider

    Guests pay into the provider's marketplace account, not yours. The provider splits each order, applies your commission and pays traders to their verified accounts on the schedule you set, which keeps your business outside the payment regulation the FCA applies to firms holding other people's money.

    Money moves correctly without you becoming a payments firm.

  • Workplace dining accounts

    For office campuses in the City, Canary Wharf or King's Cross, staff can order from several on-site kitchens and pay by card or against an employer allowance. Cost centre reporting goes to the facilities team, and each kitchen is still settled separately.

    One ordering site for a whole campus food floor.

  • Disputes with a clock

    Every complaint opens a case tied to the order line and the trader. The trader has a set window to accept or contest it; your team rules on contested cases with the ticket times and photos in front of them. Agreed refunds are charged back against that trader's next payout.

    Fair, recorded outcomes instead of arguments at the counter.

  • Accessible guest site

    The ordering site is built and tested against WCAG 2.2 at AA level: screen reader labels on every dish and modifier, enough contrast to read under dim bar lighting, large tap targets and no timers that rush a guest. Under the Equality Act, service providers must make reasonable adjustments for disabled customers, and a menu that only works for perfect eyesight falls short.

    More guests can order on their own, with fewer staff interventions.

Where this fits

Four kinds of London operator we build this for.

London's shared dining spaces vary from railway arch markets in Bermondsey to corporate food floors and arena concourses. Each needs a different balance between trader freedom and central control, and each answers to its own borough for licensing: the capital has 33 local authorities, including the City of London Corporation, and licensing conditions differ between them. Late licences in Soho differ from those near the stadium in Wembley, so trading hours are set per venue in the console, and ordering closes automatically when the licence does.

01

Food halls and covered markets

You lease space to independent kitchens and bars and take a share of their sales. Guests want to order from three traders without three queues, and traders want to see their money arrive on time with every deduction explained. The platform gives you central control over pricing rules and opening hours while each kitchen manages its own menu, stock and staff.

We plan around the licensing conditions your borough has already set.

02

Workplace and campus catering

Facilities teams running staff dining with several operators need ordering that ties into employer allowances, cost centres and building access. The platform handles card and allowance payments, separate settlement for each operator, and reporting that a facilities manager can share with finance without exporting spreadsheets by hand. Staff can also pre-order for a set collection time, which spreads the lunchtime rush across the floor and shortens the queue at the most popular counters.

03

Hotels and leisure complexes

Larger London hotels and leisure sites often host outlets run by different companies. A single code at a lobby table, pool deck or bowling lane can show every outlet that is open, take one payment and route each item to the right kitchen, with each operator paid its share.

Room charging depends on what your property system allows.

04

Platform founders

You plan to sign independent London restaurants onto a shared ordering network. Restaurant ordering platform development London founders need goes beyond a menu: self-serve trader sign-up, plan or commission billing for venues, platform terms that meet the UK's platform-to-business transparency rules, and a support desk. We help define the rules and build the product so your team can run it.

Six stages from first video call to a busy London hall.

  1. 01DiscoveryVideo sessions on your venue, traders, payment model, licensing conditions and existing tills, using floor plans and photos, ending in a written scope for the first release.
  2. 02Commercial rulesCommission, pitch fees, payout timing, refund liability and trader suspension rules are agreed and written down, ready for your lawyer to reflect in trader terms.
  3. 03DesignGuest menus, checkout, trader portal and operator console are prototyped and tested with real guests and kitchen staff, including in other languages and on small screens.
  4. 04BuildWe build the platform, connect your payment provider, kitchen screens and accounting, and keep a staging copy running for your team to try every change.
  5. 05Soft launchOne hall or floor goes live with a subset of traders. We monitor ticket times, payout accuracy and support cases and correct problems before full launch.
  6. 06Scale across sitesFurther venues are added from the operator console, each with its own traders, rules and reports, while the code base stays the same.

Technology

What we build this with.

Stack choices follow the job. A fast mobile web front end, a server application and relational database for orders, ledgers and payouts, and a payment provider with a marketplace product are the usual core. We document all of it and you hold the accounts. Queues keep orders safe if a kitchen screen drops off the network, and we load test against your busiest expected night before launch.

01Web

  • React
  • Next.js
  • TypeScript
  • Node.js
  • Laravel
  • WordPress

02Commerce

  • Shopify Plus
  • WooCommerce
  • BigCommerce
  • Headless storefronts

03Data and cloud

  • PostgreSQL
  • MySQL
  • MongoDB
  • AWS
  • Azure
  • Docker

04Marketing and tracking

  • GA4
  • Google Tag Manager
  • Search Console
  • Meta Pixel
  • Looker Studio

What London operators ask before commissioning a marketplace.

Cost and time depend on scope, so we price after discovery rather than quote blind.

The main drivers are the number of traders and venues, whether traders sign up themselves or are added by your team, how complex your commission rules are, and which kitchen screens, tills and accounting tools we connect. Multilingual menus, workplace allowance payments and custom reporting add work. After discovery we give you a written estimate and a phased plan, and each phase gets a date once its scope is agreed. Running costs, such as hosting, the payment provider's fees and ongoing support, are explained separately so you can model margins per trader before signing.

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5from 23 Google reviews