A customer portal gives the businesses you move goods for a secure login where they can book collections, see where their loads are, download proofs of delivery and pay invoices, without phoning your office. For hauliers, freight forwarders and warehouse operators around Hull and the Humber, it is one of the most practical pieces of software you can add, because it takes away the calls and emails that eat up a traffic office’s day.
This guide explains what a logistics customer portal can include, how it connects to the systems you already run, what it costs you in effort to get right, and how to roll one out without upsetting the customers who are happy with the way things work now. If you would rather talk it through, our custom client portals service is where we start.
Why the Humber suits better customer systems
Few parts of the UK move as much freight as the Humber. Associated British Ports describes the estuary as the UK’s busiest trading estuary, and its Port of Hull page says Hull alone handles around 10 million tonnes of cargo a year, worth around £12bn of trade. Hull Container Terminal handles more than 100,000 containers a year, with Samskip running daily weekday sailings to Rotterdam, and P&O runs a daily overnight ferry between Hull and Rotterdam.
Across the river, the Department for Transport’s port freight statistics for 2025 put Grimsby and Immingham second only to London for tonnage among major UK ports, and second only to Dover for roll-on roll-off freight. The Humber Freeport adds tax sites at Hull East, the Able Marine Energy Park and Goole, according to the government’s maps of the Humber Freeport tax sites.
All of that freight passes through local hauliers, forwarders, customs agents and warehouses, many of them small and medium-sized firms competing with national operators. Service is often what wins and keeps the work, and a good customer portal is a visible way to offer national-operator service without a national-operator back office.
The “where’s my load?” problem
Ask anyone who has worked in a traffic office what fills their day and you will hear the same list:
- customers phoning or emailing to ask where a load is and when it will arrive;
- requests for proof of delivery, often weeks later, when an invoice is queried;
- collection requests arriving by email, phone and text, then being typed into the transport system;
- chasing drivers for signed paperwork that is still in the cab;
- resending invoices and statements that the customer says they never received.
None of these tasks adds value. Each one interrupts someone who should be planning tomorrow’s work. Most of the information customers ask for already exists in your systems, in your tracking, your driver app or your accounts. The customer simply cannot see it. A customer portal fixes that by giving them a window onto their own data, around the clock.
What a logistics customer portal can include
Every business is different, but most logistics portals are built from the same set of features. You do not need all of them at once.
- Bookings and collection requests. Customers enter collection and delivery details, pallet counts, weights and any special instructions into a form that feeds straight into your planning, rather than an email someone has to retype.
- Shipment tracking. A clear status for each consignment, such as booked, collected, in transit, delivered or failed, with an estimated arrival time where your tracking supports it.
- Proof of delivery. Signed delivery notes, photos and timestamps captured by the driver app, available to download as soon as the drop is complete.
- Documents. Consignment notes, packing lists, customs paperwork and delivery reports in one place, grouped by shipment.
- Warehouse stock. For storage customers, live stock levels, goods in and goods out, and the ability to request picks or despatches.
- Invoices and statements. Each invoice linked to the jobs it covers and the matching proof of delivery, with an option to pay online.
- Multiple users per customer. A customer’s buyer, warehouse manager and accounts team each get their own login and see what is relevant to them.
- Notifications. Optional emails or text messages when a load is collected, delayed or delivered.
- Connections for larger customers. An API, or file exchange, for customers who want bookings and status updates to flow directly into their own systems.

Linking invoices to proofs of delivery deserves a special mention. In haulage, many invoice queries come down to whether, when and in what condition a delivery happened, which a single document can settle. When the customer can click from the invoice line to the signed delivery note, many of those queries never get raised.
Start with the data you already have
A customer portal should not become another system that someone has to keep up to date by hand. It works best as a window onto the systems you already run:
- Your transport management system, or the spreadsheet that does the job of one, for bookings, routes and job status.
- Vehicle tracking or telematics, for live locations and arrival estimates.
- A driver app, for electronic proof of delivery, photos and exceptions.
- A warehouse management system, if you store goods.
- Your accounts package, such as Xero or Sage, for invoices, credit notes and payments.
The portal reads from these sources and, for bookings, writes back to them. If your planning and driver tools are still a mix of whiteboards and phone calls, sort that out first. Our guide to job scheduling and dispatch software covers the planning side, and the portal then shows customers the result. Where a system has no way to share its data, that is worth knowing early, because it shapes the whole project.
Features by type of logistics business
Hauliers and pallet network members
The biggest wins are usually shipment tracking, proof of delivery and online booking. A haulier with regular contract customers can give each of them a booking form with their usual collection points and delivery addresses already filled in, which removes most of the errors that come from free-text emails.
Freight forwarders and customs agents
Here the portal is mainly about documents and status. Customers want to know whether a shipment has cleared customs, what is still needed from them, and where the paperwork is. A clear checklist per shipment, showing which documents have arrived and which are outstanding, saves a lot of back and forth.
Warehousing and cold storage
Storage customers want to see their stock without asking. Live stock levels, goods-in reports with photos of damaged pallets, and a simple way to request despatches are the core. For temperature-controlled storage, customers may also expect access to temperature records for their goods.
Couriers and same-day operators
Speed matters most. Fast booking, live tracking that the customer can share with their own customer, and instant proof of delivery are the features that get used every day.
An illustrative example: a Humber haulier
Here is an illustrative example. The business is made up, but its problems are typical of a growing regional haulier.
A family-run haulier near the Humber runs a mixed fleet and a small warehouse. Most of its work comes from around twenty regular customers, including manufacturers, importers using the ports and two wholesalers. Bookings arrive by email and phone. Drivers use a tracking app that captures signatures, but proofs of delivery are only sent out when someone asks for them. Two people in the office spend much of their morning answering tracking calls.

