Should we give customers a tracking portal or just send them updates?

Driver arrival and detention guideNov 17, 202617 min read

Short answer

For most customers, sending updates works better than a portal. Most customers do not log in to check. They want to hear when a load ships, runs late or is delivered. Offer a portal only to customers with many open orders who will log in. Wilson, by Cartage, an AI logistics agent, sends those updates by email or SMS from confirmed tracking facts.

Book 15 minutes with the team →

Should customers get a tracking portal or pushed updates?

A distributor's customer service lead gets the same request twice in one week. A large customer asks for “a login to see all our orders.” A smaller customer complains that it found out about a late delivery only when the truck did not show up. The sales director suggests building a tracking portal for everyone. The logistics manager is not sure anyone will use it.

For most manufacturers and distributors, pushed updates by email or SMS serve customers better than a tracking portal, because most customers do not log in to check and want to be told when something changes, especially a delay. A portal is worth adding for the few customers with many open orders who already work from supplier portals and will actually log in. In both cases, the quality of the tracking data decides whether customers trust what they see.

The choice is not really about technology. It is about who does the work. With a portal, the customer has to remember to look. With updates, the shipper has to send the right message at the right time. Customers usually prefer the second, because they have dozens of suppliers and no time to check each one.

Pull and push

A tracking portal is a pull channel. Information sits on a page until someone opens it. Updates are a push channel. The shipper sends the information when it happens.

Question Tracking portal (pull) Pushed updates (push)
Who starts the contact? The customer The shipper
When does the customer learn about a delay? When they next log in When the shipper confirms the delay
What does the customer need? A login, a password, a habit of checking An email address or phone number
What does the shipper need? A portal, user accounts and current data A list of contacts, rules for what to send and current data
Best for Customers with many open orders and a planning team Most customers, most loads
Main risk Nobody logs in; stale data on screen Too many messages, or messages without facts

Why many portals go unused

Portals often start with a big customer's request and a promise that everyone will use them. Six months later, a handful of users log in. The reasons are simple:

  • Customers buy from many suppliers. Each supplier has its own portal, login and layout.
  • Most customers only care about a load when it is late or arriving soon.
  • A portal shows status. It does not tell the customer that a delay matters to them.
  • If the data is wrong even once, customers go back to emailing the sales rep.

None of this means portals are useless. It means a portal alone does not stop “where is my order?” emails.

Why updates work for most customers

An update reaches the customer where they already work: their inbox or their phone. It arrives when there is news. A good update answers the next question before the customer asks it: the new time, the reason if known and when the next update will come. That is why updates cut questions more than portals do.

Let's review how your customers ask for shipment updates today. You don't need to prepare anything: Cartage maps the workflow with you on the call.

See it on your own loads. Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays for freight with your approved carriers.15 minutes with the team behind Wilson. No prep needed.

Book 15 minutes →

How do you set up customer updates that actually stop the questions?

Pick the moments, pick the contacts, write short messages and send them only when the facts are confirmed. The steps below work whether the updates are sent by a person or by software.

Step 1: Choose the moments

Most customers need four updates, at most five:

  • Shipped. The load picked up, with the carrier, the PRO or reference and the planned delivery date.
  • Delayed. The delivery will miss the planned date or window, with the new time and the reason if known.
  • Out for delivery or close to arrival. Useful for receivers with tight docks or appointment rules.
  • Delivered. The load arrived.
  • POD. The signed proof of delivery, for customers who need it to pay or to close the order.

Do not send “in transit” every day. It adds noise and trains customers to ignore your messages. The guide on what to send customers and when covers the timing in more detail.

Step 2: Choose the contacts

Ask each customer who should receive which updates. Often the buyer wants “shipped” and “delayed,” the receiving dock wants “close to arrival” and accounts payable wants the POD. Keep a list per customer or per ship-to. When a contact leaves, the list needs to change.

Step 3: Choose the channel

Email works for most updates. SMS works for short, urgent messages to receiving teams, such as “truck arriving in about an hour.” Ask customers what they prefer. Some receiving teams do not read email during the day.

Step 4: Write short messages

Each update should fit on a phone screen. Include:

  • The customer's PO or order number.
  • What happened.
  • The new time, if it changed.
  • When the next update will come, if one is expected.

