Services · Mobile app development · Procurement apps

Procurement software for London firms where every purchase faces an audit trail.

Codeeo offers procurement software development in London for banks, insurers, boroughs, universities and property groups that have outgrown spreadsheets and email approvals. We build requisitioning, supplier onboarding, third party risk reviews, contract records and invoice matching as one system, with a mobile approver app on top, so a purchase in the City or Canary Wharf can be traced from first request to final payment.

London buyers answer to more people than most: the FCA, internal audit, a parent company abroad, or a borough's scrutiny committee. The software has to show who approved what, against which policy, and why a supplier was chosen. That evidence is what our procurement software developers for London clients design first.

Built for
Financial services firms, public bodies, universities, property developers and multi-entity groups headquartered in London.
Typical timeline
We agree a first release and its dates in writing after discovery, then plan later phases around your audit calendar and contract renewals.
What you own
Source code, cloud accounts, supplier records, approval history and the admin system, all held in accounts your organisation controls.
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

What we build

Modules shaped around how London organisations buy.

Procurement in London rarely sits inside one company. A Canary Wharf bank may buy through a UK entity while its policy is set by a group office in New York or Frankfurt. A borough may buy alone, through a shared service with neighbouring boroughs, or through a framework run by another public body. A developer on the South Bank may manage dozens of subcontractors on one scheme. The capabilities below are the ones London clients most often put into a first and second release. We do not build every module for every client; discovery decides which ones earn a place in the first version and which can wait until people are using the system and asking for more. A small first release that people adopt is worth more than a large one they avoid.

Explain your project
  • Third party risk onboarding

    Questionnaires that change with the risk of the service being bought, so a cloud provider handling customer data answers far more than a catering firm. Answers, evidence files and reviewer decisions are stored against the supplier record and set to expire when a review is due again.

    Outsourcing and operational resilience reviews have a record behind them.

  • Multi-entity requisitions

    One request form that routes by legal entity, cost centre and currency, with approval rules that respect a group delegation matrix. A London subsidiary can follow local thresholds while the parent company sees every commitment in its own reporting view. Intercompany recharges are tagged at the point of request, not unpicked at month end.

    Group policy and local practice live in one place.

  • Approver app for commuters

    A focused iOS and Android app for approving requests, reading supplier notes and checking budget lines on the move. Approvals can be cached for poor signal and synced when the phone reconnects, which matters on Underground and rail commutes. Push notifications carry enough detail to decide, without opening a laptop.

    Requests stop waiting for someone to reach a desk.

  • Responsible sourcing records

    Fields for living wage commitments, modern slavery statements, carbon reduction plans and ethical trading standards, captured at selection and checked at renewal. This suits London public bodies and suppliers who bid for them, where these questions appear in most tenders. Evidence can be requested again before each renewal, automatically.

    Social value claims can be shown, not just stated.

  • Contract and obligation register

    Every agreement with its term, notice period, exit plan, data processing terms and named owner. Alerts go out before renewals and break clauses, and each contract links back to the sourcing decision that created it. Exit plans for critical services sit beside the contract they protect.

    No more auto-renewals discovered after the fact.

  • Supplier self-service portal

    A web portal where suppliers keep their insurance certificates, accreditations and contacts current, see the status of each purchase order and submit invoices against it. Changes to bank details trigger a separate verification step, with a call back to a known contact, because payment diversion fraud targets London finance teams constantly.

    Supplier data stays current without a chain of emails.

  • Invoice matching and accounts payable feeds

    Purchase order, goods receipt and invoice compared automatically, with exceptions routed to the buyer who raised the order. Approved invoices pass to your finance system, whether that is Dynamics, Oracle, SAP or Xero, through its API. Every score change after moderation is logged with a reason.

    Finance teams spend time on exceptions only.

  • Tender evaluation workspace

    Scoring sheets, moderation notes and conflict of interest declarations for each evaluator, locked once a decision is made. Public sector clients can export the evaluation summary they need for award letters and published notices. Evaluators working from home sign in with the same controls as the office.

    Evaluations hold up when a bidder asks questions.

  • Spend and concentration dashboards

    Views of spend by category, entity and supplier, with flags where too much depends on one provider. Risk teams in financial services use this to show which outsourced services would hurt most if a supplier failed. Reports can be grouped by important business service for resilience reviews.

    Supplier dependence becomes visible early.

  • Guided buying catalogues

    Preferred supplier catalogues for common purchases such as stationery, IT peripherals, couriers and temporary staff, with the negotiated terms already applied. Staff who buy twice a year are steered to approved routes instead of a personal card, and procurement can see which categories still leak spend outside agreed contracts.

    Off-contract spend falls without extra policing.

