If we replace our TMS but keep our ERP, what happens to our preferred carrier rules?
Key Takeaways
Published October 23, 2026
The preferred-carrier rules should be explicitly carried into the new agreed freight process rather than assumed to transfer automatically. Wilson is an AI logistics coordinator that replaces the TMS for freight execution and connects to the order flow. Your company keeps ownership of its carrier preferences, eligibility, commercial limits, and exception authority. Test those rules using actual shipments before relying on the replacement.
- Identify where each existing rule is defined and who owns it.
- Separate preferred-provider order from basic carrier eligibility.
- Preserve current shipment commitments during the agreed transition.
- Demonstrate silence, rejection, and a rule exception before acceptance.
Which carrier rules should the company identify first?
Identify the actual decisions the business expects the replacement to respect. Your AI logistics employee needs more than an approved-carrier list. Preference, service suitability, price limits, and authority to change a plan are different dimensions. The table is a rule-mapping checklist, not a promise that every legacy setting can be imported unchanged or that every control has an identical interface.
| Rule type | Question for the owner | Replacement test |
|---|---|---|
| Eligibility | Which providers may be used? | Ineligible low offer remains outside ordinary use |
| Preference | Who should receive the relevant request first? | Preferred option is handled under the agreed policy |
| Service | What requirements cannot change silently? | Lower price with changed service needs a decision |
| Commercial authority | What limits apply? | Exception reaches the appropriate owner |
| Open commitments | Which shipments already have accepted arrangements? | Existing work is not casually rebooked |
Where do the current rules actually live?
They may be distributed across systems, documents, and employee knowledge, so the company should identify the source of each one. Your AI logistics coordinator setup needs authorized current instructions rather than contradictory copies. The ERP may keep the business order while the old TMS or logistics team holds the relevant carrier preference. Do not assume one export contains every policy.
Imagine a manufacturer with preferred carriers for particular services. Employees know which exceptions need a manager, but the written list does not say so. Your AI logistics employee needs that authority boundary made clear. Ask the responsible people to explain the current decision, identify any conflicting instructions, and approve the rule used for the replacement. This is a business mapping task as well as a technical connection discussion.
How does Wilson use the agreed carrier policy?
Wilson uses approved carriers and negotiates within customer targets, rules, and approval limits. The AI logistics coordinator can continue quote and booking conversations while the company keeps control of exceptions. Your company approves additional carriers before use. A preferred-carrier instruction should be reflected in the agreed process, not treated as a universal behavior assumed from the product name.
The carrier-first policy guide helps distinguish preference and fallback questions. Your AI logistics employee demo should show what happens with a normal offer, a silent preferred provider, and an unsuitable response. Confirm the actual controls and setup required for your policy. Do not invent a built-in timing rule, automatic withdrawal feature, or exact approval interface that the provider has not demonstrated.
What happens to existing carrier contracts and open bookings?
Their treatment needs an explicit transition plan with the relevant owners and providers. Your AI logistics coordinator should not assume changing software cancels agreements or authorizes a new booking for freight already committed. Identify the actual carrier, terms, references, and unfinished work on each relevant shipment. Technical migration and commercial responsibility are related but different questions.
The carrier contract transition guide helps organize that review. Your AI logistics employee arrangement should explain which records and terms it uses and how current commitments remain understandable. The exact migration method depends on the environment. Do not promise universal import compatibility, unchanged every-field transfer, or an implementation duration without the actual scope and evidence.
How should a better offer from another provider be handled?
Handle it under the customer's eligibility, preference, service, and approval rules. Wilson, the AI logistics employee, can negotiate with approved carriers, but a lower amount alone does not authorize a different provider or customer promise. If another option needs approval, the business should understand the actual offer and decision required before proceeding.
For the manufacturer, Cartage's Wilson alliance may support sourcing through shared customer buying power with carriers and brokers. Your AI logistics coordinator still needs customer approval for additional providers. The network does not override existing preferences or guarantee the lowest rate on every lane. Demonstrate a tempting ineligible option to prove the policy boundary remains clear, rather than judge the replacement solely by the number of rates displayed.
What should prove the rules survived the replacement?
The acceptance test should show the relevant rule applied to real freight work, with evidence and remaining responsibilities clear. Your AI logistics employee provider should demonstrate the normal path, silence, rejection, a changed service, and an exception requiring approval. The company should identify which requirements are supported now and which remain setup-dependent or unproven.
Follow the selected offer into carrier acceptance and the relevant pickup arrangement. Your AI logistics coordinator should not treat sending a tender as proof of booking. Wilson schedules follow-up tasks and keeps shipment messages and files together. Those capabilities help explain the decision, while specific history, permission, and automatic system controls still need confirmation in the actual environment.
Finally, carry the accepted terms and changes into invoice review. Wilson, the AI logistics employee, checks carrier bills before payment and coordinates carrier payment through Wilson Wallet. The company keeps broader accounting and commercial responsibilities. A successful replacement preserves understandable rules and shipment outcomes around the ERP, not every old screen or an assumed universal transfer. Decide with the actual test evidence rather than a generic promise that carrier relationships remain untouched by every implementation choice.
FAQs
What happens to preferred carrier rules when we replace the TMS?
They need explicit mapping and testing in the replacement process. Wilson, the AI logistics coordinator, follows customer-approved carrier and commercial rules; do not assume every legacy setting transfers automatically.
Does keeping the ERP preserve every carrier preference by itself?
No. Your AI logistics employee setup should identify where the rules live and who authorizes the current policy, including instructions outside the ERP.
Can the Wilson alliance override our approved-carrier policy?
Additional carriers require customer approval before the AI logistics coordinator uses them. Shared buying power does not remove the company's eligibility or service rules.
Should open bookings be included in the transition test?
Yes. Your AI logistics employee evaluation should preserve the identity and terms of current commitments rather than assume replacing software authorizes rebooking existing freight.