Leave out internal codes, carrier jargon and anything the customer cannot act on.

Step 5: Send only confirmed facts

A delay update should come from a current source: the carrier, a tracking feed or the driver. Do not send a delay alert based on a stale status, and do not send a new ETA nobody confirmed. The guide on customer ETA alerts and verified carrier updates explains why a wrong alert does more harm than a late one.

Step 6: Test with a few customers

Start with three to five customers who ask for status often. Send updates for two or three weeks. Ask them whether the messages helped, which ones they ignored and what was missing. Then roll out to more customers with the changes.

Sample messages

The messages below are hypothetical. They show the length and tone, not a template any software sends.

  • Shipped: “Your PO 88213 picked up today at 2:10 p.m. Carrier PRO 5521907. Planned delivery Thursday.”
  • Delayed: “Your PO 88213 will deliver Friday morning instead of Thursday. The carrier confirmed a weather delay at 9:40 a.m. We will update you by noon Thursday.”
  • Close to arrival: “The truck with PO 88213 is about one hour from your dock, per the driver at 8:05 a.m.”
  • Delivered: “PO 88213 was delivered Friday at 9:20 a.m. The signed POD is attached.”

Each one names the order, says what happened and, when something changed, says where the fact came from. None of them asks the customer to log in anywhere.

What to do when customers reply

Updates invite replies: “Can it come earlier?”, “Please deliver to door 4,” “We are closed Friday.” Someone has to read and act on those replies. Send updates from an address that a person or a process watches, not from a no-reply address. Route replies to the person who owns the load. A reply that sits unread is worse than no update, because the customer believes they told you.

Step 7: Keep a record

Save each update on the shipment: what was sent, to whom and when. When a customer says “nobody told us,” the record shows what they received.

When does a tracking portal make sense?

A portal makes sense for a small number of customers who have many open orders at once, plan their receiving from supplier data and already log in to supplier portals. For them, a portal saves calls. For everyone else, it is a page nobody opens.

Signs a customer will use a portal

  • They have dozens of open orders with you at any time.
  • Their receiving or planning team schedules dock labor from supplier data.
  • They already use several supplier portals and asked for yours.
  • They want to see orders before they ship, not just loads in transit.
  • They will name a person who logs in.

If a customer cannot name who will log in, they probably will not.

What a portal must show to be useful

If you build or buy one, it should show:

  • Each order with its shipment status, carrier and PRO or reference.
  • Planned and current delivery dates, with the time of the last update.
  • A clear flag on late loads.
  • The BOL and POD once available.
  • Who to contact with a question.

The time of the last update matters most. A portal that shows “in transit” with no time stamp looks current when it may be two days old.

What a portal does not do

A portal does not tell a customer when something changes. Even customers who use a portal want an email or a text when a load is late. So a portal is an addition to updates, not a replacement.

Branded updates and branded portals

Some shippers want updates or a portal under their own name, not the carrier's. Customers see one consistent sender, whichever carrier moves the load. The article on branded shipment tracking for customers covers the options and why the data behind them matters more than the look.

Carrier tracking links

Some shippers send customers the carrier's tracking link. It is quick, but it has limits: each carrier's page looks different, LTL pages show terminal scans that customers find hard to read and the page does not warn anyone when the load is late. Carrier links are a fallback, not a plan.

Drop shipments and end customers

Distributors and manufacturers who ship directly to their customer's customer have a second audience. The buyer placed the order, but the end customer receives the freight. Decide who gets which updates before the first load. Often the buyer wants shipped and delivered, while the end customer's receiving contact wants close to arrival. Make sure the end customer's messages do not show prices or internal notes, and ask the buyer whether updates should go out under your name or theirs.

What a portal costs to run

The visible cost of a portal is the software. The hidden cost is upkeep: user accounts to set up and remove, passwords to reset, questions about what a status means and data that must stay current or the portal loses trust. Before building or buying one, count who on the team will own those jobs. If nobody will, the portal will go stale within months.

What goes wrong with customer tracking?

Most customer tracking fails because the data is stale, the messages are noisy or nobody owns exceptions. The channel matters less than these three problems.

Mistake 1: Building a portal nobody asked for

