LiteTMS is not a new version of LogisticsERP. We built it from scratch. The experience goes back to 2017, but the code, architecture and product decisions are new. We wanted to build a TMS around what transport companies had taught us, without carrying the limits of the older system into the next one.
LogisticsERP came first
We have been building software for transport companies since 2017. LogisticsERP was the first major chapter.
Companies used it for real daily work. Dispatchers managed orders, drivers sent updates, and owners kept an eye on vehicles and documents. That gave us something no planning session can provide: a clear view of what happens when software meets a busy transport desk.
We learned where information needs to appear. We saw small exceptions become everyday requirements. We also learned that a feature can work exactly as designed and still get in the way when it takes too many clicks.
Those lessons mattered. But they did not mean the old product had to live forever.
A larger system is not always a better system
Older software grows one layer at a time. One company needs another field. Another has a different document flow. Someone else needs a report for a specific customer. Every request makes sense on its own. Years later, the system can feel like a warehouse that contains everything but makes the right item hard to find.
Transport teams feel that weight quickly. A dispatcher cannot pause work to remember where a setting lives. A driver will not read a manual in a loading yard. An owner does not want to fund a long rollout before seeing the first real order on screen.
The biggest lesson from LogisticsERP was simple: a useful TMS must help from day one. The company should not have to learn the software before it can get back to transport.
We chose a clean start
You can keep renovating an old building. Sometimes the better answer is a clear site and a new plan.
That is how LiteTMS began. We did not move the LogisticsERP code and replace the logo. We started with the questions we had heard for years:
- How can a company start using a TMS without a rollout that takes weeks?
- How can the order, its documents and its conversation stay together?
- How can a team adjust its workspace without ordering custom development?
- How should pricing work when transport is busier one month and quieter the next?
The questions came with us. The old code did not.
Pricing had to match real transport work
Transport does not move at the same pace every month. A fixed package cannot see that. The invoice reads the same in a dead July and in a December when the fleet never stops, so the company keeps paying for capacity it is not using.
That did not feel fair to us.
LiteTMS keeps orders and contractors free and unlimited. You pay for the seats and the paid services the company actually used that month. A quieter month costs less. A heavy month costs more, but it grows with work the company really did, and nobody pays for a feature they never touched.
The full rate card is in the panel from the day you log in. The rate and current usage of every paid feature sit in the same place, before anything reaches the bill, so the end of the month is not a surprise.
This pricing model was not added as a marketing line after the product was finished. It grew from years of watching how work changes inside a transport company. You can read the full explanation in what LiteTMS is, and why it bills pay-as-you-go.
A new system backed by experience since 2017
LiteTMS is in early access because we want to grow it carefully and listen closely to the companies using it. That does not make transport software new territory for our team.
We know the cost of a screen that makes sense only to the person who designed it. We know that flexibility can become another word for a long setup. We know a feature nobody can find may as well not exist.
So we started again. We did not throw away the past. We gave ourselves room to use it properly.
If you want to see the result, register your company for free. You can add the first order the same day.
Questions people ask
- Is LiteTMS a new version of LogisticsERP?
- No. LiteTMS was built from scratch. LogisticsERP gave us experience with real transport work, but LiteTMS has new code, a new architecture and new product decisions.
- Why did you stop developing LogisticsERP?
- More changes to the older system would not give us the freedom we needed. Starting again let us design the whole product around a faster start, easier daily work and pricing that follows actual use.
- How long have you been building transport software?
- Since 2017. LiteTMS is a new system, but it is backed by experience gained while building software used by transport companies.
- Why does LiteTMS use pay-as-you-go pricing?
- Because order volume and team workload change from month to month. Orders and contractors are free and unlimited, while the company pays for the seats and paid services it actually used. Lighter use means a smaller bill, heavier use raises it, and an untouched feature costs nothing at all.