Atlas: Transportation Management System

A transportation management system is the software that runs your freight: building loads, tendering them to carriers, holding your negotiated rates, tracking shipments in transit, and auditing the invoices that come back. Atlas does all of that in one platform instead of splitting it across carrier portals, rate spreadsheets, and email. You create a shipment, Atlas tenders it to the right carrier at the right rate, posts tracking as it moves, and then checks the freight invoice against what you booked before it is paid. The point is one connected workflow from planning to settlement, so nothing falls through the gap between separate tools. Atlas covers every mode, so truckload, LTL, parcel, and intermodal all run the same way.

Atlas is built for anyone who moves enough freight that running it manually stops scaling. That falls into three shapes, and each has a tailored edition. Shippers who own their cargo use TMS for shippers to control tendering, rates, and audit across their own lanes. Brokers use TMS for brokers to cover loads at margin, manage carrier relationships, and keep settlement clean. Third-party logistics providers use TMS for 3PLs to run freight for many clients at once inside one system. The core platform is the same, but the workflows, screens, and reporting are tuned to how each role actually operates. If you are not sure which fits, a systems lead can map your operation to the right edition during the walkthrough rather than forcing you into a generic setup.

Both options exist and you choose based on your team. If you would rather hand the desk over, managed TMS runs the platform for you. Self-serve means your own dispatchers and analysts log into Atlas and run tenders, rates, tracking, and audit themselves, with our support behind them. The done-for-you route means the CargoTrans freight desk operates the same platform on your behalf, executing tenders, managing carriers, and clearing audits while you keep full visibility into everything they do. Many customers start on one and shift toward the other as their volume or staffing changes, without replacing the system, because the data lives in the same place either way. You are never locked into staffing a freight desk just to get the benefit of the platform, and you are never forced to outsource control you would rather keep.

Atlas is organized around the freight lifecycle. Load tendering builds and offers loads to carriers on your routing guide. Carrier management holds your carrier records, scorecards, and onboarding. Rate management stores contract and spot rates so the right price is applied automatically. Freight audit and payment checks invoices against booked rates before money moves. Shipment tracking posts status across modes and carriers. Reporting and analytics turn all of that into cost and service metrics. Integrations connect Atlas to your ERP, order systems, and trading partners. Each module works on its own, but the value comes from them sharing one dataset, so a rate set in one place is the rate audited in another. Beyond the core, Atlas adds route optimization, freight procurement, appointment scheduling, freight claims, freight billing, and document management, plus a carrier portal, a shipper portal, and a freight CRM.

Load tendering is how a shipment goes from a plan to an accepted booking. In Atlas you build the load, and the platform offers it to carriers in the sequence your routing guide defines, at the rate already stored for that lane. A carrier accepts or declines, and if the first choice passes, Atlas moves automatically to the next without a dispatcher chasing anyone by phone. Accepted tenders flow straight into tracking, and the agreed rate carries through to audit, so what was tendered is what gets checked at settlement. First-tender acceptance is a metric you can watch, because a high rate means your routing guide and carrier relationships are healthy. The result is faster coverage with less manual back and forth on every single load.

Freight audit and payment compares every carrier invoice against the rate and terms that were actually booked in Atlas. Because tendering, rates, and audit share one dataset, the system already knows what the move was supposed to cost, so a duplicate charge, an incorrect accessorial, or a rate that does not match the contract is flagged before payment, not discovered in a quarterly review. Exceptions route to your team for a decision, while clean invoices pass through automatically. Over a large freight spend, small recurring errors add up to real money, and catching them at the invoice stage recovers it without a separate recovery project. You get a match rate you can monitor, so audit performance is a visible number rather than a hope that the carrier billed correctly.

Yes. Integrations connect Atlas to the systems where your orders and financials already live, so freight data flows automatically instead of being re-keyed. Common connections include ERP platforms, order management systems, e-commerce stores, and EDI trading-partner feeds for retail routing. Orders can drop into Atlas as shipments, tracking and status can post back to your system of record, and settled freight costs can feed your accounting. The depth is configurable: some customers want a full two-way integration, others start with a lighter feed and expand later. The goal is that your order system, your freight platform, and your finance system agree on the same shipment and the same cost, so nobody reconciles three versions of the truth by hand at the end of the month.

