Your TMS manages freight. It does not coordinate the work.

Key Takeaways

• A transportation management system supports transportation planning, rating, settlement, and record-keeping, but it does not perform every carrier follow-up or exception response.

• Daily freight coordination includes requesting quotes, booking carriers, scheduling pickups, checking status, collecting documents, communicating updates, and responding when shipments fall behind plan.

• Wilson, by Cartage, handles recurring coordination work within the manufacturer’s or distributor’s operating rules, approved carrier relationships, and approval requirements.

• Wilson replaces the TMS for freight execution and connects to the company’s ERP. It works from the data flow the company already has (ERP feed, scheduled file drop, spreadsheet, email, or API) and maintains searchable, exportable operational records.

• A company without a TMS does not need to implement one first. A company with a TMS can move freight execution to Wilson lane by lane.

What a transportation management system actually manages

A transportation management system plans shipments, rates transportation options, supports freight settlement, and keeps network records. Manufacturers and distributors use TMS software to organize transportation orders, planned routes, carrier information, shipment status, and related documents. Settlement functions can compare freight invoices with agreed rates and route charges for review or payment.

TMS capabilities depend on the product, purchased modules, configuration, and connected data sources. Some systems calculate rates and tender loads to carriers. Others support appointment scheduling, tracking updates, reporting, or freight audit workflows. Each function helps maintain a structured record of transportation activity and apply established business rules.

A TMS does not itself place a phone call to a carrier or keep pursuing an unanswered status request. It cannot resolve every delay through a status field or alert. When a pickup fails, someone still needs to contact the carrier, determine the available options, communicate the impact, and carry out the approved response.

TMS software can detect or record an exception without completing the coordination required to resolve it. An alert may tell the logistics team that a shipment missed pickup. The remaining work includes confirming what happened, finding a new plan, updating affected parties, and documenting the outcome. Those actions belong to freight execution and daily coordination rather than transportation record-keeping alone.

The work a TMS leaves for someone to do by hand

Capabilities differ by product and configuration. Some TMS platforms include automated tendering, carrier portals, tracking connections, or AI features, so the gap described here is a pattern to test in your own operation, not a rule for every TMS.

A TMS can record a shipment without completing the coordination required to move it. A logistics coordinator still requests quotes, follows up on missing responses, applies approval rules, and books the selected carrier. The coordinator then schedules pickup and delivery appointments, confirms details with the shipper and consignee, and updates the transportation record.

Shipment monitoring creates another recurring workload. Someone must request status updates, identify late pickups or delays, and communicate changes to internal stakeholders or customers. Proof-of-delivery documents also require follow-up when carriers do not send them promptly. Each action may take only a few minutes, but repeated emails, calls, and record updates consume a substantial share of the workday.

Logistics teams can spend significant time chasing information and prompting the next action, even when TMS software already holds the shipment record.

Exception response makes the distinction especially clear. A TMS may display a missed pickup or delayed delivery, but a person often must contact the carrier, determine the available options, notify affected parties, and arrange an approved response. Detecting the exception provides useful information. Resolving it requires communication and follow-through.

Transportation management and freight coordination therefore cover different work. Transportation management software organizes plans, rates, shipment records, and settlement data. Daily freight coordination carries out the quoting, booking, scheduling, communication, documentation, and exception actions that keep each shipment moving.

Wilson, by Cartage: an AI logistics coordinator for that daily work

Wilson, by Cartage, is an AI logistics coordinator that carries out recurring freight work for manufacturers and distributors. Wilson replaces the TMS for freight execution and connects to the company’s ERP. It coordinates loads within the shipper’s approved carrier relationships, operating rules, and approval requirements.

Wilson organizes each load around seven stages. Those stages are quote, book, schedule, in transit, deliver, audit, and pay. During quoting, Wilson requests rates, follows up with carriers, compares responses, and applies configured approval rules. After booking, it coordinates scheduling, monitors shipment status, collects delivery documentation, and maintains the communication needed to move the load forward. After delivery, Wilson audits and reconciles each carrier invoice against what was booked and pays carriers from the Wilson Wallet. Payments above approval limits or outside the rules wait for a person.

Communication provides the mechanism for that coordination. Wilson uses phone, email, Microsoft Teams, Slack, and SMS to request information and distribute configured updates. For example, Wilson can ask a carrier for status by email or API, then notify the customer’s team through Slack or Microsoft Teams. It can also update a shipper by email and a consignee by email or SMS at supported shipment events.

Wilson can act on exceptions instead of merely displaying them. When Wilson detects a missed pickup, cancellation, or delay, it contacts the carrier and sends configured notifications to internal teams and customers. It can then initiate rebooking from the customer’s approved carrier list. Workflow rules determine whether rebooking requires approval. Strategic decisions and situations that fall outside those rules remain with the logistics team.

How Wilson gets orders and keeps its own records

Wilson can ingest orders without a TMS or a full integration project. Order data can arrive through an ERP, spreadsheet, email, or scheduled file drop. 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.

Write-back to the ERP depends on scope. EDI exchange depends on carrier support.

Wilson maintains searchable and exportable operational records after order intake. Those records cover shipments, quotes, sales orders, vendors, products, and addresses. Change history lets logistics staff review updates and identify when shipment information changed.

