Twenty-two modules. One record.
Twenty-two modules is too many to hold in your head. Six is not. Below they are grouped the way an owner would describe the departments of a trucking company, rather than the way an engineer would describe a codebase — and every one of them reads and writes the same shipment record.
From the Lanexa 2.0 capability register · version 2.0.37 · reviewed 2026-08-24 · what we have chosen not to build is listed on its own page
One record. Eleven steps. Typed once.
A shipment enters Lanexa at the quote and leaves it as a settled driver payment. Every step below reads from the same record — which is why nothing is re-keyed at a department boundary, and why nothing quietly goes missing there either.
- Quoteprice the job
- Loadcustomer books it
- Tripplan the run
- Assigndriver + truck
- BorderACE / ACI filed
- PickupBOL signed
- Deliverfreight lands
- ProofPOD on file
- Invoicecustomer billed
- Collectmoney in, partners paid
- Settledriver paid
Revenue & Movement
This is the business. Everything else exists to serve or observe it — pricing work before it is committed, turning an accepted quote into a load, planning which truck runs it, watching what gets stuck, and handing work to a partner when you cannot cover it yourself.
Resources
The people and equipment the business runs on. These three modules answer the same question from different angles — is there a driver, is there equipment, and is the customer good for the money.
Border & Compliance
Most transportation software treats the border as somebody else's problem and fuel tax as a spreadsheet exercise. Here both are first-class parts of the load lifecycle — which, for a carrier running into the United States, is the difference between one system and three.
Money
Money in, money out, and the books that reconcile them. The ledger is what makes this a financial system rather than a billing screen: every invoice, bill, settlement and fuel receipt posts double-entry lines on its own.
Command & Insight
Knowing what is going on, and being able to prove what went on. Analytics is for exploring when you do not know what you are looking for; Reports is a catalogue for when you know exactly what you need and want it as a file.
Platform & Control
The configuration layer. Settings has the widest reach of any module — it writes the rules the other twenty-one obey — which makes it the highest-privilege surface in the product and the one most worth guarding.
