What to Ask Before Hiring a TMS for Your Fleet

Your logistics team has spent weeks capturing shipping manifests by hand and fixing Carta Porte errors before every shipment, because a single wrong data point can leave a unit stopped on the highway. Leadership already approved the budget for a TMS, but the first three demos look alike: maps with moving units, screens in corporate colors, promises of "total control of your fleet." None of them explained what happens the day the SAT updates a catalog, or whether manifests are really generated on their own or someone is still capturing them by hand behind the pretty screen.

Before hiring a TMS, it's worth asking three concrete things: whether Carta Porte compliance is built in natively, whether manifests generate automatically or require manual capture, and whether unit and driver control lives in the same system or in separate tools.

The mistake of choosing a TMS based only on the tracking map shown in the demo

GPS tracking is the easiest part to demo in a sales presentation: a map with moving units always looks impressive. The problem is that tracking, on its own, isn't what costs a transport operation the most when it fails. What stops a unit on the road is a badly generated manifest or an incomplete Carta Porte data point, not a missing dot on a map.

Why tax compliance matters more than on-road visualization

Since January 2026, Mexico's tax authority (SAT) tightened Carta Porte validations and updates catalogs more frequently. A TMS that doesn't keep up with those changes shifts the risk back to your team, which ends up manually reviewing what the system should validate on its own before the unit leaves for the road.

The three questions that actually separate a functional TMS from one that just looks good in the demo

Is Carta Porte compliance built in natively?

Ask directly whether Carta Porte SAT validation lives inside the TMS or depends on an external add-on that has to be configured and maintained separately. A system with native compliance updates its catalogs automatically; one that depends on a third party shifts that responsibility, and the delay, back to your team.

Are shipping manifests generated automatically?

Ask them to show you, in the demo itself, a complete manifest being generated from the order data to the final document, with no manual capture in between. If at any point in the process someone has to copy data from one system to another, that manual step remains a point where your fleet can get stuck.

Does unit and driver control live in the same system?

A TMS that separates unit control from driver control into different modules, or worse, different systems, forces your team to manually cross-reference information to know which driver is assigned to which unit and whether their paperwork is current. That information should live in one place, viewable on a single screen.

What happens if your TMS isn't integrated with your ERP

A TMS that operates in isolation from the ERP forces your billing team to re-enter what logistics already recorded, with the risk that the two numbers won't match. At Oasys we integrate TMS, ERP, and WMS into a single system, with native Carta Porte SAT compliance, automatic manifests, and unit and driver control on the same platform, running on our own servers in a data center.

Frequently asked questions

What happens if the SAT updates a Carta Porte catalog mid-operation?

A TMS with native compliance updates the catalog on the vendor's side, without your team having to intervene manually to keep generating valid manifests.

Can a TMS work without being connected to the ERP?

It can work in isolation, but it forces information to be captured twice between logistics and billing, with the risk of inconsistencies between the two systems.

How long does it take to implement a TMS integrated with ERP and WMS?

It depends on your unit volume and the complexity of your current operation; ask each vendor for a specific timeline with a post-launch support protocol, not just the system's delivery date.