How can freight software record why a carrier was selected?
Key Takeaways
Freight software can record why a carrier was selected by saving the full decision with the load: which carriers were asked, what each one answered, which rule was applied, why the winner was chosen and who approved it if approval was needed. An AI logistics agent such as Wilson, by Cartage, builds this record as part of the work, because it is the one requesting the quotes, comparing them and tendering the load. Nobody has to write a note after the fact.
- A selection record answers one question: why this carrier, at this price, on this load?
- It should include the carriers that did not answer and the quotes that lost, not only the winner.
- The rule matters as much as the result. "Lowest total cost that meets the date" explains the choice; "Carrier A" does not.
- Approvals should be recorded with the person, the time and what they saw.
- The record should be created when the decision is made, not reconstructed later from email.
- The same record later checks the invoice and supports carrier reviews.
What should a carrier selection record contain?
A carrier selection record should contain the request, every response, the comparison, the rule, the decision and any approval. An AI logistics agent can capture all of these because each one is a step it performs. The table lists the fields and the question each one answers.
| Field | What it holds | Question it answers |
|---|---|---|
| Shipment details sent | Lane, dates, weight, count, accessorials | Did every carrier price the same thing? |
| Carriers asked | The approved carriers contacted, and when | Was the right list used? |
| Responses | Each quote with all charges, transit, validity, conditions | What were the real options? |
| Non-responses | Carriers that did not answer by the deadline | Who was unavailable? |
| Rule applied | The lane rule in force at the time | What was the basis for the choice? |
| Ranking | The quotes in order under that rule | Where did each carrier land? |
| Decision | The chosen carrier and the reason in plain words | Why this carrier? |
| Approval | Who approved, when, and what they saw | Was an exception authorized? |
| Tender and acceptance | The tender, the written acceptance, the rate confirmation | Did the carrier commit to these terms? |
Why record the losing quotes?
The losing quotes matter because they show the decision was fair and they make later questions easy. If finance asks why a load cost $1,450, the answer is stronger with the three other quotes beside it. If a carrier asks why it never wins on a lane, the record shows how far its quotes were from the winner. Losing quotes also show market movement on the lane over time, which helps when the team reviews its rate targets.
Why record carriers that did not answer?
Carriers that did not answer are part of the decision, because the winner was chosen from those available. If the primary carrier on a lane did not respond, that explains why a backup was used. Over several weeks, the non-answers also show which carriers are reliable responders on each lane. A carrier that rarely answers may not belong on the quote list for that lane.
Where should the record live?
The record should live with the load, not in a separate report or a shared drive. When someone opens the load, they should see the selection next to the tracking, the documents and the invoice. A record stored elsewhere tends to fall out of sync: the load is rebooked, but the spreadsheet still shows the first carrier. Keeping everything on one load record also makes the history searchable by order number, carrier number, lane or date.
How detailed should each quote be?
Each quote should be detailed enough to rebuild the comparison without asking the carrier again. That means the base rate, fuel, each accessorial, any minimum charge, the total, the transit time, the pickup window, the validity and any condition. The original reply should be attached as well, because the structured fields are an interpretation of what the carrier wrote. If a dispute arises, the original wording settles it.
Why does it matter to record the reason?
Recording the reason matters because freight decisions get questioned later, often by people who were not there. An AI logistics agent that records the reason with every load protects the team from reconstructing decisions from memory. The common situations are predictable.
| Who asks | When | What they want to know |
|---|---|---|
| Finance | Month-end or budget review | Why a load cost more than the lane average |
| Logistics lead | Weekly or monthly review | Whether the rules are working |
| Customer | After a late or damaged delivery | Why that carrier was used |
| Carrier | When it stops winning loads | Why another carrier was chosen |
| Auditor or compliance | Periodic review | Whether approvals followed policy |
| New team member | Taking over a lane | How decisions have been made |
Why do carriers ask?
Carriers ask because they want more of your freight and need to know how to win it. A carrier that quotes often and never wins may lower its rates, improve its service or stop quoting. Sharing the general reason, such as "your rate was 9% above the winning quote" or "your transit time missed the delivery date", helps the carrier compete and helps the company keep a healthy pool of carriers on each lane. A selection record makes these answers easy to give without sharing other carriers' prices.
What happens without a record?
Without a record, the reason lives in someone's inbox or memory. A hypothetical example: a customer complains about a late delivery and asks why the company used a carrier with a weak record on that lane. The coordinator who booked the load is on vacation. The emails are in a personal mailbox. Nobody can show that the usual carrier declined and the backup was the only option that met the date. The team looks careless, even though the decision was sound.
Does the record matter for small shipments?
The record matters for small shipments too, because small shipments add up. A company may move hundreds of LTL and parcel shipments a month. Each one is a small decision, but together they are a large share of freight spend. Patterns only show up when every shipment has a record: one carrier winning most small loads on a lane, accessorials creeping up, or quotes that are often incomplete. A system that records every selection automatically makes this possible without extra work.
Is a note in a spreadsheet enough?
A note in a spreadsheet is better than nothing, but it depends on someone remembering to write it, and it is separate from the load. Notes are usually written at the end of a busy day, if at all, and they rarely include the losing quotes or the exact rule. A record built by the system that made the comparison is complete by default and sits with the load.
How does the record get built during the work?
The record gets built during the work when the same system requests the quotes, reads the replies, applies the rule and tenders the load. An AI logistics agent like Wilson does each of those steps, so each step leaves its trace automatically. The steps are:
- Request. The shipment details and the approved carrier list are saved with the request time.
- Responses. Each reply is read into the same structure, with the original email or file attached.
- Clarifications. Questions to carriers and their answers are saved, such as a missing liftgate charge.
- Comparison. Quotes are ranked under the lane rule in force that day.
- Negotiation. If the best quote is above target, the negotiation messages are saved.
- Decision or approval. The chosen carrier is recorded with the reason; if approval was needed, the request and the answer are saved.
- Tender and acceptance. The tender, the written acceptance and the rate confirmation complete the record.
What does a full record look like for one load?
A hypothetical record for one truckload shows the pieces together. The order is a dry van from a plant in Indiana to a customer in Texas, pickup Tuesday, delivery Thursday.
| Step | Recorded detail |
|---|---|
| Request | Sent Monday 9:02 a.m. to four approved carriers; answer due 11:00 a.m. |
| Carrier A | $2,980 all-in, Thursday delivery, valid until Monday 5 p.m. |
| Carrier B | $2,860, Friday delivery |
| Carrier C | $3,050, Thursday delivery |
| Carrier D | No answer by 11:00; reminder at 10:30 |
| Rule | Lowest total cost that meets the Thursday delivery |
| Decision | Carrier A: lowest that meets Thursday; Carrier B misses the date |
| Approval | Not needed; within the lane limit |
| Tender | Sent 11:06 a.m.; accepted in writing 11:41 a.m. |
| Rate confirmation | On file, $2,980 all-in |
Anyone can read this table and understand the decision in seconds.
What should the reason look like?
The reason should be one or two plain sentences that a person outside logistics can read. For example: "Lowest total cost among approved carriers that met the Thursday delivery. Primary carrier declined." Or: "Second-lowest quote chosen because the lowest had two missed pickups on this lane in the last month; within the 5% service premium allowed by the lane rule." The reason should name the rule, not just the outcome.
What if two quotes tie?
When two quotes tie under the rule, the record should show the tiebreaker used. Common tiebreakers include the carrier's recent on-time record on the lane, whether the carrier is a contract carrier, the earlier pickup window or the faster transit. The tiebreaker should be part of the lane rule, so the decision is not made by whoever happens to look first. If there is no written tiebreaker, the decision goes to a person and the person's choice is recorded.
Should the rule be saved with the load?
The rule should be saved as it was at the time of the decision. Rules change. A lane rule that allowed a 5% premium in October may allow 3% in December. If the record only links to the current rule, an old decision can look wrong. Saving the rule with the load keeps the decision understandable later.
How are negotiations recorded?
Negotiations are recorded as messages and outcomes. Wilson negotiates rates against the customer's rate targets under configured rules and approval limits. The record shows the first offer, each counter, the final rate and whether it came within the target. If the negotiation ended above the target and went to approval, the approver sees the full exchange.
How should multi-stop or multi-mode loads be recorded?
Multi-stop and multi-mode loads should be recorded as one decision with clear parts. A multi-stop truckload has one carrier but several deliveries, each with its own appointment and possibly its own charges. A cross-border move may use a domestic carrier, a border crossing and a carrier on the other side. An import may combine ocean, drayage and a final truckload. The record should show the selection for each part and how the parts connect, so a delay or a charge on one part can be traced to the right decision.
How are approvals recorded?
Approvals are recorded with the approver's name, the time, the channel and what they were shown. If the approver saw three quotes and approved the second-lowest, that is in the record. If the approver changed the decision, the change is recorded too. This makes approvals reviewable without asking the approver to remember.
Which selection decisions need extra detail?
Some selection decisions need extra detail because they depart from the usual rule. An AI logistics agent should add context whenever the chosen carrier is not the one the rule would normally pick. These are the decisions that get questioned.
| Situation | Extra detail to record |
|---|---|
| Higher-priced carrier chosen | The service reason and the approval |
| Primary contract carrier skipped | Why: declined, no answer, no capacity, service issue |
| Carrier outside the usual lane list | Who approved and why |
| Rebooking after a cancellation | The original carrier, the cancellation and the time pressure |
| Mode change, such as LTL to partial truckload | The comparison across modes and who approved |
| Expedited or premium service | The customer or production reason |
How should rebooking decisions be recorded?
Rebooking decisions should be recorded as a new selection linked to the original. When a carrier cancels, Wilson detects the cancellation, contacts the carrier, tells the team and starts rebooking from the approved carrier list, automatically within the rules or with approval. The rebooking record shows the original booking, the cancellation message, the new quotes and the new decision. If the new rate is higher, the reason is clear: the original carrier cancelled the day before pickup.
How should a carrier's past performance be noted?
When past performance affects a decision, the record should say what was considered and where it came from. For example: "Carrier B not chosen: two missed pickups on this lane in the last 30 days, per load records." This keeps the decision fair and explainable. It also protects the company if a carrier asks why it lost a load. The source should be the company's own load history, not an impression.
What about decisions made by phone?
Decisions made by phone should be recorded the same way. If the coordinator calls a carrier and agrees a rate, the rate and the terms should be confirmed in writing and saved to the load. Wilson can make calls to carriers where configured and records what was said with the time and the source. A rate agreed by phone is only booked when the rate confirmation is on file.
What if the shipment changes after selection?
If the shipment changes after selection, the record should show the change and whether the selection still holds. A heavier load, a new delivery address or a later pickup can change the carrier's price or its ability to take the load. The agent asks the carrier to confirm the change and updates the rate confirmation if the price moves. If the new price is outside the limit, the change goes to approval, and the record shows the original selection, the change and the new decision together.
What if the team overrides the agent?
If the team overrides the agent's choice, the override is recorded with the person and the reason. Overrides are normal: the team may know something the rules do not, such as a customer preference or a carrier's recent issue. The record keeps the agent's suggestion and the human decision side by side. Over time, frequent overrides on a lane are a sign that the lane rule should change.
How is the selection record used after the load?
The selection record is used after the load to check the invoice, review carriers and improve the rules. An AI logistics agent uses the same record at each step, so the information collected at booking keeps paying off.
How does it help with the invoice?
The record helps with the invoice because it shows exactly what the carrier agreed. Wilson audits each carrier invoice against what was booked, the rate confirmation and the proof of delivery, and pays the carrier from the Wilson Wallet. A charge that was not on the rate confirmation is held for a person or sent back to the carrier with the evidence. A mismatched invoice is not paid in part; the whole invoice waits until the question is settled.
How does it help a new team member?
The record helps a new team member learn how each lane works without relying on someone else's memory. They can open recent loads on a lane and see which carriers were asked, who usually answers, who usually wins and why. They can see which decisions needed approval and what the approver chose. This shortens the time it takes for someone new to make good decisions, and it keeps the knowledge with the company when people change roles.
How does it help with carrier reviews?
The record helps with carrier reviews because it shows each carrier's quotes, wins, losses, non-answers and service on each lane. Wilson does not keep a standing carrier scorecard by default, but it can produce carrier-performance and lane-rate reports on request from the loads it has handled. Those reports come from the selection records and the tracking history, so they reflect real loads, not estimates.
How does it help when a customer asks questions?
The record helps when a customer asks questions because the answer is already written down. If a customer asks why a delivery was late, the team can show which carrier was chosen, why, and what happened after pickup from the tracking history on the same load. If a customer asks why freight costs rose on its lanes, the selection records show the quotes and the market over the period. Clear answers build trust with customers who are paying for, or depending on, that freight.
How does it help improve the rules?
The record helps improve the rules by showing where they produce bad outcomes. If the cheapest carrier keeps winning a lane and keeps arriving late, the rule for that lane may need a service premium. If approvals are requested on most loads on a lane, the target may be out of date. The logistics lead can review these patterns and change the rule. For more on comparing quotes under lane rules, see how to compare freight quotes from approved carriers.
Can the record support an audit?
The record can support an internal or external audit because it shows that the company's own rules and approval limits were followed on each load. An auditor can pick a sample of loads and see, for each one, the quotes, the rule, the decision and the approval when it was needed. Wilson keeps searchable and exportable records with a change history, so the evidence can be pulled without rebuilding it from email.
How long should records be kept?
Records should be kept as long as the company keeps other shipment and payment records, which is often set by finance or legal policy. Wilson keeps searchable and exportable records with a change history, so the company can keep its own copy under its own policy.
How does Wilson, by Cartage, record carrier selection?
Wilson, by Cartage, is an AI logistics agent that requests quotes from approved carriers, compares them under the company's lane rules, negotiates toward the rate target, books within the approval limits and records every step with the load. The selection record is not an extra task; it is the history of work Wilson already did.
Wilson replaces the TMS for freight execution and connects to the company's ERP. It handles LTL, FTL, ocean, drayage, parcel and cross-border freight and works with carriers by email, API, EDI where supported and phone calls where configured. Teams use Wilson's dashboard and records the way they would use a TMS.
What does the team see day to day?
Day to day, the team sees a booked load with a short reason next to the carrier, and can open the full comparison when it wants. Updates arrive in Slack, Microsoft Teams or email, depending on the company's setup. Approval requests arrive in the same channel with the quotes attached. The team does not have to write anything down for the record to be complete.
What stays with the team?
The team sets the approved carriers, the lane rules and the approval limits, and approves anything outside them. Wilson starts with assisted execution, and more routine bookings run within the rules as the team sees the results. For what else to automate in carrier work, see what a carrier management system should actually automate.
What does Wilson not decide?
Wilson does not decide which carriers are approved, what the lane rules are or what the approval limits should be. It does not change contracts with carriers. It applies the rules the team sets, records how it applied them and sends exceptions to the team.
How is Wilson priced?
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.
Can the records be exported?
Yes. The records are searchable and exportable, with a change history, so finance, audit or a customer can receive the history of a load or a lane in a format they can use. The company owns this data. Cartage states that customer lanes, rates and carriers are never sold or shown to another shipper.
How do teams start?
Most teams start Wilson on a few lanes and expand from there. Cartage helps map the highest-impact workflow during discovery. A good first lane is one where selection decisions are questioned often, such as a lane with frequent rebookings or a lane where the cost has been rising, because the records start paying off right away.
FAQs
How can freight software record why a carrier was selected?
It should save the request, every quote and non-answer, the lane rule, the ranking, the reason for the choice and any approval with the load. An AI logistics agent like Wilson, by Cartage, builds this record as it does the quoting and booking work.
What should the reason say?
One or two plain sentences that name the rule and the outcome, such as "lowest total cost that met the delivery date; primary carrier declined." An AI logistics agent records the reason at the moment of the decision.
Are approvals part of the record?
Yes. An AI logistics agent records who approved, when, in which channel and what they were shown. Overrides by the team are recorded with the person and the reason.
Can the record be used to check the carrier's invoice?
Yes. An AI logistics agent like Wilson audits the invoice against the rate confirmation, the proof of delivery and the booked terms, and holds any unsupported charge for a person.
Sources
- Cartage, Wilson product FAQ and product scope, November 2026: https://cartage.ai
If your team cannot easily answer why a carrier was chosen last month, book a demo to see how Wilson, the AI logistics agent by Cartage, records every selection as it books.