Almost half of NZ's automation expo came from firms of 50 or fewer

By DataForge team18 November 20265 min read

Logistics Automation NZ drew over 2,200 visitors, many from small firms. Here's what owners should check before buying picking systems or robots.

What the first show reported

New Zealand's first Logistics Automation NZ ran at Auckland Showgrounds on 10 and 11 November. XPO Exhibitions ran the show under the CeMAT brand from Hannover Fairs Australia. XPO says more than 2,200 people attended over the two days and more than 90 companies exhibited. On 16 November FMCG Business published a wrap-up with a visitor profile that's more useful than the headcount. According to that report, almost half of attendees worked for businesses with 50 or fewer employees, and nearly 80% made or influenced purchasing decisions.

The organisers also reported more than $260 million in purchasing power among visitors. They haven't said how they calculated that figure. We'd read it as what visitors said they might spend. It doesn't tell you anything about signed contracts. The same report says warehousing solutions, automated picking and sorting, and robotics drew the most interest, and more than a quarter of visitors were looking at AI-driven predictive analytics. Just over 12% of visitors came from general manufacturing and 10% from food, beverage and FMCG. A session from Mushiny on flexible automation for smaller businesses had standing room only.

Large names attended too, including Fonterra, Foodstuffs North Island, Mainfreight, NZ Post and Woolworths NZ. Briscoe Group's general manager of supply chain, Darren Porteous, said local suppliers made the technology "so much easier for us to see it when it comes to our backyard." The next show is in November 2028.

Why the small-firm share stands out

Warehouse automation in New Zealand has mostly been visible at big distribution centres run by grocers, retailers and 3PLs. Those operators have engineering teams, dedicated warehouse management systems and the volume to cover a long payback period. A business with 40 staff and one warehouse is usually in a different position. Stock might be managed in an accounting package with add-ons, or in an ERP nobody has reconfigured since go-live. There's often one internet connection and nobody whose job is integration.

When a large share of the people walking an automation expo come from firms that size, we read it as serious interest from smaller operators. Many of them are now pricing goods-to-person units, autonomous mobile robots and automated sorting for the first time. Over the next year or two, many of those firms will be talking to vendors. Some will sign, and their projects will go live before the next show in 2028.

The equipment itself is rarely where a small or mid-sized project gets stuck. The risk sits in the systems and data around the equipment, which the buyer owns and the robot vendor often doesn't scope in detail.

Where warehouse projects stall

Thomas Jackson, founder of Auckland warehouse software company Thomax, set out the common failure points in an IT Brief column on 13 November. Thomax sells warehouse software, so Jackson has a commercial angle, but his points match what we see in system integration work.

Robots need precise item data such as dimensions, weights and whether a product fits a tote. Jackson notes that many businesses don't have that data ready when automation is deployed. He also warns that systems built around batch processing don't suit robots that expect near-instant instructions. Batch processing is common in older ERPs, where orders are released to the floor every half hour or overnight. Cloud-controlled systems add another dependency. Jackson recommends a backup internet connection because the automation needs reliable, low-latency connectivity. In Auckland, where fibre outages from cable damage do happen, a single connection is a real exposure.

The column also points out that simulations and digital twins tend to model a tidier warehouse than the real one. Some problems only appear after go-live, when cracked totes, odd-shaped products and mixed manual and automated orders run into each other. Jackson suggests asking vendors how much of a project is configuration and how much is custom code. He also suggests asking how operations carry on while the automation is offline.

What NZ businesses should take from the expo

For a business with 50 staff, the work that decides whether warehouse automation pays off mostly happens outside the warehouse. Product master data has to be complete and accurate. The ERP or warehouse system has to release orders as fast as the equipment can pick them. Staff need a documented manual fallback for the hours the system is down. Each of those can be fixed before a purchase order is raised, and each is cheaper to fix then than during commissioning.

The integration layer deserves its own budget line. Vendors quoting picking hardware will often assume a standard connector to a known warehouse management system. If your stock lives in an accounting package or a lightly configured ERP, someone has to build and support the link between that system and the robots. Clarify who builds that link, who supports it, and what it costs before you compare hardware quotes. Our ERP team usually starts there, because order release timing and stock accuracy in the core system set the upper limit on what any automation downstream can achieve.

Smaller firms should also be realistic about scale. The ready-made case studies at an expo come from operations moving thousands of orders a day. A business shipping a few hundred orders a day might get more from barcode scanning, pick-to-light or better slotting than from robots, at least in the short term. The numbers should decide that, so measure current performance before talking to vendors.

Practical next steps

  • Pull your product master data and count how many active SKUs are missing dimensions, weights or barcodes. Fix the gaps before any vendor scoping session.
  • Write down how orders reach the warehouse today: how often your ERP or accounting system releases orders and what triggers a release. Ask each vendor what release frequency their equipment needs.
  • Measure a baseline for at least four weeks, covering picks per labour hour, pick error rate, order cycle time and overtime. Without one, you can't judge a vendor's projected savings.
  • Ask every vendor for a written split between configuration and custom code, and for a named reference site in New Zealand or Australia of similar size to yours.
  • Price the integration between your core system and the automation as a separate line item, with a named owner for ongoing support.
  • Draft a downtime procedure before go-live: who switches to manual picking, how orders are re-queued, and how long the site can run that way. Add a second internet connection if the control system is cloud-hosted.
  • Talk to warehouse staff early about which tasks change and how roles will shift, and record what you've told them.

If you're working out whether automation suits your operation, our process and automation practice covers process mapping, data clean-up and systems integration ahead of hardware decisions.

Want to know what this means for your organisation? Our team in Auckland can show you your top three opportunities in a free 30 minute assessment.

Get my free assessment How we help
Get new articles by RSS