From order intake to POD: how an AI logistics agent coordinates a freight load
From order intake to POD: how an AI logistics agent coordinates a freight load
Key Takeaways
- Wilson, by Cartage, executes configured freight coordination tasks instead of only displaying shipment status.
- Wilson moves loads through quoting, booking, scheduling, in-transit monitoring, delivery, and POD filing, then audits, reconciles, and pays carrier invoices from the Wilson Wallet.
- Approval rules can permit routine actions or require review when a load exceeds defined cost, lane, or exception thresholds.
- Wilson supports LTL, FTL, ocean, drayage, parcel, and cross-border freight.
- Wilson accepts orders through ERP feeds, spreadsheets, email, or scheduled file drops and coordinates stakeholders through phone, email, Microsoft Teams, Slack, and SMS.
What an AI logistics agent is, and how it differs from a TMS or tracking dashboard
An AI logistics agent is software that reads shipment information, executes configured freight coordination tasks, and escalates decisions that require human judgment.
A tracking dashboard shows shipment status and may alert staff to a delay. An execution agent uses that information to complete the next approved action. For example, the agent can contact the carrier for an update, notify affected stakeholders, or initiate rebooking from an approved carrier list.
A transportation management system supports functions such as transportation planning and settlement. It may also maintain carrier, shipment, and network records. An AI logistics agent focuses on day-to-day execution, including quoting, booking, scheduling, carrier follow-up, and document collection. The two categories can serve different operational needs.
Wilson, by Cartage, replaces the TMS for freight execution and connects to the company’s ERP. Teams can use Wilson’s dashboard and shipment records the way they would use a traditional TMS. A manufacturer without a TMS does not need to implement one first, and a manufacturer that has one can move freight execution to Wilson lane by lane.
Wilson maintains searchable shipment records and acts through supported systems and communication channels. Configured approval rules determine whether Wilson completes a routine action or requests review. Logistics professionals still set carrier policies, define thresholds, and handle strategic or unusual exceptions.
The seven stages of a freight load and where Wilson acts
A freight load moves through seven operational stages. Wilson carries order information through quote, book, schedule, in-transit, deliver, audit, and pay workflows while keeping shipment records and stakeholder updates tied to the load.
Across the stages from quote to delivery, Wilson requests quotes, applies configured carrier and approval rules, books and schedules the load, monitors progress, handles configured exception steps, and follows up for proof of delivery. Approval rules can permit routine actions or route threshold breaches and non-routine exceptions to logistics professionals.
Audit and pay complete the lifecycle. Wilson audits and reconciles each carrier invoice against what was booked and pays the carrier from the Wilson Wallet; payments above approval limits or outside the rules wait for a person. The workflow table below maps each stage to Wilson’s actions, approval patterns, and retained human decisions.
Workflow table: order intake through POD
Wilson, by Cartage, executes configured freight coordination steps while the logistics team retains strategic and exception-based decisions.
| Stage | Wilson's action | Autonomy/approval pattern | Human judgment retained |
|---|---|---|---|
| Order intake | Ingests orders from an ERP feed, spreadsheet, email, or scheduled file drop. | Available. Validation rules can flag incomplete records. | Resolves unusual or conflicting order data. |
| Quote | Requests quotes, follows up, and compares responses. | Configurable by lane, mode, carrier, and cost threshold. | Sets sourcing strategy and handles nonstandard needs. |
| Carrier selection and booking | Applies rules and books from approved carriers. | Routine loads can proceed automatically. Other loads require approval. | Approves exceptions and changes carrier policy. |
| Schedule | Coordinates pickup and delivery timing with relevant parties. | Configurable communication and escalation rules apply. | Resolves capacity conflicts and unusual constraints. |
| In transit | Monitors carrier updates and identifies missed pickups, cancellations, or delays. | Uses the best source per load: carrier API, GPS/ELD data, or the carrier’s website by PRO number, with email or call follow-up. | Assesses exceptions with broader operational impact. |
| Exception response | Contacts the carrier, sends configured notifications, and initiates rebooking from the approved list. | Rebooking can proceed automatically or require approval. | Handles nonroutine escalation and carrier relationship decisions. |
| Delivery and POD | Confirms delivery, follows up for POD, files it, and updates configured records. | Available with configurable stakeholder notifications. | Resolves damaged, disputed, or incomplete deliveries. |
Invoice audit and payment follow delivery: Wilson reconciles the carrier invoice against the booking and pays approved invoices from the Wilson Wallet.
Order intake: supported inputs and freight modes
Wilson can ingest orders through an ERP feed, spreadsheet, email, or scheduled file drop. Each order becomes a searchable shipment record that supports the later quoting, booking, scheduling, tracking, and documentation steps.
Wilson works with SAP, NetSuite, Microsoft Dynamics 365, Oracle, Infor, Epicor, Sage, Acumatica, and other ERP environments, with the exact connection depending on the customer’s data flow and scope. It works from the ERP connection or the data flow the company already has: an ERP feed, scheduled file drop, spreadsheet, email, or API, depending on the environment. The exact connection and any write-back to the ERP depend on scope.
A manufacturer or distributor can start with a daily order feed instead of completing an integration project first. Cartage can deepen the connection over time, for example by adding write-back once order intake is working.
Wilson coordinates LTL, FTL, ocean, drayage, parcel, and cross-border freight. The order source does not determine the mode. Wilson uses the shipment record and the company’s configured operating rules to route the load into the appropriate quoting and coordination workflow.
Quoting and approved-carrier selection
Wilson requests quotes, follows up with carriers, compares responses, and applies the shipper’s configured selection rules. Those rules can account for approved vendors, price limits, lane preferences, and required approvals. Routine loads may proceed without case-by-case approval, while quotes above a cost threshold or outside normal lane rules can go to the logistics team.
Wilson tenders the customer’s own approved carriers first. If those carriers cannot cover the load, Cartage can introduce additional carrier capacity, including on cross-border lanes. Any new carrier must be approved by the company before Wilson uses it. Wilson shows the selected carrier and price, while carriers the customer brings remain the customer’s direct relationships.
Wilson also negotiates. Its standard workflow gathers available rates, negotiates them against the company’s rate targets, and books the best approved option according to configured rules. Negotiation stays within the approval limits the company sets, so a rate that remains outside those limits goes to the logistics team for a decision.
Logistics professionals still set the approved carrier list, selection criteria, spending thresholds, and escalation rules. Wilson books only from that approved list, so every carrier it uses has been approved by the company.
Booking and documentation
Wilson executes the booking once carrier selection and approval rules identify an acceptable option. It sends the tender to the carrier and records the response. Wilson confirms the booking with the carrier through email, API, EDI where the carrier supports it, or phone where configured, while the customer’s team can receive the booked update through Slack or Microsoft Teams.
Wilson produces the standard documents needed to release and move the load. The supported document set includes rate confirmations, bills of lading, packing slips, and pallet labels. Wilson stores these documents with its searchable shipment records, which keeps the booking details and change history connected to the load.
Each company determines when Wilson can book without case-by-case approval. For example, Wilson may execute routine bookings within an approved lane and cost threshold. A higher-cost quote, an unfamiliar lane, or another configured exception can trigger an approval request. Logistics professionals retain decisions involving carrier strategy, unusual service requirements, and exceptions outside the configured rules.
Scheduling and stakeholder communication
Wilson schedules pickup and delivery windows through carrier communication and the customer’s operating preferences. Approval rules can allow routine appointments to proceed automatically, while unusual timing, capacity, or consignee constraints can require logistics staff to review the plan.
Wilson asks the carrier for shipment status and distributes updates according to the configured communication matrix.
| Stakeholder | Events communicated | Channel |
|---|---|---|
| Customer team | Booked, picked up, running late, delivered, and POD filed | Slack or Microsoft Teams |
| Carrier | Booked, picked up, running late, delivered, and POD filed | Email or API |
| Shipper | Booked, picked up, running late, delivered, and POD filed | |
| Consignee | Picked up, running late, delivered, and POD filed | Email or SMS |
Wilson uses the best tracking source available for each load: the carrier’s API, GPS or ELD data from the truck, or the carrier’s website by PRO number. When none of those exist, Wilson emails or calls the carrier for status. Wilson uses the received status to notify the customer team, shipper, and consignee according to their configured channels and preferences.
Ongoing monitoring and exception handling in transit
Wilson uses in-transit status to execute a configured exception workflow rather than stopping at an alert. Wilson monitors each shipment through the best source available, whether a carrier API, GPS or ELD data, or the carrier’s website by PRO number. When no source is available, it follows up with the carrier by email or phone.
When Wilson detects a missed pickup, cancellation, or delay, it contacts the carrier to get the new ETA and the reason for the delay, and requests an updated plan. Wilson then notifies the internal logistics team through Slack or Microsoft Teams. It can also update the customer through email or SMS when the workflow includes customer notifications.
When a disruption requires another carrier, Wilson initiates rebooking from the company’s approved carrier list. Approval rules can let Wilson proceed automatically for routine cases or require a logistics professional to approve the proposed carrier and cost. For example, Wilson could tender an approved backup carrier when a regular carrier cancels on a standard lane, provided the quote stays within the configured threshold.
Wilson rebooks only with carriers the company has approved, including any capacity Cartage introduced that the company has accepted. Logistics professionals control the approved carrier list and set cost thresholds, lane preferences, and escalation rules. They also decide how to handle exceptions outside those boundaries, such as accepting a major service tradeoff or changing the broader carrier strategy.
Delivery and proof-of-delivery filing
Delivery confirmation and proof of delivery are separate events. Wilson asks the carrier for delivery status, records the confirmation, and follows up for the POD document. Persistent follow-up helps prevent delivered loads from remaining open because the carrier has not supplied the paperwork.
After Wilson receives the POD, it files the document with the shipment record and records the filing event. Wilson can also write the confirmation back to the ERP when write-back is part of the scope, for example through an updated file for import or an API connection where one is available.
Configured notifications keep stakeholders informed. Wilson can notify the customer team through Slack or Microsoft Teams when the load is delivered and when the POD is filed. The shipper receives email updates, while the consignee can receive email or SMS updates. Logistics professionals handle disputed deliveries, damaged freight, incomplete documents, and other exceptions that require judgment.
Invoice audit follows POD filing. Wilson checks the carrier’s invoice against what was booked, reconciles any differences, and pays from the Wilson Wallet; payments above approval limits or outside the rules wait for a person.
Invoice audit and payment: how the load closes
The load is not finished at POD. It closes when the carrier invoice is audited against what was booked and the carrier is paid within the company's approval limits. An AI logistics coordinator should carry the same shipment record from order intake all the way to payment, so the audit has every fact it needs.
A POD, or proof of delivery, is the document the receiver signs to show the freight arrived. An accessorial charge is a fee for extra service beyond the base rate, such as a liftgate or detention. Detention is a fee a carrier bills when its truck waits too long at a dock.
| Step | What Wilson checks | When a person steps in |
|---|---|---|
| Match the invoice | Invoice is tied to the right load, carrier, and reference numbers | The invoice cannot be matched to one load |
| Compare the rate | Linehaul and fuel match the booked rate and rate confirmation | The billed rate is higher than the booked rate |
| Check accessorials | Each extra charge was agreed or is supported by load events, such as arrival and departure times for detention | A charge was never agreed or has no supporting record |
| Confirm delivery | POD is filed and shows no damage or shortage | The POD notes damage, shortage, or refusal |
| Apply approval limits | Payment amount is within the company's rules | The amount is above the approval limit or outside the rules |
| Pay | Carrier is paid from the Wilson Wallet | Never for routine payments within the rules |
How approval limits work at payment
Approval limits are set by the company, not by Wilson. A common setup lets invoices that match the booking be paid within the rules, sends small differences to a coordinator, and sends larger differences or new charges to a manager or finance. The same limits that apply to booking and rebooking also apply to payment, so a cost that was never approved does not get paid by default.
Customers can also require a signed POD before payment releases. Wilson audits each carrier invoice against the POD and the rate confirmation, and if any line does not match what was booked, the whole invoice waits for a person instead of being partly paid.
Wilson has no subscription or platform fee. Its pricing is a percentage of the freight payments coordinated through the Wilson Wallet. Pricing scales down as volume grows, and Enterprise pricing is custom.
Hypothetical example: an invoice with one extra charge
This example is hypothetical and does not describe a real customer. A manufacturer's load delivers and the POD is filed the same day. The carrier invoice shows the booked $1,450 linehaul plus a $90 detention charge. Wilson checks the rate confirmation, which gives two free hours at delivery, and the recorded arrival and departure times, which show a one-hour wait. The detention charge is not supported, so the invoice does not match the rules. Wilson sends it to the logistics coordinator with the times attached instead of paying it. The coordinator asks the carrier for a corrected invoice at $1,450, and Wilson pays the corrected invoice from the Wilson Wallet.
Where autonomy is configurable versus where judgment stays human
Wilson applies approval rules workflow by workflow, using rules and thresholds set by the logistics team. A routine load on an established lane can move through quoting and booking without approval when the carrier is approved and the price falls below a set limit. A higher-cost quote, unfamiliar lane, or service exception can pause while Wilson requests approval through a configured channel.
Wilson starts with assisted execution, and the company decides which actions need approval. As Wilson proves reliable within a defined workflow, more actions can run automatically within the company’s rules, and the change history records each one. Approval rules can vary by action. For example, Wilson might book routine shipments automatically but require approval before initiating rebooking after a cancellation. Rebooking always uses the organization’s approved carrier list.
Logistics professionals retain decisions that depend on commercial context or broader operating priorities. The team determines carrier capacity strategy, negotiates contracts and long-term rates, and handles non-routine escalations that threaten production or customer commitments. Wilson can gather quotes, contact carriers, update stakeholders, and prepare an approved next step, while the logistics team makes the judgment-heavy decision.
FAQs
Does Wilson need a TMS?
No. Teams don’t need a separate TMS for freight execution: Wilson runs it, keeps searchable, exportable shipment records, and connects to the ERP.
What freight modes does Wilson support?
Wilson supports LTL, FTL, ocean, drayage, parcel, and cross-border freight.
How does Wilson handle a missed pickup or delay?
Wilson contacts the carrier, alerts the internal team, and notifies the customer when configured. It can then initiate rebooking from the approved carrier list. Workflow rules determine whether rebooking proceeds automatically or requires approval.
What documents does Wilson produce?
Wilson produces rate confirmations, bills of lading, packing slips, and pallet labels. It also follows up on proof of delivery and files the POD with the shipment record.
Is the Wilson wallet available now?
Yes. Wilson audits and reconciles carrier invoices against what was booked and pays carriers from the Wilson Wallet. Payments above approval limits or outside the company’s rules wait for a person to approve them.
Getting started with an AI logistics agent
Wilson fits manufacturers and distributors whose in-house logistics staff spend substantial time on manual carrier follow-ups, booking, shipment monitoring, status updates, and exception response. Company size, shipment volume, and location count do not determine fit.
During discovery, Cartage helps identify and map a high-impact coordination workflow within the company’s current operations. A practical starting point is a first workflow on a few lanes, measured against the existing process; timing depends on scope. Cartage then onboards Wilson on the company’s operating preferences and approval rules before expanding its responsibilities.
Bring one load your team coordinated last week and walk through how Wilson would run it from order intake to POD.