Which freight decisions can the software make without calling you?

Key Takeaways

By Maria Romero · Updated October 18, 2026

Freight software can make the decisions your company has authorized within a clear operating scope and approval boundary. Define the action, eligible carriers, commercial limits, and exception owner before deciding how much work can proceed. Wilson, by Cartage, negotiates and executes freight within customer-configured rules while the company retains carrier approval and decisions beyond those limits.

Permission to gather information is different from permission to commit spend.
An approved carrier still needs to meet the shipment's requirements.
An unanswered approval request is not permission to proceed.
Test combined conditions and missing information, not only an ordinary load inside the rules.

Build an approval matrix around actions

An action-based matrix gives operations and finance a usable starting point. The examples below are suggested company policy decisions; confirm which controls the proposed implementation can enforce.

Action	Boundary the company should define	Evidence before proceeding	Owner when outside the boundary
Request quotes	Eligible carriers and shipment scope	Usable shipping requirement	Logistics owner
Negotiate an offer	Company targets, terms, and permitted limits	Comparable service and current offer	Commercial approver
Book freight	Approved carrier, service, and spending authority	Accepted terms and required approval	Booking approver
Change a commitment	Allowed timing, cost, and customer effects	Current booking and proposed revision	Service or customer decision owner
Resolve an invoice difference	Charge evidence and financial authority	Booking terms and documented changes	Finance or authorized dispute owner

Write the matrix in business language first. The technical configuration should implement an agreed policy, not become the place where employees discover what the company permits.

Separate asking from committing

Information gathering does not necessarily create the same obligation as accepting a carrier offer. Define the difference so routine requests can proceed without accidentally granting broader authority.

A quote request can seek an available service. Negotiation can explore terms within company targets. Booking creates a carrier arrangement that the company must understand and control. A later change may affect both cost and the customer's expectation.

For each action, identify the result that would count as a commitment. If a message could reasonably be read as an accepted instruction, the workflow needs the relevant authority before sending it.

Wilson requests and compares approved carrier quotes, negotiates within limits, and handles booking and follow-up under customer rules. The configurable approval article explains the general boundary. This matrix helps the buyer translate that boundary into a specific set of permitted actions.

Combine eligibility, service, and cost conditions

A spending limit alone is not a complete freight policy. A low price can still be unsuitable if the carrier, equipment, or service does not meet the requirement.

Define the conditions that must all be satisfied before the selected action proceeds. The company may need carrier approval, an applicable service, usable shipment data, and the relevant commercial authority. Treat these as policy requirements to demonstrate in the proposed setup.

Consider an illustrative offer below the usual spending limit from a carrier that has not been approved. It should not become acceptable merely because its price fits. Another offer from an approved carrier may still fail the required pickup or delivery arrangement.

Wilson uses approved carriers. Cartage may introduce additional capacity, but a carrier becomes available to Wilson only after the customer approves it. Keep that carrier decision separate from the authority to book an individual load.

Treat incomplete information as a decision boundary

Missing information can prevent a valid decision even when a numerical limit appears satisfied. Identify the fields and facts each action requires.

A quote without a clearly stated service can be hard to compare. A shipment without reliable freight characteristics can produce an unsuitable offer. An invoice difference without supporting evidence can require investigation before approval.

The workflow should make the missing requirement and next owner clear. Do not assume the software may invent a value or treat an unanswered question as an acceptable default. Define permitted fallback behavior and demonstrate it.

For a buyer test, remove a required fact from an otherwise ordinary load. Ask what action remains allowed and which action waits. The result should be observable in the proposed implementation, not only described as a general promise that the system uses good judgment.

Make the approval request useful to the person receiving it

A useful request includes the affected shipment, proposed action, reason approval is needed, supporting evidence, and current alternatives. The approver should not have to reconstruct the entire carrier conversation.

Also state what happens if nobody answers. The permitted response may be to hold the commitment, continue allowed information gathering, or escalate to another authorized person. Define that response instead of assuming silence grants authority.

Read who approves the rate and owns the exception to connect the request with the operating role. A notification delivered to a group does not establish which person owns the decision.

Wilson carries out configured freight work and brings decisions beyond its boundaries to the appropriate people. Specific notification paths, timing, substitute approvers, and control details should be agreed and tested for the actual workflow rather than inferred as universal features.

Test the matrix before allowing broader action

A good test includes an ordinary permitted action, an action beyond a limit, a disallowed carrier, missing information, and a later change to a confirmed shipment. Each case should have a predetermined expected result.

Use controlled records and authorized communications. Observe the permitted action or hold, the evidence presented, the assigned owner, and the result after an approver responds. Test an unanswered request too, because a correct first notification does not prove the later behavior.

Wilson replaces the TMS for freight execution and connects to the ERP order flow. Its work spans creating, quoting, tendering, tracking, audit, and payment. That scope does not remove the need for company policy or establish every proposed matrix control by default.

Review the matrix when the operating scope changes. A new mode, business unit, or carrier arrangement can create a different requirement. Keep the business authority and demonstrated configuration aligned so staff know which decisions software can complete and which remain theirs.

FAQs

Which freight decisions can Wilson make without calling us?

Wilson can perform configured freight work within customer rules and approval limits. Define the permitted action, carrier eligibility, service requirement, and escalation boundary for your scope.

Is a spending threshold enough?

No. Also consider carrier approval, service suitability, required data, and the kind of commitment being made.

Can an unanswered approval request become automatic consent?

Do not assume that policy. Define the permitted hold or escalation behavior explicitly and test it.

Should every action require a person?

That is a company policy choice. Separate routine authorized work from commitments and exceptions that require human judgment, then demonstrate the configured boundary.