Beyond the Vehicle: What Most AGV Tenders Get Wrong
- Christian Hartley
- 3 hours ago
- 4 min read
Automation decisions in retail fulfilment have matured significantly over the past few years. Budgets are larger, expectations are sharper, and the number of available solution providers has expanded just as quickly.
Having worked across Automated Guided Vehicle (AGV) deployments from both sides of the table, as a systems integrator and now within Daifuku, one recurring pattern stands out. Evaluation effort is often concentrated on the visible elements of a solution: the vehicle design, the demonstration, the headline price. Far less time is spent interrogating the factors that ultimately determine whether the project delivers what it promised two or three years after go-live.
This is not a criticism. It is a structural challenge. When organisations evaluate technology, they have never operated before, uncertainty is unavoidable. Quite simply, you do not yet know what you do not know.
So rather than prescribing what “good” looks like, it is more useful to focus on the questions worth sitting with, before issuing a tender and again when assessing the responses.
Do you know what you are actually buying?
The headline specifications of an AGV are easy to obtain. The fleet management software that governs performance, scalability, and flexibility is far less visible.
In many deployments, software is where the true constraints emerge:
How easily workflows can be modified
Whether additional vehicles genuinely increase throughput
How congestion impacts cycle times as fleets grow
The level of independence your operation retains from the vendor.
When a provider describes a system as scalable, it is critical to understand whether that refers to vehicle quantity, software architecture, or both. These distinctions rarely matter on day one - but they matter enormously when you attempt to expand capacity two years later and discover the answer is more complex than expected.
How much do you know about what happens after installation?
Go-live is not the finish line. In many ways, it is the starting gun. The stabilisation period following commissioning, the first peak-period equipment fault, or the first time a new mission must be introduced - these are the moments that reveal whether a vendor relationship is genuinely supportive or merely transactional.
A robust tender process should therefore ask vendors to describe:
Their ramp-up and stabilisation methodology
Training depth and operator readiness
The structure of supervised support during early operation
Response models during peak-period disruption.
These elements define operational confidence far more than a successful factory acceptance test ever will.
Who can change the system, and who cannot?
This question remains under-explored in many tenders.
Some vendors retain complete control of source code and system configuration, meaning even minor adjustments require vendor intervention, scheduling, and cost. Others enable meaningful in-house control, allowing operational teams to adapt missions, workflows, and logic independently.
In retail fulfilment, where volumes shift, SKUs evolve, and customer expectations rarely stand still, this distinction is not theoretical. It is operational reality.
Understanding precisely where control boundaries sit before contract signature is one of the most consequential steps an organisation can take.
Do you know what it will cost to run, not just to buy?
Capital expenditure is the number presented in boardrooms. Total cost of ownership is the number that shapes operational reality.
Key variables often overlooked include:
Software licensing structures (perpetual vs subscription)
Upgrade inclusion or additional charging
Spare-parts strategy and on-site inventory requirements
Component lifecycles and replacement costs
Support models and response SLAs.
In some cases, even documentation translation or regional compliance adjustments introduce unexpected post-purchase cost.
The lowest upfront figure does not always equate to the lowest lifetime cost. True comparison requires vendors to quantify long-term economics clearly, so decisions are made on value, not simply price.
The questions that prevent future surprises
None of these questions offer simple answers - and that is precisely the point.
They are the questions that distinguish confident, well-structured automation programs from projects that inherit avoidable operational surprises.
They shift evaluation from technology selection to performance assurance, and in an environment where automation decisions increasingly shape cost-to-serve, labour resilience, and long-term competitiveness, that distinction matters more than ever.
If these reflections prompt a conversation, you have not yet had, it is likely the right time to have it. We'd welcome the opportunity to continue the discussion.
Join the Daifuku team at the Retail Fulfilment Show to explore what smarter, lower-risk automation decisions look like in practice.
Christian Hartley
Business Solutions Manager
Email Schedule a meeting
Call: +61 416 529 597
About Christian
Christian Hartley is a commercial automation strategist with over a decade of experience aligning business outcomes with operational performance. With a background spanning financial services, partnership-led automation, and workflow optimisation across Europe and Australia, he specialises in ROI-driven decision-making, investment justification, and scalable system integration. His perspective prioritises practical performance, sustainable efficiency, and measurable commercial impact in modern fulfilment environments.
Comments