Industries/ Logistics/ Customer tracking and booking
A track and trace portal that stops the where-is-it calls
Your customers book collections, follow each consignment and download proof of delivery and invoices from one login in your brand. The office sees the same status they do, so a call that does come in takes seconds rather than a round of phone calls to the driver.

- Used by
- Shippers, their goods-in teams, your customer service and accounts
- Takes the place of
- Booking emails, where-is-it calls and POD requests by email
- Connects to
- Your transport system, driver app, accounts software and email
- Built with
- Our customer portals service
Where it hurts today
A normal week, before it exists
Every morning the phones start with the same question in different voices. A goods-in manager wants to know whether the pallets will arrive before the bay closes. A shipper wants to tell their own customer when to expect a delivery. Customer service puts them on hold, tries the driver, who is driving, then rings back with a guess. Across a fleet of vans and hundreds of consignments, that is a full-time job that adds nothing.
Bookings arrive the same way: an email with a spreadsheet attached, a phone call taken on a pad, a message to someone's mobile on a Saturday. Collection addresses are incomplete, pallet counts are wrong, and the ready time turns out to mean 'some time after lunch'. Someone retypes each one into the transport system and rings back to fill the gaps, and the ones that arrive at the weekend wait until Monday.
Then come the paperwork requests. A customer's accounts team will not pay an invoice until they see proof for every consignment on it, so someone in your office digs out scans, matches them by reference and emails a bundle. Next month the same customer asks for the same kind of bundle. The information exists, just not anywhere the customer can reach it without asking a person.
What it does
Customer tracking and booking, feature by feature
What customers and your own team can do in the portal, built around the questions they ask most.
- 01
Track and trace in plain words
Each consignment shows where it is in words a shipper understands: collected, at the depot, out for delivery, delivered, or failed with a reason. Status comes from the driver app and your transport system, not from someone updating a spreadsheet, and the time of the last update is always shown.
- 02
Online collection booking
Customers book a collection with the fields your planners need: address, ready time, closing time, pallet or cage count, weight, tail lift and any special handling. Required fields stop the vague bookings, and each accepted booking drops straight into the planning queue rather than an inbox.
- 03
Proof of delivery downloads
Once a drop is done, the photo, signature, printed name and any remark made at the door appear against the consignment. Customers download one proof or a bundle for a whole invoice, so their accounts team no longer has to hold payment while they wait for your paperwork.
- 04
Each customer sees only their own
A shipper sees their consignments and nothing else. Larger customers can have several logins with different rights: the transport buyer books, the warehouse follows deliveries, accounts sees invoices. Their own customers can get a tracking link for a single delivery, with no login and no other details shown.
- 05
Invoices and delivery history
Invoices sit next to the consignments they cover, with proof attached, and customers can search their own history by reference, date or delivery address. Queries are raised against a specific consignment, so your accounts team sees exactly which drop is in question.
- 06
Delivery notifications customers choose
Customers pick what they hear about and how: an email when a collection is confirmed, a text when a delivery is out, an alert only when something fails. The aim is fewer messages that matter, not a stream of updates nobody reads.
A day with it
How the day runs instead
A normal week for a regional haulier's customer service desk and one of its regular shippers, with the portal running.
- Monday, 7.30amShipper's transport buyer
The buyer books three collections for Tuesday in the portal. One booking will not go through without a pallet count, so they add it. All three appear in your planners' queue with ready times, closing times and tail lift needs.
- Monday, 9.00amTransport planner
The planner accepts two bookings and moves the third to Wednesday because the site closes at noon. The customer gets an email with the new date and the reason, and nobody has to pick up the phone.
- Tuesday, 11.20amGoods-in manager
At the receiving site, the goods-in manager opens the tracking link from the shipper's email, sees the van is two drops away, and moves a forklift driver to the bay rather than ringing anyone to ask.
- Tuesday, 3.40pmCustomer service adviser
A shipper calls about a failed delivery. The adviser opens the same screen the shipper sees, reads out the reason and the time of the photo, and books a redelivery while they are still on the call.
- FridayShipper's accounts clerk
Before approving the week's invoice, the shipper's accounts clerk downloads proof for every consignment on it as a single file. They approve it without emailing anyone, and your accounts team never has to build the bundle.
What it connects to
Works with what you already run
The portal shows what your other systems know. It is only as current as the connections behind it, so we build those carefully.
Transport management system
Consignments, statuses and delivery windows are read from your transport system, and accepted bookings are written back to it as jobs. Where there is no API, we work from scheduled exports and say clearly how current that makes the portal.
Driver app
Proof of delivery and failure reasons appear in the portal as soon as the driver's phone syncs, whether that app is one we build or one you already use, provided it can share its data.
Accounts software
Invoices and credit notes come from your accounts package, for example QuickBooks or Microsoft Dynamics 365 where it offers an API, so customers see the same figures your accounts team does.
Email and text messages
Booking confirmations, delivery alerts and failure notices go out through an email and SMS service under your name and reply address, so replies reach your team rather than a no-reply box.
The first version
Start small, then grow it
A first version should be useful on day one and small enough to get right. This is where we would usually draw the line, and what tends to follow once people are using it.
In the first version
- A tracking page for each consignment, fed from your existing transport system
- Proof of delivery ready to download as soon as a drop is complete
- Customer logins that show each shipper only their own consignments
- Collection booking with the fields your planners actually need
- Email alerts for delivered and failed drops, sent in your brand
Once it is in use
- Proof bundles downloadable for a whole invoice in one file
- Several logins per customer, with different rights for buyers, warehouse and accounts
- Text alerts with an arrival window as the van gets close
- Booking by spreadsheet upload for customers who already plan in spreadsheets
Buyer's guide
Before you commission one
Four decisions worth making before you commission a customer delivery portal.
- 01
Your TMS portal module or a custom portal
Many transport systems offer a customer portal module, and tracking pages are sold as packaged products too. If yours covers booking, tracking and proof download in a way your customers find easy, switch it on and save the build. Custom is worth it when several systems must be joined up behind one login, or when the portal itself helps you win work.
- 02
What to gather first
Log a fortnight of customer calls and emails by type: where is it, can I book, send me the POD, why is this invoice wrong. Collect the booking forms and spreadsheets customers send today. Find out which statuses your TMS records and how current they are. That list becomes the portal's first screens.
- 03
Who should own it
The customer service or commercial lead, because the portal is part of how customers experience you. Operations decides which statuses customers see and what each one means. Accounts owns invoices and proof bundles. One named person should approve each new customer login and review old ones, so access is checked rather than forgotten.
- 04
How you will know it is working
Count where-is-it calls and POD requests before launch, and keep counting afterwards. Watch how many bookings arrive through the portal instead of by email, how often customers log in, and which pages they open. If your customer service team still answers the same questions by phone, the portal is not answering them yet.
Terms worth knowing
The words you will meet
- Track and trace
- Following a consignment through each stage, from collection to delivery, with a timestamped status at every step. For a haulier, the quality of track and trace depends on how often the driver app and TMS update, so ask how current each status really is.
- Role-based access
- Permissions set by role rather than by person: a transport buyer can book, a warehouse user can track, an accounts user can see invoices. It matters because larger customers have several people in the portal, and each should see only what their job needs.
- Tracking link or customer portal
- A tracking link shows one consignment to whoever has it, with no login. A portal sits behind a login and holds a customer's whole relationship with you: bookings, history, proof and invoices. Many firms offer both, with links for receivers and the portal for shippers.
Handled with care
The details that matter here
A portal puts your operational data in front of customers. These are the details we handle with particular care.
Only their own consignments
We enforce what each login can see on the server, not just by hiding things on screen, and we test it by deliberately trying to reach another customer's consignment. Single-delivery tracking links carry no other customer details and stop working after a period you choose.
Honest status
If a status has not changed for a while, the portal says when it last updated rather than presenting an old position as current. We agree with your operations team which statuses customers see, so internal notes and depot shorthand stay internal.
Driver location shown with restraint
Customers rarely need a van on a map, and a dot on a map is your driver's location. We agree with your data protection lead what customers see: often an arrival window or the number of drops remaining, and only once the delivery is close.
Easy for people with other jobs
Goods-in managers and accounts clerks use the portal between other tasks, often on a phone. We design for accessibility from the start, with clear contrast, plain labels, keyboard and screen reader support, keep each main task to a couple of steps, and test with real customers first.
Guides
Worth reading first
Questions
What buyers ask first
Will customers actually use a delivery tracking portal?
Some will straight away and some never will, which is why the phone line stays. We start with the questions your customer service team answers most and make each one quicker in the portal than a phone call. We pilot with a few regular shippers, watch where they get stuck, and fix that before inviting everyone. A tracking link in the delivery email needs no login at all, which helps.
Can customers still phone or email us?
Yes. The portal is there for the routine questions, not to put a wall between you and your customers. When someone does call, your team sees the same screen the customer sees, so the answer takes seconds. Complicated or urgent problems still go to a person, and the portal makes it easy to raise a query that reaches the right one.
Do we need to replace our TMS to add a customer portal?
No. The portal sits on top of what you run today, reading consignments from it and writing bookings back. If your system has an API, that is the simplest route. If it only produces exports, we work with those and tell you honestly how current the portal can be as a result. Replacing the transport system is a separate decision, and often not needed.
Who owns the portal and the customer data in it?
You do. The portal carries your name and branding, runs in accounts that belong to you, and the customer data in it is yours. You get the source code and documentation, so another team could look after it if you ever chose to. We can host it and look after it for you, but that is your choice, not a condition.
Can customers upload bookings in bulk?
Yes. Customers who plan in spreadsheets can upload a file of collections and deliveries in a template agreed with them. Each row is checked for a valid postcode, date and pallet count before it becomes a booking, and any row with a problem is shown back to the customer to fix. Larger customers can send bookings straight from their own system instead.
Count the calls that a screen could answer
Tell us the five questions your customer service desk hears most. We will reply within 48 hours with how a portal would answer each one, and which still need a person.
More for logistics
What else we build for logistics
Driver and proof-of-delivery apps
The day's manifest on the driver's phone, scanning at load and drop, photo and signature capture at the door, reason codes for failed deliveries, and everything saved safely when signal drops and synced as soon as it returns.
Paperwork read automatically
Delivery notes, consignment notes, customs paperwork and supplier invoices read as they arrive, with reference numbers, signatures and handwritten notes about damage pulled out and matched to the right job, and anything unclear flagged for a person.
Operations and fleet dashboards
Drops completed, late and failed, vehicle utilisation and on-time performance by customer, route and depot, on a wallboard in the office and a phone in the yard, so problems show up during the shift rather than at month end.
Dispatch and planning tools
Internal screens for your planners: jobs allocated to vehicles and drivers, capacity and delivery windows visible at a glance, and changes pushed straight to the driver's app, replacing the whiteboard and the spreadsheet only one person can read.
Systems that talk together
Orders from customers' systems flowing into your transport software, completed jobs flowing on to your accounts, and every scheduled transfer watched, so a silent failure becomes an alert the same day rather than a month-end surprise.


