How to evaluate visibility software for cross-border shipments
Key Takeaways
To evaluate visibility software for cross-border shipments, test it on your own lanes with every leg, every handoff, and the customs broker's status, and judge it by what it does when a load stops at the border. An AI logistics coordinator should track each step, separate carrier status from customs status, and follow up with the right party when a step stalls.
- Cross-border shipments often have several carriers, border yards, and a customs broker. Visibility must cover all of them.
- A single ETA from the final carrier hides where delays start.
- Carrier status and customs status are different facts from different owners. Good software keeps them apart.
- Many cross-border carriers lack APIs, so the software must reach them by email, phone, or portal.
- The best test is a real lane with a handoff and a document problem, not a clean demo load.
- Wilson, by Cartage, is an AI logistics coordinator that supports cross-border workflows within the agreed customer scope and tracks each load as part of executing it. It does not perform customs clearance.
What makes cross-border visibility different from domestic tracking?
Cross-border visibility is different because the move has more legs, more parties, and a government step that no carrier controls. An AI logistics coordinator needs to watch each of these, because a cross-border delay can start at any of them.
A domestic truckload has one carrier and one route. A cross-border load from a plant in Mexico to a distribution center in the United States may have an origin carrier, a crossing carrier, a destination carrier, two yards, and a customs broker. A customs broker is a licensed professional or company that prepares and files the documents needed to clear goods for the importer. Each party has its own systems, hours, and ways of sharing status.
The table below compares domestic and cross-border tracking needs.
| Need | Domestic truckload | Cross-border load |
|---|---|---|
| Carriers per load | Usually one | Often two or three |
| Handoffs | Pickup and delivery | Pickup, yard, crossing, yard, delivery |
| Government step | None | Customs release on entry |
| Status sources | One carrier | Several carriers, broker, yards |
| Business hours | One country | Two countries, different holidays |
| Typical delay points | Traffic, breakdowns | Documents, inspections, missed handoffs |
Who uses cross-border visibility
Several teams depend on cross-border visibility. Logistics uses it to manage carriers. Purchasing uses it to know when imported materials will arrive. Production uses it to plan runs. Customer service uses it to answer customers. Finance uses it to match invoices to moves. An AI logistics coordinator should give each team the view it needs, from step-level detail for logistics to a simple date for customer service.
Why a single ETA is not enough
A single ETA from the final carrier tells you when the load might arrive. It does not tell you that the load has been sitting at a border yard for six hours because the crossing carrier was never dispatched. Visibility software for cross-border freight should show each step, so the team can see where time is being lost.
The cost of poor cross-border visibility
Poor cross-border visibility costs time and money. A trailer that waits a day at a yard may add yard fees and delay a production run. A missing document found at the border may hold the load until the shipper fixes it. A customer told the wrong date loses trust. An AI logistics coordinator that watches each step and follows up early reduces the number of days lost at the border.
Customs status is not carrier status
A carrier may report "at the border" while customs has not released the goods. A broker may report "released" while no carrier has picked up the trailer. These are two different facts. Software that merges them into one status makes it hard to know who must act. An AI logistics employee should show carrier and customs status side by side.
Border yards are blind spots
Border yards are where trailers wait between legs. Many yards do not share data electronically. A trailer can sit in a yard for a day while every carrier believes another party is moving it. Visibility software should treat yard arrival and yard departure as tracked events. An AI logistics coordinator can confirm both with the carriers involved when the yard does not report them.
Many cross-border carriers lack APIs
Many carriers that serve cross-border lanes are regional fleets. Some offer GPS tracking links; many do not offer APIs. An API, or application programming interface, is a direct system connection. Visibility software that relies only on APIs will have gaps on these lanes. The software must reach carriers by email, phone, or portal when needed.
What should the software track on each cross-border load?
The software should track each leg, each handoff, the customs broker's status, and the documents each step needs. An AI logistics coordinator should know the expected time for each step and flag any step that misses it.
Build the step list at booking
The step list should be built when the load is booked, not after a problem. At booking, the team knows the legs, the carriers, the yards, and the broker. An AI logistics coordinator that books the legs can create the step list at the same time, with expected times for each. A list built after the fact misses the early warning signs.
Steps to track
| Step | Evidence to track | Typical source |
|---|---|---|
| Origin pickup | Signed bill of lading or pickup confirmation | Origin carrier |
| Documents ready | Broker confirms documents are complete | Customs broker |
| Arrival at origin-side yard | Yard arrival time | Origin carrier |
| Crossing | Crossing carrier has the trailer and crossed | Crossing carrier |
| Customs release | Broker confirms release | Customs broker |
| Arrival at destination-side yard | Yard arrival time | Crossing carrier |
| Handoff to destination carrier | Pickup from the yard | Destination carrier |
| Delivery | Delivery confirmation and POD | Destination carrier |
A bill of lading, or BOL, is the shipping document that lists the freight and serves as a receipt. A POD, or proof of delivery, is the signed record that the receiver took the freight.
Plan crossing windows
Many crossings work best at certain times of day. Crossing carriers may run set schedules, and brokers may need documents by a cutoff to process a same-day release. Software should know these windows and plan each step to meet them. An AI logistics employee can flag a load that will reach the border too late for the planned crossing, so the team can adjust before the trailer sits overnight.
Expected times and holidays
Each step should have an expected time based on the plan and the parties' hours. Holidays differ between the United States, Mexico, and Canada. A broker closed for a national holiday cannot release goods that day. Software that ignores holidays will predict impossible dates. An AI logistics coordinator should apply each party's calendar where the team records it.
Reference numbers that follow the load
A cross-border load collects many reference numbers: the shipper's order, the origin carrier's load number, the crossing carrier's number, the broker's entry number, and the destination carrier's PRO or load number. A PRO number is the tracking number an LTL carrier assigns. Software should keep all of them on one record, so each party can be asked about the load using its own number. An AI logistics employee can collect each number as the load moves.
Documents as a tracked step
Documents often cause border delays. A commercial invoice missing a detail can hold a load. Treating "documents ready" as a tracked step, confirmed by the broker before pickup, catches many problems early. The shipper and broker own the documents; the AI logistics employee can track whether they are confirmed.
Southbound and northbound loads
Exports and imports follow different steps. A southbound load into Mexico needs Mexican customs clearance and often a Mexican broker. A northbound load into the United States needs U.S. clearance and a U.S. broker. Each direction has its own documents, brokers, and typical delays. Software should handle both, and an AI logistics employee should apply the right steps to each direction.
Through service versus split legs
Some loads use one carrier for the whole move. Others split the move among carriers. Software should handle both. For split legs, it should show which carrier holds the freight at each step.
Hypothetical example: tracking a split move
This example is hypothetical and does not describe a real customer. An auto parts supplier ships from Saltillo to a plant in Ohio. The move uses a Mexican carrier to a Laredo-area yard, a crossing carrier, and a U.S. carrier to Ohio. The AI logistics coordinator tracks eight steps. On Tuesday, the broker confirms release at 11 a.m., but the U.S. carrier has not picked up by 3 p.m. The coordinator contacts the U.S. carrier, which had the wrong yard address. The carrier corrects it and picks up by 5 p.m. Delivery holds for Thursday.
How should the software respond when a cross-border step stalls?
When a step stalls, the software should identify the owner, contact them, and update the plan. An AI logistics coordinator should start follow-up as soon as a step misses its expected time, because border windows and yard hours can turn a short delay into a lost day.
Start with the stalled step's owner
Contact the owner of the stalled step first. The broker owns customs, the crossing carrier owns the crossing, and the destination carrier owns the final leg. An AI logistics coordinator saves time by asking the right party first.
Response by stalled step
| Stalled step | First contact | Typical fix |
|---|---|---|
| Documents not ready | Shipper and broker | Send missing document |
| Origin pickup late | Origin carrier | Confirm new time, adjust crossing plan |
| Crossing not dispatched | Crossing carrier | Dispatch with yard reference |
| Customs not released | Broker | Wait for release; confirm what is pending |
| Handoff missed | Destination carrier | Redirect driver or rebook from approved list |
| Delivery late | Destination carrier | Confirm new time, update receiver |
Escalate early on high-value loads
High-value or time-critical cross-border loads deserve faster escalation. A stall of two hours may be fine for a routine load and serious for a load that feeds a production line. An AI logistics coordinator can apply shorter escalation times to loads marked critical, so a person steps in sooner.
Rebooking a leg
If a carrier on one leg cannot perform, the replacement should come from the approved list for that leg. 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.
Hypothetical example: a document hold found before pickup
This example is hypothetical and does not describe a real customer. A furniture maker plans a northbound load from Tijuana to Los Angeles. The day before pickup, the AI logistics coordinator asks the broker to confirm documents are complete. The broker reports a missing certificate. The coordinator alerts the shipper's export contact, who sends it that afternoon. The broker confirms documents complete before pickup, and the load crosses on schedule.
Customs delays need the broker
If customs has not released the goods, the broker owns the next step. The software should not promise a release time. It can ask the broker for status and pass on what is missing. Wilson does not perform customs clearance.
Recalculate the rest of the move
A stall at one step shifts every step after it. A crossing that slips from Tuesday morning to Tuesday evening may miss the destination carrier's last pickup and push delivery a day. The software should recalculate each later step and check it against business hours. An AI logistics coordinator should then confirm the new plan with the carriers involved.
Telling the customer
The customer needs one verified delivery date and a short reason when the date changes. Too many step-by-step messages confuse customers. An AI logistics coordinator should send internal teams the details and customers the outcome.
Record the cause of every stall
Each stall should have a recorded cause: documents, late pickup, missed dispatch, customs hold, or missed handoff. The causes show which steps need attention on each lane. An AI logistics coordinator can tag each stall when it is resolved, so lane reviews use facts instead of memory.
Common mistakes in stall response
- Waiting for the final ETA to move. By then, the stall has cost a day.
- Asking the wrong party. The carrier cannot answer a customs question.
- Rebooking with an unapproved carrier. A new risk at a sensitive point.
- Not updating later steps. The destination carrier arrives at an empty yard.
Which questions should you ask cross-border visibility vendors?
Ask vendors how they track each party, how they handle carriers without APIs, how they show customs status, and what they do when a step stalls. An AI logistics coordinator should be able to answer each question with a demonstration on your lanes.
Ask for a real timeline
Ask each vendor to show the full timeline of a past cross-border load from one of its customers, with names removed. A real timeline shows what the tool actually records: each step, each source, each time. A scripted demo can hide gaps that a real record reveals.
Coverage questions
- Which of our cross-border carriers can you track, and how?
- How do you get status from carriers without APIs?
- How do you get status from our customs brokers?
- Can you track yard arrivals and departures?
- How do you handle holidays in each country?
Integration questions
- How does the software receive orders from our ERP or other systems?
- Can it send status back to our systems, or does a person update them?
- How does it share status with our customs broker?
An ERP, or enterprise resource planning system, holds orders and customer data. Not every connection writes data back, so the answers matter for how much manual updating remains.
Action questions
- What happens when a step misses its expected time?
- Who receives each alert, and what does it include?
- Can you rebook a leg from our approved list within our rules?
- How do you tell our customer about a changed date?
- How are actions recorded?
Communication questions
Cross-border carriers and yards may prefer to communicate in Spanish or French. Ask how the vendor handles communication with parties who work in a language other than English. This is a practical question for many Mexico and Quebec lanes. Ask to see examples rather than assume.
Escalation questions
- Who receives an alert when a step stalls past a set time?
- Can escalation rules differ by lane, customer, or load value?
- How does the system handle a stall outside business hours on either side of the border?
An AI logistics coordinator should escalate with the full history of what was checked and when.
Data and record questions
- Can we export the full timeline of a cross-border load?
- How long are records kept?
- Can we see delays by step, party, and lane?
Hypothetical example: a vendor question that mattered
This example is hypothetical and does not describe a real customer. A distributor evaluating two tools asks each to show how it would track a crossing carrier with no API that answers only by phone. One vendor says the customer's team would need to call. The other shows its AI logistics coordinator calling the carrier where configured and recording the answer. The distributor's coordinators spend much of their day on these calls, so the answer decides the evaluation.
How should you run the evaluation?
Run the evaluation on your own lanes, with your own carriers and broker, using a set of scenarios that includes at least one handoff problem and one document problem. An AI logistics coordinator should be scored on what it caught, what it did, and what it recorded.
Demo tests for cross-border visibility
| Buyer requirement | Demo test | Evidence to see |
|---|---|---|
| Step-level tracking | Run a split-leg load | Each step shown with owner and time |
| Separate customs status | Delay the broker's release | Customs status shown apart from carrier status |
| Non-API carriers | Use a crossing carrier without an API | Status obtained by email or phone |
| Handoff stall | Skip the destination carrier pickup | Flag and follow-up with that carrier |
| Document problem | Hold documents before pickup | Shipper and broker contacted |
| Holiday handling | Run a load over a national holiday | Dates adjusted |
| Customer update | Change the delivery date | One verified date sent |
Score the effort, not only the result
Count how many minutes each scenario took from your team. A tool that catches every stall but leaves your coordinators to make every call saves little time. An AI logistics coordinator should cut the follow-up effort, not only show the problem.
Demo questions about cross-border visibility
- How does the AI logistics coordinator build the step list for each load?
- How often does it check each step?
- How does it decide a step is late?
- Which follow-ups run within rules, and which need a person?
- How does it handle a broker who shares status only by email?
- Can it show delays by step for each lane over time?
Include a stall outside business hours
Run one stall in the evening or on a weekend. Border parties often work different hours. Watch whether the AI logistics coordinator follows up within the off-hours rules and whether the morning team starts with a clear summary.
How to measure cross-border visibility work
Track how many stalls were caught before they changed the delivery date. Count how many date changes were traced to a specific step. Measure how much person-time follow-up took before and after. These measures show whether the AI logistics employee improves cross-border execution, not only reporting.
Use your own broker in the test
Ask the vendor to include your actual customs broker in the test, or at least to show how it would receive status from that broker. Brokers differ in how they share information. A tool that works with one broker's portal may not work with your broker's email updates.
Scoring the cross-border visibility demo
Score each test as pass, partial, or fail. A pass means the stall was caught at its step, the right party was contacted, and the customer got one verified date. A partial means the stall was seen but a person did the follow-up. A fail means only the final ETA was tracked.
Warning signs in a cross-border visibility demo
- Only the final carrier's ETA appears.
- Customs status is missing or mixed with carrier status.
- Carriers without APIs show "no data."
- Holidays are ignored.
- The demo uses a single carrier for a through move only.
Where does Wilson fit in cross-border visibility?
Wilson, by Cartage, is an AI logistics coordinator that supports cross-border workflows within the agreed customer scope. It tracks each load as part of executing it, follows up with carriers when steps slip, and informs the people who need to know. It is not a standalone visibility platform.
Wilson replaces the TMS for freight execution and connects to the company's ERP through a method that fits the customer's environment. It tracks each load using the best source available, including carrier APIs, GPS or ELD data where it exists, carrier websites, and email or direct outreach, including calls where configured. An ELD, or electronic logging device, records a truck's location and the driver's hours.
Carriers and rules
Wilson uses the customer's approved carriers for each leg and negotiates against the customer's rate targets within configured rules and approval limits. Rates outside those limits go to the logistics team. Cartage can present additional carrier capacity, but the customer approves any carrier before Wilson uses it.
What Cartage asks about cross-border visibility in discovery
Cartage asks which cross-border lanes the team runs, how each is split into legs, which brokers handle clearance, and how status is shared today. These answers shape the steps an AI logistics coordinator tracks and the follow-up it runs.
What Wilson does not do for cross-border visibility
Wilson does not perform customs clearance or predict government release times. It does not claim route or network optimization. The specific legs and parties in scope should be agreed during discovery. Communication needs for non-English-speaking parties should be confirmed in a demo. Exact ERP connection details depend on the customer's systems.
Lane reports on request
Over time, the step records show where each lane loses time. One lane may stall most often at documents; another at the destination handoff. Wilson can use shipment data from the loads it runs to produce carrier-performance and lane-rate reports on request. Teams can use those reports to fix the step that causes the most delay.
Where teams start with cross-border visibility
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 one high-volume cross-border lane.
Teams preparing vendor questions can read a list of cross-border freight software questions. Teams shipping to Mexico and Canada can see how to compare cross-border freight software for Mexico and Canada. Both topics shape how an AI logistics coordinator should be tested. Teams running several modes can review how LTL, parcel, and cross-border freight fit one workflow.
FAQs
How should you evaluate visibility software for cross-border shipments?
Test it on your own lanes with every leg, handoff, and broker status, and judge it by what it does when a step stalls. An AI logistics coordinator should track each step and follow up with the right party.
Why is a single ETA not enough for cross-border freight?
It hides where delays start. An AI logistics employee should show each step, so the team knows whether a delay is at the yard, the border, or the final leg.
Can visibility software track carriers without APIs?
It should, using email, phone, or portals. An AI logistics coordinator can reach carriers through the channels they use.
Does cross-border visibility software clear customs?
No. A licensed customs broker handles clearance. An AI logistics employee can track the broker's status and tell the shipper what is missing.
Sources
- Cartage, Wilson product scope, October 2026: https://cartage.ai
Ask Cartage to run one of your cross-border lanes and show how an AI logistics coordinator tracks each leg, separates customs status from carrier status, and follows up on a stalled handoff: talk to the Cartage team.