How to evaluate this requirement
A TMS price has meaning only alongside the work it includes. Ask for a written proposal covering users, shipping locations, shipment volume, modes, integrations, historical data, training, support and optional modules. Record one-time implementation charges, recurring software or service charges and any usage thresholds. This guide does not invent a MyMGN subscription price.
Define the connections and responsibilities
List the ERP, warehouse, order and accounting systems that must exchange data. Specify required fields, direction, timing, error handling and the owner of each interface. Ask who maintains carrier credentials and rate connections, and what happens when a carrier changes its interface or a business unit changes its shipping process.
Set measurable acceptance conditions
Use representative shipments to test rating, service eligibility, documents, pickup workflow, tracking and invoice exceptions. Confirm permissions, approval rules, data export and agreed support responsibilities. Include a difficult shipment and a corrected invoice rather than demonstrating only the cleanest happy path. Agree which unresolved items must be closed before rollout.
Introduce locations in a sequence your team can support. Assign training owners, a process for collecting issues and an operating fallback. Preserve original quote and shipment evidence so the new workflow can be checked against familiar records.
Compare the economics consistently
Evaluate proposals over the same planning period using the same volume and implementation assumptions. Separate a documented fee from an estimated internal effort or a hoped-for benefit. If a vendor proposes savings, ask for its baseline, service assumptions and measurement method. Select the system whose tested scope, responsibilities and economics support your LTL operation, then document why.