How Chicago's Serbian Trucking Companies Run Their Fleets, and What Every Carrier Can Learn

Chicago moves more freight than almost any city in the country. It's the largest rail hub in the United States, it sits where I-55, I-57, I-80, I-88, I-90 and I-94 meet, and its suburbs are full of warehouses, intermodal ramps and truck yards. It's also home to one of the largest Serbian communities in the United States, and a lot of that community works in trucking.

Drive through Elk Grove Village, Des Plaines, Bolingbrook or Joliet and you'll pass yards owned by carriers that started with one truck and an owner who drove it. Many were founded by people from Serbia, Bosnia and Herzegovina, Montenegro, Croatia and North Macedonia, and they grew into fleets of twenty, fifty or a hundred trucks. They run differently from a textbook carrier, and most trucking software wasn't built with them in mind.

This article is about what those fleets need from a transportation management system (TMS). If you run a carrier anywhere in the US, most of it applies to you too.

How many Balkan-owned fleets actually run

Every company is different, but a few patterns come up again and again:

• The owner still knows every truck. The company is often family-run, and the owner, a spouse or a son or daughter handles the money, the insurance and the big customers.
• A mix of company drivers and owner-operators. Leased-on owner-operators are common, and each of them expects an accurate statement every week.
• The back office is split across an ocean. Dispatch, billing or safety is often handled partly from Serbia or elsewhere in the Balkans, by people who work while Chicago sleeps.
• Conversations happen in Serbian. Drivers, dispatchers and the office talk on Viber or WhatsApp, while brokers, shippers and factoring companies get everything in English.
• Growth comes in jumps. A new contract or a friend's fleet joining can add ten trucks in a month, and the software has to keep up without a new price every time.

Dispatching Chicago trucks from Belgrade or Novi Sad

Central European time is seven hours ahead of Chicago for most of the year, and six hours ahead for a few weeks in March and around the end of October, when the US and Europe change their clocks on different dates. A dispatcher in Serbia covering the US day shift works from early afternoon into the night.

That works well, as long as the software doesn't make people do time-zone math in their heads. A TMS for a split team should:

• Show every pickup and delivery appointment in the facility's local time, the way the rate confirmation states it, so nobody converts a 7:00 AM appointment in Dallas by hand.
• Keep the whole story on the load: notes, status changes and documents, so the morning shift in Chicago can pick up where the night shift in Serbia stopped.
• Show where each truck is and whether it will make the appointment, without phoning the driver. In Ella, the dispatch board shows the truck's position, miles and drive time left, and whether the load is on time, at risk or late.
• Record who changed what and when, so a wrong rate or a changed appointment can be traced in a minute instead of argued about.

We cover this in more detail in running a dispatch team from another country.

Owner-operators and weekly settlements

Owner-operators stay with carriers that pay them correctly and on time. For a fleet with many leased-on trucks, the weekly settlement is the most sensitive document the company produces: gross per load, minus fuel, insurance, trailer rent, ELD fees, escrow and advances, plus reimbursements.

When that statement is built in a spreadsheet, every week carries a risk of a missed fuel transaction or a deduction charged twice. A TMS should build it from the loads, fuel card imports and recurring deductions already in the system, send it to the driver by email or the driver app, and keep proof that it was delivered. When a driver questions a number, you open the load and the deduction instead of searching through a chat thread.

Your data should stay in the family

A family business plans in decades. The load history, customer list, lane rates and settlement records you build over ten years are worth real money, to you and to anyone who might buy the company one day.

With most subscription software, that history lives on the vendor's servers and leaves only as whatever export the vendor allows. Ella works the other way: you own the code and the database, it runs on accounts in your company's name, and there's no per-truck fee when the fleet grows. If you ever stop working with us, the system and every record stay with you. See ownership and privacy for how that works.

Talking to drivers in their own language

With Ella's driver app, an add-on published under your company's own name, drivers see their loads, scan BOLs and receive their statements on their phones. For safety messages, the office can text one driver or the whole fleet at once through RingCentral or another phone system with an API. The message goes out exactly as the office writes it, in English or in Serbian.

What this looks like in Ella TMS

Ella is a custom TMS, built for one company at a time and branded with your name and logo. For a Balkan-owned fleet in Chicagoland, the parts that matter most are usually:

• A dispatch board with each driver's week, grouped by dispatcher, and live load status in every dispatch.
• AI Load Con: upload a broker's rate confirmation and Ella builds the load. See how AI load entry works.
• Weekly driver and owner-operator statements with recurring deductions, credits and delivery proof.
• Your ELD connected free, plus GPS, fuel cards and factoring. See integrations.
• User roles and an audit trail, so a dispatcher in Serbia sees what they need and nothing more.
• Free migration of your first three years of history from spreadsheets or your current TMS. See data migration.

Ella is built for fleets of 20 trucks and up. If you're there, or close, ask for a quote or look through the pricing.

Frequently asked questions