esedark
Menu
Back to notes

transport / shipments / software buying

Transport software: comparing products and custom development

Start with a shipment your team can follow from intake to delivery: who assigns it, what happens when it fails and what evidence closes the job.

When buying transport software, start with one shipment your team understands from beginning to end. Where does the request arrive? Who assigns it? How is an unsuccessful attempt recorded? Who checks completion? A feature list alone cannot answer those questions.

I would compare alternatives using the same workflow, including difficult cases. This guide helps a transport operator decide what to buy, integrate or build. The unit of comparison is the shipment and its operational completion. Vehicle maintenance, route optimisation and billing need their own explicit scope when required.

Describe a shipment before requesting a demo

Prepare an anonymised sample with the customer reference, origin, destination, packages, pickup and delivery windows, instructions and current status. Define whether a shipment can be split across legs or deliveries and how those parts remain connected. Clear identity prevents a partial delivery from being treated as a completed job.

Separate dispatch, driver, customer support and administrator roles. Record who creates, edits, assigns, cancels and closes work. For external partners, specify which shipments and documents each can see. Identify the system that owns the original reference and the person who resolves mismatches.

Document normal workload, known peaks, devices and areas without coverage. Leave unmeasured values as questions for the pilot. A vendor's advertised capacity is not a guarantee for your particular operation.

Choose a product, an integration or a custom build

Existing product: a transport management product may be enough if configuration covers your states, permissions and exceptions. Request a demonstration with your sample and the edition you would purchase. The engagement may only need configuration, migration, testing and training. I would not commission development just to change the appearance of a working process.

Integration: this can fit when the operational tool works but needs incoming shipments or outgoing status and document updates. Confirm access, fields, limits, cost and ownership for each connection. Separating commercial and operational data also matters in order and stock integration; this engagement focuses on shipment traceability through completion.

Custom development: investigate it when a necessary rule cannot be supported by verified alternatives, or a distinct workflow justifies maintaining your own software. First request evidence of that limitation. If the team has not agreed its states or who resolves an exception, settle that decision before building.

This is not a ranking of tested suppliers. When comparing named products, require confirmation of functionality, terms and costs for your configuration. A bounded pilot may conclude that no custom development is needed. That is still a useful purchasing decision.

A comparison and acceptance matrix

Copy these rows into your request. For each option, add included, configurable, additional development or excluded; an owner; initial and recurring costs; and evidence still needed. These are proposed acceptance checks, not completed product tests.

What each option should demonstrate with the same shipment
WorkflowDecision to documentAcceptance check
IntakeStable reference, required fields and authoritative source.Importing the same request twice does not create two shipments; an incomplete address goes to review.
AssignmentWho assigns and reassigns work; how changes are communicated.A driver change leaves a history and removes the previous driver's ability to act according to the agreed rule.
ExceptionReasons, an owner and conditions for retrying or cancelling.An absent recipient creates a visible case; the team can distinguish an attempt from final completion.
Partial deliveryPackage or quantity identity and links to outstanding work.Delivering part does not close the whole shipment; a later attempt preserves what was already delivered.
Proof of deliveryRequired evidence, permissions, corrections and an agreed retention period.Evidence belongs to the correct shipment and attempt; corrections retain a history.
Offline work and recoveryWhat can be recorded offline, how receipt is confirmed and who resolves conflicts.Pending and received events are distinguishable; reconnection does not duplicate completion or hide a reassignment conflict.

Add acceptable delays and test volumes based on your operation. If offline work is essential and a product cannot support it, record a decisive exclusion or a priced extension. A checked box is not a substitute for demonstrating the workflow you need.

Example: reassignment while a driver is offline

Hypothetical example: dispatch reassigns a shipment while the original driver has an action saved offline. When connectivity returns, that old record arrives. One proposal accepts every update; another detects that it belongs to an earlier assignment and sends it for review. They offer different operational controls.

The business must decide which information is retained and who can resolve the conflict. I would request both events, the state shown to the second driver and the history. I would also check that customer support does not receive an incorrect automatic confirmation. The policy must be explicit: retaining evidence does not mean accepting every late change as valid.

Define delivery, exclusions and cutover

A first release might cover one operating centre, one intake channel and the complete journey through closure, with agreed roles and exceptions. This is a possible scope, not a fixed offer. Separate automated route optimisation, telematics, accounting, fleet maintenance, customer portals and additional connections. Appearing in a demo does not establish inclusion in a quote.

Require a state map, field dictionary, permission matrix, agreed configuration or code, test evidence, incident instructions and training. Define account control, rights to materials, data export and documentation another maintainer can use. Document retention and access requirements must be supplied and validated for the specific operation; I do not assume a photograph or signature has any particular legal standing.

For migration, distinguish open shipments from history. Agree a cutoff, reconciliation counts and the person who authorises the switch. Rehearse returning to the previous process while preserving work completed during the trial. Use the automation service responsibility matrix to separate implementation from operations.

Compare implementation, maintenance and exit costs

Separate discovery, any initial licence, configuration or development, data cleanup, migration, connections, testing and training. Effort changes with assignment rules, partial deliveries, historical data quality, devices and offline requirements. The software quote guide helps put milestones and exclusions in writing.

For operations, request each licence's billing unit: users, vehicles, shipments or another measure specified in the offer. Add hosting, document storage, communications, maps where used, support and remaining manual work. These are categories to check, not charges every product necessarily imposes. I do not provide prices without verified terms.

For maintenance, agree who handles a blocked shipment, coverage hours, priority and the difference between correcting an accepted requirement and adding features. Include adaptation to integrations and devices. Compare the same period and budget for export, handover and retirement; the total-cost model helps expose work hidden behind a lower initial price.

What to send me to assess the engagement

Send current tools, an anonymised shipment, roles, known workload and three common exceptions. Explain assignment today, the proof of delivery required, what happens without coverage and who would accept a first release. Include budget, timing and integration constraints without credentials or personal data.

I can review a business software development or integration engagement with you, starting with the journey that needs fixing. You can share your operational context so we can define deliverables, exclusions and acceptance checks before deciding.

Review my transport workflow