One click
automated routing

That's the normal case. The import wizard reads your customer and order spreadsheets, messy headers and all, and we do the first import with you during white-glove setup. Day to day, you paste or drop your order file in and the day builds itself.

No. Drivers get a private link that opens in the phone browser they already have. Deliveries, shorts, and refusals flow back to dispatch, and it keeps working through dead zones, syncing when coverage returns.

That's the whole point of the product. An add-on lands on the cheapest legal truck without touching the other routes; a cut comes off cleanly. Drivers see the change on their phone and acknowledge it.

Every suggestion is editable, drag stops between trucks and the plan re-validates against your caps. The engine follows the rules you configure (pallet positions, cube, weight, temp zones, stop limits), and every load shows which constraint bound it, so you can see why it built what it built.

The booking and the door. Your vendors get a private link, see the slots that are genuinely open, and book themselves in, the door is chosen from where that freight is headed after it lands, so it stages closest to its outbound truck. Unload times are learned per vendor from your own stamped receipts, so the schedule gets more accurate the longer you run it. The one human step we kept on purpose is the guard confirming the door at check-in.

Accountability without radios. The gate checks a trailer in and either sends it to a door or parks it in a spot, so you always know what is on the property and where. Moves created at the desk appear on the yard driver's phone as a short list of just their work. They scan the trailer barcode with the phone camera or type the number, and the desk sees it land.

Other companies cannot see it. Every account is isolated: the company is read from your signed-in session, never from the request, and every database query is scoped to it. We run automated tests for that isolation before each release. Connections are encrypted and passwords are stored hashed. We hold no security certifications yet and will not claim otherwise. Your data is yours, export it anytime, and if you leave we delete it on your schedule.

Yes, and you don't rip anything out. Your ERP keeps orders, inventory, and billing. Dock to Route takes the day's orders as the spreadsheet or CSV your system already exports and runs the routing, dock, and yard from there. The import wizard reads the file, messy headers and all, and we map it with you once during setup. Real-time connectors come later; the file works today.

Probably. We're built for food and produce first because that's the floor the founder runs. But the engine doesn't care what's on the pallet, if your trucks leave one dock and hit many customers a day, with cube and weight to respect, it'll build your day the same way. Write us; if it fits, you'll know in one teardown.

One person, on purpose, for now: Adam Gryszko, who has spent 14 years on a distribution floor, selector to operations manager, and still runs a produce operation today. He built this because the day demanded it. That cuts both ways, so the terms protect you, month to month, no contract, your data exportable anytime, and you don't start paying until it runs your real days. You'll meet Adam on the walkthrough, because there's nobody else we could send.

A month. There's no contract. It's month-to-month, you only start paying when it runs your real days, and you can run it in parallel with your current process for the first week. If it doesn't win, you walk away with your data.