3 September 2026
In short
What should a customer portal do for a Northampton business?
A customer portal for a Northampton operator should answer the three things clients ring about and show honestly how fresh each figure is. GTX Digital gets the operational data accurate and reachable first, because a portal is a window and nothing more.
- A portal is a window. If the data behind it is wrong, it shows.
- Say how fresh each figure is. Customers forgive honest, not confident and wrong.
- Expect a few weeks of clients finding errors that were always there.
- Design multi-site access at the start. Bolting it on later is painful.
- A portal half your clients use has still removed half the calls.
Think this applies to your business?
We will tell you straight whether it is worth doing, what it would take, and what we would do instead if it is not.
Phones ringing with the same question all day? Book a technology review. The answer is often a portal, and sometimes it is just a better email.
A customer portal is one of the few pieces of software where you can predict the benefit before you build it. Count the calls.
What a brand client wants to see
Spend a week writing down what clients actually ring about. In most Northampton operations the list is short and repetitive.
| The screen | Who asks for it | How fresh it has to be |
|---|---|---|
| Order and despatch status | Everybody, constantly | Live, or close to it |
| Proof of delivery and paperwork | Customer service, after a query | Available within minutes of the event |
| Stock on hand by SKU | The brand's planner, weekly and at month end | Overnight is fine if you say so |
| Exceptions and shortages | The account manager, before you ring them | Live, and pushed rather than waited for |
| Storage and handling charges | Finance, monthly | Monthly, and reconciled |
Resist the feature list that arrives once people get interested. Messaging, uploads, a dashboard of charts. Most of it never needs building.
A portal cannot be fresher than your capture
This is where portals go wrong, and it is not a design problem.
The screen can only show what the system beneath it knows, and in a warehouse that system is only as current as the last scan. If despatch is confirmed on a clipboard and keyed at four, a live status page is wrong for most of the afternoon, and it is wrong in the direction that makes you look careless.
So the sequence is not negotiable: make the capture current, then put a window on it. That is why a portal project here frequently turns out to be a capture project with a screen at the end, which the customer portal development page explains, with the local version on the Northampton page for it.
The alternative — building the portal first and promising to fix the data later — produces something that is right often enough to be trusted and wrong often enough to be dangerous. Clients will ring to check, and you will have added a system without removing a call.
## Stale data is worse than nothing
A portal that is sometimes right trains clients to ring anyway. Now you maintain a portal and answer the calls.
Decide how fresh each figure has to be and say so on the screen. "Stock as at 06:00" is fine. What clients cannot forgive is a page that looked confident and was wrong.
The fastest way to lose trust is a contradiction between the portal and a member of your team. Your people should be looking at the same figure the client sees.
They will see your mistakes
Nobody warns operators about this, and it is the part that stings.
Once a brand can see the data, they notice when it is wrong. Expect a few weeks of being told about discrepancies that were always there and nobody had visibility of.
That is uncomfortable and it is genuinely useful. The errors existed before the portal; the portal just found them. Say that out loud internally before you launch, so the first weeks are treated as a clean-up rather than as evidence the project failed.
The operators who handle this well go further: they publish the exceptions themselves, before the client finds them. A shortage you flagged is a service issue. A shortage they found is a trust issue.
Who at the client can see what
Worth designing at the start, because retrofitting it is painful.
| The role | Should see | Should not see |
|---|---|---|
| Brand planner | Stock, forecasts, inbound | Other clients, obviously, and your internal costs |
| Their customer service | Order status, POD, exceptions | Commercial terms |
| Their finance | Charges, volumes, reconciliation | Operational detail they will misread |
| A client with three sites | Only the sites they are responsible for | The other two, unless they are the group account |
That last row is the one that gets bolted on late. Multi-site access is common in supply chains and much easier designed in than added.
Be deliberate about documents too. Proof of delivery and paperwork usually should be downloadable. The internal note attached to the same consignment should not.
Adoption is a change to how you answer the phone
Building it is half the job. The other half is your own team, and it is the half that is usually left to chance.
Clients do not arrive at a portal by accident. They arrive because somebody told them it exists at the moment they needed it, which means the person answering the phone has to change what they say.
"It is on the van, due before two — you can see that yourself any time at this link, shall I send it over?" That sentence, said repeatedly for a month, moves more clients than any announcement, and it works because it answers the question first and offers the tool second.
Put the link where they already look: the despatch confirmation, the invoice, the signature of whoever they speak to most. Then watch which accounts log in. The ones that do not are either not getting the link or not getting value, and those are different problems with different fixes.
Expect some who will never use it. Do not force them by removing the phone number — in a business where service is the product, that is how a portal becomes the reason a client goes to tender.
## Portal or app
For clients who touch you occasionally, a portal wins. Nothing to install, any device, reachable from a link. An app is for daily operational use, offline work or the camera, and the distinction is set out in mobile app development in Northampton.
The same data problem sits underneath both, and software development for Northampton logistics companies covers getting it right.
What it does to your own team
The point is fewer interruptions, and the effect is real. But it changes what your people do, and that is worth saying out loud.
The calls that remain are the harder ones, because the easy ones have gone. That is a better use of experienced staff. It is rarely a smaller team, and promising one is how these projects lose the room.
A sensible first phase
One screen. Order and despatch status, pulled live from the system that knows, with an honest freshness note.
Give it to the ten clients who ring most. Watch what they do and what they still phone about. That second list is phase two, and it will be shorter and different from what you would have guessed.
We work across logistics and 3PL and retail and e-commerce clients here, with the wider picture on the Northampton page. When you want it scoped, get in touch.
Common questions
What should the portal show first?
Order and despatch status, the documents that go with it, and current stock. Those three cover most of what clients ring about.
What if our data is not accurate enough?
Then fix that first. A portal that is sometimes right trains clients to ring anyway, and you have a portal to maintain as well as the calls.
Will clients actually use it?
The ones who ring most will, if the link is in the places they already look. Watch which accounts log in; the ones who do not are either not getting the link or not getting value.
Next step
Start with a technology review, not a proposal.
A short, structured conversation about where your systems are costing you time, margin or growth — and what the realistic options are. No pitch deck.