Atlas posts shipment status as it happens across every mode and carrier, so you see tender, pickup, in-transit milestones, and delivery in one view rather than logging into a different carrier site for each load. Configurable alerts flag shipments that are running late or at risk, so your team can act while there is still time to fix something instead of explaining a miss afterward. The same tracking data feeds reporting, so on-time performance becomes a measured metric per lane and per carrier. Because visibility lives in the same platform as execution and audit, the shipment you tendered, the shipment you are tracking, and the invoice you settle are all the same record. That continuity is what removes the blind spots that open up when tracking sits in a separate tool.

A carrier portal only shows you that one carrier's freight, and only the way that carrier wants to present it. Atlas is carrier-neutral and mode-neutral, so it shows all of your freight, across every carrier and mode, in one workflow with your rates and your rules applied. It also does things a carrier portal never will: enforce your routing guide, audit invoices against your contracts, and report cost and service across your whole network rather than a single vendor's lane. Carrier portals are useful for that carrier's tracking detail, and Atlas can sit above them. But the system of record for your freight, the place where tendering, rates, audit, and analytics come together, is the TMS, not a tool built to serve one carrier's view of your shipments.

A focused rollout on a defined lane set can be live in a few weeks: about a week to review your workflow and lanes, a few days to load rates and routing guides and connect an order feed, then a pilot on live loads before you scale. Broader programs with many carriers, deep rate structures, retail routing rules, or full ERP integration take longer because there is more data to load and validate. We sequence it so execution goes live first on a controlled lane set, then expand once tenders and audit matches are confirmed against real freight. The usual gate is not our setup work, it is how clean and complete your rate, carrier, and item data is on day one. Validated data up front is the biggest driver of a fast, low-exception launch.

Atlas is the transportation execution layer of the wider Captain platform. Captain covers supply chain visibility, customs and trade compliance, and warehouse tooling, while Atlas owns the freight side: tendering, rates, tracking, and audit. Because they share the same foundation, a shipment moving through Atlas can carry into the broader visibility and compliance view without a separate handoff or a second data entry. You can adopt Atlas on its own if freight execution is your immediate problem, and connect the rest of Captain as your needs grow. Buying the transportation system and the surrounding supply chain tooling from one platform means the pieces are designed to work together, rather than integrated after the fact between vendors who built to different assumptions.

Atlas is built to run every domestic mode in one system: full truckload, less-than-truckload, parcel, and intermodal, with the same tender, track, and audit workflow across all of them. That matters because most operations move more than one mode, and juggling a separate tool per mode is where errors and blind spots start. Rates, routing rules, and carrier records are configured per mode, so an LTL classification rule and a truckload lane rate both live in the platform and are applied automatically to the right shipment. Reporting then rolls all modes into one view of cost and service, so you can compare and shift freight between modes on data rather than habit. If your network spans several modes, the value of a single multi-mode platform grows with every additional lane.

Yes. Access is governed by role-based permissions, so each user sees and does only what their role allows, and every meaningful action, tendering a load, changing a rate, approving an invoice, is written to an audit trail. That means a rate change or a payment approval is traceable to a person and a time rather than a mystery during a dispute. Data is encrypted in transit and at rest, and the platform runs with monitored uptime and redundancy so freight operations are not stranded by an outage. Controls scale from a single dispatcher to a multi-branch operation without loosening. Because Atlas handles both freight execution and freight payment, the same controls that protect your shipment data also protect the money moving through audit and settlement.

Pricing follows how you use the platform rather than one flat license for everyone. The main drivers are which modules you turn on, your freight volume, the number of users, and whether you run self-serve or have our desk operate it for you. A shipper adopting execution and audit on a lane set looks different from a 3PL running many clients across every module, so the number is scoped to your operation. The done-for-you route folds the desk's labor into the arrangement rather than billing it as separate headcount. We start with a free walkthrough that maps your freight workflow and volume before quoting, so the price reflects your real usage instead of a generic rate card. That review also surfaces where the platform recovers cost, in audit and better tendering, which usually offsets a meaningful part of it.