And how to fix them

There’s a common belief among transportation company owners:
“If we get more orders, we’ll make more money and profit.”

In reality, the opposite often happens: orders grow, but profit stays flat or even drops.

Why? Because as volume increases, so does:

• Dispatcher and ops workload
• Headcount and operating costs
• Mistakes from manual work and human error
• Service quality issues: cancellations, refunds, credits, negative reviews

And the worst part is that information starts to spread everywhere: spreadsheets, chats, email threads, notes, different systems.

It gets harder for the owner to see the real picture – and harder for the team to stay aligned.

That’s when familiar scenarios show up:

• Ride changes don’t get entered in time
• Supplier pricing changes, but the customer price doesn’t
• The route or pickup time changes, but the calculation stays the same
• Paid waiting, overtime gets lost, logged late, or estimated “by feel”

So margin doesn’t leak because you don’t have orders. It leaks because you don’t have consistent control over costs and changes.

Here’s a simple test:
Can you quickly answer this for a specific ride?
“Who executed it, what changed, what did it actually cost us, and what did we earn?”

If you can’t. Can you really trust your reporting?

Problem: The route, time, or conditions change, but pricing isn’t updated fast enough, and margin slips through your fingers.

How iTransfers fixes it:

• Automatic price recalculation: if important ride parameters change – such as route, duration, waiting time – the system instantly updates the ride cost.
• Rides: Changes are captured at the ride level, not “somewhere in a chat.”
• Notifications: Dispatchers/managers see updates immediately (email, in-app, and – if needed – in the apps).
• History: You can see who changed what, with before/after values, great for control and post-mortems.

Problem: Paid waiting and overtime are either money or a customer dispute. But in practice they get missed, logged after the fact, or estimated.

How iTransfers fixes it:

• iTransfers automatically calculates and records paid waiting and overtime per ride, so it doesn’t depend on human memory.
• If manual control is needed (edge case, time adjustment, special agreement), a dispatcher can edit it manually.
• The result: Waiting and overtime stop being a “verbal agreement” and become a transparent part of the ride economics, easy to reconcile in reports.

Problem: The supplier updated the ride cost – changed the rate, a reroute happened, and extra services were added – but the customer price stayed the same. As a result, you’re losing margin because you didn’t update the customer’s price in time.

How iTransfers fixes it:

• Each ride has a dedicated Supplier tab showing the final supplier cost with full line-item detail.
• If the final cost changes: the old price is struck through, and the new price is shown.
  That way a dispatcher can’t miss it – and can re-check the financial parameters in time.
• A flexible notification system helps the team align on the update and communicate it to customers and suppliers when needed.

Problem: You have a supplier, a driver, or a shift, but costs live somewhere else. Later, it’s impossible to tell who actually generated profit and which rides went negative.

How iTransfers fixes it:

• Shifts: Create a shift as driver + vehicle, then assign that shift to a specific ride.
• In the App the driver can add ride-specific expenses: toll roads, paid parking, a car wash, water, and any other execution-related costs.
• Those expenses are automatically tied to the ride, visible in the ride card and reports.
• Linking Shift/Supplier with Rides gives you data for analysis: who executed, ride count, exceptions, paid waiting, and extra costs.

Problem: Copy-paste, duplicated information, constant reconciling, “who changed this?” in chats, that’s paid team time, every day. The more orders you have, the more chaos and the more expensive mistakes become.

How iTransfers fixes it:

• Control Center: a task list for dispatchers tied to each ride what needs to be done: call the driver, notify the customer, attach a supplier, check payment, etc.
  Tasks appear automatically via a flexible rules-and-triggers system: you define what events should generate a task for a specific dispatcher.
• Transparent statuses + notifications: iTransfers has statuses for orders and rides, payment statuses.
  This reduces manual syncing and calls: you can see whether the customer paid, whether you paid the supplier, and what status the ride is in on the supplier side.
• Roles & Permissions: less chaos and fewer “everyone has full access,” making it easier to replace staff, scale, and control responsibility.
• History: every ride has a History tab showing all actions with timestamp, user, and before/after values – no more “memory debates,” faster root-cause analysis.