The records give manufacturers and distributors a working source for daily freight execution. Staff can find prior quotes, review shipment details, confirm vendor information, and export data for reporting or another business system. Teams can use Wilson’s dashboard and shipment records the way they would use a traditional TMS, and a company without a TMS does not need to implement one first.

A day of freight coordination with and without a TMS

When a company already uses a TMS

A manufacturer that already uses a TMS can move freight execution to Wilson, by Cartage lane by lane. Wilson connects to the manufacturer’s ERP and works from the data flow it already has, whether that is an ERP feed, email, spreadsheet, scheduled file drop, or API.

For a new shipment, Wilson requests quotes from approved carriers, follows up on missing responses, and applies the manufacturer’s approval rules before booking. Wilson keeps the shipment record, including the quote and booking activity, so the team can work from Wilson’s dashboard the way it would in a traditional TMS.

If the carrier later reports a missed pickup, Wilson contacts the carrier and alerts the internal team through Slack or Microsoft Teams. Wilson can also notify the customer when configured. When another carrier is required, Wilson initiates rebooking from the approved carrier list. Workflow rules determine whether Wilson proceeds automatically or waits for approval.

After delivery, Wilson follows up with the carrier for proof of delivery and records the document in its shipment history. The team can find the document in Wilson’s shipment record instead of updating a separate system.

When a company has no TMS

A distributor without a TMS can run the same operating workflow through Wilson and its own records. For example, Wilson can ingest a sales order from an emailed spreadsheet, request and compare carrier quotes, complete the approved booking, and coordinate pickup details with the relevant parties.

During transit, Wilson asks the carrier for status and records each update. If a delay threatens a customer commitment, Wilson contacts the carrier and sends configured notifications. After delivery, Wilson pursues the POD and files it with the shipment record.

Wilson maintains searchable and exportable records for shipments, quotes, sales orders, vendors, products, addresses, and change history. Teams can use Wilson’s dashboard and those records the way they would use a traditional TMS, without implementing one first.

TMS vs. Wilson: purpose, records, and daily coordination compared

A TMS and Wilson, by Cartage handle freight execution differently. The comparison below shows how Wilson replaces the TMS for freight execution and what each one records.

Do you need a TMS, Wilson, or both

Choose between a TMS, Wilson, or both based on the work the operation needs to perform. Company size and shipment volume reveal little about whether staff spend each day requesting quotes, chasing carriers, booking loads, checking status, and responding to exceptions.

A company that already uses a TMS can move freight execution to Wilson, by Cartage lane by lane, starting where staff still handle recurring follow-up manually. Wilson connects to the company’s ERP and works from the data flow it already has, whether that is an ERP feed, scheduled file drop, spreadsheet, email, or API, then maintains its own operational records while carrying out configured coordination work.

A company without a TMS does not need to implement one first. Wilson keeps searchable and exportable records for shipments, quotes, sales orders, vendors, products, addresses, and change history. Those records can support quoting, booking, scheduling, status follow-up, documentation, and communication without a separate TMS implementation. Write-back to the ERP depends on scope, and EDI depends on carrier support.

Wilson replaces the TMS for freight execution, and teams can use its dashboard and shipment records the way they would use a traditional TMS. Wilson fits when manual coordination consumes staff time, whether the company already uses a TMS or manages freight through other systems. A company with a TMS can move lanes to Wilson gradually instead of running two separate workflows.

Frequently asked questions

Does Wilson integrate with a TMS?

Wilson, by Cartage, replaces the TMS for freight execution rather than running next to it. Wilson connects to the company’s ERP and maintains its own operational records, and a company with a TMS can move freight execution to Wilson lane by lane.

How does Wilson get order data without a TMS?

Wilson can ingest orders from an ERP, spreadsheet, email, or scheduled file drop. 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. Write-back to the ERP depends on scope, while EDI depends on carrier support.

What records does Wilson keep on its own?

Wilson keeps searchable and exportable records for shipments, quotes, sales orders, vendors, products, and addresses. Each record includes change history, which helps logistics staff review prior actions and export operational data when needed.

Does Wilson replace a TMS?

Yes, for freight execution. Wilson connects to the company’s ERP, and teams can use Wilson’s dashboard and shipment records the way they would use a traditional TMS. A company without a TMS does not need to implement one first, and a company with one can move freight execution to Wilson lane by lane.

How does Wilson handle exceptions and rebooking?

Wilson detects shipment exceptions, contacts the carrier, and notifies internal staff. Wilson can also notify the customer when configured. When rebooking is required, Wilson initiates rebooking from the approved carrier list. Workflow rules determine whether Wilson proceeds automatically or requests approval.

What is the difference between a TMS and a logistics coordinator?

A transportation management system manages transportation plans, rates, settlement, and records. A logistics coordinator carries out the recurring actions that move freight forward, including requesting quotes, following up with carriers, booking loads, scheduling pickups, checking status, collecting documents, communicating updates, and responding to exceptions.

Where to start

The operational gap should drive the software decision, not the category label. A shipment that repeatedly waits for carrier follow-up, an appointment, or missing documentation reveals where coordination work slows execution. Reviewing those delays shows whether the current transportation tools cover the required work or leave recurring actions to staff.

During discovery, Cartage helps identify and map a high-impact coordination workflow. Cartage can trace a representative load and document its manual handoffs, approval requirements, and communication rules. Timing depends on scope: most teams start on a few lanes and expand from there, comparing Wilson against the current process under the same operating conditions.