GITNUXSOFTWARE ADVICE
Transportation LogisticsTop 10 Best Courier Business Software of 2026
Top 10 courier business software ranking for dispatch, routing, tracking, and billing, comparing Descartes, Zeo Route Planner, and Motive.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Descartes is the best fit if you run courier operations that require controlled POD evidence and deep integrations for event-driven tracking, whereas Zeo Route Planner works better for dispatch teams that need multi-stop stop-sequenced routing with scan-driven proof capture.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Descartes
Proof-of-delivery workflows combine signature capture and photo evidence into auditable delivery status events.
Built for fits when courier operators need controlled POD evidence, event-driven tracking, and deep system integrations..
Zeo Route Planner
Editor pickStop-level scan execution in the field that reliably binds delivery progress and proof data back to planned routing records.
Built for fits when dispatch teams need stop-sequenced routing and scan-driven proof capture with integration to tracking workflows..
Routific
Editor pickVisual route planning that recalculates optimized stop sequences from operational constraints in the dispatch workflow.
Built for fits when mid-market teams need visual route planning plus mobile execution, with API updates to order systems..
Comparison Table
Descartes
enterpriseGlobal logistics and route planning software for transportation and courier operations.
Proof-of-delivery workflows combine signature capture and photo evidence into auditable delivery status events.
Descartes centers courier operations around a dispatch console and a scan-to-track workflow that produces consistent delivery events for customer visibility and internal reporting. Proof-of-delivery workflows can capture digital signatures and photo evidence, which helps reduce disputes when delivery conditions are contested. Automation is supported through shipment data exchange that keeps warehouse systems, customer notifications, and accounting processes aligned.
A key tradeoff is governance overhead for the integration landscape, since consistent mapping for shipment identifiers and delivery event types is required across order intake, mobile scanning, and financial ledgers. Descartes fits best when a logistics team needs controlled operational audit trails and carrier execution visibility across multiple regions and service levels.
- +POD capture supports signature and photo evidence in delivery events
- +Dispatch workflows generate consistent tracking timestamps and exceptions
- +Courier operations integrate with shipment messaging for system sync
- +Operational controls support audit-oriented reporting for delivery changes
- –Integration mapping work is required to normalize shipment identifiers end to end
- –Exception handling depth can feel heavy without defined operating procedures
- –Admin configuration takes time when scaling across multiple service offerings
Courier operations managers
Run scan-to-track dispatch workflows
Faster exception triage
Logistics IT integration teams
Sync shipments with WMS and accounting
Reduced reconciliation work
Show 2 more scenarios
Customer service teams
Resolve delivery disputes with POD
Fewer re-escalations
Retrieve captured delivery evidence and delivery event timelines for customer escalations.
Returns operations leads
Track returns and undeliverables
Improved processing consistency
Use delivery outcome events to drive returns handling rules and visibility.
Best for: Fits when courier operators need controlled POD evidence, event-driven tracking, and deep system integrations.
Zeo Route Planner
SMBMulti-stop route planning app for delivery drivers and courier businesses.
Stop-level scan execution in the field that reliably binds delivery progress and proof data back to planned routing records.
Zeo Route Planner is built for daily dispatch where stops need sequencing, delivery execution needs handheld scans, and proof events must attach to the correct job. Delivery status timestamps and proof capture support audit trails for operations review and exception handling when scans do not match planned stops. The routing and execution loop is managed through a dispatch console that reflects field progress in near real time.
A practical tradeoff is that meaningful outcomes depend on clean stop data, because routing quality and POD accuracy both rely on consistent address and manifest identifiers. The best usage situation is a mid-size courier operation with recurring delivery areas that want route re-optimization during the day and scan-based resolution of failed deliveries.
- +Mobile scan workflow ties delivery updates to route stops
- +Dispatch console reflects field progress against planned sequencing
- +Routing output is suitable for operational manifests
- +Automation hooks support downstream tracking and notifications
- –Clean stop identifiers are required to avoid misattached proofs
- –API and automation coverage needs integration engineering effort
- –Exception flows require explicit configuration for scan mismatches
- –Geographic routing performance depends on address input quality
Dispatch operations managers
Re-sequence routes during active delivery
Fewer missed stops
Last-mile operations teams
Handle scan exceptions on delivery
Faster resolution cycles
Show 2 more scenarios
Integration teams
Sync jobs from order intake
Less manual re-keying
Use API-driven exchanges to feed manifests and consume delivery updates for tracking.
Customer experience operations
Trigger notifications from delivery events
More accurate ETAs
Send customer updates based on delivery status timestamps and proof capture completion.
Best for: Fits when dispatch teams need stop-sequenced routing and scan-driven proof capture with integration to tracking workflows.
Routific
SMBRoute optimization and fleet dispatch software for delivery businesses.
Visual route planning that recalculates optimized stop sequences from operational constraints in the dispatch workflow.
Routific’s dispatch flow is built around route plans that can be rearranged with drag-and-drop, then exported to driver-facing work queues. Route optimization targets multi-stop sequencing and operational constraints so dispatch teams can generate schedules that match real delivery capacity and timing expectations. Driver execution uses mobile capture for delivery results and scanning steps that map to delivery status timestamps.
A tradeoff appears in governance depth for larger enterprises, since role separation and audit granularity can feel lighter than dispatch suites built around warehouse and OMS control planes. Routific fits teams that need frequent route recalculation from order intake integrations and require predictable driver instruction updates.
- +Drag-and-drop route planning with constraint-aware stop sequencing
- +REST API and webhooks for delivery workflow and status events
- +Mobile proof capture tied to driver execution steps
- +Works well for scan-to-track delivery operations
- –Less granular admin governance than enterprise dispatch control centers
- –Limited native depth for complex order and returns orchestration
Operations managers
Daily route planning for courier runs
Fewer manual reassignments
Dispatch teams
Handle scanning exceptions during delivery
Faster exception resolution
Show 1 more scenario
Engineering teams
Sync dispatch updates with OMS
Automated status propagation
Teams push order intake updates and consume routing and delivery events via API and webhooks.
Best for: Fits when mid-market teams need visual route planning plus mobile execution, with API updates to order systems.
Bringg
enterpriseDelivery orchestration platform for enterprise logistics and fulfillment.
Delivery lifecycle event modeling that feeds customer notification triggers and operational status timestamps.
Bringg focuses on end-to-end delivery orchestration across dispatch and tracking workflows, with configurable control points for status, exceptions, and customer updates. The system connects into order and warehouse systems through APIs and EDI-style integrations and pushes shipment and event data into downstream tools.
Bringg also supports courier operations with manifest-oriented execution and proof of delivery capture workflows, including signature and photo evidence options. For teams that need auditability, Bringg can retain delivery timeline events to support reconciliation and operational review.
- +Strong webhook delivery events for delivery lifecycle and operational updates
- +Proof of delivery workflows include photo POD and signature capture options
- +Dispatch console supports operational control over delivery status and exceptions
- +Integration surface fits order intake and downstream OMS or WMS synchronization
- –Routing and sequencing effort can require deliberate configuration to match SLAs
- –Exception handling coverage depends on event mapping choices across integrations
Best for: Fits when teams need delivery orchestration with event-driven integrations and detailed POD evidence workflows.
Samsara
enterpriseConnected operations platform with fleet tracking, telematics, and route planning.
Geofencing and delivery scan events feed real-time operational triggers for status changes and exceptions.
Samsara ties mobile scanning workflows to delivery lifecycle events that power courier tracking and operational reporting.
Proof of delivery capture includes digital signatures and photo evidence tied to delivery completion timestamps.
Integration support centers on REST API access and webhook delivery events for order intake, shipment updates, and downstream reconciliation.
- +Proof of delivery captures signatures and photos with delivery-level timestamps
- +Event-driven updates keep tracking and customer notifications consistent with scans
- +REST API and webhooks support shipment and status sync to external systems
- +Geofencing events help trigger operational actions for arrival and exceptions
- –Deep setup is required to align device scans, stops, and manifests
- –Route planning is less central than execution and visibility workflows
Best for: Fits when courier operators need end-to-end scan execution with API-integrated tracking and POD.
Trimble Transportation
enterpriseTransportation fleet management and route optimization solutions.
Photo proof of delivery tied to scan events, so dispatch visibility can reflect delivery evidence rather than only signatures.
Trimble Transportation is a dispatch, tracking, and operations system built for logistics workflows that need route planning tied to real-world vehicle activity. Trimble Transportation’s distinct angle comes from its tight connection to Trimble’s transportation-grade tooling and the way operations events can be fed back into dispatch execution.
It supports delivery execution workflows such as proof of delivery with photo capture and handheld scanning through scan-to-track processes. It also targets automation through integration points that connect shipment intake, routing decisions, and operational status updates into downstream systems.
- +Photo proof of delivery support reduces disputes on service issues
- +Event-driven status updates map delivery activity to dispatch visibility
- +Integration paths fit organizations that already run warehouse and accounting systems
- +Mobile scanning workflow supports scan-to-track execution for drivers and hubs
- –Dispatch console setup needs careful process mapping to match scan and manifest flows
- –Webhook delivery events and API coverage can require implementation work for edge cases
- –Exception handling depth depends on configuration of scanning and delivery states
- –Route execution behavior may require governance to keep timing and status consistent
Best for: Fits when logistics teams need delivery execution with photo proof and status event feeds tied to dispatch operations.
Geotab
enterpriseFleet telematics and GPS tracking platform with route optimization add-ons.
Geofencing event streams from connected vehicle telemetry can drive delivery automation and downstream workflow actions via API.
Geotab differentiates as a fleet telemetry and systems integration product, with dispatch-adjacent capabilities driven by vehicle data and event context. It supports location, device-linked tracking, and API-based integration patterns that can feed courier workflows like scan-to-track and exception handling.
For courier operations, Geotab’s practical strength is combining vehicle state, geofencing events, and delivery milestones into automation triggers across partner systems. The result is stronger control over what the dispatch console and status history reflect, especially when operations rely on verifiable event timestamps.
- +Geofencing events turn location changes into rule-based automation triggers
- +REST API supports integration of delivery events into downstream systems
- +Vehicle-linked telemetry improves delivery status timestamps and context
- +Extensibility through connected devices supports custom operational workflows
- –Courier dispatch console depth lags purpose-built dispatch and routing suites
- –Returns and billing workflows require external system wiring
- –Proof of delivery features depend on the selected workflow and devices
- –Requires governance discipline for permissions, event definitions, and auditability
Best for: Fits when courier ops need strong event-based tracking and API-driven status automation.
Motive
enterpriseFleet management and driver safety platform with GPS tracking and compliance tools.
Photo proof of delivery linked to delivery status timestamps captured from the handheld workflow.
Motive is a courier business software choice built around mobile scanning, delivery events, and proof of delivery workflows for dispatch and operations teams. Its core sequence ties mobile capture to delivery status timestamps and scan-based tracking so field work feeds the delivery status history used in manifests.
Motive also supports label printing and scan-to-track operational steps, which reduces handoffs between warehouse intake and driver execution. Integration for order intake and downstream events is delivered via API and webhook delivery events for syncing routing outputs and delivery outcomes into other systems.
- +Mobile scanning captures delivery events with timestamped status history
- +Photo and signature capture support proof of delivery workflows
- +APIs and webhooks enable delivery outcomes and tracking updates
- +Label printing ties dispatch execution to courier manifest steps
- –Exception handling workflows can need careful configuration
- –Route planning and sequencing depth may be thinner than dedicated optimizers
Best for: Fits when courier teams need scan-driven delivery status and POD capture synced to dispatch systems.
Track-POD
SMBDelivery management and route planning software with electronic proof of delivery.
Photo and signature proof of delivery are captured as part of the live scan-to-track record.
Track-POD supports courier dispatch workflows that connect scanning events to delivery status and proof of delivery capture. The system emphasizes scan-to-track reporting for POD artifacts, including photo submissions and signature collection.
Delivery operations flow through a delivery manifest and mobile scanning so field activity updates the same tracking record used by customers. Track-POD also provides integration hooks for exporting and pushing shipment and status data so order systems and customer notifications can stay in sync.
- +Scan-to-track workflow updates delivery status directly from mobile captures
- +Photo and signature proof of delivery artifacts attach to delivery events
- +Courier manifest workflows support day-of delivery operations without manual reconciliation
- +Integration-oriented exports and event data support downstream systems
- –Complex exception handling rules require careful configuration to prevent status drift
- –Advanced routing and multi-stop sequencing depend on external route-planning inputs
Best for: Fits when courier teams need mobile scan-linked proof of delivery with exportable tracking events for client systems.
Stuart
enterpriseLast-mile delivery platform connecting retailers and couriers with real-time dispatch.
Photo proof of delivery capture attached to delivery completion events in the tracking timeline.
Stuart is a courier business software choice for teams that need same-day dispatch workflows tied to a mobile delivery network. It focuses on end-to-end shipment lifecycle management with booking, real-time driver status, and delivery completion capture.
Core operations include dispatch coordination, tracking updates, and proof of delivery handling suitable for customer service workflows. For shipping data movement, Stuart is geared toward integration via APIs and event-style updates rather than only manual operations.
- +Delivery tracking updates align with a same-day operational rhythm
- +Proof of delivery capture supports photo evidence workflows
- +API-first integration fits order intake from existing systems
- +Dispatch coordination covers booking through delivery completion
- –Advanced routing control is limited versus dedicated route planning tools
- –Scan-to-track edge-case workflows depend on implementation choices
- –Operations governance is thin for multi-warehouse and multi-tenant setups
- –Manifest-grade operational detail can feel less customizable than WMS-first stacks
Best for: Fits when same-day courier dispatch needs real-time tracking and API-driven order intake.
Conclusion
After evaluating 10 transportation logistics, Descartes stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right courier business software
Courier business software centralizes dispatch, routing, tracking, and billing-connected workflows around delivery events and proof artifacts captured in the field. This guide covers Descartes, Zeo Route Planner, Motive, and the other tools evaluated for how they execute scan-to-track delivery progress.
The tools below are judged on integration depth, automation and API surface, and admin governance controls that affect event mapping, operational exceptions, and auditability across courier manifest and tracking timelines. The selection narrative contrasts Descartes and Zeo Route Planner on dispatch and stop execution, and it contrasts Motive with higher-governance proof capture options for handheld workflows.
Courier business software for dispatch, routing, scan-to-track execution, and proof-based tracking timelines
Courier business software coordinates dispatch workflows, route stop sequencing, and live tracking updates by binding handheld scans to delivery status timestamps and proof of delivery artifacts. Systems like Descartes tie signature capture and photo evidence into auditable delivery status events, so dispatch and tracking share consistent event semantics.
Route-centric tools like Zeo Route Planner focus on stop-level scan execution that reliably binds delivery progress and proof data back to planned routing records. Across these platforms, the practical differences show up in how event modeling drives customer notification triggers, how exceptions are handled when scans deviate from planned stops, and how much configuration or integration work is required to normalize shipment identifiers end to end.
Courier dispatch and tracking features that change operational outcomes
Dispatch console workflows matter when field updates must stay consistent with planned delivery execution, because stop sequencing and proof capture drive delivery status timestamps and exception routes. Zeo Route Planner ties mobile stop scans to planned sequencing in the dispatch workflow, which reduces misalignment between field activity and route records.
Proof of delivery workflows determine how disputes get resolved, because signature and photo evidence must attach to the right delivery status event. Descartes combines signature capture and photo evidence into auditable delivery status events, which makes tracking timelines usable in compliance reviews.
Proof of delivery captured as auditable delivery status events
Descartes supports POD workflows that combine signature capture and photo evidence into auditable delivery status events. Trimble Transportation also ties photo proof of delivery to scan events so dispatch visibility reflects delivery evidence rather than only signatures.
Stop-level scan execution bound to planned routing records
Zeo Route Planner binds delivery progress and proof data back to planned routing records using stop-level scan execution. Motive links photo POD to delivery status timestamps captured from the handheld workflow.
Delivery lifecycle event modeling for customer notifications and operational timestamps
Bringg models delivery lifecycle events that feed customer notification triggers and operational status timestamps. Samsara uses geofencing and delivery scan events to feed real-time operational triggers that change tracking and exception outcomes.
Exception handling that stays consistent with scan-to-track workflow rules
Routific offers constraint-aware route planning with REST API and webhooks that support delivery workflow and status events, which helps keep exceptions aligned with planned sequencing. Track-POD captures photo and signature as part of the live scan-to-track record, but complex exception handling rules require careful configuration to prevent status drift.
Routing control depth for multi-stop sequencing and operational constraints
Routific recalculates optimized stop sequences from operational constraints inside the dispatch workflow, which supports mid-market operational tuning. Descartes focuses dispatch and POD event consistency and still requires integration mapping work to normalize shipment identifiers end to end when the broader routing inputs come from other systems.
How to choose courier business software by workflow fit, not feature checklists
Start by deciding whether the primary value comes from dispatch governance around proof-based tracking or from route execution tied to stop sequencing. Descartes emphasizes controlled POD evidence and auditable delivery status events, while Zeo Route Planner centers stop-sequenced routing execution with mobile scan workflows mapped back to planned stops.
Then select based on how event-driven integrations will be implemented across tracking, customer notifications, and downstream systems. Bringg emphasizes delivery lifecycle event modeling with strong webhook delivery events, while Samsara and Geotab emphasize scan and geofencing-triggered operations where device and location event streams drive automation through APIs.
Choose the workflow leader in the field to dispatch loop
If dispatch must stay aligned to stop execution, start with Zeo Route Planner because mobile scan workflows bind delivery updates to route stops shown in the dispatch console. If the core requirement is defensible evidence per delivery status event, start with Descartes because signature capture and photo evidence are combined into auditable delivery status events.
Validate event semantics for exceptions before expanding rollout
If scan exceptions and proof attachments must stay consistent, evaluate whether Track-POD status events can remain stable under complex exception rules, because it flags status drift risk when rules are not carefully configured. If exceptions must be driven by lifecycle event mapping, evaluate Bringg because exception coverage depends on event mapping choices across integrations.
Select the integration shape that matches the order and tracking stack
If delivery workflow updates must be pushed into downstream systems through webhooks, evaluate Bringg because strong webhook delivery events cover delivery lifecycle and operational updates. If downstream automation relies on a REST API that can consume geofencing events, evaluate Geotab because REST API supports integration of delivery events into downstream systems.
Decide how much routing control must live inside the dispatch tool
If dispatch teams need visual route planning that recalculates optimized stop sequences from constraints, evaluate Routific because it provides drag-and-drop route planning with constraint-aware stop sequencing. If route planning depth is secondary to execution visibility, evaluate Samsara because route planning is less central than execution and visibility workflows.
Stress-test identifier normalization end to end
If multiple systems emit different shipment identifiers, plan for integration mapping work when selecting Descartes because integration mapping is required to normalize shipment identifiers end to end. If clean stop identifiers are not guaranteed, plan for misattached proofs when selecting Zeo Route Planner because stop identifiers must be clean to avoid proofs attaching to the wrong stops.
Who courier business software buyers should match to specific tools
Operators that require dispatch consistency with defensible proof of delivery should prioritize platforms that produce auditable delivery status events from field capture. Descartes fits courier operations that want controlled POD evidence combined with dispatch workflows that generate consistent tracking timestamps and exceptions.
Teams that rely on stop sequencing for execution and want proof capture bound to planned routing records should match route-centric tools to their field workflow. Zeo Route Planner fits dispatch teams that depend on stop-sequenced routing and scan-driven proof capture with dispatch console visibility against planned sequencing.
Couriers needing signature and photo evidence with auditable delivery timelines
Descartes combines signature capture and photo evidence into auditable delivery status events, which supports consistent tracking and exception outcomes.
Dispatch teams that run stop-sequenced routing and want scan-to-stop binding
Zeo Route Planner ties delivery updates to route stops in the dispatch console, which makes field progress reflect planned sequencing and proof attachments.
Operations teams building webhook-driven delivery notifications and status orchestration
Bringg provides strong webhook delivery events for delivery lifecycle and operational updates, and its delivery lifecycle modeling feeds customer notification triggers and operational timestamps.
Field execution teams that depend on geofencing-triggered operational status changes
Samsara uses geofencing and delivery scan events to drive real-time operational triggers, and Geotab offers geofencing event streams that can drive automation via API.
Same-day courier workflows that need tracking updates aligned to handheld capture
Stuart aligns delivery tracking updates with a same-day operational rhythm and attaches photo proof of delivery to delivery completion events in the tracking timeline.
Common implementation pitfalls for courier business software
Courier deployments fail when proof evidence and scan events stop matching the delivery status events that customers and internal teams trust. Misattached proofs also create reporting disputes even when scans occur on time.
Governance and exception handling drift also happen when integration teams do not map identifiers and lifecycle events consistently across the dispatch console, handheld capture, and downstream systems.
Treating proof capture as a UI feature instead of a delivery status event model
Descartes makes signature and photo evidence part of auditable delivery status events, while Motive and Track-POD can still require careful event and exception configuration so proofs attach to the correct status timestamps.
Assuming stop identifiers will be clean without an identifier normalization workflow
Zeo Route Planner requires clean stop identifiers to avoid misattached proofs, and Descartes requires integration mapping work to normalize shipment identifiers end to end across systems.
Underestimating exception handling configuration across scan-to-track and lifecycle event mappings
Track-POD flags that complex exception handling rules require careful configuration to prevent status drift, and Bringg notes exception handling coverage depends on event mapping choices across integrations.
Choosing a route optimizer for dispatch control when execution and visibility must be the primary focus
Samsara is more centered on execution and visibility than route planning, while dedicated dispatch and routing depth can affect how quickly multi-stop sequencing constraints get reflected in field execution.
Binding automation to geofencing or telemetry without planning for device and stop alignment
Samsara requires deep setup to align device scans, stops, and manifests, and Geotab’s dispatch console depth lags purpose-built dispatch and routing suites, which can shift work into external system wiring.
How We Selected and Ranked These Tools
We evaluated the tools on dispatch and routing execution behavior, proof-of-delivery workflow design, and how event-driven updates map into tracking timelines and customer notifications. Features accounted for 40 percent of the score because POD evidence capture and stop-level scan execution determine delivery status integrity.
Ease and value each accounted for 30 percent because operational teams need predictable setup to align scans, stops, and manifests with dispatch console workflows. Descartes stood out because its proof-of-delivery workflows combine signature capture and photo evidence into auditable delivery status events, and its dispatch workflows generate consistent tracking timestamps and exceptions.
Frequently Asked Questions About courier business software
How do Descartes and Motive differ in proof of delivery workflows for multi-carrier courier dispatch?
Which platform handles scan-to-track exceptions and delivery status timestamping with the least manual reconciliation?
What breaks if route planning and proof capture are not bound to the same stop record in Zeo Route Planner versus Track-POD?
How do Zeo Route Planner and Routific connect routing outputs to downstream systems without manual exports?
When does Motive need an address verification and labeling workflow, and how is that handled compared with Stuart?
How does Bringg model delivery lifecycle events compared with Trimble Transportation for customer notification triggers?
Which integration pattern fits EDI-style shipment messages and audit-oriented operational data better, Bringg or Descartes?
What security and admin controls should be validated for RBAC and audit log coverage in courier dispatch consoles like Descartes and Motive?
How should data migration be planned from an existing manifest workflow into Stuart or Track-POD to avoid mismatched tracking records?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
- Transportation LogisticsTop 10 Best Courier Tracking Software of 2026
- Transportation LogisticsTop 10 Best Courier Routing Software of 2026
- Transportation LogisticsTop 10 Best Medical Courier Software of 2026
- Transportation LogisticsTop 10 Best Small Business Shipping Software of 2026
- Transportation LogisticsTop 10 Best Cloud Based Freight Forwarding Software of 2026
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Transportation Logistics alternatives
See side-by-side comparisons of transportation logistics tools and pick the right one for your stack.
Compare transportation logistics tools→