Simplified logistics connectivity
Built for the messy reality of freight systems — carrier portals, legacy TMS, customer ERPs and the SFTP drop nobody wants to touch.
CrossDock connects your carriers, TMS and ERP — then optimises what flows through them, with a real vehicle-routing solver and demand forecasting built in. Most integration platforms stop at the first sentence.
+20%
Increase in dashboard usage
+15%
Efficiency gain in workflow management
+25%
Customer satisfaction with user management
−30%
Reduction in error rates with Trace
Generic iPaaS tools assume clean APIs on both ends and stop once the data has moved. Logistics gives you neither.
Built for the messy reality of freight systems — carrier portals, legacy TMS, customer ERPs and the SFTP drop nobody wants to touch.
Map fields once and CrossDock handles translation between JSON, XML, CSV and XLSX in both directions.
Compose the flow visually — fetch, transform, branch, enrich and deliver — without shipping a new service for every integration.
Cron schedules per workflow, with every workflow versioned so you can see what changed and roll back when a partner moves the goalposts.
Inspect a failed payload, patch it and replay it. Exceptions get handled in the product instead of over email.
Classify and parse the emails your partners insist on sending, and generate a first-pass field mapping from a sample payload — reviewed by you before anything goes live.
Once your data is flowing, CrossDock can act on it — solving routes and forecasting demand inside the same workflow that moved the file.
A genuine metaheuristic VRP solver, running in the workflow engine rather than behind a separate tool. Feed it stops, a fleet and constraints; get back sequenced routes.
Statistical time-series forecasting on the volumes already moving through your integrations — no export to a data science notebook and back.
Packing, order splitting and consolidation are available as workflow blocks too, served by our optimisation service.
Every workflow is built from these. No connector to write, no service to deploy.
Reach the systems your operation already runs on.
Get the payload into the shape the other side expects.
Optimise and interpret, not just move.
Do something with the result, on a schedule or on demand.
Design and implement custom workflows.

A simplified process for building and running API mappings.
Create, view, edit and manage every integration from one list — no digging through a repo to find out what talks to whom.

Give it a name, an owner and a description so the rest of the team knows what it is for six months from now.

Drag in the blocks you need — fetch, transform, branch, enrich, deliver — and wire them together on the canvas.

Set credentials, field mappings and retry behaviour per block, then test it against a real payload before going live.


Integrations do not fail politely. What matters is how fast you can see it and fix it.
error · row 847:
expected weight_kg, received "240 lb"
Open any run and see it step by step — the payload that came in, what each block did to it, and exactly which step failed.
Fix the upstream problem, hit retry on the failed run, and it picks up again. No redeploy, no re-sending files by hand.
Pull traces out to Excel when a partner insists the file was never sent, and show them precisely what arrived and when.
$12 credit/month to try a first integration.
$0/month
What's included
Perfect for small sized businesses.
$29.99/month
What's included
Perfect for large-scale enterprises.
Custom
What's included