Rather than replacing its transport system, the haulier adds a customer portal on top of it in three stages:
- Tracking and proof of delivery. Each customer logs in to see their own consignments, with signed delivery notes and photos pulled from the driver app as soon as a drop is complete.
- Online bookings. Regular customers book collections through a form with their usual addresses saved. Bookings appear in the planning system for the traffic office to accept, so nothing is retyped.
- Invoices and statements. Invoices come through from the accounts package, each linked to its jobs and proofs of delivery, with an option to pay by card or bank transfer.
The office still takes calls, but they are about exceptions rather than routine updates. Customers who preferred the old way can still phone, and the office answers using the same screen the customer would see.
Security and permissions
A logistics customer portal holds commercially sensitive information: who your customers ship to, what, how often and at what price. It also holds personal data, such as delivery contact names and addresses, which brings UK GDPR into play. Security needs designing in from the start, not adding later.
- Strict separation between customers. Every request must be checked so a user only ever sees their own organisation’s data, even if they change a number in the web address.
- Roles within each customer. An accounts user might see invoices but not book collections, and a site user might see one depot only.
- Two-factor authentication for logins, especially for users who can see pricing or change bookings.
- An audit trail of who booked, changed or downloaded what, and when.
- Sensible retention. Decide how long proofs of delivery and documents stay available, and delete what you no longer need.
Our article on client portals explained covers the general principles of portal security and access in more depth.
Off-the-shelf portal or custom build?
Many transport management systems include a basic customer portal, and if yours does, try it first. If it gives customers tracking and proofs of delivery and they actually use it, that may be all you need.
A custom customer portal starts to make sense when:
- your information is spread across several systems, such as a TMS, a separate warehouse system and an accounts package, and no single product’s portal can show it all together;
- you run transport and warehousing, and customers want one login for both;
- your large customers need bookings and status to flow into their own systems in a particular format;
- the built-in portal looks like someone else’s product, and you want customers to see your brand;
- you want features that reflect how you work, such as booking rules for particular customers or sites.
Costs depend heavily on how many systems need connecting and how clean their data is, so be wary of anyone who quotes a fixed price before seeing your set-up. A first phase that covers tracking and proofs of delivery for a handful of customers is a sensible, contained place to start. If you are weighing up local developers, our guide to custom software development in Hull explains how we approach projects like this.
How to roll out a customer portal
The technology is rarely the hard part. Getting customers to change habits is. A few things help:
- Pilot with friendly customers. Pick two or three regular customers who ask for updates often, and build the first version with their feedback.
- Launch with tracking and proofs of delivery. These are useful from day one and need no change in how customers work.
- Add bookings next. Once customers are logging in, moving bookings into the portal is a small step for them.
- Bring in invoices and payments. Linking invoices to proofs of delivery reduces queries, and online payment can shorten the time to get paid.
- Keep the phone line. A portal should be the easiest option, not the only one.

Notifications matter more than people expect. Automatic emails at the right moments, such as booking confirmed, collected and delivered, mean customers rarely need to log in to check. We used the same building blocks in CoachSync, a booking app for session-based professionals, where each coach has their own booking page, payments are taken upfront through Stripe and confirmation and reminder emails go out automatically. The setting is different, but the principle of letting customers serve themselves, with the system sending updates, is the same.
Questions to ask before you build
- Which of our systems can share data automatically, and which cannot?
- What will customers see on day one, and what comes later?
- How is each customer’s data kept separate from every other customer’s?
- Who owns the code and the data, and can we move them if we change supplier?
- How will the portal handle exceptions, such as failed deliveries and part loads?
- What happens when our transport or accounts software is updated or replaced?
Customer portal questions from logistics firms
Will our customers actually use it?
The ones who currently phone for updates usually will, especially if the portal answers their question faster than a call. Starting with tracking and proofs of delivery, and sending automatic notifications, gives people a reason to log in without asking them to change how they book.
Can a portal work with our existing transport system?
Usually, if the system can share data through an API, a database connection or regular file exports. Older systems sometimes need a small connector built for them. It is worth finding out what yours supports before deciding anything else.
Does a customer portal replace EDI with our largest customers?
Not necessarily. Large customers who already exchange data electronically can keep doing so, and the portal can sit alongside for their staff who want to look things up. For smaller customers, the portal is often the first step towards electronic bookings.
Can drivers’ proofs of delivery appear automatically?
Yes, if your driver app or tracking system makes them available. The portal collects the signature, photos and timestamp after each drop and attaches them to the right consignment and invoice.
The bottom line
For logistics firms around Hull and the Humber, a customer portal is not about looking modern. It is about giving customers answers without a phone call, settling invoice queries with a click, and freeing your traffic office to plan the work rather than report on it.
If you want to see what a portal could look like on top of your existing systems, tell us how you work today or call us on 01482 212499. We will start with what your customers ask for most, and build from there.