A portal built for all customers because one large customer asked. Usage stays low. Fix: offer it only to customers who ask and name a user.

Mistake 2: Showing stale data

A portal or an email says “in transit” with no time. The load has actually been sitting at a terminal for a day. Fix: show when each status was last confirmed, and refresh it from the best source available.

Mistake 3: Sending too many messages

Daily “in transit” emails teach customers to ignore all messages, including the delay that matters. Fix: send only the updates customers need.

Mistake 4: Sending alerts without checking

A tracking feed shows a late scan, and an alert goes to the customer. The carrier was actually on time. Fix: confirm with the carrier before telling the customer about a delay.

Mistake 5: No owner for exceptions

A delay is spotted, but nobody decides what to tell the customer or whether to rebook. Fix: name who handles delays for each customer, and what the customer hears.

Mistake 6: Forgetting the POD

The customer gets “delivered” but not the signed POD, and their accounts payable team holds payment. Fix: add the POD to the updates for customers who need it.

Mistake 7: Different answers from different people

Sales tells the customer one time, customer service another, the portal a third. Fix: all of them read from one shipment record.

Mistake 8: Contact lists that never change

The buyer who asked for updates two years ago has left. Messages go to an inbox nobody reads, and the new buyer says nobody tells them anything. Fix: check customer contacts at least once a quarter, and remove any address that bounces.

Mistake 9: Treating every customer the same

One customer wants every update. Another wants only delays. Sending both the same set annoys one and underserves the other. Fix: set the moments and channels per customer, starting from what each one asked for.

A decision table

Customer situation Best channel
Few orders, asks for status only when late Pushed updates by email
Receiving dock needs a heads-up before trucks arrive SMS or email close to arrival
Many open orders, planning team logs in to supplier sites Portal plus pushed updates for delays
Accounts payable needs proof of delivery POD sent by email after delivery
Customer asked for a portal but cannot name a user Pushed updates; revisit later
Customer wants your name, not the carrier's Branded updates; portal only if they will log in

What checklist should you use before choosing?

Use one checklist to decide, customer by customer, what each one gets. It keeps the decision simple and prevents building more than customers will use.

Item Question Owner
Request What did the customer actually ask for? Sales or customer service
Volume How many open orders does the customer have at a time? Customer service
Users Who at the customer would read updates or log in? Customer service
Moments Which updates do they need: shipped, delayed, close to arrival, delivered, POD? Customer service and logistics
Channel Email, SMS or both? Customer service
Contacts Who gets which update? Customer service
Data source Where does each status come from, and how current is it? Logistics
Delay rule Who confirms a delay before the customer is told? Logistics
Exception owner Who decides what to tell the customer when a load is late? Logistics
Documents Does the customer need the BOL or POD sent? Customer service
Portal Will the customer name a user who logs in each week? Sales
Review When will you ask the customer if the updates help? Customer service

Where to start

Start with updates, not a portal. Pick the customers who ask for status most often. Set up shipped, delayed and delivered messages for them, sent by email or SMS from confirmed facts. Measure how many “where is my order?” emails come in before and after. If a large customer still wants a portal after a month of good updates, consider one for that customer. Before you do, ask what the portal would show them that the updates do not. Often the answer is a list of open orders that have not shipped yet. That list can sometimes be sent as a short weekly email instead, which costs far less to run and does not need a login. If the customer still prefers a portal after that conversation, the case for it is real.

How delays should be handled

Delays are where trust is won or lost. When a load is late, the customer should hear before they notice, with a new time and what you are doing about it. The guide on customer updates when a shipment is delayed covers how to time and word that message.

Collect and customer-routed shipments

When the customer books and pays for the freight, the customer's own carrier holds the tracking. You may not have the PRO until pickup, and the carrier will not send you updates. In that case, send the customer a pickup confirmation with the PRO and the time the truck left, and let the customer track from there. Do not promise delay updates on loads you do not control. Write this down in your update rules, so customers know which loads you will report on.

What to measure

Track a few numbers each month: how many status questions customers send, how many delays were told to the customer before delivery, and how many customer contacts are out of date. If status questions fall and delay notices go up, the updates are working. If they do not, look at the data source and the timing before changing the channel.

