ELL ADVISORY

AI for UK Logistics: Where the 3PL Admin Burden Actually Sits

Fawad Bhatti, Founder of Ell Advisory
Founder, Ell Advisory · Ex-Hilti Principal PM · HEC Paris MBA
24 min read

TL;DR

I pulled twelve sets of filed accounts for UK 3PLs and hauliers. Median operating margin: 3.95%. In every one that discloses both, administrative expenses exceed operating profit — 4.34× at Eddie Stobart, 3.45× at Menzies Distribution Solutions. That is the leverage. The structural reason admin never gets fixed is buried in the standards: across all 194 message types in the current UN/EDIFACT directory, there is no proof-of-delivery message. Five stages carry the burden; only three are safe to point a language model at. Start by measuring which costs you most — the Hidden Waste Audit.

A pallet leaves a factory in Wigan on Tuesday and is signed for at a distribution centre outside Bristol on Wednesday. It moved once.

Its paperwork got handled five times. At booking, when a traffic clerk retyped a customer's email into the TMS. At collection, with a delivery note, a walkaround check and manual tachograph entries. At delivery, when a signature and a pallet count landed on a POD. At invoicing, when somebody assembled a rate, a fuel surcharge, waiting time and a tail-lift charge from four different places. And three weeks later, when the customer disputed two crushed cases and somebody had to find that POD.

Not one enormous inefficiency, then, but five small ones stacked. Most AI conversations in logistics start at the wrong end — routing, which I covered in the distribution and wholesale guide. Routing is worth doing. It is just not where mid-market 3PLs bleed.

3.95%

Median operating margin

12 UK 3PL filings, Companies House

0

EDIFACT messages for a POD

of 194 in directory D.21B

£40,502

Overhead per vehicle per year

RHA Cost Tables 2026

7 days

To notify a damage claim, with evidence

RHA Conditions 2024, cl. 14(1)(a)

Exhibit 1 — The 3PL admin map

One pallet moves once. Its paperwork gets handled five times.

1. Booking
Order in, job on the board
Customer email or portal order, spreadsheet manifest, EDIFACT IFTMIN if you are lucky, rate enquiry, booking-in slot request at the RDC.
Re-key
order → TMS → sheet
Traffic office types the order into the TMS. Somebody types the slot reference into a spreadsheet, because the TMS has no field for it.
2. Collection
Driver, vehicle, hours
Delivery note, CMR consignment note with eleven mandatory particulars, walkaround check, defect report, driver card, tachograph manual entries, ADR paperwork.
28 / 90 / 365
day compliance cycle
Driver cards downloaded at least every 28 calendar days, vehicle units at least every 90, records producible to enforcement officers for 12 months.
3. POD
The document that gets you paid
Signed delivery note, quantity expected against quantity delivered, adjustment code, damage notation, photograph, timestamp, GPS fix — or paper in the cab door pocket.
No standard
EDI message exists
Nothing in UN/EDIFACT carries a POD. It travels as a status event or a proprietary payload — which is exactly why it does not reach your invoicing system.
4. Invoice
Rate card meets reality
Rate matrix, fuel surcharge, waiting time, pallet exchange, re-delivery, tail-lift, out-of-hours, storage over free days, self-bill statement, credit note.
4 sources
for one invoice
Charges live in the TMS, the WMS, the telematics unit and the traffic clerk’s memory. Whatever nobody remembers to add is margin given away free.
5. Claims
Dispute, credit, write-off
Claim notification with supporting evidence, POD copy, photographs, weight tickets, temperature trace, correspondence chain, insurer notification, credit note.
7 / 28 / 365
day claim windows
Seven working days to notify loss or damage in writing with evidence, twenty-eight for other loss, one year to issue proceedings. Miss one and it fails on procedure.
Document lists compiled from RHA Conditions of Carriage 2024 (conditions 6, 9, 12, 14), the CMR Convention as scheduled to the Carriage of Goods by Road Act 1965 (articles 6, 30, 32), GOV.UK drivers’ hours, tachograph and ADR guidance, and the UN/EDIFACT D.21B message directory. Stage characterisations reflect patterns I see in mid-market operations; they are not published statistics.

Stage 1 — Booking: the same data, typed twice

The EDI accounts are the well-behaved ones. UN/EDIFACT has a message for this: IFTMIN, which UNECE says "is the one and only message which results in the actual contract" (UNECE directory D.21B).

