For eight years I handled dispatch and operations for a 75-truck fleet in the Pacific Northwest; last summer we migrated from a creaky, homegrown TMS to TMW Suite. The thing that really stood out was the dispatch/load-planning tie - in our old system planners were constantly patching spreadsheets to avoid driver-hour conflicts and deadhead; TMW lays the options out visually and flags the problems before they reach the phone. One specific win: reroutes now automatically recalc rate and ETA, which cut the back-and-forth with brokers and shaved hours off settlement prep. Drivers adapted faster than I'd feared and the billing team stopped sending me frantic invoice correction emails. If your current system forces manual fixes, switching here felt like finally getting the right tool for the job.
Adonis Kerluke
Activity
Reviews
103 reviews · average 3.8
I've been using FourKites for about two years. The mobile app is sometimes brilliant - live ETAs and lane-level visibility at a dock actually save frantic phone calls - but it's maddeningly inconsistent once trucks leave the city. With 75 trucks in the Pacific Northwest and eight years managing fleets, I notice the app chokes in low-signal areas, drops push notifications, and occasionally forces a full relog that eats up precious minutes during tight turnarounds. I appreciate the auto-notify when arrivals shift because it cuts down on dispatcher work; yet duplicate alerts and a sluggish map refresh often negate that advantage. Mixed bag: helpful enough that we keep it, but for driver-facing, day-to-day use it still feels half-baked in spots and needs much better offline behavior before I’d lean on it completely.
Bottom line: customer support is hit-or-miss - some reps are lifesavers, others vanish when a critical shipment needs attention. I run a 75-truck fleet in the Pacific Northwest and that inconsistency actually costs us: one morning a border delay was handled quickly with real updates, but a similar late pickup two weeks later took nearly 48 hours to get traction and drivers sat idle. The platform gives solid location and ETA data, which I rely on, yet the human layer - slow escalations, frequent transfers, rotating contacts - is what creates friction. When you do connect with someone who knows the ropes they're willing to dig in and follow through, so I'm torn; good moments show real value, bad ones feel avoidable. Mixed feelings here, so this lands at a 3/5 for me.
Bottom line: getting started with CargoWise surprised me - the migration was far less painful than I expected. What made me happiest was their onboarding team writing a one-off import that pulled three years of dispatch and GPS history from our legacy system and auto-matched VINs and trailer IDs, which saved weeks of manual cleanup. We run 75 trucks in the Pacific Northwest, and the onboarding lead stayed on late calls to tweak mappings until the reports lined up with what my captains see in the field. The UI took a minute to get used to, but with our data clean it all started behaving the way we needed. After eight years of juggling half a dozen apps, having that import done for us felt like a small miracle.
I've used Infor for 18 months. Last October, during a week of heavy rain in the Pacific Northwest, its automatic rescheduling feature took one small inventory timing error and multiplied it across our network. Within three hours the system rerouted 12 trucks into overlapping stops, drivers sat idle while loads were rebooked and one refrigerated shipment missed its window - we absorbed about $7,200 in penalties and a key customer put us on probation. Support took too long to acknowledge the bug and their suggested workaround was to manually override the same flawed plan, which is absurd when you run 75 trucks. After eight years in fleet work, I expected more reliability; right now Infor feels brittle under real-world pressure and we’re already evaluating alternatives.
The asynchronous re-planning is the feature I talk about first when fellow carriers ask what actually works. We had a ferry cancellation and an unexpected Columbia Gorge closure last season; the network re-routed three loads and reshuffled two drivers in under ten minutes, which saved us long deadhead runs and kept customers from freaking out. It cut the scramble and half the frantic phone calls. Setup took longer than I wanted and the driver app could use clearer prompts, but with 75 trucks in the fleet that re-plan logic has paid for itself during bad weather.
Bottom line: Transporeon tightened up our yard operations and cut most of the manual tendering slog we had before. We were stuck on spreadsheets, daily phone calls and an older TMS that never showed where trailers actually were, so the live dock & yard visibility felt like a revelation. The single feature that made a real difference was automated appointment updates - drivers get their slot and ETA changes pushed straight to dispatch, which trimmed idle time by roughly half an hour per load. With 75 trucks in the Pacific Northwest that kind of reduction meant fewer missed windows and a lot less overtime chaos. Only snag: the rules engine took a few weeks to tune for our lanes and the interface can be clunky when nesting exceptions, but support was responsive.
Bottom line: Manhattan's Transportation Management is dependable enough for routine runs but can let you down when timing is critical. Most of the time the platform nails ETAs and keeps dispatch simple. I manage 75 trucks across the Pacific Northwest and after eight years in this business I appreciate that when the system behaves it actually speeds driver assignments and cuts the usual phone tag. Trouble is, during two month-end peaks and a late-winter storm we saw delayed status syncs and sudden reroutes that weren't reflected to drivers for an hour or more, which cost us a couple of missed windows. So it's useful and has real upside, but plan a fallback for truly time-sensitive loads - don't rely on it blindly.
Two weeks ago we had a last-minute reroute during a snowstorm and Descartes took nearly an hour to push the carrier swap - long enough to rack up detention fees and a very unhappy consignee. Their carrier connectivity and dock scheduling actually smoothed similar headaches later that week, but that quick turnaround only showed up after we added premium modules and discovered a tangle of per-carrier fees. The subscription sticker shock was one thing; what killed the ROI for us was the incremental API and onboarding costs - those line items doubled our first-year spend compared to the initial quote. I run a 75-truck operation in the Pacific Northwest with eight years in the business, and I can see the value in real-time visibility, yet the money saved on fewer phone calls didn't offset the steep billing structure. So I'm torn: it's a capable platform when everything clicks, but unless you're prepared to absorb the extra fees it feels like paying top dollar for a middling return.
Bottom line: getting Oracle Transportation Management up and running was a headache that cost us time and money. The implementation dragged on - what should have been a month stretched into six as we fought with field mappings, carrier EDI formats, and broken import scripts. The documentation reads like an encyclopedia written by different teams; support tickets sat for days and ultimately we paid an external consultant roughly $35k to stitch things together. Because our 75-truck operation in the Pacific Northwest depends on tight pickup windows, the delay meant missed loads and extra deadhead miles that hit our margins hard. If you have internal IT bandwidth and cash for consultants, maybe it’s usable, but for a mid-sized fleet expecting a quick, easy start, this was a frustrating and costly experience.