How to get a shipment update from a carrier without a tracking API
Key Takeaways
A carrier email becomes a useful customer update only after its facts are linked to the correct shipment and checked for meaning and timing. Your AI logistics coordinator should separate a confirmed event from an estimate or a pending answer. Notify the authorized recipient when the customer's rule requires it. Missing API access does not remove the need for verification, approval boundaries, or ownership of the next question.
- An API, or application programming interface, is a direct system connection. Many carriers, especially smaller ones, do not offer a tracking API.
- No API does not mean no data. Most carriers share status through a website, email, phone, or EDI.
- The right channel depends on the carrier and the mode. LTL carriers usually have website tracking. Small truckload carriers often answer best by phone.
- Specific questions get specific answers. "Where is load 4410 and when will it deliver?" works better than "any update?"
- The record should show the channel, the time, and the answer for every update.
- Wilson, by Cartage, is an AI logistics coordinator that tracks each load using the best source available, including carrier websites, email, and calls where configured, when no API exists.
Updated November 2, 2026
Why do so many carriers lack a tracking API?
Many carriers lack a tracking API because building and maintaining one takes money and staff that small and mid-sized fleets often do not have. An AI logistics coordinator should plan for carriers without APIs as the normal case on many lanes, not the exception.
Large national carriers and big LTL networks often offer APIs. Many regional and local carriers do not. A manufacturer or distributor may use dozens of carriers, and the best ones on certain lanes are often small fleets with excellent service and no API. Dropping them for lack of an API would cost service and price. The better answer is to track them through the channels they use.
The table below lists the main tracking channels and their trade-offs.
| Channel | How it works | Strength | Weakness |
|---|---|---|---|
| Carrier API | System-to-system connection | Fast, structured | Not offered by many carriers |
| EDI status messages | Standard electronic status updates | Structured, widely used | Setup required; not every carrier |
| Carrier website by PRO or load number | Lookup on the carrier's site | Easy for LTL | Updates may lag; manual without automation |
| Shared location link | Carrier shares a GPS or ELD tracking link | Fresh location | Depends on carrier and driver |
| Email to dispatch | Written status request | Clear record | Reply time varies |
| Phone call | Direct conversation | Fast, can reach the driver | Must be recorded by hand or by the system |
EDI, or electronic data interchange, is an older standard for exchanging business documents. Many carriers send shipment status through an EDI message often called a 214. A PRO number is the tracking number an LTL carrier assigns. An ELD, or electronic logging device, records a truck's location and the driver's hours.
What each channel can and cannot tell you
Each channel answers different questions. A website lookup shows the carrier's last recorded event, such as "arrived at terminal," but not why the freight is waiting. An email reply from dispatch can explain a delay but may be hours old by the time it arrives. A location link shows where the truck is but not whether the driver is on a break. A phone call can answer everything but leaves no written record unless someone writes it down. An AI logistics coordinator should combine channels when one alone cannot answer the question.
No API is not a reason to drop a carrier
A carrier's tracking technology is one factor among many. Service, price, reliability, and the relationship matter more. An AI logistics employee that can track through email and calls lets the team keep strong carriers that lack an API.
Small carriers are often the best on their lanes
Regional carriers often know their lanes, docks, and customers better than large networks. They may offer better service and fairer rates on short and medium hauls. Many manufacturers and distributors rely on them for their most important regional freight. An AI logistics coordinator that tracks them well lets the team keep that advantage without adding manual work.
What "update" should mean
An update is a fresh fact about the load: its location, its status, its expected delivery, or a problem. An update should have a time and a source. A reply that only repeats the original ETA is not a new update. The AI logistics coordinator should ask for facts it can record.
APIs can fail too
Even carriers with APIs sometimes stop sending data. A connection breaks, a field changes, or the carrier's system has an outage. When that happens, the same fallback channels apply: website, email, and phone. An AI logistics coordinator that already knows how to track without an API can keep updates flowing when an API goes quiet.
The cost of manual follow-up
Without automation, following up with non-API carriers takes hours each day. A coordinator may send dozens of emails and make many calls just to learn that most loads are fine. That time is the main reason teams want tracking software. An AI logistics coordinator can take over the routine requests and leave people the exceptions.
Which channel should you use for each carrier?
Use the channel each carrier answers most reliably, and set a default order to try when the first channel is silent. An AI logistics coordinator should store each carrier's preferred channel and contact, and adjust as it learns who responds where.
A default order by mode
| Mode | First channel | Second channel | Third channel |
|---|---|---|---|
| LTL | Carrier website by PRO | Email to customer service | Phone |
| Full truckload, small carrier | Shared location link if offered | Email to dispatch | Phone to dispatch or driver |
| Full truckload, larger carrier | EDI status if set up | Carrier portal | Email, then phone |
| Drayage | Email to dispatch | Phone | Terminal status where available |
| Cross-border leg | Email to the leg's carrier | Phone | Yard or broker confirmation |
LTL, or less-than-truckload, freight shares a trailer with other shippers' goods. Full truckload, or FTL, uses one truck for one shipper's freight. Drayage is the short truck move of a container to or from a port or rail yard.
Find the right contact
The right contact is usually dispatch for truckload carriers and customer service or a tracking desk for LTL carriers. Sales contacts often cannot answer status questions quickly. When a reply comes from the wrong person, ask for the right contact and save it. An AI logistics employee can update the carrier's contact list as it learns who answers.
Record carrier preferences
Each carrier entry should list its tracking channels, contacts, and hours. Some dispatchers answer email within minutes. Others only answer the phone. An AI logistics employee can note which channel worked for each carrier and use it first next time.
Agree on update expectations at booking
The booking is the best moment to agree on updates. The tender can say which events the shipper needs confirmed, such as pickup, any delay, and delivery with the POD. Carriers that accept the tender accept the expectation. An AI logistics coordinator can include these expectations in every tender, which reduces the number of requests needed later.
Ask carriers for a location link
Many small carriers use ELDs or phone apps that can share a tracking link. They may not have an API, but they can send a link for a specific load. Asking at booking costs nothing. If the carrier agrees, the AI logistics coordinator can check the link before contacting dispatch.
Website lookups need a reference number
Website tracking works only with the right reference. LTL carriers use the PRO number. Some truckload carriers use a load or order number. The reference should be captured at booking, from the carrier's confirmation or the bill of lading. A bill of lading, or BOL, is the shipping document that lists the freight and serves as a receipt. An AI logistics employee should store the reference with the load so lookups work from the first day.
Set up EDI where volume justifies it
For carriers with high volume on your lanes, EDI status messages may be worth setting up. EDI takes setup on both sides. It often makes sense for a handful of large carriers. For carriers with occasional loads, website lookups, email, and calls are usually enough.
Hypothetical example: a mixed carrier base
This example is hypothetical and does not describe a real customer. A metal products distributor uses 14 carriers. Three national LTL carriers offer website tracking by PRO. Two large truckload carriers send EDI status messages. Nine small regional truckload carriers have no API or EDI.
The AI logistics coordinator checks the LTL carriers' websites twice a day, reads the EDI messages as they arrive, and asks the nine small carriers for a location link at booking. Six agree. For the other three, it emails dispatch at set times and calls when email goes unanswered. The team keeps all 14 carriers and gets updates on every load.
How should you ask a carrier for an update?
Ask with a short, specific message that names the load and the facts you need. An AI logistics coordinator should ask for location, status, delivery time, and any problem in one message, so the carrier can answer in one reply.
How does an email answer become a customer notice?
The answer should be checked and connected to the relevant shipment before it supports a notice. Your AI logistics coordinator should follow this buyer sequence:
Identify the active load using the carrier reference and source-order relationship.
Check whether the reply describes this movement and a current fact, estimate, or unanswered question.
Preserve the source, fact time, message receipt time, and relevant condition.
Compare the answer with the current receiving arrangement or customer commitment.
Notify the authorized recipient when the customer's rule requires it and name the remaining action.
Your AI logistics employee should seek clarification when the email fits several loads or repeats an old plan. Do not assume universal automatic email matching. A revised carrier estimate does not change a receiving appointment. An early notice can identify uncertainty when needed, but it must not present an unconfirmed time as a new commitment.
Your AI logistics coordinator evaluation should show the outbound notice and the relevant reply or escalation. A message sent to the customer does not prove the customer accepted the change. Supported recipients, channels, and any acknowledgment need agreement in the actual setup.
A good update request
"Load 4410, picked up Monday in Dayton for Nashville. Please confirm current location, delivery ETA, and any delays. Receiver appointment is Wednesday 8 a.m." This request names the load, the stakes, and three facts. A dispatcher can answer in one line.
Match the request to the mode
LTL and truckload need different questions. For LTL, ask which terminal holds the freight and when it will move next. For truckload, ask where the truck is and when the driver expects to arrive. For drayage, ask whether the container has been picked up and when it will deliver. An AI logistics employee should use the right question for each mode.
Ask at the right times
Ask when an update is useful, not on a random schedule. Useful times include the morning after pickup, the day before delivery, and when a scheduled event did not happen. An AI logistics employee can set check times by mode and distance, so carriers are not asked more than needed.
Ask for the next checkpoint
Each update should also ask when the next event will happen. For example: "When will the truck reach Louisville?" or "When will the freight leave the terminal?" The answer tells the team when to check again. An AI logistics coordinator can schedule its next check for that time instead of asking at random.
Respect the carrier's time
Carriers handle many shippers. Short, clear requests at sensible times get faster answers. Bundling several loads into one message for the same carrier also helps: "Please confirm status for loads 4410, 4411, and 4415." An AI logistics employee can group requests by carrier when several loads are open.
Use the phone for urgent questions
Email works for routine updates. For urgent questions, such as a load due in two hours with no news, a phone call is faster. Wilson works with carriers through email, API, EDI where the carrier supports it, and phone calls where configured.
Read replies carefully
Carrier replies are often short and informal. "Running a little late, should be there after lunch" contains a delay and a rough time. An AI logistics employee should read the reply, record the delay, and ask for a specific time if the receiver's appointment is at risk. A vague reply is a reason for one more specific question, not a final answer.
Record the answer
Each answer should be recorded with the time, the channel, and the person who gave it. A phone answer needs to be written down; otherwise, it is lost. The AI logistics coordinator should save phone answers in the same record as email answers.
Say why you are asking
A short reason helps the dispatcher prioritize. "The receiver needs to confirm a dock door by 3 p.m." tells the carrier the answer matters now. An AI logistics coordinator can add the reason in one line.
Common mistakes when asking
- Asking "any update?" The reply is often as vague as the question.
- Asking too often. Carriers stop responding to frequent requests.
- Asking the wrong contact. Sales reps often cannot answer tracking questions.
- Not recording phone answers. The next person asks again.
How do you keep non-API tracking from becoming a full-time job?
Keep it manageable by checking only when it matters, letting automation handle routine requests, and focusing people on exceptions. An AI logistics coordinator should take over the repeated checks and send people only the loads that need a decision.
Hypothetical example: a reply that triggered action
This example is hypothetical and does not describe a real customer. A distributor's AI logistics coordinator emails a small carrier the morning before a delivery. The dispatcher replies that the truck had a mechanical problem and will arrive a day late. The coordinator records the new date, tells the receiver, and asks the logistics manager whether to rebook with another approved carrier. The manager decides to accept the delay because the customer has stock. The whole exchange takes minutes of the manager's time.
Check by exception, not by habit
Not every load needs the same attention. A short regional truckload with a reliable carrier may need one check the morning of delivery. A long cross-country load may need daily checks. An LTL shipment may need checks at each terminal event. Set the schedule by risk. An AI logistics employee can apply the schedule and add checks when a scheduled event is missed.
Keep one thread per load
Keep all messages about a load in one thread with the carrier. The dispatcher sees the history and gives better answers. An AI logistics coordinator should reply in the same thread and attach call notes to the same record.
Use events to trigger checks
The best time to ask is when something expected did not happen. If a pickup scan did not appear, ask. If the delivery day arrives and no out-for-delivery status shows, ask. Event-based checks find problems without asking about loads that are fine.
Escalate silence with a deadline
If a carrier does not answer after the planned follow-ups, the load needs a person. Set a deadline by urgency, such as two hours for a load due today. The AI logistics coordinator should escalate with the full history of what was asked and when, so the person can call a manager at the carrier without repeating the steps.
Let the system handle routine replies
Many carrier replies are routine: "on time," "delivering tomorrow 9 a.m." These can be recorded without a person. Replies that report a problem, such as a breakdown or a missed transfer, should trigger the next step. An AI logistics coordinator can read replies, record routine ones, and act or escalate on problems.
Teach carriers what you need
Some carriers send updates on their own once they know what the shipper needs. A short note at onboarding, such as "Please email a pickup confirmation and a delivery confirmation with the POD for every load," can cut follow-up in half. A POD, or proof of delivery, is the signed record that the receiver took the freight. An AI logistics coordinator can include this request in each tender to carriers that do not send updates on their own.
Measure the effort
Track how many updates came from each channel and how much person-time they took. If one carrier takes much more follow-up than others, talk to the carrier about a location link or a better contact. Wilson can use shipment data from the loads it runs to produce carrier-performance reports on request.
Hypothetical example: from hours to minutes
This example is hypothetical and does not describe a real customer. Before automating, a building materials distributor's two coordinators spent about three hours a day emailing and calling small carriers for updates. After the change, the AI logistics coordinator sends the routine requests, records the routine replies, and passes only the problem replies to the coordinators. The coordinators now spend their time on a handful of exceptions each day.
How should you evaluate tracking software for carriers without APIs?
Evaluate tracking software by giving it a set of carriers without APIs and checking how it gets updates from each. An AI logistics coordinator should use websites, EDI, email, and calls, record each answer, and escalate problems.
Demo tests for non-API carriers
| Buyer requirement | Demo test | Evidence to see |
|---|---|---|
| Website lookups | Use an LTL carrier with PRO tracking | Status read and recorded |
| Email requests | Use a small truckload carrier | Specific request sent, reply recorded |
| Phone follow-up | Keep email silent | Call made where configured, answer recorded |
| Location links | Provide a carrier tracking link | Location used as a source |
| Event-based checks | Skip a pickup scan | Request sent because of the missing event |
| Reply handling | Send a routine reply and a problem reply | Routine recorded; problem acted on |
| Record | Open the load | Each channel, time, and answer saved |
Demo questions about non-API carriers
- Which channels can the AI logistics coordinator use for each carrier?
- How does it store each carrier's preferred channel and contacts?
- How are phone calls made and recorded?
- How does it decide when to ask for an update?
- What happens when a carrier never replies?
- Can the team see follow-up effort by carrier?
Ask how phone calls are recorded
Phone calls are often the most useful channel and the least recorded. Ask the vendor how its AI logistics coordinator makes calls where configured, how it captures the answer, and where the answer appears on the load. If calls happen outside the system, the record will have gaps.
How to measure non-API tracking work
Track the share of loads with a verified update before delivery day. Measure person-time spent on routine tracking. Count problems found before the receiver noticed. These measures show whether the AI logistics employee removes manual follow-up.
Use your own small carriers in the test
Ask the vendor to track loads with two or three of your own small carriers that have no API. Demo carriers with good systems hide the problem. Your carriers show whether the AI logistics coordinator can actually get answers by email and phone.
Scoring the non-API demo
Score each test as pass, partial, or fail. A pass means the update was obtained through the right channel and recorded with its source. A partial means the update was obtained but a person had to make the contact. A fail means the tool showed "no data" and stopped.
Warning signs in a non-API demo
- The vendor tracks only API-connected carriers.
- "No data" is shown with no follow-up.
- Phone calls are outside the tool.
- Every load gets the same check schedule.
- Replies are not read or recorded.
Where does Wilson fit for carriers without a tracking API?
Wilson, by Cartage, is an AI logistics coordinator that tracks each load using the best source available for that load. When a carrier has no API, Wilson can use the carrier's website by PRO number, GPS or ELD data where shared, email, and direct outreach, including calls where configured.
Wilson replaces the TMS for freight execution and connects to the company's ERP through a method that fits the customer's environment. It works with carriers through email, API, EDI where the carrier supports it, and phone calls where configured. Wilson asks the carrier for status and informs the people who need to know.
Exceptions found during follow-up
When Wilson detects a missed pickup, a cancellation, or a delay, it contacts the carrier, notifies the internal team, notifies the customer where configured, and initiates rebooking from the approved carrier list within the customer's rules or with approval. Each step is saved in searchable shipment records with change history.
What Cartage asks about non-API carriers in discovery
Cartage asks which carriers the team uses, which offer APIs or EDI, and how the team reaches the others today. Typical questions also cover dispatcher contacts and which carriers answer best by phone. These answers shape the channels an AI logistics coordinator uses for each carrier.
What Wilson does not do for non-API carriers
Wilson does not guarantee fresh location data for every load at every moment. The freshness of each update depends on the channels each carrier offers. Wilson is not a standalone visibility platform; it tracks loads as part of moving them. Call configuration should be confirmed during setup.
Where teams start with non-API carriers
Most teams start their AI logistics coordinator on a few lanes and expand from there. Timing depends on scope. Cartage helps identify the first workflow during discovery. Teams often start with the small carriers that take the most follow-up time.
Teams choosing a follow-up order can read whether email, phone, or API carrier follow-up should run first. Teams whose carriers do not use apps can see how shipment tracking works without a driver app. Both topics shape how an AI logistics coordinator reaches carriers. Teams comparing data sources can review carrier API, PRO tracking, and check calls.
FAQs
How do you get a shipment update from a carrier without a tracking API?
Use the carrier's website by PRO or load number, EDI status where available, a shared location link, a specific email to dispatch, or a phone call. An AI logistics coordinator should record each answer with its source and time.
Should you stop using carriers that lack an API?
No. Many strong carriers lack APIs. An AI logistics employee can track them through the channels they use.
What is an EDI 214?
It is a common electronic data interchange message used by carriers to send shipment status updates. An AI logistics coordinator can read these messages where the carrier sends them.
How often should you ask a carrier for an update?
When it matters: after pickup, before delivery, and when an expected event is missing. An AI logistics employee should avoid routine requests that carriers will learn to ignore.
Sources
- Cartage, Wilson product scope, October 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator gets a verified update from a small carrier with no API, by email and then by phone, and records the answer on the load: talk to the Cartage team.