Most of your volume will not arrive that way. It arrives as a spreadsheet with the columns in a different order to last week, or as free text in an email, and somebody in the traffic office types it into the TMS — doing the job of an expensive optical character reader while also being the only person who knows this customer means the goods-in door.

Then it gets typed again. The RDC slot is booked in the retailer's portal, which does not talk to your TMS, so the slot reference goes into a spreadsheet kept alongside it. That spreadsheet is a ghost workflow — invisible on any process map, nobody's job, load-bearing. And HMRC's Making Tax Digital rules require data to move between systems "without manual intervention like cut-and-paste" (VAT Notice 700/21). A lot of traffic offices would struggle to defend that spreadsheet against that sentence.

Stage 2 — Collection: the day is not mostly driving

Operators must download data from each driver card at least every 28 calendar days and each vehicle unit at least every 90, must produce those records to enforcement officers for 12 months, and must "make regular checks of charts, manual records and digital data to ensure compliance" (GOV.UK, 1 July 2026). Drivers must produce their own records for the current day and previous 28 calendar days — 56 days for international journeys to and from the EU.

The record is broader than driving. Working time includes loading and unloading, vehicle maintenance, administrative tasks, and waiting where duration is not known in advance; it must average no more than 48 hours a week and be kept two years (GOV.UK, Annex 2). The framework already assumes much of the shift is not driving — and explicitly names admin as work you must record.

Stage 3 — POD: the document that decides whether you get paid

One document decides whether you get paid, and the contract terms explain why.

Under condition 9(3) of the RHA Conditions of Carriage 2024: "No payment shall however be withheld by the Customer where the Carrier is unable to provide a proof of delivery unless notification of non-delivery is received by the Carrier no more than 48 hours after the expected time of delivery of the Consignment and the Carrier is subsequently unable to evidence proof of delivery" (RHA Conditions of Carriage 2024). That is a 48-hour clock, and your protection is producible evidence, quickly. Condition 6 permits ePOD — a receipt may be "a document or electronic record" — while placing on the customer "the burden of proving the condition of the Consignment... at the time of that receipt".

Now the operational reality. In many mid-market operations the POD is still paper travelling back in a vehicle, then scanned, filed and keyed. A tramper on a four-day run carries four days of billing evidence with them, and since POD receipt usually triggers invoicing, the cash cycle is gated by a sheet in a cab door pocket — which you must then keep for six years under the general VAT records rule.

ePOD closes both gaps: capture once at the kerb, reuse everywhere. That is not AI, it is data capture — which is why a 3PL still on paper should fix it before buying anything with "AI" in the name. Downstream automation only pays if the data arrives clean, the pattern behind why 70% of AI projects fail. Where AI earns its place is the paperwork you cannot control — the subcontractor's scan, the photo taken in a dark yard — a document extraction problem costed in job sheet parsing.

Stage 4 — Invoice: four sources, and the charges nobody added

The base rate is in the TMS. The fuel surcharge is a monthly formula in a spreadsheet. Waiting time is on the driver's record or in telematics. Pallet exchange, tail-lift, out-of-hours, re-delivery and storage over the free period each live somewhere different, and each depends on a human remembering to look. The failure mode is not overcharging. It is undercharging by omission: nobody audits the charges you forgot to raise, and there is no exception report for revenue you never invoiced.

Internationally the volume is growing. UK declarants cleared 91.3 million customs declarations in 2025, up 7.9%, while the number of declarants fell from 5,650 to 4,880, down 13.7% (HMRC, 14 May 2026). HMRC puts the administrative burden of GB–EU declarations in 2022 at £1.8bn, an average of £48 per declaration (HMRC, 15 July 2025). Then you wait to be paid — and large companies must publish how long they take, under the Reporting on Payment Practices and Performance Regulations 2017.

Average days to pay suppliers, as filed on the DBT payment practices register

Tesco Distribution Ltd (to 1 Mar 2026) — 67% paid at 61+ days58 days
Gregory Distribution (to 31 Mar 2026)55 days
Wincanton Holdings (to 31 Dec 2025)45 days
XPO Transport Solutions UK (to 31 Dec 2025)41 days
DHL Supply Chain (to 30 Jun 2026)36 days
GXO Logistics UK (to 31 Dec 2025)32 days

