Business management · TMS, Freight and Deliveries
Freight transport management: carriers registered with versioned freight rate tables, quoting that compares tables and carrier integrations, loads consolidated by vehicle weight and cubage, deliveries routed with time windows, a driver app with delivery receipt and signature, freight bill audit that blocks the payable when it falls outside tolerance, OTIF measured properly and the tax side of transport with CT-e and MDF-e assembled and validated.
The problem and the fix
If any of these situations sounds familiar, it is because they happen in almost every graduation company, until the right system comes in.
The carrier sends the invoice and nobody checks it: whatever came in gets paid.
Freight bill audit against the rate table in force, line by line. A variance above tolerance blocks the payable on the server, not just on the screen.
Freight is quoted over the phone and every order goes out at a different price.
Rate tables per carrier with weight bands, cubage, minimum charge, ad valorem, GRIS (cargo risk management fee), tolls and ICMS (state VAT), versioned with effective dates. The quote compares the options and records the one chosen.
The load goes out however it fitted, and the truck comes back either half empty or over weight.
Consolidation against the vehicle's real capacity, taking both weight and cubage into account, with utilization calculated before loading.
The delivery arrives and nobody knows who signed for it, and the complaint turns into one person's word against another's.
Driver app with check-in at the destination, photo, delivery receipt, signature and the name of whoever took delivery, all stored as proof of delivery.
The on-time delivery metric looks good because it only counts what happened to be delivered in full.
OTIF calculated as a logical AND: on time and in full, with the agreed window taking precedence over the promised date and each criterion carrying its own denominator.
In practice
Everyday situations at graduation companies, from the problem to the result, using the modules on this page.
The carrier bills above what the rate table allows on a batch of deliveries.
Every line of the invoice is recalculated using the rate table in force on the shipping date. The difference shows up per bill of lading, with the reason, and the payable is blocked.
The conversation with the carrier starts from the calculation breakdown, and payment only goes out after someone decides.
Five destinations, different time windows and one company vehicle.
The load consolidates the orders by weight and cubage, route optimization sequences the stops and the driver gets the sequence in the app.
Fewer kilometers driven, delivery windows met and proof of delivery with a signature at every stop.
The company's own load leaves for another state and needs an electronic manifest.
The MDF-e (electronic manifest of fiscal documents, model 58) is assembled from the load, with drivers, route and the linked documents, validated against the rules that cause rejection.
The document comes out complete and checked. Filing with SEFAZ (the state tax authority) is the step that depends on certification in a live environment.
How it works
Every step is a real module, and what comes out of one goes into the next without anyone typing it again.
Module by module
7 modules and 41 features on this page, all running on the same class, graduate and event records.
Who does the hauling, with the terms agreed on record.
The agreed price, versioned, in the shape the carrier sends it.
The options side by side, and the choice on record.
What travels together, in which vehicle, at what utilization.
The stop, the proof and the exception, in the hands of whoever delivers.
Check before paying, and measure what was promised.
CT-e and MDF-e assembled, numbered and validated.
Compare the modules and choose the setup that fits your operation.