Automating carrier coordination shouldn't require replacing the ERP
Key Takeaways
- Manufacturers and distributors can automate carrier coordination, load scheduling and carrier quoting without a full system overhaul, by adding an AI logistics agent that works from the ERP they already use.
- Wilson, by Cartage, is an AI logistics agent that executes carrier management work: requesting, negotiating and comparing carrier quotes, booking loads, scheduling pickups and deliveries, following up with carriers, responding to exceptions, and auditing and paying carrier invoices.
- Wilson works with existing ERPs, including 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 can also start from a spreadsheet, email, scheduled file drop or API.
- No ERP replacement is required to start. Many companies begin with a simple daily order feed. How long deployment takes depends on scope: standard freight with existing carriers is the fastest to set up, and ERP integrations and custom workflows are scoped up front. Wilson replaces the TMS and connects to the ERP, not to another TMS.
- Wilson negotiates quotes against the company's targets and books the best option, under the rules and approval limits the company sets.
Why manual carrier coordination gets expensive
A distributor's logistics team runs every load the same way: orders come out of the ERP, a coordinator emails carriers for rates, waits, compares, books, confirms the pickup, reconfirms it the day before and answers status questions until delivery. As volume grows, the team adds people to keep up. Leadership starts looking for a carrier management system, and every option on the shortlist seems to start with replacing or re-implementing something.
Manual carrier coordination gets expensive because every load repeats the same chain of emails and calls, and the only way to handle more loads is to add more people. The cost is often labor and rushed decisions, not the software the company already has.
The ERP usually isn't the problem. It already holds the orders, customers and ship-to addresses. What's missing is something that takes those orders and does the carrier work around them: quoting, booking, scheduling, follow-ups and updates. When that work stays manual, companies often pay for it twice, once in coordinator hours and again in freight costs, because busy teams ask fewer carriers for quotes and accept the first reasonable answer.
What "automating rate negotiation" usually means in practice
For most shippers, “automating rate negotiation” means getting more competitive quotes on every load, negotiating them against clear targets and choosing consistently. Wilson, by Cartage, gets the quotes, negotiates them against the company’s targets and books the best option, under the rules and approval limits the company sets.
In practice, the cost levers a logistics team controls day to day are:
- Asking more carriers on every load, not just the one or two who answer fastest.
- Following up on missing quotes, so decisions aren’t made with half the responses.
- Negotiating against targets, so quotes above the company’s target don’t get booked by default.
- Comparing quotes the same way every time, on price, transit time and service.
- Applying approval limits, so routine loads book directly and expensive exceptions go to a person.
Wilson handles all five. It books only carriers the company has approved, starting with the company’s own carriers. Cartage can also introduce carriers from its network, and they’re available to Wilson only after the company approves them. For every load, the company sees the carrier and the price. Wilson can also use shipment and rate data from the loads it runs to produce carrier performance or lane-rate reports on request. For more on this, see freight cost optimization software workflows and AI carrier quoting.
What to look for in a carrier management system that won't require an overhaul
A carrier management system avoids a full overhaul when it works from the ERP and channels a company already uses, and when it can start small.
The criteria that matter most:
It reads orders from the current ERP, or from a spreadsheet, email or file drop while a deeper connection is set up.
It doesn't require replacing the ERP, and it keeps the shipment record itself instead of depending on a separate TMS.
It works with carriers the way they already work, which for many carriers means email.
It executes the work, not just stores carrier records: quoting, booking, scheduling, follow-ups and updates.
It keeps the team in control, with approved carriers and approval rules.
It can start on a few lanes and prove results before expanding.
How Wilson, by Cartage, connects to an existing ERP
Wilson, by Cartage, connects to a company’s existing ERP instead of replacing it. Orders flow from the ERP to Wilson, Wilson coordinates the freight, and Wilson is the system of record for shipments. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
| Connection option | How it works | Good for |
|---|---|---|
| ERP order feed | Wilson ingests orders directly from the ERP | Companies ready to connect their ERP |
| Daily order feed or scheduled file drop | A regular export of orders is sent to Wilson | Starting quickly, without an integration project |
| Spreadsheet | Orders are shared in a spreadsheet or as CSV or Excel files, which Wilson reads on a schedule | Teams that manage shipments in spreadsheets today |
| Orders are sent to Wilson’s email address | Teams whose orders arrive by email |
ERPs: 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.
Writing back to the ERP: write-back is optional and set up per customer. Wilson can send an updated CSV or Excel file by email for the ERP to import, write to a shared table, or update the ERP through an API connection where one is available. The method is defined during onboarding.
Records: Wilson is the system of record for shipments, quotes, carriers and documents, and every message, confirmation and change is recorded in a change history.
What Wilson is not: Wilson is not an ERP and doesn’t replace one. Wilson replaces the TMS: it is the system of record for shipments and the execution layer that does the work, and teams can use its dashboard the way they would use a traditional TMS. It connects to the ERP, not to another TMS. It is not a freight broker; carrier relationships, contracts and rates stay with the company.
Wilson replaces the TMS and connects to the ERP
To be precise: Wilson replaces the TMS for freight execution and connects to the company's ERP. A TMS, or transportation management system, is software used to plan, book, and track freight. An ERP, or enterprise resource planning system, is the company's main business system for orders, inventory, and accounting. The ERP stays. Wilson takes orders from it, runs each load, and can send results back when write-back is in scope. A company without a TMS does not need to buy one first, and a company that has one can move execution to Wilson lane by lane.
A daily file versus a full connection
There is more than one way to connect, and they are not the same. A daily file is the fastest way to start. A full connection does more, but takes more setup. Wilson works from the connection or data flow the company already has.
| Connection type | How orders reach Wilson | How results get back to the ERP | Good for |
|---|---|---|---|
| Daily or scheduled file | The ERP exports open orders to a file on a schedule | A return file the ERP imports, if in scope | Starting fast with no IT project |
| Spreadsheet or email | Orders are shared as a sheet or an email | Updates by email or a shared sheet | Small volumes or a first lane |
| ERP feed or API | Orders flow from the ERP as they are released | Status, costs, and documents written back where the ERP allows it | Higher volumes and fewer manual steps |
With a daily file, new orders reach Wilson once or a few times a day, and anything released between files waits for the next one. With a feed or API, orders arrive as they are released and updates can go back sooner. Many teams start with a file and add write-back later. 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.
What Wilson automates: carrier quoting, load scheduling, booking and follow-up
Wilson, by Cartage, automates the day-to-day carrier coordination behind every load, across all 6 stages of the shipment lifecycle: create, quote, tender, track, audit and pay.
| Workflow | What Wilson does |
|---|---|
| Carrier quoting | Requests quotes from the company’s approved carriers, follows up, negotiates against the company’s targets, compares responses and applies approval rules |
| Booking | Tenders the company’s approved carriers, starting with its own, and produces rate confirmations and bills of lading |
| Load scheduling | Confirms and reconfirms pickup and delivery times with carriers (more on load scheduling) |
| Carrier communication | Communicates by phone, email, Slack, Microsoft Teams and SMS |
| Tracking and updates | Tracks each load through the best source available (carrier API, GPS or ELD data, or the carrier’s website by PRO number, otherwise by email or phone) and updates the team, shipper and consignee at every milestone |
| Exceptions | Contacts the carrier, notifies stakeholders and initiates rebooking from the approved carrier list, with or without approval |
| Documentation | Produces packing slips and pallet labels, and follows up on proof of delivery |
| Audit and pay | Audits and reconciles carrier invoices against what was booked, and pays carriers from a wallet the company preloads |
| Carrier performance | Produces carrier performance or lane-rate reports on request, using shipment and rate data from the loads it runs |
Wilson supports LTL, FTL, ocean, drayage, parcel and cross-border freight. Most customers start on a few lanes and expand from there. Impact is measured by comparing the lanes Wilson runs with how those lanes ran before. Companies onboard Wilson like a new hire, with its own email address, access to their systems and their playbook (carriers, rules, approval limits and contacts), either on their own or with the Cartage team.
FAQs
- What carrier management systems can integrate with an existing ERP without a full system overhaul? Wilson, by Cartage, is an AI logistics agent that works from a company's existing ERP, including 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 automates carrier quoting, negotiation, booking, load scheduling, carrier follow-up and freight invoice payment without replacing the ERP.
- Can carrier coordination be automated without an integration project? Yes. Many companies start Wilson with a simple daily order feed, spreadsheet, email or scheduled file drop, and expand to a deeper ERP connection later. How long deployment takes depends on scope: standard freight with existing carriers is the fastest to set up, and ERP integrations and custom workflows are scoped up front.
- Can AI automate load scheduling? Yes. Wilson confirms and reconfirms pickup and delivery times with carriers, updates everyone involved and responds when a pickup slips.
- Does Wilson automate rate negotiation? Yes. Wilson gets the quotes, negotiates them against the company's targets and books the best option, under the rules and approval limits the company sets.
- Does Wilson write data back to the ERP? Yes, when the customer wants it. Write-back is optional and set up per customer: an updated CSV or Excel file by email, a shared table, or an API connection where one is available.
- Does Wilson replace a TMS or an ERP? Wilson replaces the TMS: it is the system of record for shipments and the execution layer, and teams can use its dashboard like a traditional TMS. It does not replace the ERP; it connects to it.
- Is Wilson a carrier management system? Wilson is an AI logistics agent that executes carrier management work, including quoting, negotiation, selection, booking, scheduling, communication, exception response and carrier performance reports on request, connected to the company's existing ERP and channels.
- How is Wilson priced? There's no subscription fee. Pricing is a percentage of the carrier payments that run through Wilson, and it covers the full lifecycle: create, quote, tender, track, audit and pay. Pricing scales down as volume grows, and Enterprise pricing is custom.
Conclusion
Spending too much on manual carrier coordination usually doesn't mean the ERP needs replacing. It means the work around each load, like quotes, bookings, schedules, follow-ups and updates, still depends on people doing it by hand. Wilson, by Cartage, takes that work on, starting from the ERP a company already has, without replacing the ERP. The practical first step is to connect a daily order feed and start Wilson on a few lanes, comparing them with how those lanes ran before. Companies can set Wilson up themselves or with the Cartage team.
Sources
- Cartage, Wilson product FAQ, October 2026: https://cartage.ai