How should freight software match a pickup-change email to a load?
Key Takeaways
Freight software should match a pickup-change email to a load by reading every reference in the email, following the email thread, and comparing the details with open loads for that carrier. When the match is not certain, it should ask the carrier instead of guessing. An AI logistics coordinator should only change a load when it is sure the email belongs to it.
- Matching means deciding which shipment an email is about.
- The strongest matches use exact references: the shipper's load number, the purchase order, or the carrier's own load number.
- The email thread is often the best clue, because many replies have no number at all.
- Weaker clues, such as city and date, need a second check.
- A wrong match is worse than a slow match, because it changes the wrong freight and misses the right one.
- Wilson, by Cartage, is an AI logistics coordinator that reads carrier emails, matches them to shipments, and asks carriers to clarify when the match is unclear.
Why is matching a carrier email to a load hard?
Matching is hard because carriers write in many styles, use their own numbers, and often reply without any reference at all. An AI logistics coordinator needs several ways to match, ranked from strongest to weakest.
One carrier writes "Load 4410 moving to Thursday." Another writes "Your Dallas pickup tomorrow is now 3 p.m." A third replies "Can't make it, how about Friday?" to a thread from last week. A fourth forwards the shipper's original email with a note on top. Each email is about one load, but each gives different clues. Software that only looks for one kind of number will miss most of them.
The table below lists common clues and how strong each one is.
| Clue | Example | Strength |
|---|---|---|
| Shipper's load number | "Load 4410" | Strong |
| Purchase order number | "PO 55102" | Strong |
| Carrier's load or trip number | "Our trip 88231" | Strong if saved at booking |
| PRO number | "PRO 4418823" | Strong for LTL |
| BOL number | "BOL 7720" | Strong |
| Email thread | Reply to the tender email | Strong if the thread was tied to a load |
| Pickup city and date | "Dallas pickup Wednesday" | Medium |
| Consignee or destination | "the Atlanta load" | Medium |
| Weight or pallet count | "the 18-pallet load" | Weak alone |
A purchase order, or PO, is the document a customer uses to place an order. A PRO number is the tracking number an LTL carrier assigns. A bill of lading, or BOL, is the shipping document that lists the freight and serves as a receipt. A consignee is the party receiving the freight.
Subject lines help
Many carriers put the key reference in the subject line, such as "Load 4410 pickup change." Others leave the subject from the original email, which may already hold the shipper's load number. Reading the subject first often settles the match. An AI logistics coordinator should read the subject, the body, and any quoted text.
Carriers use their own numbers
Many carriers track loads by their own trip or load numbers, not the shipper's. If the shipper saved the carrier's number at booking, it becomes a strong clue. If not, the carrier's number means nothing to the shipper's system. An AI logistics employee should save the carrier's number from the tender acceptance.
Open loads narrow the search
Matching should search open loads first: loads that are booked but not yet picked up or delivered. A pickup change for a load that already delivered makes no sense. Limiting the search to open loads with that carrier reduces wrong matches. An AI logistics coordinator can filter by carrier, status, and date before comparing details.
Many replies have no number
People reply to the last email without retyping references. A reply like "Can we push to Friday?" has no number, but it sits in a thread. If the thread started with a tender for load 4410, the reply is about load 4410. Software that ignores threads loses this clue.
Who sees the email first
Carrier emails often land in several places: a coordinator's inbox, a shared logistics inbox, and sometimes a sales or customer service inbox. Each person may try to match the email in their own way. Central matching, done once and recorded on the load, avoids duplicate work and conflicting updates. An AI logistics coordinator can read the agreed inboxes and match each email once.
Volume makes matching a daily task
A shipper with many open loads may receive dozens of carrier emails a day. Matching each one by hand takes minutes. Across a week, that is hours of searching. Most of those matches are routine and follow the same patterns. An AI logistics employee can handle the routine matches and leave people only the unclear ones.
The cost of a wrong match
A wrong match changes the wrong load. The right load keeps the old time, and the carrier arrives when nobody expects it. The wrong load gets a new time it never needed. Two shipments are now wrong. That is why a careful match matters more than a fast one.
How should the software match, step by step?
The software should try the strongest clues first, then weaker clues, and ask the carrier when no strong clue settles the match. An AI logistics coordinator should record which clue it used for each match.
Why the order matters
Strong clues should win over weak ones. If an email says "PO 55102" and also "Dallas pickup," and the PO points to a Houston load, the PO is more likely right and the city may be a mistake. That conflict should trigger a question. An AI logistics employee should follow the order and flag conflicts between clues.
A practical matching order
Exact references. Look for the shipper's load number, PO, BOL, or PRO.
Carrier references. Look for the carrier's trip or load number saved at booking.
Thread. If the email is a reply, find the load the thread belongs to.
Attachments. Read any attached confirmation or BOL for references.
Details. Compare pickup city, date, consignee, and size with open loads for that carrier.
Confirm. If more than one load fits, ask the carrier which one.
Save references at booking
Matching gets easier when every reference is saved at booking: the shipper's load number, the PO, the carrier's trip number, the PRO number when assigned, and the BOL number. Each saved reference is another way to match a future email. An AI logistics coordinator can save every reference from the tender, the acceptance, and the documents as the load moves.
Combine clues when one is weak
When no single clue is strong, combine several: carrier, city, date, destination, and size. If they all point to one load, the match is likely. An AI logistics coordinator can weigh clues together before acting.
Check the sender
The email should come from the carrier that holds the load. A change from a carrier with no open loads at that facility is a warning sign. It may be a wrong address, a mistake, or, rarely, fraud. An AI logistics employee should check that the sender's company matches the booked carrier.
Record the clue used
For every match, save which clue was used: load number, thread, carrier trip number, or details confirmed with the carrier. If a match is ever questioned, the record shows why it was made. An AI logistics employee can store the clue next to the email on the load.
Confidence levels
| Level | When | Action |
|---|---|---|
| Certain | Exact reference or thread match with matching details | Act on the email |
| Likely | One open load fits the details, no reference | Act, and confirm with the carrier in the reply |
| Unclear | Several loads fit, or details conflict | Ask the carrier before acting |
| No match | No open load fits | Ask the carrier; check for errors |
Confirm "likely" matches in the reply
When a match is likely but not certain, the reply to the carrier can confirm it. For example: "Confirming load 6612 (Dallas to Memphis, 18 pallets) moves to Thursday 9 a.m." If the carrier meant another load, it will say so. This keeps work moving while still checking. An AI logistics coordinator can phrase replies to confirm both the load and the change.
Hypothetical example: a reply with no number
This example is hypothetical and does not describe a real customer. A carrier replies "Need to push this one to Thursday" to an email thread. The thread began with the tender for load 6612. The AI logistics coordinator matches the reply to load 6612 through the thread, checks that the carrier is the one booked, and confirms: "Load 6612 pickup moved to Thursday 9 a.m.?" The carrier replies "Yes." The coordinator updates the load.
Ask questions that are easy to answer
When asking the carrier which load, give it choices it can recognize: its own trip number, the destination, the pallet count. A question that lists only the shipper's numbers may mean nothing to the dispatcher. An AI logistics employee can include the details the carrier uses to tell loads apart.
Hypothetical example: two loads fit
This example is hypothetical and does not describe a real customer. A carrier emails "Tomorrow's Chicago pickup is moving to 2 p.m." The shipper has two loads with that carrier picking up in Chicago tomorrow. The AI logistics coordinator does not guess. It replies: "We have two pickups with you in Chicago tomorrow: load 7101 (12 pallets, to Detroit) and load 7104 (8 pallets, to Columbus). Which one moves to 2 p.m.?" The carrier answers "7104." Only that load changes.
How should the software handle tricky emails?
The software should handle tricky emails, such as forwards, attachments, multi-load messages, and vague wording, by reading every part and asking when the meaning is unclear. An AI logistics coordinator should not treat a tricky email as a simple one.
Read before acting
Read the whole email, including quoted text and attachments, before deciding. An AI logistics coordinator should never act on the first line alone.
Forwarded emails
A carrier may forward the shipper's original email with a new note on top. The references are in the forwarded part. The software should read the whole message, not only the top line.
Images and scanned documents
Some carriers send a photo or a scan instead of a typed email. The references may be inside the image. The software should read scanned documents where possible, or ask the carrier to type the key numbers. An AI logistics employee can read common document types and ask when the image is unclear.
Attachments
Some carriers attach a revised load confirmation or a new BOL. The attachment holds the references and the new time. The software should read the attachment and compare it with the booking.
Partial information
Sometimes an email gives the new time but not the date, or the date but not the time. The software should not fill the gap with a guess. It should ask for the missing part. A short reply such as "Thanks. What time on Thursday?" keeps the record precise. An AI logistics coordinator can ask for the missing detail before updating.
One email, several loads
A dispatcher may write about three loads in one email: "4410 moves to Thursday, 4411 stays, 4415 moves to Friday." The software should split the email and apply each line to its own load. An AI logistics employee can confirm each change separately.
Replies in other languages
Some carriers, especially on cross-border lanes, may write in Spanish or French. The matching should still read references, which are usually numbers, and the meaning of the change. Language handling should be confirmed for the customer's carriers in a demo. An AI logistics coordinator should ask for clarification when it is not sure what the message means.
Note the matched load in the reply
Name the load in every reply. An AI logistics coordinator can include the load number so the carrier sees which load changed.
Vague wording
Some emails do not say what changed clearly: "Running behind on the Dallas one." The software should ask for the specific new time. Vague wording should never become a recorded change.
Emails meant for another shipper
Dispatchers handle many shippers. Sometimes an email meant for another shipper arrives by mistake. If no open load fits, the email may not be for you. Reply politely and say so. An AI logistics coordinator can recognize when no load matches and ask the carrier to check.
New sender, same carrier
A new dispatcher may write from a personal address or a new email. The software should check the signature and the carrier name, and, if unsure, confirm with a known contact before acting.
Ask carriers to include references
The easiest fix is upstream. Ask each carrier, in the tender or a routing guide, to include the load number or PO in every email. A routing guide is a document that tells carriers how to work with the shipper. Carriers that follow it make matching nearly automatic. An AI logistics coordinator can remind carriers that leave references out.
Common matching mistakes
- Matching on city and date alone. Picks the wrong load when there are several.
- Ignoring the thread. Misses replies without numbers.
- Reading only the top of the email. Misses forwarded references and attachments.
- Applying a multi-load email to one load. Leaves the others unchanged.
- Trusting any sender. Risks acting on a wrong or false message.
What should happen after the email is matched?
After the email is matched, the software should attach it to the load, read the change, check the impact, confirm with the carrier, and update the record and the people affected. An AI logistics coordinator should keep the match and the change together in the record.
Keep the thread tied to the load
Once a thread is tied to a load, every later reply in that thread should follow. This makes future matches easy. If a carrier starts a new thread, tie that one too. An AI logistics employee can keep a list of threads linked to each load.
Attach the email to the load
Save the email with the shipment record so anyone can see it later. The record should show which clue was used to match it. If the match was confirmed with the carrier, save that reply too. Wilson keeps searchable shipment records with change history.
Matching is the first step, not the last
A correct match only tells you which load the email is about. The change still needs to be checked, confirmed, recorded, and shared. Software that stops at matching leaves most of the work. An AI logistics employee should carry each matched email through to a confirmed update.
Read and check the change
Once matched, read the requested change and check dock availability, freight readiness, and the delivery promise. Accept, counter, or rebook within the shipper's rules.
Tell the people who depend on the load
After the change is confirmed, the dock, customer service, and sometimes the customer need to know. The match decides which load's contacts get the update, which is another reason a correct match matters. An AI logistics coordinator can send each update to the contacts tied to the matched load.
Confirm and update
Confirm the change in writing to the carrier, update the record with history, and tell the dock and others who depend on the time. Wilson sends internal updates through channels such as Slack, Microsoft Teams, or email.
Correct a wrong match quickly
If a wrong match happens, fix it at once. Move the email to the right load, restore the wrong load's original time, and tell anyone who acted on the wrong change. Record what happened so the same mistake is less likely. An AI logistics employee can reverse the change and keep both versions in the history.
Reply in the same thread
Reply in the thread the carrier used, so the next message stays linked. An AI logistics employee can keep every reply in-thread.
Learn from each match
Each confirmed match teaches the software how that carrier writes. One carrier always uses its trip number; another always replies in-thread. Using these patterns makes the next match faster and safer. An AI logistics employee can note each carrier's habits.
How should you evaluate email matching in freight software?
Evaluate email matching by giving the software a set of real carrier emails, including vague, forwarded, and multi-load ones, and checking every match. An AI logistics coordinator should be right on clear cases and ask on unclear ones.
Judge safety, not only speed
A tool that matches every email instantly but sometimes wrongly is risky. Ask how often the vendor's tool asks for clarification. A good AI logistics coordinator asks when it should.
Demo tests for email matching
| Buyer requirement | Demo test | Evidence to see |
|---|---|---|
| Exact references | Email with load number | Correct load matched |
| Carrier numbers | Email with carrier trip number only | Correct load via saved number |
| Threads | Reply with no number | Matched through the thread |
| Attachments | Revised confirmation attached | References read from attachment |
| Ambiguity | Email fitting two loads | Carrier asked which one |
| Multi-load email | Three loads in one email | Each applied to its own load |
| Sender check | Email from an unknown sender | Confirmed with known contact first |
Test a forwarded email with a note
Forward an old shipper email with a carrier note on top, as many dispatchers do. Watch whether the AI logistics coordinator reads the forwarded references and matches the load correctly.
Demo questions about email matching
- Which references does the AI logistics coordinator look for?
- Does it save carrier load numbers at booking?
- How does it use email threads and attachments?
- What does it do when several loads fit?
- How does it check the sender?
- How is the match recorded?
Ask how unclear cases are tracked
Ask how the vendor tracks emails waiting for a carrier's clarification. They should not be lost while waiting. An AI logistics coordinator should keep a list of open clarifications and follow up if the carrier does not answer.
How to measure email matching work
Count emails matched correctly without a person. Count clarification questions and how fast carriers answered. Track any wrong-load updates. These measures show whether the AI logistics employee matches safely and quickly.
Use a week of your carriers' emails
Give the vendor a week of real carrier emails. Your carriers' habits, typos, and missing numbers make the best test. Count how many the AI logistics coordinator matched correctly, how many it asked about, and whether any were matched wrongly.
Scoring the email matching demo
Score each test as pass, partial, or fail. A pass means the right load was matched, or the carrier was asked when unclear. A partial means the right load was found but only after a person searched. A fail means the wrong load was changed.
Warning signs in an email matching demo
- Matching works only with the shipper's load number.
- Threads and attachments are ignored.
- The tool guesses when several loads fit.
- No record of how each email was matched.
Where does Wilson fit in matching pickup-change emails?
Wilson, by Cartage, is an AI logistics coordinator that reads carrier emails, matches them to shipments, and asks carriers to clarify when a match is unclear. It works with carriers through email, API, EDI where the carrier supports it, and phone 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 uses an email address on the customer's own domain, so carrier replies reach it in the same threads the team already uses.
Records that make matching easier
Wilson saves the tender, the carrier's acceptance, and documents with each load, including the references they contain. Those saved references give future carrier emails more ways to match.
What Cartage asks about email matching in discovery
Cartage asks which inboxes carriers write to, which references carriers usually include, and how often carriers reply without numbers. These answers shape how an AI logistics coordinator matches emails for the customer.
What Wilson does not do for email matching
Wilson does not act on an email it cannot match with confidence; it asks. Specific inbox setup and matching rules should be confirmed in a demo. Exact ERP connection details depend on the customer's systems.
Reports on matching
Over time, records show which carriers usually include references and which do not. Teams can ask carriers that rarely include numbers to add them. Wilson can use shipment data from the loads it runs to produce carrier-performance reports on request.
Where teams start with email matching
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 shared inbox that receives the most carrier email.
Teams keeping carrier email in order can read how carrier emails are matched to the right shipment. Teams adding context to messages can see how a manufacturer can route carrier emails with shipment context. Both topics shape how an AI logistics coordinator matches email. Teams worried about missed replies can review what happens when a carrier reply is missed.
This article is part of our complete guide to freight pickup confirmations, changes, and missed pickups and our guide to carrier email and shared freight inboxes.
FAQs
How should freight software match a pickup-change email to a load?
Use exact references first, then carrier numbers, the email thread, attachments, and finally details like city and date. An AI logistics coordinator should ask the carrier when the match is not certain.
What if the carrier's email has no load number?
Use the email thread and the details, and confirm with the carrier if more than one load fits. An AI logistics employee should not guess.
What if one email mentions several loads?
Split the email and apply each change to its own load, confirming each. An AI logistics coordinator should not apply a multi-load email to one load.
Why check who sent the email?
A change from an unknown sender could be a mistake or fraud. An AI logistics employee should confirm with a known carrier contact before acting.
Sources
- Cartage, Wilson product scope, October 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator matches a carrier reply with no load number to the right shipment, and asks the carrier when two loads could fit: talk to the Cartage team.