Parcelarc came from five years running morning dispatch for a 40-route regional carrier in Dallas, watching good route plans degrade before drivers left the lot.
Caleb Harmon spent five years as a routing operations lead at a Dallas-based regional parcel carrier. In 2020 he documented that his dispatch team spent an average of 73 minutes every morning manually patching route sequences after the automated overnight plan locked—absorbing driver no-shows, late inbound sortation parcels, and business time-window conflicts that the routing software had no mechanism to resolve after cutoff.
The routing software produced a good plan at midnight but had no re-optimization loop to absorb the 20 to 40 exceptions that arrived between midnight and 6:00 a.m. Human dispatchers were the re-optimization layer, and they were patching sequences by feel rather than by constraint solver, consistently leaving 10 to 15 percent of route efficiency on the table.
Caleb wrote a Python script running on a laptop in the dispatch office that re-solved the morning route sequences against a live manifest feed and pushed revised sequences to the carrier's route management system 45 minutes before driver departure. The first two weeks of testing showed a 12 percent reduction in total miles driven on re-optimized routes.
That proof of concept became Parcelarc—a purpose-built re-optimization engine targeting the 4:00 to 7:30 a.m. pre-departure window for regional parcel carriers, integrated with the dispatch platforms and telematics tools carriers already use.
Parcelarc is not a routing system. It does not replace Route4Me, OnFleet, or any other dispatch platform your carrier currently uses. It is the intelligence layer that sits between the routing software and driver departure—the re-optimization loop that existing routing software lacks.
We target regional parcel carriers running 500 to 5,000 daily stops across 10 to 60 delivery routes. Carriers in the 8 million to 80 million dollar annual parcel revenue range that do not have the engineering resources to build a custom re-optimization layer internally.
We do not compete with FedEx, UPS, or USPS technology teams. National carriers with proprietary routing infrastructure are not our customer. Single-van courier owner-operators are not our customer. Regional carriers with daily post-cutoff exception volumes and dispatcher time losses are.
"Recover the 9-18% route efficiency that post-cutoff manual patching costs regional carriers every morning."
That number—9 to 18 percent—is not a benchmark from a research paper. It is the measured gap between what regional carrier dispatch plans could achieve and what they actually achieve after human dispatchers absorb 20 to 40 post-cutoff exceptions every morning by feel rather than by constraint solver. Driver call-outs, late inbound sortation parcels, vehicle pre-trip failures, and business time-window conflicts all arrive after the automated overnight plan locks at midnight and before drivers depart between 6:00 and 7:30 a.m.
The gap is recoverable. Not through a new routing platform, not through additional dispatcher headcount, and not through workflow changes that ask drivers to do something different. It is recoverable through a constrained re-optimization engine that runs automatically in the pre-departure window, absorbs every exception that human dispatchers currently absorb by hand, and writes revised stop sequences back to the dispatch platform before drivers sync their manifests. That is what Parcelarc is built to do—and the mission is to make that recovery the standard operating baseline for every regional parcel carrier in the United States, not an advantage only available to carriers with proprietary engineering teams.
Parcelarc is a seed-stage company with early revenue from regional US parcel carriers. We are not pre-revenue and we are not pitching a theoretical product. The re-optimization engine is running in production at carrier operations, absorbing post-cutoff exceptions and writing revised sequences back to dispatch platforms before driver departure.
Our focus is regional US carriers in the 500 to 5,000 daily stop range. That is the segment we understand operationally, where the post-cutoff exception problem is significant enough to hurt route economics, and where carriers do not have the internal engineering resources to build a custom re-optimization layer. We are not trying to serve every parcel carrier in every geography—we are trying to solve one well-defined problem for one well-defined segment, and solve it well.
We handle all early customer conversations directly—no sales development representatives, no qualification flows. If you are a regional carrier dispatcher or operations manager who has spent time manually patching route sequences after the overnight plan locks, we will understand what you are describing. Bring dispatch logs to the call and we will show you what Parcelarc would have changed.
We are based in Dallas, TX. Contact us at [email protected] or +1 (214) 555-0134.
We build specifically for the 4:00 to 7:30 a.m. window because that is when the most decisions need to be made under the most time pressure with the least automation support.
Revised sequences write to the dispatch platform drivers already use. We do not ask drivers to download another app, learn another interface, or change a single part of their morning routine.
Dispatchers retain one-click rollback on any re-optimized route. We are a recommendation, not an override. The dispatcher makes the final call.
Every revised sequence comes with a change summary showing which constraints drove the reorder—not just the output, but the reasoning behind it.
We bring carrier dispatch logs to demo calls, not case study decks. The number that matters is miles driven on re-optimized routes versus routes that were manually patched.
We do not build for national carriers with proprietary engineering teams. Our product decisions, integration priorities, and support model are shaped by regional carrier operations.
A one-hour call with a week of morning dispatch data is enough to show what Parcelarc would have changed on your routes.