One line on that register is worth the whole section: Tesco Distribution Ltd pays 67% of its invoices at 61 days or more; Tesco Stores Ltd pays 6% that late. Same group, split along the retail-versus-distribution line. Wincanton's filed statement notes "90 days, 60 days for sub-contract haulage". On 24 July 2026 DBT committed to legislate for a hard 60-day maximum term and a statutory deadline for raising invoice disputes (DBT). If customers must dispute inside a fixed window, clean evidence produced fast is worth more again.

Stage 5 — Claims: short windows, long correspondence

The windows here are shorter than most operators keep in their heads.

Under condition 14(1)(a) of the RHA Conditions of Carriage 2024 the carrier is not liable for physical loss, mis- or non-delivery or damage "unless advised thereof in writing, together with such evidence as may reasonably be required to prove that the physical loss... was caused by the Carrier, within seven days after the termination of transit". Condition 14(1)(b) allows twenty-eight days for "any other type of loss"; 14(2) discharges liability unless proceedings are issued within one year. And 14(3) matters more than it looks: where a period is seven days or less, "Saturdays, Sundays and all statutory public holidays shall be excluded" — so seven days means seven working days.

Note what 14(1)(a) requires: not just notification but evidence, inside the same window. That is a documentation deadline, not a correspondence deadline. Liability is capped by condition 12(1)(c) at "£1,300 Sterling per tonne". Internationally, CMR runs in parallel: seven days for non-apparent damage, twenty-one days for delay, a one-year limitation period and a cap of 8.33 SDR per kilogram (CMR, scheduled to the Carriage of Goods by Road Act 1965).

Where the systems don't meet — and why POD data never flows

Here is the structural finding that explains more than any vendor deck will. UN/EDIFACT directory D.21B contains 194 message types — booking instruction, status, consolidation, despatch advice, receiving advice, invoice. There is none for a proof of delivery. So the single document that unlocks your invoice and defends your claim is the one with no standard route between systems. Every 3PL solves it locally, which is why every 3PL solves it badly.

GS1 gets closer: its logistic label standard makes the SSCC the one mandatory element on every logistic unit, precisely because scanning it "allows the physical movement of units to be matched with the electronic business messages that refer to them" (GS1, July 2019). If your PODs, claims and invoices all carry SSCCs, matching becomes mechanical; if they carry a mix of references and handwritten pallet counts, it stays human.

Two things I verified explain why the seams stay manual. First, "does your TMS have an API?" is a pricing question, not a technical one. Mandata, widely used by UK hauliers, documents three tiers: Mandata Go offers "simple file-based imports and exports" and no API, while GoPlus adds a "Developer API for seamless data transfer with third-party products". Integration gated behind the price list — and most operators find out after committing.

Second, warehouse systems often cannot export the thing a 3PL bills on. SnapFulfil publishes an open API specification of around 250 endpoints, and not one is a billing endpoint, despite the product supporting a dozen charge types in its own interface. Mintsoft, by contrast, publishes invoice endpoints decomposed by activity. If your WMS is in the first camp, client billing is a spreadsheet job.

The worst seam is telematics into billing: the vehicle knows exactly when it arrived and left, but the waiting-time charge comes off the driver's note. These seams stay manual because nobody has counted what manual costs — the same sales-to-operations handoff problem, transplanted into a traffic office. The legal obstacles are gone: the Electronic Trade Documents Act 2023 gives electronic trade documents "the same effect as an equivalent paper trade document", and from July 2027 EU authorities must accept regulatory information submitted through certified eFTI platforms.

Technology investment intentions of UK logistics operators — January 2026 survey (Logistics UK, June 2026)

Battery electric vehicles66.4%
Vehicle technologies64.3%
Fleet management data systems57.4%
Supply chain data systems52%
Transport planning / route optimisation50.7%
Hydrotreated vegetable oil (HVO)41.8%

Where large language models genuinely help

Three uses map cleanly onto 3PL admin. Each turns messy text into structured data or a draft a human approves; none makes an unreviewed decision.

Reading unstructured inbound documents — order emails, manifests with inconsistent columns, scanned delivery notes, subcontractor invoices. Highest-volume, lowest-risk win in the building, because the output is checkable in one glance. Run it with a confidence threshold and a review queue, not unattended.

Drafting claims and dispute correspondence. A claims response is a structured argument from a fixed evidence set: what the POD says, what the photographs show, what condition 14 says about the window. Given those inputs a model produces a competent first draft in seconds; a human still sends it. The gain is that the draft exists the day the claim arrives, not the week the backlog clears — which matters when the window is seven working days.