Who this suits

Four London buyers we design for.

The same word, procurement, covers very different work across London. A trading floor buying market data, a borough commissioning adult social care and a developer ordering steel for a tower in Stratford need different screens and different rules. These four profiles are the ones we see most. If yours sits between two of them, discovery is where we work out the mix. Every conversation, review and demo runs by video call, since Codeeo works with London clients remotely from its teams in Dubai, Riyadh and Karachi.

01

Regulated financial services firms

Banks, insurers, payment firms and asset managers around the City and Canary Wharf must show the FCA that material outsourcing is assessed, monitored and exitable. We build onboarding, due diligence, contract obligations and exit planning into one record per supplier, with an audit log of every change. Data protection terms under UK GDPR sit alongside the commercial ones, so legal and risk teams read from the same file rather than chasing each other for the latest version. Concentration reports show where several important services rely on the same cloud or data provider.

Built to support your compliance team, not to replace its judgement.

02

Boroughs and other London public bodies

Councils, housing bodies and NHS trusts in London buy under the Procurement Act 2023. Their suppliers register on the Central Digital Platform, and notices are published through Find a Tender. We build internal systems that prepare the data those notices need, track contract milestones and keep evaluation records, while the official publishing stays on the government platform where it belongs. Many London boroughs share services or buy jointly, so we design for more than one contracting authority in the same system where that applies.

We integrate with official services where APIs allow; we do not replace them.

03

Universities and research institutions

London universities buy laboratory equipment, research services and campus contracts across many departments, often with grant conditions attached to the money. The software needs department level budgets, grant codes on each order, and approvals that reach academics who are rarely at a desk. Funders may ask later how a piece of equipment was sourced, so quotations and the reason for the final choice stay attached to the order. We keep the forms short so researchers actually use them, and we let central procurement see every department's pipeline in one view.

04

Property and construction groups

Developers and contractors working on schemes across the capital manage packages of subcontractors, each with insurance, accreditation and payment terms. We build supplier compliance checks, package level budgets and valuation approvals, so a site manager in Battersea and a commercial director in an office in Mayfair see the same numbers. Retentions, variations and payment notices are tracked against each package, so disputes start from shared facts. Site staff confirm completed work on their phones, which keeps valuations moving. Insurance expiry alerts reach the package manager first.

How a London procurement build moves from brief to live use.

  1. 01Policy and process mappingWe read your procurement policy, delegation matrix and audit findings, then map how requests really move today, including the workarounds people use when the official route is too slow. Interviews include a few requesters who buy rarely.
  2. 02Risk and data designSupplier tiers, data classifications, retention periods and access roles are agreed with your risk, legal and information security colleagues before screens are drawn. Third party risk tiers are defined in your own terminology.
  3. 03Interface designShort request forms for occasional buyers, dense working views for procurement staff, and a mobile approver app, all checked against WCAG 2.2 so staff using assistive technology can complete every task.
  4. 04Build and integrationDevelopment in short cycles with a working demo every sprint, connected to your finance system, identity provider and document storage as each module reaches them. Each demo is recorded for absent stakeholders.
  5. 05Testing with real casesLast quarter's purchases are replayed through the system to prove approval rules, matching tolerances and reports behave as your policy says they should. Mismatches are fixed before any London team goes live.
  6. 06Rollout and refinementOne department or entity goes first, its feedback shapes the next release, and the rest of the organisation follows once the process has settled. Training material is written for London staff in their own roles.

Technology

What we build this with.

We choose the stack around your existing estate: often .NET or Node services, React interfaces, Flutter or native mobile apps, and hosting in UK cloud regions so procurement and supplier data stays where your policy expects it. Sign in runs through your existing identity provider, usually Microsoft Entra ID, so leavers lose access the day HR closes their account.

01Mobile

  • Swift
  • Kotlin
  • Flutter
  • React Native

02Data and cloud

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

03Marketing and tracking

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

What London teams ask before commissioning procurement software.

Because many London organisations have rules a packaged suite bends badly around.

Packaged procurement suites suit standard purchasing. Custom procurement software development in London makes sense when you run several legal entities, carry regulatory duties on outsourcing, or need approval rules that follow an unusual delegation matrix. A custom build can also sit beside a suite you already own, filling a gap such as third party risk or contract obligations, rather than replacing it outright. We usually recommend reviewing what your current licences already cover before writing any new code.

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