Here's what stood out.
1. Hardware has commoditized, and software is where it matters now
Walk the show floor and you'll notice something. The physical automation solutions, the AMRs, sortation systems, goods-to-person setups, all look remarkably similar. Speed and capacity across different bot types have landed in the same ballpark.
That's not a bad thing. It means the technology has matured. But it creates a problem for buyers who still rely on spec sheet comparisons to make decisions.
The real separation is happening in software. Computer vision and agentic AI are where we saw the biggest gaps between vendors. These aren't buzzword implementations. We watched systems make independent decisions and adjust to changing conditions without human input. Some vendors are clearly ahead. Others are still demoing slideware.
If your evaluation process starts and ends with hardware specs, you're looking at the wrong layer.
2. The warehouse operating system is coming
For years, the industry has drawn clean lines between WMS, WES, and WCS. Those lines are disappearing.
Feature sets are bleeding into each other. A WMS increasingly handles execution logic. A WES manages tasks that once belonged to a WCS. The distinctions that used to drive purchasing decisions are getting harder to defend.
We heard a new term gaining traction at Manifest: warehouse operating system, or WOS. It's early, but the label fits better than the legacy categories. As these tools merge, operations teams will need to rethink how they evaluate platforms.
If you're invested in legacy systems, this cuts both ways. Fewer integration points is good. Getting locked into a platform that handles the merge poorly is not.
3. Yard and cold chain have moved from niche to core
The yard management and cold chain sessions were packed. Standing room only.
We spent time with Terminal and Technova, two companies doing strong work in yard and gate management technology and cold chain support. The conversations were different this year. Operations leaders aren't asking whether they need yard visibility or cold chain monitoring. They're asking which solution fits their operation. That's a meaningful shift.
Labor is driving a lot of this urgency. When you're running a cold storage facility with tight temperature windows and chronic staffing gaps, yard and gate automation stops being a nice-to-have pretty quickly.
4. The "single pane of glass" is getting real
Multiple companies at Manifest demonstrated data aggregation platforms that pull from ERPs, OMS, WMS, and other systems into a unified view. The concept isn't new. What's new is that some of these actually work.
For operations teams juggling four or five platforms, having metrics in one place changes how quickly you can respond to problems. We saw demos where a yard delay triggered automatic dock rescheduling and carrier notification from the same dashboard. That's not a mockup. That was live.
Quality varies, though. Some platforms aggregate data without actually connecting workflows. You get a prettier dashboard but no faster decision-making. The real test: does it help you act on what it shows you, or just show you more stuff?
5. Integration capability is the real bottleneck
Here's what surprised us most at Manifest: multiple companies approached us about serving as chief integrators. Not for one project, but as an ongoing capability.
The pattern keeps repeating. Companies like Shipium, EasyPost, and Gray Matter Systems build impressive technology. Their demos are sharp. But making that technology work inside an existing operation, connecting to legacy systems, fitting into workflows that weren't designed for it, handling the edge cases that never show up in controlled environments, that's where projects succeed or die.
That interface layer matters more than most people realize. We keep seeing great technology fail not because of the technology, but because nobody planned the last mile of integration.
What this means if you're evaluating automation
Manifest made one thing clear: advanced automation isn't optional anymore. The question is which technology solves your specific operational problems. And honestly, the harder question after that is who's going to make it work inside your four walls.
If you need help separating real capability from marketing claims, that's what Prism Insight is built for. We start with your operation, not a vendor's pitch deck.
Frequently Asked Questions
What is a warehouse operating system (WOS) and how is it different from a WMS?
A WOS combines the capabilities of WMS, WES, and WCS into a single platform that manages inventory, execution, and equipment control together. Traditional WMS focuses on inventory and order management while relying on separate systems for execution logic. The term is still emerging, but the convergence it describes is already happening across major platforms. Learn more about how WMS and YMS differ →
How long does a warehouse automation implementation typically take?
It depends on scope, but most mid-size operations should expect 6-12 months from assessment to go-live for a significant automation project. The technology installation is usually the faster part. Integration with existing systems, workflow redesign, and staff training take longer than people expect. A thorough discovery assessment before vendor selection can cut months off the overall timeline by identifying integration risks early.
Where should I start if I'm considering yard management technology for the first time?
Start with your current pain points: dock congestion, carrier wait times, trailer dwell time, or manual gate check-ins. Quantify the cost of those problems before looking at solutions. Most yard management deployments pay for themselves within 12-18 months when matched to the right operational gaps. Our yard management primer covers the basics →
Do I need a chief integrator, or can my internal IT team handle automation implementation?
It depends on your team's experience with operational technology, not just IT systems. Warehouse automation involves physical workflows, equipment coordination, and vendor management that most IT teams haven't encountered. A chief integrator brings cross-vendor experience and can spot integration risks your team might miss. For straightforward, single-vendor deployments, internal teams can often manage. Multi-vendor or brownfield projects are where outside integration expertise pays off.