Classifying and triaging inbound email. A traffic office inbox mixes bookings, amendments, POD requests, invoice queries and claims. Sorting it into queues with the right job reference attached is measurable inside a fortnight.

Two places a language model must not go

Tachograph and drivers' hours compliance. Do not let a model interpret, summarise or infill drivers' hours records. The operator's duty is to hold accurate records and produce them for 12 months, and false records carry a Level 5 fine or, on indictment, two years' imprisonment (GOV.UK). A plausible-but-wrong reconstruction of a missing manual entry is a falsified record. Deterministic tachograph analysis software already exists and is the right tool. Use AI to flag an overdue download; never to produce the record.

Dangerous goods documentation. ADR instructions in writing use a prescribed four-page model, and GOV.UK states plainly that "you cannot amend the instructions in writing, as the statements have been agreed and translated into other languages" (GOV.UK). A generative model's function is fluent variation — precisely the wrong property for a document whose legal force depends on being verbatim. Controlled templates, not generation. Customs classification belongs here too: autonomous commodity-code classification is not a job for a model.

The commercial argument, honestly stated

I pulled twelve sets of filed accounts from Companies House for UK 3PLs and hauliers. Median operating margin: 3.95%, with ten of the twelve below 5% — Turners (Soham) at 10.5% and Culina Logistics at 9.5% are genuine outliers, and Suttons International Holdings ran at −0.14%. But the margin is not the interesting number. The interesting number is the ratio in the same accounts between administrative expenses and operating profit.

Administrative expenses as a multiple of operating profit — filed accounts, FY2024

Eddie Stobart Ltd4.34×
Menzies Distribution Solutions3.45×
Fowler Welch Ltd1.68×
Culina Logistics Ltd1.33×
Turners (Soham) Holdings1.23×

Read that as gearing: a 10% cut in administrative cost lifts operating profit by 12.3% at Turners, 34.5% at Menzies and 43.4% at Eddie Stobart. Nothing else available to a mid-market 3PL has that ratio, and none of it needs capital.

Headcount says the same. Wincanton splits staff into warehouse, transport and administration: administration was 16.2%, Turners 15.5%, Culina Logistics 14.9% — one person in six. Per vehicle, the RHA's Cost Tables 2026 put overhead at £40,502 a year, 19.18% of total operating cost, nearly double depreciation; the RHA's own definition of that line includes "Supervisory and Clerical Salaries and Wages... excluding drivers", administration overheads including IT systems, and "Operator's licence fees... tachograph analysis".

So, an illustrative model. Assumptions, not client results. Take a 3PL running 600 consignments a week — 31,200 a year — at 12 minutes of avoidable document handling each: 6,240 hours a year. ONS ASHE 2025 puts median hourly pay for transport and distribution clerks (SOC 4134) at £15.78 excluding overtime; at a fully-loaded £21 that is roughly £131,000 a year. Remove a third and you free about £44,000 — which, on Eddie Stobart's ratio, is a double-digit percentage of operating profit.

Methodology and sources

Every figure above was read on its primary source and linked or named inline with its date. All figures are sterling. Sources: accounts filed at Companies House, ONS ASHE 2025, HMRC statistics and guidance, GOV.UK statutory guidance on drivers' hours, tachographs and ADR, the UN/EDIFACT D.21B directory, GS1, the RHA, the CMR Convention as scheduled to the Carriage of Goods by Road Act 1965, Logistics UK, and the DBT payment practices register.

Company financials. Margins, administrative-expense ratios and staff splits come from accounts filed at Companies House and read directly — among them Wincanton (04178808), GXO Logistics UK (SC037270), Turners (Soham) Holdings (07889555), Eddie Stobart (00995045), Culina Logistics (05128194), Menzies Distribution Solutions (03805401) and Fowler Welch (01001101), mostly periods ending 2024. Two caveats: Wincanton's margins are underlying, with a statutory operating loss in both periods; and the expense ratio is only computable where the line is disclosed separately, so the chart shows those companies, not all twelve.

On the RHA Conditions. The RHA publishes its Conditions as member-only, copyright-protected content, so the clause text quoted here is the 2024 edition as published in full by Kuehne+Nagel. A 2026 edition took effect on 1 January 2026 and I could not obtain its text, so numbering and the condition 14 evidence requirement may have moved. Check which edition you trade on, and your subcontractor terms separately.

