Which pickup changes need a shipper’s approval?
Key Takeaways
A pickup change needs the shipper's approval when it breaks the delivery promise, adds cost, changes the pickup location, equipment, carrier, or freight, or falls outside the dock's hours. Small changes that stay inside the dock's hours, keep the delivery date, and add no cost can be handled under written rules. An AI logistics coordinator should apply these rules on every change and send only the approval cases to a person, with the facts and options.
- An approval rule says which changes can be accepted without a person and which need one.
- The main triggers for approval are customer impact, cost, and changes to what or where is being shipped.
- Routine changes, like a one-hour shift within the same day, usually do not need a person.
- The approver should be named for each kind of change.
- Every approval, and every change accepted under rules, should be recorded.
- Wilson, by Cartage, is an AI logistics coordinator that starts with assisted execution, follows approval limits set by the customer, and sends out-of-rule decisions to a person.
Why not approve every pickup change by hand?
Approving every pickup change by hand slows down routine work and leaves less time for the changes that matter. An AI logistics coordinator should handle routine changes under rules and save people for decisions with real impact.
A busy shipper may see many pickup changes a week. Most are small: a truck an hour late, a dispatcher asking for 10 a.m. instead of 9 a.m. If a manager must approve each one, carriers wait for answers, dock plans change late, and the manager spends the day on minor decisions. Clear rules let small changes move quickly and make sure large ones get attention.
The table below shows how changes usually split.
| Change | Typical impact | Approval needed? |
|---|---|---|
| Time shift within the same day and dock hours, delivery unchanged | Small | No, accept under rules |
| Window narrowed by the carrier, still fits the dock | Small | No |
| Move to the next day, delivery still on time | Medium | Often no, if within rules |
| Move that breaks the delivery promise | High | Yes |
| Change that adds cost (accessorial, higher rate) | High | Yes, above set limits |
| Change of pickup location | High | Yes |
| Change of equipment type | High | Yes |
| Change of carrier | High | Yes, unless an approved backup within limits |
| Change in freight (pallet count, weight) | Medium to high | Yes, if it affects price or equipment |
| Pickup outside dock hours | High | Yes |
An accessorial charge is a fee for extra service beyond the base rate, such as a liftgate or after-hours pickup.
Who writes the rules
The logistics manager usually writes the rules, with input from customer service on delivery promises, finance on cost limits, and facility leads on dock hours. The rules should be short enough to fit on one page. An AI logistics coordinator follows the rules but does not set them.
Rules protect speed and control
Rules let routine work move without waiting. They also make sure changes with real risk reach a person. Without rules, teams either approve everything slowly or accept everything quickly. Neither is safe.
Approval and information are different
Approval means a person decides. Information means a person is told. Many changes need information but not approval: the dock must know about a one-hour shift, but no manager needs to approve it. Mixing the two leads to managers being asked to approve things they only need to know. An AI logistics coordinator can send information to those who need it and approval requests only to approvers.
Approval is about authority
The approver should be someone with authority to accept the impact: a logistics manager for cost, an account owner for customer impact, a facility lead for dock hours. Naming the approver by type of change prevents delays. An AI logistics employee can route each decision to the right person.
The cost of approving nothing
When nothing needs approval, risky changes slip through. A carrier hands the load to an unknown company. A pickup moves to a weekend and adds an after-hours fee. A delivery to a key customer slips without anyone deciding. Each mistake may look small, but they add cost and damage relationships. Written approval triggers prevent these. An AI logistics coordinator can check every change against the triggers.
The cost of approving everything
When everything needs approval, carriers wait for answers and give trucks to other shippers. Managers spend their day on small decisions. Dock plans change late. The approval process itself becomes the cause of delays. Rules that let routine changes move remove this bottleneck. An AI logistics employee can handle the routine ones and leave managers only the important ones.
Assisted first, more automatic over time
Many teams start by approving more changes by hand, then widen the rules as they see the results. Wilson starts with assisted execution, and approval limits are set by the customer. Routine actions can run automatically within those rules as reliability is proven.
Which changes should always need approval?
Changes that affect the customer, the cost, or what is being shipped should always need approval. An AI logistics coordinator should send these to a named approver with the facts, options, and a deadline.
Changes that break the delivery promise
If the new pickup means the freight will arrive after the date the customer was promised, someone with authority over the customer relationship should decide. Options may include accepting the delay, paying for a faster service, or rebooking with another approved carrier.
Set a cost limit in dollars
A cost limit should be a number, not a feeling. For example: changes that add up to a set dollar amount per load can be accepted under rules; anything above goes to the logistics manager. A clear number is easy to apply and easy to review. An AI logistics employee can compare each change's added cost with the limit.
Changes that add cost
A later pickup may need a weekend delivery. A rebooked carrier may charge more. A new appointment may carry a fee. Any added cost above a set limit should be approved. Small costs within a limit may be accepted under rules.
Pickups outside dock hours
A carrier may propose an early morning or late evening pickup when the dock is normally closed. Opening the dock costs labor and may need a supervisor. That decision belongs to the facility manager. An AI logistics coordinator should never confirm a pickup outside dock hours without the facility's approval.
Changes to location
A carrier proposing to pick up at a different facility, or a different dock address, changes the shipment. The freight, documents, and dock plan must change too. Location changes should always be approved.
Changes close to pickup
A change requested a few hours before pickup leaves little time to find options. The rule may require faster approval for these, or allow a short default. An AI logistics coordinator can mark late changes as urgent and shorten the approval deadline.
Changes to equipment
A carrier offering a different trailer, such as a flatbed instead of a dry van, may not be able to carry the freight safely. Equipment changes should always be approved by someone who knows the freight.
Changes to the carrier
If the booked carrier wants to hand the load to another company, the shipper must know and approve. The new company must be approved for the shipper's freight. Cartage can present additional carrier capacity, but the customer approves any carrier before Wilson uses it.
Changes that affect other loads
Sometimes a pickup change affects other shipments. Moving one pickup may push another out of its dock slot. A carrier may want to combine two pickups into one truck. These changes need a person who can see the whole day's plan. An AI logistics coordinator can flag when a change affects other loads at the same facility.
Changes to the freight
If the pallet count or weight changes, the price, equipment, and documents may change. These changes should be approved and the carrier asked to confirm the new details.
Carrier changes need extra care
When a carrier wants to pass a load to another company, this is sometimes called re-brokering or double brokering. It means the freight moves with a company the shipper did not choose. The shipper should know who is actually picking up its freight. Any carrier change should be approved and checked. An AI logistics employee can flag a change of carrier name, truck, or contact as a possible handoff and ask the booked carrier to confirm.
Hypothetical example: a change that needed approval
This example is hypothetical and does not describe a real customer. A carrier proposes moving a Thursday pickup to Friday. Friday pickup would deliver Monday instead of Friday. The customer is a retailer with a weekend promotion. The AI logistics coordinator sends the account owner the facts and two options: accept the delay, or rebook with an approved carrier that can pick up Thursday for 8 percent more. The account owner approves the rebook. The coordinator books it and records the approval.
Which changes can be handled under rules?
Changes that stay within the dock's hours, keep the delivery promise, add no cost, and do not change the location, equipment, carrier, or freight can be handled under rules. An AI logistics coordinator should accept these, confirm them in writing, and record them.
Start tight, then widen
Many teams start with tight rules: almost every change goes to a person. After a few weeks, they review the decisions. If most were routine approvals, the rules can widen. This builds trust in the process step by step. An AI logistics coordinator can show which approved changes would have qualified as routine under wider rules.
Example routine rules
- Accept a time change on the same day if it falls within dock hours and the dock confirms a door.
- Accept a move to the next day if delivery still meets the promise and the dock can load.
- Accept a narrower window inside the original window.
- Accept a short delay of up to a set number of hours that does not affect delivery.
Rules by customer and lane
Rules can differ by customer and lane. A retailer with strict appointments may need approval for any change that moves delivery by even a few hours. A restock to the shipper's own warehouse may accept day-level changes. An AI logistics employee can apply customer-level and lane-level rules on top of the general ones.
Conditions for routine changes
| Condition | Must be true |
|---|---|
| Dock | Facility open and door available |
| Freight | Ready by the new time |
| Delivery | Still meets the promise and appointment |
| Cost | No added charge |
| Carrier | Same booked carrier |
| Location and equipment | Unchanged |
Check every condition
A change is routine only when every condition is true. If one fails, such as the dock having no door, it needs a person. An AI logistics coordinator can check all six conditions on each change.
Record routine changes too
A change accepted under rules should still be recorded: what changed, which rule allowed it, and when. If questions come later, the record shows the decision was within the rules. Wilson keeps searchable shipment records with change history.
Routine does not mean silent
A routine change still changes the plan. The dock, and sometimes customer service, should hear about it. The only difference is that no one needs to approve it first. An AI logistics coordinator can send routine updates in the same format as approved ones, so people always see what changed.
Tell the right people
Even routine changes need to reach the dock and, sometimes, the customer. An approval rule decides whether a person must agree; it does not remove the need to inform others. An AI logistics employee can send updates through channels such as Slack, Microsoft Teams, or email.
Rules for customer-routed loads
When the customer books its own carrier, the shipper may still need to approve pickup changes that affect its dock. Delivery is the customer's concern, but dock hours and readiness are the shipper's. Rules for these loads can focus on the dock. An AI logistics employee can apply a separate rule set to customer-routed pickups.
Hypothetical example: a routine change
This example is hypothetical and does not describe a real customer. A carrier asks to move a pickup from 9 a.m. to 11 a.m. The dock is open and has a door at 11 a.m. Delivery the next day is not affected, and no extra cost applies. The AI logistics coordinator accepts under the rules, confirms in writing, tells the dock, and records the rule used. No manager is involved.
How should approval requests be sent and recorded?
Approval requests should go to a named approver with the facts, the options, the cost of each, and a deadline, and the decision should be recorded with the change. An AI logistics coordinator should make the request easy to answer.
Include a recommendation
An approval request is easier to answer when it includes a recommendation and the reason. For example: "Recommend rebooking, because the customer's promotion starts Friday." The approver can agree or choose another option. An AI logistics coordinator can suggest the option that best fits the shipper's rules.
What the request should include
| Item | Example |
|---|---|
| Load and customer | Load 6612, Retailer X |
| Change requested | Pickup Thursday to Friday |
| Impact | Delivery moves from Friday to Monday |
| Options | Accept delay; rebook with approved carrier at +8% |
| Cost | $140 extra for rebooking |
| Deadline | Decide by 2 p.m. to keep Thursday pickup |
| Recommendation | Rebook, based on promotion deadline |
Make approval easy to give
An approver should be able to answer in one reply: "approve," "decline," or "option 2." Requests that need the approver to log in, search, or call someone get delayed. An AI logistics coordinator can send requests in a format that takes seconds to answer.
Send one request per change
Do not bundle several changes in one approval request. An AI logistics coordinator can send each change separately so each gets a clear answer.
Name the approver by change type
| Change type | Approver |
|---|---|
| Delivery promise | Account owner or customer service lead |
| Added cost above limit | Logistics manager |
| Location or equipment | Logistics manager with facility lead |
| New carrier | Carrier approval owner |
| Outside dock hours | Facility manager |
What happens when the deadline passes
If neither the approver nor the backup answers in time, the rule should say what happens. For example, keep the original pickup and ask the carrier to honor it, or accept the change if it only affects cost within a small amount. A default prevents the load from being stuck. An AI logistics employee can apply the default and record that no answer came.
Backups and deadlines
Every approver needs a backup. If the approver does not answer before the deadline, the request goes to the backup. An AI logistics employee can track the deadline and escalate.
Review declined approvals
When an approver declines a change, the load still needs a plan: keep the original time, find another carrier, or adjust delivery. The record should show the plan as well as the decline. An AI logistics employee can carry out the next step and record it.
Record the decision
Save the approver's decision, the time, and the reason with the shipment. The record shows who approved what and why.
Approvals in writing
A spoken "OK" from a manager should be followed by a written note on the record. An AI logistics employee can ask for the approval in writing or record it after a call.
Common approval mistakes
- No written rules. Each coordinator decides differently.
- Everything needs approval. Routine changes wait too long.
- Nothing needs approval. Costly changes slip through.
- No deadline. Approvals arrive after the option has expired.
- No record. Nobody can show who approved a change.
How should you evaluate software on pickup change approvals?
Evaluate software by sending it a mix of routine and high-impact pickup changes and checking which it accepts, which it routes, and how it records each decision. An AI logistics coordinator should follow your rules exactly.
Demo tests for pickup change approvals
| Buyer requirement | Demo test | Evidence to see |
|---|---|---|
| Routine changes accepted | Shift pickup by one hour within dock hours | Accepted, confirmed, recorded with rule |
| Promise check | Move pickup so delivery is late | Sent to account owner with options |
| Cost check | Change adds a fee above the limit | Sent to logistics manager |
| Location change | Carrier proposes another address | Approval requested |
| Carrier change | Carrier wants to hand off the load | Carrier approval owner asked |
| Deadline and backup | Approver silent | Escalated to backup in time |
| Record | Open the shipment | Rule or approver, time, and reason saved |
Test a carrier handoff
Ask the vendor to simulate a booked carrier that wants to pass the load to another company. Watch whether the AI logistics coordinator stops and asks for approval, rather than accepting the new carrier.
Demo questions about pickup change approvals
- How are approval rules set, and who can change them?
- How does the AI logistics coordinator decide a change is routine?
- Who receives each type of approval request?
- How are deadlines and backups handled?
- How are decisions recorded?
- Can the rules change by customer or lane?
Ask how rules are changed
Rules will change over time. Ask how the vendor's tool lets you update them, who can make changes, and how changes are recorded. An AI logistics coordinator should apply each rule change from a known time and keep the history.
How to measure approval work
Track the share of pickup changes handled under rules. Track the time from request to approval. Count costly changes that were accepted without approval. These measures show whether the AI logistics employee balances speed and control.
Use your real change history
Bring a month of real pickup changes. Ask the vendor to sort them by its rules: which would be accepted, which would need approval, and who would approve. Compare with what actually happened. The result shows whether the rules fit your business.
Scoring the approval demo
Score each test as pass, partial, or fail. A pass means routine changes moved fast and high-impact changes reached the right approver with options. A partial means the routing was right but the request lacked options or a deadline. A fail means a high-impact change was accepted without approval.
Warning signs in an approval demo
- All changes go to one manager.
- Routine changes cannot be accepted without a person.
- Approval requests lack options or costs.
- Decisions are not recorded.
Where does Wilson fit in pickup change approvals?
Wilson, by Cartage, is an AI logistics coordinator that follows approval limits set by the customer, accepts routine changes within those rules, and sends out-of-rule decisions to the logistics team. It starts with assisted execution, and routine actions can run automatically within the rules as reliability is proven.
Wilson replaces the TMS for freight execution and connects to the company's ERP through a method that fits the customer's environment. It negotiates against the customer's rate targets within configured rules and approval limits, and rates outside those limits go to the logistics team. It keeps searchable shipment records with change history.
When a change becomes a rebooking
If a pickup change cannot be accepted, rebooking may be the answer. 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.
Records that show every decision
Wilson records whether each change was accepted under a rule or approved by a person, with the time and the reason. Those records help when reviewing the rules or answering questions later.
What Cartage asks about approvals in discovery
Cartage asks which pickup changes need a person today, who approves each kind, what cost limits apply, and which customers have strict delivery dates. These answers become the first rules an AI logistics coordinator follows.
What Wilson does not do for approvals
Wilson does not set your approval rules or limits; the customer does. It does not approve new carriers on its own. Specific rule settings and routing should be confirmed in a demo. Exact ERP connection details depend on the customer's systems.
Reports on approvals
Over time, records show how many changes needed approval, how fast approvals came, and how often approvers declined. Wilson can use shipment data from the loads it runs to produce reports on request. Teams can use these to tune their rules.
Where teams start with approval rules
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 tight rules and widen them as they see results.
Teams writing rules can read about booking approval rules before automating. Teams deciding limits can see what a freight AI can do before it asks for approval. Both topics shape the rules an AI logistics coordinator follows. Teams setting human checkpoints can review AI logistics agent human approval rules.
This article is part of our complete guide to freight pickup confirmations, changes, and missed pickups.
FAQs
Which pickup changes need a shipper's approval?
Changes that break the delivery promise, add cost above a limit, or change the location, equipment, carrier, or freight, and pickups outside dock hours. An AI logistics coordinator should route these to a named approver.
Which pickup changes can be handled without approval?
Changes that stay within dock hours, keep the delivery date, add no cost, and keep the same carrier, location, equipment, and freight. An AI logistics employee can accept these under written rules.
Who should approve a pickup change?
The person with authority over the impact: the account owner for customer impact, the logistics manager for cost, the facility lead for dock hours. An AI logistics coordinator can route each request.
Should routine changes be recorded too?
Yes. Record the change and the rule that allowed it. An AI logistics employee should keep every change in the shipment history.
Sources
- Cartage, Wilson product scope, October 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator accepts a routine pickup change under your rules and routes a change that breaks your delivery promise to the right approver: talk to the Cartage team.