How does Wilson, by Cartage, keep customers updated on their shipments?

Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays freight for manufacturers and distributors, and it sends customers or consignees shipment updates by email or SMS where configured, built from the same shipment record it works from. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward. Wilson does not provide a customer tracking portal; it pushes updates instead.

Wilson works as a free logistics department in four parts.

The labor

The labor is what keeps updates accurate. Wilson tracks each load with the best source available: the carrier's API or EDI, GPS or ELD data where the carrier shares it, the carrier's website by PRO number, and email or phone calls when nothing else is current. When the source is old, Wilson follows up with the carrier by phone and email until it gets an answer. When a pickup is missed, a load is cancelled or a delivery is delayed, Wilson contacts the carrier, tells the team and tells the customer if that is configured. It requests and files PODs, so the proof of delivery is on the shipment when the customer needs it.

Wilson reaches the team in Slack, Microsoft Teams or email, and customers or consignees by email or SMS where configured. The company decides which customers get which updates.

The data

The data is the record every update comes from. Wilson keeps every order, load, quote, rate, document and contact on record as it works. Every message, confirmation and change is kept in the shipment's change history, including updates sent to customers. Sales, customer service and logistics read the same record, so the customer hears one answer. Wilson replaces the TMS for freight execution and connects to the company's ERP. Wilson works with SAP, NetSuite, Microsoft Dynamics 365, Oracle, Infor, Epicor, Sage, Acumatica and other ERP environments, with the exact connection depending on the customer's data flow and scope.

The network

The network gives the shipper better freight rates on its lanes because its volume counts with every other Wilson customer's. The network includes carriers and brokers, and the company still approves who hauls its freight.

The payments

The payments close the load. Wilson audits each carrier invoice against the rate confirmation and the POD before money moves, then pays carriers from the Wilson Wallet. Invoices over the rate or outside the rules wait for a person.

Control

Control starts with assisted execution. The company sets which updates go to which customers, and routine updates can run automatically within those rules as the workflow is proven. Timing depends on scope: most teams start on a few lanes and expand from there.

Pricing

Wilson is free on Wilson's network: the shipper pays the freight rate and nothing on top. When a shipper keeps its own carriers, the fee is 2% to 0.5% of what Wilson pays them, falling with volume. There are no seat fees, no setup cost and no contract.

See it on your own loads. Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays for freight with your approved carriers.15 minutes with the team behind Wilson. No prep needed.

Book 15 minutes →

FAQs

Does Wilson give our customers a tracking portal?

Wilson, by Cartage, an AI logistics agent, does not provide a customer tracking portal. It sends customers or consignees updates by email or SMS where configured, built from the shipment record it works from. The company decides which customers get which updates.

Do customers actually use tracking portals?

A few do: usually large customers with many open orders and a team that plans receiving. Most customers do not log in and prefer to be told when something changes.

Which updates should customers get?

Usually shipped, delayed, delivered and the POD. Add a close-to-arrival message for receivers with tight docks. Skip daily in-transit messages.

Should we send carrier tracking links?

They are a quick fallback but have limits. Each carrier's page looks different, and the page does not warn anyone when a load is late.

How do we avoid false delay alerts?

Confirm the delay with the carrier or a current tracking source before telling the customer. A wrong alert hurts trust more than a late one.

Email or SMS?

Email for most updates. SMS for short, urgent messages to receiving teams. Ask each customer what they prefer.

Can customers get the POD automatically?

The POD can be sent as part of the updates for customers who need it. Wilson requests and files PODs on each shipment, and what is sent to customers depends on the setup.

What if a customer insists on a portal?

Ask who will log in and how often. If they name a user and have many open orders, a portal may be worth it for that customer. Keep sending updates for delays either way.

How do we know if our updates are working?

Count status questions from customers before and after, and check how many delays customers heard about before delivery. Fewer questions and earlier delay notices mean the updates work.

Who should own customer updates on our side?

Logistics should own the facts, because it talks to carriers. Customer service or sales can own the relationship and the contact list. Agree who decides what the customer hears when a load is late.

Sources

Let's review how your customers ask for shipment updates today. You don't need to prepare anything: Cartage maps the workflow with you on the call.

Add Cartage as a preferred source on Google