Other sources and their limits. Payment figures are as published by those companies on the DBT register; do not compare their "% not paid within agreed period" columns across filers, because they interpret it inconsistently. RHA Cost Tables 2026 covers a 44-tonne 6x2 artic at 75,000 miles and 240 earning days. ASHE 2025 was released 23 October 2025 with an April 2025 reference date; the £21 fully-loaded rate, the 12 minutes per consignment and Exhibit 1 are my assumptions. HMRC's £48 and £1.8bn apply to GB–EU declarations in 2022 and "may not necessarily be applicable to non-EU declarations". The Logistics UK figures are stated investment intentions, not completed investments. No result is attributed to any named client.

What I could not verify, and left out. The quoted "5–15% freight invoice error rate" has no traceable primary source — every version leads to freight audit vendors citing unnamed "industry studies", and the figures contradict each other. There is no defensible published split of an HGV driver's shift between driving and non-driving work; that claim traces only to commercial blogs, and the DfT-commissioned TRL study contains no such breakdown, so I used the regulatory definition instead. ONS publishes no rate of return for transport and storage, and no official statistic breaks out AI adoption for the sector. And no UK statute sets a POD-specific retention period; six years is the general VAT rule.

What to do on Monday morning

Four things, none requiring a purchase.

Find the administrative expenses line in your own accounts and divide it by operating profit. That ratio tells you what a 10% admin saving is worth, and it takes two minutes.

Count the re-keys on ten consignments. Take ten jobs from last week across your worst-behaved customers and note every point where a human typed information that already existed somewhere.

Pull your last twenty paid claims and ask of each: could we have produced a legible POD, inside the window? How many you paid on an evidence gap rather than a real failure is your ePOD business case. Then check which edition of the conditions of carriage you trade on, and diarise the windows.

Check your tachograph download cadence against the statutory cycle — cards every 28 calendar days, vehicle units every 90, records producible for 12 months. If that is a diary reminder rather than a system alert, fix the alert this week. It is the one place here where I would automate and stop there.

If you would rather the counting were done properly, that is what the Hidden Waste Audit is for. Or book a 30-minute call and we will map your five stages against Exhibit 1.

Frequently Asked Questions

Where does the admin burden in a 3PL actually sit?

In five places: booking, collection, proof of delivery, invoicing and claims. Booking and invoicing carry the most re-keying; POD carries the most financial leverage, because it gates both invoicing and claims defence; collection carries the statutory compliance load.

Why doesn't POD data flow between systems automatically?

Because there is no standard message for it. UN/EDIFACT directory D.21B has 194 message types, including IFTMIN for booking instructions and INVOIC for invoices — but nothing for a proof of delivery. POD data travels as a status event or in a proprietary format, so every operator solves it locally. Carrying the GS1 SSCC on PODs, claims and invoices is the practical workaround, because it makes matching mechanical.

How much of a 3PL's cost is administration?

More than the accounts suggest at a glance. Administrative expenses run at 1.2 to 4.3 times operating profit across filed UK accounts, administration is roughly 15–16% of headcount at Wincanton, Turners and Culina Logistics, and the RHA puts overhead at £40,502 per vehicle per year — 19.18% of total operating cost.

How long do I have to notify a freight claim in the UK?

Under the RHA Conditions of Carriage 2024, seven days after termination of transit to advise physical loss, mis-delivery or damage in writing with supporting evidence, and twenty-eight days for other loss, with liability discharged unless proceedings are issued within one year. Since periods of seven days or less exclude weekends and public holidays, that is seven working days. A 2026 edition took effect on 1 January 2026.

Can AI handle tachograph and drivers' hours compliance?

No, and it is not a close call. Operators must hold accurate records and produce them to enforcement officers for 12 months, with driver cards downloaded at least every 28 calendar days and vehicle units at least every 90 (GOV.UK). False records carry a Level 5 fine or two years' imprisonment on indictment, and deterministic tachograph analysis software already solves this. Use AI to flag an overdue download; never to reconstruct a record.

What is a realistic first AI project for a mid-market 3PL?

Document extraction on inbound orders and subcontractor invoices, with a confidence threshold and a human review queue. The output is checkable in one glance, volume is high, and the risk of an unreviewed error reaching a customer is low. Fix paper PODs first, though — that is data capture, not AI.