What Does It Cost to Replace a TMS Without Replacing the ERP?

Key Takeaways

By Maria Romero · Updated October 19, 2026

TMS replacement cost depends on the freight scope, supplier charges, ERP connection work, transition obligations, and retained internal effort. Keeping the ERP preserves its business role, but the freight handoff still needs definition. Wilson, by Cartage, replaces the TMS for freight execution and connects to the ERP order flow. A buyer needs an actual proposal to calculate the cost.

The cost worksheet should separate recurring and one-time items.
The ERP connection should identify fields, direction, timing, and error ownership.
Open shipments and financial records create transition work.
Unquoted requirements should remain pending rather than appear as zero.

Which cost lines belong in the replacement worksheet?

The replacement worksheet should expose the work each party must perform. The buyer should enter actual quoted terms and company-approved estimates for the selected scope.

Cost line	Input to request	Scope question	Responsible owner
Supplier charges	Proposed fee basis and applicable terms	Which freight activity does the price cover?	Procurement and finance
Setup	Quoted work and customer responsibilities	Who configures the operating workflow?	Supplier and operations
ERP handoff	Defined method, fields, and technical work	Which reads and writes are included?	IT and supplier
Transition	Open-load and unfinished-task plan	Which process finishes each obligation?	Operations and finance
Retained capabilities	Required planning or specialist functions	Which services remain outside the replacement?	Business owners
Internal effort	Observed or clearly labeled estimated work	Which roles still operate and support the process?	Department owners

The worksheet is a buying framework. The worksheet does not establish a market price or implementation duration.

What stays in the ERP after replacement?

The ERP retains its agreed business responsibilities after a freight execution replacement. The project should identify the order information Wilson receives and the shipment results the company wants returned.

The business should define the release condition before selecting a technical method. An order can exist before the company authorizes quoting or booking. The freight process needs the relevant instruction and usable shipment details.

The implementation should specify identifiers, locations, freight characteristics, timing, permissions, and update direction. The company should also identify the owner of an unsuccessful transfer. A connected system is not automatically a complete operating handoff.

Wilson's exact ERP method depends on the customer environment and agreed scope. The freight software cost questions help identify commercial inputs. The buyer should list required ERP work separately. The buyer should not assume a universal connector or unrestricted write-back.

How should buyers calculate Wilson's supplier charge?

Buyers should calculate Wilson's charge using the applicable proposal and freight payments coordinated through Wilson Wallet. Wilson does not charge a subscription or platform fee.

Wilson pricing is a percentage of Wallet-coordinated freight payments. The proposal should supply the relevant percentage and payment scope. The buyer should not invent a flat fee per shipment or apply an assumed percentage to all company freight.

A deployment fee applies when the customer wants Cartage to handle setup. The amount depends on setup complexity. The worksheet should distinguish that proposed work from customer-owned integration, training, or operating responsibilities.

Carrier transport charges should remain visible separately from software and service charges. Freight payments can determine the fee base without becoming entirely software expense. The buyer should identify which period and shipment population the comparison covers before calculating an operating total.

Which capabilities might remain outside the replacement?

The company may retain capabilities outside freight execution even when Wilson replaces the TMS for that execution scope. The cost review should identify those requirements explicitly.

Wilson handles creating, quoting, tendering, tracking, audit, and payment within company rules. Wilson does not provide route optimization, network planning, or customs clearance. Cross-border freight coordination does not make Wilson a customs broker.

The current TMS may supply a planning function the business still uses. Oracle's public logistics documentation illustrates the breadth available within transportation software. The buyer should inspect the actual installed functions before assuming every responsibility disappears.

The worksheet should name the future owner of each retained requirement. A specialist product, existing process, or another approved service may remain necessary. A supplier price that excludes a required function should not be compared with a broader proposal without showing the difference.

What transition work should finance and operations include?

The transition plan should account for commitments that remain unfinished when execution changes hands. Delivered loads can still need documents, invoice reconciliation, or payment.

Operations should identify unbooked requests, accepted loads, in-transit freight, and pending changes. Finance should identify unresolved invoices and payment responsibilities. The team should decide which process finishes each group.

The plan should preserve the records needed for later review. A carrier's original terms may still matter after the transport task ends. A supplier exit or account change should not remove evidence the company still needs.

The TMS departure records checklist helps identify the handover. The worksheet should include any applicable record-access or transition work using the actual agreement. The buyer should not infer standard exit terms from another company's project.

How should the company compare the replacement choices?

The company should compare the same freight responsibility over an explicitly stated evaluation period. A license total and an execution proposal can buy different work.

The comparison should separate quoted charges, observed baseline effort, estimated future work, and unresolved items. An uncertain integration line should remain pending. A blank cell should not reduce the total by silently becoming zero.

The review should test changes in covered volume, scope, and required connections using company-supplied assumptions. The worksheet should expose those inputs so finance can revise the model without rebuilding the entire business case.

The purchase recommendation should connect the cost model with demonstrated workflow evidence. A cheaper configuration may leave important carrier tasks with employees. A broader proposal may include work the business does not need. The defensible choice meets the defined freight requirement and preserves the ERP's role without inventing savings or a universal replacement price.

FAQs

How much does TMS replacement cost when the ERP stays?

The amount requires an actual scope and proposal. Buyers should include supplier charges, ERP work, transition tasks, retained capabilities, and internal effort.

Does Wilson require a new ERP?

No. Wilson connects to the ERP order flow and replaces the TMS for freight execution. The connection method depends on the environment.

Does no subscription fee mean no project cost?

No. Wilson uses Wallet-based pricing, and Cartage-handled setup can carry a complexity-dependent fee. Other responsibilities need explicit scoping.

Should unquoted work appear as zero?

No. The worksheet should mark unquoted work pending and assign an owner to obtain the necessary scope and price.