If you've reached the point where your planning and scheduling processes can't keep up — where spreadsheets are buckling under the weight of your product mix, your ERP's planning module is generating schedules that nobody trusts, and your planning team spends more time firefighting than actually planning — then you're probably looking at advanced planning and scheduling (APS) software.

You're not alone. The global APS software market was valued at roughly USD 2.8 billion in 2025 and is projected to grow at around 10–20% annually through the end of the decade, depending on whose numbers you use. Cloud-based deployment now accounts for over 60% of new installations, and the integration of AI and machine learning into planning algorithms is accelerating fast. For Australian manufacturers, distributors, and supply chain operators, the case for better planning technology is getting harder to ignore.

But here's the thing: going to market for an APS solution is one of the more consequential technology decisions a supply chain organisation will make. Get it right, and you unlock genuine step-changes in service levels, inventory performance, production efficiency, and decision-making speed. Get it wrong, and you're looking at a six- or seven-figure investment that never delivers its promised returns — or worse, a system that the planning team quietly works around because it doesn't reflect how the operation actually runs.

This article is a practical guide for Australian businesses thinking about going to market for APS. It covers what APS actually does, when it makes sense to invest, how to structure a selection process that produces a good outcome, and the mistakes that trip most organisations up along the way.

What Is APS, and How Is It Different From What You've Already Got?

Advanced planning and scheduling software simultaneously plans and schedules production, procurement, and distribution by considering available materials, labour, and plant capacity together — in real time. That last part is what makes it fundamentally different from the planning modules embedded in most ERP systems.

Traditional MRP (material requirements planning) and the planning functions inside ERPs like SAP, Oracle, or MYOB Advanced work sequentially. They calculate material requirements first, then try to fit those requirements into a production schedule, typically assuming infinite capacity. The result is a plan that looks reasonable on paper but falls apart the moment it hits the constraints of the real operation — machine availability, changeover times, labour shifts, material lead times, minimum batch sizes, and all the other messy realities of actually making things.

APS works differently. It models the operation's actual constraints — finite capacity, real material availability, sequencing rules, setup dependencies, labour rostering — and produces plans and schedules that are feasible from the start. Good APS platforms also support what-if scenario modelling, letting planners test the impact of accepting an urgent order, bringing forward a maintenance window, or reallocating capacity between production lines before committing to a decision.

For businesses where planning complexity is genuinely simple — a narrow product range, stable demand, limited make-to-order work — the planning module in your ERP may be perfectly adequate. APS earns its keep where one or more of the following conditions are present: high product mix competing for shared capacity, significant make-to-order or configure-to-order production, capital-intensive processes where machine utilisation matters, frequent schedule changes driven by demand variability or supply disruptions, or multi-site operations requiring coordinated planning across facilities.

If any of that sounds familiar, you're in APS territory.

When Is the Right Time to Go to Market?

Timing matters. Going to market too early — before you've properly understood the problem you're solving — leads to vendor-led selection processes where the technology shapes the conversation rather than the operation's needs. Going too late, when the pain is acute and leadership is demanding a solution immediately, compresses the timeline and forces shortcuts that compromise the outcome.

The right time to go to market is when you've done the foundational work to understand three things clearly.

First, what's actually broken in your current planning process. This isn't "we need better planning" — that's a symptom, not a diagnosis. Is the problem demand forecasting accuracy? Production scheduling feasibility? Inventory positioning? Supplier lead time variability? The inability to respond quickly to changes? Each of these points to different APS capabilities, and understanding the root cause shapes the requirements.

Second, what your target operating model looks like. How do you want planning and scheduling to work in three to five years? What level of automation do you want in the planning process? How should planning interact with sales, procurement, and the shop floor? What decisions should planners be making versus what should the system handle? This is where planning and operations strategy and APS technology selection intersect — and where many organisations make the mistake of jumping to software before defining the operating model.

Third, what your integration landscape looks like. No APS operates in isolation. It needs clean data from your ERP — bills of material, routings, work centres, inventory levels, sales orders, purchase orders. It may need to interface with a manufacturing execution system (MES), a warehouse management system, or a transport management system. Understanding the integration requirements and the quality of your master data before going to market saves enormous pain during implementation.

Once you have clarity on those three things, you're ready to engage the market properly.

Structuring the Selection Process

A well-run APS selection process typically follows a sequence that looks something like this: requirements definition, market scan, long-list, shortlist, detailed evaluation, and final selection. Each stage has a purpose, and skipping stages is where the problems start.

Requirements Definition

This is the non-negotiable foundation. A structured requirements document captures the functional capabilities the APS must deliver (demand planning, production scheduling, capacity planning, material planning, what-if analysis, and so on), the non-functional requirements (performance, scalability, security, user experience), and the integration requirements (what systems the APS must connect with, what data flows are needed, and what the latency and frequency requirements are).

The requirements should distinguish between must-haves — capabilities the system absolutely needs on day one — and desirables, which would improve the operation but aren't essential at launch. This distinction matters because it prevents the selection from being dominated by feature checklists that obscure the genuinely critical requirements.

A good requirements process also documents the operational context — what does the planning team actually do day-to-day? What decisions do they make? What data do they use? What workarounds have they built? This operational understanding is what separates a requirements document that drives a good selection from one that reads like a generic wish list.

This is an area where having an independent advisor — someone who's seen enough APS implementations to know which requirements actually matter in practice — makes a material difference. Internal teams often lack the cross-industry perspective to benchmark their requirements against what's realistic and what's overkill. A firm like Trace Consultants that works across manufacturing, retail, government, and services can bring that perspective.

Market Scan and Long-List

The APS market is crowded. At the enterprise end, you've got platforms from the likes of Kinaxis, o9 Solutions, Blue Yonder, SAP IBP, and Oracle. In the mid-market, there's DELMIA Quintiq (Dassault Systèmes), Opcenter APS (Siemens), PlanetTogether, Logility, and others. At the smaller end, solutions like Tactic, CyberPlan, and various ERP-embedded modules serve less complex operations.

The market scan identifies which vendors are credible candidates for your specific requirements. Not all APS platforms are created equal — some are stronger in production scheduling, others in demand planning or supply network optimisation. Some are purpose-built for process manufacturing (food, beverages, chemicals), while others are designed for discrete manufacturing (machinery, electronics, automotive). Getting the sector and complexity fit right at the long-list stage saves significant time later.

For Australian businesses, local support and implementation capability is a practical consideration that's easy to overlook. A platform might be market-leading globally, but if the vendor's nearest implementation team is in Chicago and there's no local partner with deep APS experience, you're carrying additional risk and cost. Understanding the vendor's ANZ footprint — direct presence, certified partners, existing customer base — should be part of the assessment.

Shortlist and Detailed Evaluation

The shortlist — typically three to four vendors — should be evaluated through structured demonstrations scripted against your operational scenarios, not the vendor's standard demo. This is a critical distinction. Every APS vendor can show you a polished demo using their reference data set. What you need to see is how the platform handles your product mix, your constraints, your scheduling rules, and your planning complexity.

A scripted demonstration provides a test data set and a set of planning scenarios that reflect your actual operation. You ask each vendor to configure their platform against that data and demonstrate how it handles the scenarios. This levels the playing field, exposes genuine capability gaps, and gives the planning team — who should absolutely be in the room — the ability to assess whether the tool will actually work in their world.

Alongside the demonstrations, reference checks with comparable operations are essential. Ask the vendor for references in your industry, of similar scale and complexity, preferably in the ANZ region. Talk to the planning managers, not the CIO — the people who actually use the system every day. Ask what they'd do differently. Ask what surprised them during implementation. Ask whether the system delivers what was promised during the sales process.

The evaluation should also include a total cost of ownership (TCO) analysis that looks beyond the licence fee. Implementation costs, integration development, data migration, training, ongoing support, and the internal effort required from your team all factor into the true cost. For cloud-based APS platforms, the subscription model smooths the upfront investment but the cumulative cost over five to seven years can exceed an on-premise deployment — it depends on the platform and your scale.

Final Selection

The final selection should synthesise all the evidence — functional fit, integration feasibility, vendor capability, reference feedback, TCO, and strategic alignment. It's worth noting that there's rarely a perfect answer. Every platform will have trade-offs. The goal is to select the platform that best fits your requirements and your organisation's ability to implement and sustain it, not the platform with the longest feature list.

The Mistakes That Trip Most Organisations Up

Having seen how APS selections play out across a range of Australian businesses, there are patterns worth calling out.

Letting the Vendor Drive the Conversation

This is the single biggest risk. APS vendors are sophisticated sales organisations. They know how to steer conversations toward their platform's strengths and away from its limitations. Without a clear set of requirements and a structured evaluation process, it's remarkably easy to end up selecting the platform that gave the best presentation rather than the one that's the best fit.

The antidote is simple: own the process. Define the requirements before you talk to vendors. Script the demonstrations. Control the evaluation criteria. Use an independent advisor if you don't have the internal capability to manage this — it's a fraction of the cost of getting the selection wrong.

Over-Specifying the Solution

There's a temptation, particularly in larger organisations, to select the most sophisticated platform on the market on the assumption that you'll "grow into it." This sounds reasonable but often plays out poorly. Enterprise-grade APS platforms are powerful but complex. They require significant configuration, substantial data quality, skilled users, and ongoing investment to maintain. If your organisation isn't ready for that level of complexity — if your master data is patchy, your planning processes are immature, or your team doesn't have the analytical capability to use the tool effectively — you'll end up with an expensive platform running at a fraction of its potential.

A better approach is to match the APS tier to your current maturity and your realistic three-year trajectory. A mid-market APS that's well-implemented and well-adopted will outperform an enterprise platform that's under-utilised. This is where honest self-assessment — or an independent maturity assessment from an advisor — pays dividends.

Underinvesting in Data Readiness

APS systems are only as good as the data they consume. If your bills of material are inaccurate, your routings don't reflect actual cycle times, your inventory records are unreliable, or your demand signals are noisy, the APS will produce plans that nobody trusts. And when the planning team doesn't trust the system, they revert to spreadsheets — which is exactly where you started.

Data readiness should be treated as a workstream in its own right, starting before the APS implementation begins. This means auditing and cleansing master data, establishing data governance processes, and ensuring the data pipeline from ERP to APS is reliable and timely. It's unglamorous work, but it's the difference between an APS that delivers value and one that sits alongside the planning team's "real" spreadsheets.

Treating Implementation as a Software Project

This parallels what we see in warehouse management technology projects. An APS implementation changes how the planning team works. It changes their daily routines, their decision-making processes, their interactions with sales, procurement, and the shop floor. It may change roles and responsibilities. It may require new skills.

Organisations that treat APS implementation as a software deployment — hand it to IT, configure it, switch it on — consistently underperform. The ones that succeed invest in change management, process redesign, training, and the organisational effort required to embed new ways of working. They recognise that the technology is the enabler, not the solution.

Ignoring the Planning Operating Model

This is perhaps the most subtle but most important point. An APS is a tool that supports a planning process. If the planning process itself is poorly designed — unclear roles, fragmented decision rights, no structured cadence of planning meetings, no connection between demand planning and supply planning — then layering technology on top will amplify the dysfunction, not fix it.

Before going to market for an APS, it's worth investing in planning and operations design work. Define the planning operating model: What are the key planning processes? Who makes which decisions? What's the rhythm of the planning cycle? How does planning connect to execution? This work doesn't require technology — it requires clear thinking about how the organisation should plan. The APS then becomes the tool that enables that model.

The AI Question

It's impossible to discuss APS in 2026 without addressing artificial intelligence. Every vendor in the market is now leading with AI capabilities — AI-powered demand sensing, machine learning-optimised scheduling, autonomous planning, predictive analytics. Some of this is genuine and valuable. Some of it is marketing ahead of reality.

The practical state of AI in APS today is that machine learning is delivering real value in demand forecasting — identifying patterns in historical data, incorporating external signals (weather, promotions, events), and improving forecast accuracy at the SKU level. AI-driven scheduling optimisation is also maturing, particularly for complex sequencing problems where the number of possible combinations exceeds what heuristic rules can handle efficiently.

What AI is not yet doing reliably is replacing the judgement of experienced planners. The best APS implementations use AI to augment planners — providing better inputs, faster scenario analysis, and recommended actions — while keeping humans in the decision loop for the exceptions, trade-offs, and business context that algorithms can't fully capture.

When evaluating AI capabilities in APS vendors, focus on practical outcomes rather than buzzwords. Ask for evidence of AI improving forecast accuracy or scheduling efficiency in comparable operations. Ask how the AI models are trained and validated. Ask what happens when the AI gets it wrong — how does the planner override and the system learn?

How Trace Consultants Can Help

Trace Consultants is an Australian supply chain consultancy that helps organisations get APS selection and implementation right. Our job is to make sure the technology you invest in genuinely fits your operation.

Here's where we typically add value:

Planning maturity assessment. Before you go to market, we assess the current state of your planning processes, data quality, organisational capability, and planning and operations model. This work identifies what needs to be fixed before technology is layered on, and shapes the requirements for the APS selection.

Requirements definition. We work with your planning, operations, and technology teams to build a structured requirements specification — functional, non-functional, and integration — grounded in how the operation actually works and where it needs to get to. We bring cross-industry perspective from working across FMCG and manufacturing, retail, government and defence, and property, hospitality and services.

Market scan and vendor evaluation. We know the APS market — who does what well, where the strengths and limitations are, and which platforms suit which types of operation. We run structured selection processes including scripted vendor demonstrations, reference checks, and total cost of ownership analysis.

Implementation oversight. We work alongside your team and the vendor through implementation to keep the project focused on operational outcomes. This includes process redesign, data readiness, training design, and change management — the things that determine whether the APS actually sticks.

Broader supply chain strategy. APS selection often sits alongside bigger questions about your distribution network, procurement operating model, workforce planning, or organisational design. We help clients connect the technology decision to the wider strategic context so you're not optimising in isolation.

If you're thinking about going to market for an APS — or if you've already started and the process isn't going as planned — get in touch. We'd welcome the conversation.

The Bottom Line

Going to market for an APS solution is a significant undertaking. The technology has never been more capable, and the market has never offered more choice. But choice without structure leads to poor decisions. The organisations that get the best outcomes are the ones that invest in understanding their requirements before they talk to vendors, run a disciplined evaluation process, match the technology tier to their actual complexity, and invest in the data, processes, and people that make the technology work.

It's not the most exciting part of supply chain transformation. But it's the part that determines whether the investment delivers.

Trace Consultants is an Australian supply chain and procurement consultancy specialising in strategy, operations, and technology. For more insights, visit our insights page or explore our technology advisory services.

‍

There's a familiar arc to most warehouse technology projects. The vendor demos look sharp. The business case stacks up. The implementation timeline feels manageable. And then reality hits — the system doesn't handle your specific pick logic without expensive customisation, the integration with your ERP turns out to be twice as complex as anyone estimated, and six months after go-live, half the warehouse team is still using workarounds because the platform doesn't match how the operation actually runs.

It's not a niche problem. Industry data suggests roughly 60% of warehouse management system (WMS) projects experience budget overruns or schedule delays. Over 44% of companies report delayed return on investment due to drawn-out integration timelines and undercooked training programs. The global WMS market is forecast to grow from around USD 3.4 billion in 2025 to nearly USD 16 billion by 2033, and order management systems (OMS) are on a similar trajectory. Australian businesses are clearly investing. The question is whether they're investing well.

This article is for supply chain leaders, operations managers, and technology teams at Australian businesses who are either evaluating warehouse and order management technology for the first time or looking to get more out of what they've already got. We'll cover what these systems actually do, where organisations typically go wrong, and how to approach selection and implementation in a way that delivers lasting value.

What Are We Actually Talking About?

It's worth getting the definitions straight, because the lines between warehouse management systems and order management systems have blurred significantly in recent years.

A warehouse management system is software that manages and optimises the physical operations inside a warehouse or distribution centre — receiving, putaway, inventory tracking, picking, packing, shipping, and returns. A good WMS gives you real-time visibility of stock across locations, directs your workforce through optimised task sequences, and integrates with hardware like barcode scanners, conveyor systems, and sortation equipment.

An order management system sits a layer above. It manages the lifecycle of a customer order from the moment it's placed through to fulfilment and post-purchase service. In a multi-channel environment — which is most Australian retailers and wholesalers at this point — the OMS is what decides which fulfilment location should handle each order, manages inventory visibility across channels, coordinates ship-from-store and click-and-collect, and handles the increasingly complex world of returns and exchanges.

Many modern platforms blend both capabilities. Manhattan Associates, for instance, has pushed hard on unifying WMS and OMS into a single platform. At the other end of the market, you've got lightweight cloud-based solutions like CartonCloud or Cin7 that combine basic warehouse management with order and inventory management in a single subscription. The right answer for your business depends entirely on how complex your operation is — and that's where most organisations go wrong.

It's also worth noting that the distinction between WMS and OMS matters most for businesses operating across multiple fulfilment channels. If you're running a single warehouse shipping B2B orders, a solid WMS with basic order management may be all you need. But if you're a retailer fulfilling from DCs, stores, and third-party partners — managing click-and-collect, ship-from-store, marketplace orders, and returns across all of them — the OMS layer becomes critical. It's the orchestration engine that decides where each order gets fulfilled, based on inventory availability, proximity to the customer, fulfilment cost, and capacity. Without it, you're making those decisions manually or not making them at all.

Why This Matters More in Australia

Australia's geography creates supply chain challenges that don't exist in many other markets. Vast distances between major population centres, high domestic freight costs, and a relatively small consumer base spread across an enormous landmass all mean that warehouse and distribution efficiency matters disproportionately here.

Add to that the rapid growth of online retail. Australian e-commerce has grown consistently over the past five years, and consumer expectations around delivery speed, real-time tracking, and seamless returns have sharpened dramatically. For retailers operating across in-store and online channels, the operational complexity of fulfilling orders profitably from multiple locations — DCs, stores, third-party logistics providers — is a fundamentally different challenge than it was even five years ago.

For FMCG and manufacturing businesses, the pressures are different but no less acute. Higher SKU counts, shorter product lifecycles, and the shift toward more frequent, smaller deliveries are all stretching warehouse operations that were designed for a different era. Many Australian manufacturers are still running warehouse processes on spreadsheets, or on basic ERP modules that were never designed to handle the picking complexity, labour management, or automation interfaces that modern operations require.

The technology exists to solve these problems. The challenge is picking the right technology and implementing it properly.

Where Organisations Get It Wrong

Having worked across numerous warehouse technology projects, there are patterns that come up again and again. They're worth understanding because they're almost always avoidable.

Starting with the Technology, Not the Operation

The most consequential mistake happens before a single vendor has been shortlisted. Someone in the leadership team sees a compelling demo at a conference, or a vendor approaches the business with an attractive proposition, and the conversation jumps straight to features, modules, and pricing. What gets skipped is the foundational work of understanding what the operation actually needs.

A proper selection process starts with a thorough assessment of the current operation — how goods flow through the facility, where the bottlenecks sit, what workarounds the team relies on, where errors originate, and what the operation needs to look like in three to five years. This work produces the functional requirements specification that drives the entire selection. Without it, you're evaluating technology in a vacuum.

This is where having an independent advisor makes a significant difference. Vendors will always present their platform in the best light, and internal teams often lack the cross-industry perspective to know what "good" looks like. A firm like Trace Consultants that works across multiple sectors and has seen dozens of WMS and OMS implementations can bring a level of objectivity that's hard to replicate internally.

The Tier Mismatch

WMS and OMS platforms exist across a spectrum. At one end, you've got enterprise-grade platforms from the likes of Manhattan Associates, Blue Yonder, and SAP — capable of managing complex, multi-site, multi-channel operations with advanced optimisation, labour management, and automation interfaces. At the other end, you've got cloud-native solutions designed for simpler operations that can be up and running in weeks rather than months.

One of the most common selection errors is a tier mismatch. Over-specifying — selecting a Tier 1 enterprise WMS for a single-site operation that doesn't need or can't absorb that complexity — wastes money and overwhelms the team. Under-specifying — selecting a basic system for a complex multi-site distribution network — forces expensive customisation, workarounds, and eventually re-implementation.

Getting the tier right requires an honest, data-driven assessment of operational complexity. A business running straightforward pick-pack-ship out of a single DC has fundamentally different requirements from one managing mixed B2B and B2C fulfilment, cross-docking, value-added services, and automation interfaces across multiple sites.

Underestimating Integration Complexity

No WMS or OMS operates in isolation. It sits within an ecosystem of enterprise systems — ERP, e-commerce platforms, carrier management, point-of-sale, and potentially warehouse automation control systems. The quality of these integrations is what determines whether the technology delivers its promised value or becomes a source of ongoing operational friction.

Yet integration complexity is consistently underestimated. Organisations evaluate platforms based on standalone capabilities and assume the integration will be straightforward. It rarely is. Legacy ERP systems may lack the APIs or data standards needed for real-time integration. Data formats may be inconsistent across systems. Business rules embedded in existing platforms may conflict with the logic in the new WMS or OMS.

A proper selection process evaluates integration requirements with the same rigour as functional requirements. It maps the specific data flows between systems, the frequency and latency requirements, and the technical approach — whether through middleware, direct API connections, or file-based exchange. This work isn't glamorous, but it's where projects succeed or fail.

Treating It as a Technology Project Rather Than an Operational Transformation

This one is worth dwelling on because it's the root cause of most implementation failures. A WMS or OMS implementation isn't primarily a technology project — it's an operational transformation that happens to involve technology. The system will change how every person in the warehouse does their job. It will change processes, responsibilities, performance measurement, and daily workflows.

Organisations that treat implementation as a software deployment project — hand it to IT, configure the system, switch it on — consistently underperform. The ones that succeed invest heavily in change management, workforce training, process redesign, and the organisational effort required to make the technology stick.

What Good Looks Like

So if those are the common pitfalls, what does a well-executed warehouse and order management technology project look like?

Requirements-Led Selection

It starts with requirements, not vendors. A thorough current-state assessment of warehouse operations, order profiles, inventory characteristics, integration landscape, and future-state ambitions. This produces a structured requirements document that distinguishes between non-negotiable functional requirements, desirable capabilities, and integration needs. Only then do you go to market.

The selection process itself should be structured and transparent — a long list based on market scan, a shortlist based on requirements fit, detailed demonstrations scripted against your actual operational scenarios (not the vendor's standard demo), reference checks with comparable operations, and a total cost of ownership analysis that accounts for implementation, integration, training, and ongoing support.

Phased Implementation with Operational Focus

Rather than a big-bang go-live, best practice is a phased approach that sequences functionality based on operational priority and organisational readiness. Start with core inventory management and basic warehouse processes, stabilise, then layer on more advanced capabilities like labour management, wave planning optimisation, or automation interfaces.

Each phase should include thorough process redesign — not just configuring the system to replicate existing processes, but rethinking workflows to take advantage of what the technology enables. This is where experienced supply chain consultants add real value. They've seen enough implementations to know which process changes deliver the biggest gains, and which ones will trip up the warehouse team.

Workforce Readiness

The technology is only as good as the people using it. Training needs to go well beyond "how to use the screen." Warehouse teams need to understand why processes are changing, how the new system supports their work, and what the performance expectations look like. Supervisors and team leaders need deeper training on exception handling, system configuration, and performance analytics.

This ties directly into workforce planning — understanding how the new system will change labour requirements, shift patterns, and skill profiles. A WMS that introduces wave-based picking or directed putaway changes the nature of warehouse work. That needs to be planned for, not discovered on day one.

Measuring What Matters

Post-implementation, the organisations that extract the most value from their WMS and OMS investment are the ones that actively manage performance against a clear set of operational KPIs — order accuracy, pick rates, inventory accuracy, order-to-ship cycle time, and cost per order. The technology provides the data. The discipline of actually using that data to drive continuous improvement is an organisational capability, not a system feature.

This is an area where many Australian businesses leave significant value on the table. They invest heavily in the technology, stabilise the operation after go-live, and then move on to the next priority. But the real payoff comes from ongoing optimisation — refining pick paths as order profiles change, adjusting slotting strategies based on seasonal demand patterns, using labour management data to improve rostering and productivity, and leveraging order data to refine fulfilment allocation rules. A WMS or OMS that's been live for two years should be performing materially better than it did at go-live. If it isn't, that's a process and discipline issue, not a technology issue.

This is also where robust planning and operations processes make a tangible difference. If your demand planning is poor, your warehouse will always be reacting — expediting orders, dealing with stockouts, and absorbing the cost of unplanned activity. The technology can't compensate for bad inputs.

The Emerging Technology Landscape

It's worth touching on where the technology is heading, because decisions made today need to account for what's coming.

Cloud-based WMS adoption is accelerating. The flexibility, lower upfront costs, and faster deployment timelines of cloud platforms are making them the default choice for a growing number of Australian businesses. The global cloud WMS segment is growing at over 22% annually, and for good reason — cloud platforms are easier to update, scale, and integrate than traditional on-premise deployments.

Artificial intelligence and machine learning are starting to move from marketing buzzwords into practical warehouse applications. AI-powered demand forecasting that adjusts inventory positioning ahead of seasonal peaks. Machine learning algorithms that optimise picking routes based on historical order patterns. Predictive maintenance that flags equipment issues before they cause downtime. These capabilities are increasingly available as standard features in the leading WMS and OMS platforms, not as bolt-on modules that require separate implementation.

Warehouse automation — from goods-to-person robotics to automated storage and retrieval systems — is growing rapidly in Australia, with major retailers and logistics providers investing heavily. Woolworths' automated case picking distribution centres are a good example of what's coming — purpose-built facilities using shuttle technology and automated guided vehicles to process tens of thousands of products daily with near-perfect picking accuracy. The critical point for most businesses isn't whether to automate, but how to ensure their WMS can interface with and orchestrate the automation they're likely to adopt over the next five to ten years. Selecting a WMS that can't grow into automation is an expensive mistake.

For Australian businesses specifically, local carrier and integration ecosystem support is a practical consideration that's easy to overlook. Your WMS or OMS needs to integrate with Australia Post, StarTrack, Toll, Aramex, and multi-carrier platforms like Shippit or Starshipit. It needs to work with Xero or MYOB for accounting. And if you're in retail, it needs clean connections to Shopify, BigCommerce, Amazon AU, eBay, Catch, and whatever marketplace comes next. These aren't edge cases — they're table stakes for operating in the Australian market.

How Trace Consultants Can Help

Trace Consultants is an Australian supply chain consultancy that works with organisations across retail, FMCG and manufacturing, government and defence, and property, hospitality and services to get warehouse and order management technology right.

Our approach is vendor-independent and requirements-led. Our job is to make sure the technology you select is genuinely the best fit for your operation — not the best fit for the vendor's sales target.

Here's what we typically help with:

Operational assessment and requirements definition. Before any technology conversation, we map the current state of your warehouse and distribution operations — material flows, process bottlenecks, labour utilisation, inventory accuracy, and order profiles. We document functional and integration requirements, assess the gap between current state and target state, and build the business case for investment.

Technology selection. We run structured selection processes — market scans, vendor long-listing and shortlisting, scripted demonstrations against your operational scenarios, reference checks, and total cost of ownership analysis. We help you evaluate not just the technology, but the vendor's implementation capability, local support model, and product roadmap.

Implementation support. We work alongside your team and the vendor's implementation team to ensure the project stays focused on operational outcomes, not just system configuration. This includes process redesign, integration design and testing, data migration planning, training design, and go-live support.

Network and distribution strategy. Often, the right time to evaluate warehouse technology is alongside a broader review of your distribution network. Where should your DCs be? How many do you need? What's the right balance between centralised and decentralised fulfilment? These strategic questions shape the technology requirements, and we help clients work through both together.

Planning and operations improvement. Technology is one part of the equation. We also help clients improve the planning and operational processes that sit around the technology — demand planning, inventory management, procurement, and supplier management. A brilliant WMS bolted onto poor planning processes will underperform. We help clients address both.

If you're evaluating warehouse or order management technology — or if you've already implemented a system and aren't getting the value you expected — we'd welcome a conversation. You can reach us here.

The Bottom Line

Warehouse and order management technology, properly selected and implemented, transforms operations. It drives measurable improvements in productivity, accuracy, cost performance, and customer experience. The Australian WMS market alone is forecast to grow at over 20% annually through the end of the decade — this isn't a passing trend, it's a structural shift in how supply chains operate.

But the technology is only as good as the process that selects it and the organisation that implements it. Start with the operation, not the vendor. Be honest about your complexity. Invest in integration and change management with the same rigour you invest in the software licence. And measure what matters after go-live.

Get those things right, and the returns will follow.

Trace Consultants is an Australian supply chain and procurement consultancy specialising in strategy, operations, and technology. For more insights, visit our insights page or explore our technology advisory services.

‍

There's a particular kind of optimism that takes hold when an organisation decides to invest in a new warehouse management system or transport management system. The vendor demonstrations look impressive. The business case projects compelling returns. The implementation timeline seems manageable. And then reality arrives.

The warehouse team discovers the system doesn't handle their specific pick-and-pack processes without expensive customisation. The transport planners find the routing algorithms don't account for the access restrictions at half their delivery sites. The integration with the ERP turns out to be far more complex than anyone estimated. The go-live date slips. The budget expands. And six months after implementation, half the warehouse staff are still using workarounds because the system doesn't match how the operation actually runs.

This isn't a rare outcome. Industry data suggests that roughly 60% of WMS projects experience budget overruns or schedule delays, often because organisations underestimate the complexity of change management and system integration. Over 44% of companies report delayed return on investment due to prolonged integration timelines and training requirements. Average WMS implementation costs range from US$70,000 to US$500,000 depending on features and scale — before you account for the overruns.

The pattern for TMS implementations is similar. Organisations invest in sophisticated route optimisation and freight management capabilities, only to discover that the technology works brilliantly in the demonstration environment and poorly in the messy reality of their actual transport network, carrier relationships, and operational constraints.

None of this means the technology isn't valuable. WMS and TMS platforms, properly selected and implemented, transform warehouse and transport operations. They drive measurable improvements in productivity, accuracy, visibility, and cost performance. The problem isn't the technology itself — it's how organisations go about choosing and deploying it.

The selection problem: why organisations pick the wrong system

The most consequential mistake in any WMS or TMS project happens before a single line of code is configured — it happens during selection. And the root cause is almost always the same: the organisation starts with the technology rather than starting with the operation.

Vendor-led versus requirements-led selection

Most WMS and TMS selection processes begin when a vendor approaches the business, or when someone in the leadership team sees a compelling demonstration at a conference. The conversation immediately shifts to features, modules, and pricing tiers. What gets skipped is the hard, unglamorous work of understanding what the operation actually needs.

A requirements-led selection process starts differently. It starts with a thorough assessment of current warehouse and distribution operations — how goods flow through the facility, where the bottlenecks are, what workarounds the team relies on, where errors originate, and what the operation needs to look like in three to five years. It documents the non-negotiable functional requirements (the things the system absolutely must do on day one), the desirable capabilities (the things that would improve operations but aren't essential at launch), and the integration requirements (how the WMS or TMS needs to communicate with ERP, order management, carrier systems, and hardware like scanners, sorters, and printers).

This requirements work is what separates organisations that select a system well-matched to their operation from organisations that spend eighteen months and several hundred thousand dollars implementing a platform that was never the right fit.

The tier mismatch

WMS and TMS platforms exist across a spectrum from lightweight, cloud-based solutions designed for simpler operations through to enterprise-grade platforms capable of managing complex, multi-site, multi-channel operations with advanced optimisation, labour management, and automation interfaces.

One of the most common selection errors is a tier mismatch — either over-specifying (selecting a complex, expensive Tier 1 system for an operation that doesn't need or can't absorb that level of sophistication) or under-specifying (selecting a basic system that can't handle the operational complexity, forcing expensive customisation or an eventual re-implementation).

Getting the tier right requires an honest assessment of operational complexity — current and projected. A single-site operation running straightforward pick-pack-ship processes has fundamentally different requirements from a multi-site distribution network managing mixed B2B and B2C fulfilment, cross-docking, value-added services, and automation interfaces. The right system for one is the wrong system for the other.

Ignoring the integration reality

No WMS or TMS operates in isolation. It sits within an ecosystem of enterprise systems — ERP, order management, e-commerce platforms, carrier systems, yard management, and potentially warehouse automation control systems. The quality of these integrations determines whether the technology delivers its promised value or becomes a source of ongoing operational friction.

Yet integration complexity is consistently underestimated during selection. Organisations evaluate WMS and TMS platforms based on their standalone capabilities and assume the integration will be straightforward. It rarely is. Legacy ERP systems may lack the APIs or data standards needed for real-time integration. Data formats may be inconsistent. Business rules embedded in existing systems may conflict with the logic in the new platform.

A proper selection process evaluates integration requirements with the same rigour as functional requirements. It identifies the specific data flows between systems, the frequency and latency requirements for those flows, and the technical approach to integration — whether through middleware, direct API connections, or file-based exchange.

The implementation problem: where good selections go wrong

Even when an organisation selects the right system, implementation is where value is won or lost. The technology vendors have strong implementation methodologies. The challenge is that implementation is not primarily a technology project — it's an operational transformation project that happens to involve technology.

Process design before system configuration

The single most important principle in WMS and TMS implementation is this: design your processes before you configure your system, not the other way around.

Too many implementations begin with system configuration based on how the operation currently works. The team documents existing processes, configures the system to replicate them, and then wonders why the new technology hasn't delivered the step-change improvement they expected. The answer is obvious in hindsight — if you automate a bad process, you get a faster bad process.

Effective implementation starts with process redesign. Before the system is configured, the project team should define the target-state processes — how receiving, put-away, replenishment, picking, packing, shipping, cycle counting, and returns should work in the new environment. For TMS, this means defining how orders are consolidated, how loads are planned and optimised, how carriers are selected and tendered, how shipments are tracked, and how freight is audited and settled.

This process design work often reveals opportunities that the technology alone would never have surfaced — changes to warehouse layout, slotting strategy, pick methodology, wave planning logic, or transport routing that deliver benefits independent of the system. It also ensures that the system is configured to support the operation you want, not the operation you have.

Data readiness: the unsexy foundation

Every WMS and TMS implementation depends on clean, accurate master data — item masters with correct dimensions and weights, location masters with accurate capacity and constraint information, carrier rate tables, vehicle specifications, delivery windows, and customer shipping requirements. If this data is incomplete, inconsistent, or wrong, the system will produce incorrect put-away decisions, suboptimal pick paths, inaccurate load plans, and unreliable cost estimates.

Data migration and cleansing is consistently the least glamorous and most underestimated workstream in any implementation. It requires painstaking effort to audit existing data, identify and correct errors, fill gaps, and establish data governance processes to maintain quality post-go-live. Organisations that shortcut this work pay for it repeatedly in operational errors, workarounds, and lost confidence in the system.

Change management: the difference between go-live and adoption

A WMS or TMS goes live on a specific date. But going live and achieving adoption are very different things. Industry research indicates that 70% of software implementations fail to deliver expected results due to poor user adoption, and 63% of employees stop using technology if they don't see its relevance to their daily work.

In a warehouse environment, this translates directly to operational performance. If pickers revert to paper-based processes because the RF-directed workflow is confusing, you've spent hundreds of thousands of dollars on a system that isn't being used. If transport planners override the TMS optimisation because they don't trust it, you're paying for a planning tool that's functioning as an expensive spreadsheet.

Effective change management for WMS and TMS implementations requires investment in three areas. First, stakeholder engagement — involving warehouse supervisors, team leaders, and experienced operators in process design and system configuration so they understand and own the new way of working. Second, training — not generic vendor training, but role-specific training that shows each user exactly how the system supports their daily tasks, delivered close to go-live and reinforced in the weeks afterwards. Third, sustained support — recognising that the first four to eight weeks after go-live are when adoption is won or lost, and providing sufficient floor support, super-users, and rapid issue resolution to build confidence.

This is where project and change management capability makes the difference between a system that delivers its business case and a system that becomes an expensive source of operational frustration.

WMS and TMS: different systems, different challenges

While WMS and TMS share many of the same selection and implementation pitfalls, they present distinct challenges that warrant separate consideration.

WMS-specific considerations

Warehouse management systems are deeply operational — they direct the physical movement of goods through a facility, and their effectiveness is measured in real-time productivity metrics. Key considerations for Australian businesses include hardware dependency (WMS relies on scanners, mobile devices, label printers, and potentially automation interfaces — hardware selection and network infrastructure are implementation workstreams in their own right), warehouse layout and slotting (the system's performance depends on how well the facility is configured to support directed work — poor slotting or layout design will undermine even the best WMS), scalability for peak periods (Australian retail and FMCG operations experience significant seasonal peaks, and the WMS needs to handle peak volumes — including temporary labour using the system with minimal training — without degradation), and multi-channel complexity (organisations running B2B wholesale and B2C e-commerce from the same facility need a WMS that can manage fundamentally different fulfilment profiles without operational conflict).

The global WMS market is growing at roughly 19.5% CAGR, with cloud-based deployments gaining share rapidly. For Australian businesses, cloud WMS platforms offer faster deployment and lower upfront capital, but require careful evaluation of data sovereignty, network latency, and vendor support in Australian time zones.

TMS-specific considerations

Transport management systems operate across a broader ecosystem of carriers, routes, rates, and service levels, and their value depends heavily on the quality of data flowing in and out. Key considerations include carrier integration (a TMS is only as useful as its connectivity to your carrier base — Australian businesses often work with a mix of national carriers, regional operators, and specialist providers, and the system needs to accommodate this diversity), rate management complexity (Australian freight operates across a complicated rate structure involving zone-based pricing, weight breaks, fuel levies, accessorial charges, and contract-specific arrangements — the TMS must handle this granularity accurately or its cost calculations are meaningless), geographic and network challenges (Australia's vast distances, concentrated population centres, and thin regional freight networks create optimisation challenges that many TMS platforms — designed primarily for denser US or European markets — handle poorly without configuration), and visibility and exception management (the real value of a TMS often isn't in the initial load plan but in the ability to identify and manage exceptions — late pickups, missed deliveries, carrier capacity issues — in near real time).

The Australian context

Australian supply chain operations face specific challenges that influence both WMS and TMS selection. Our geographic distances make transport cost a larger proportion of total supply chain cost than in most comparable markets. Our concentrated population distribution — with the majority of demand in the eastern seaboard capital cities — creates particular network design dynamics. Our labour market — characterised by higher wages and increasing difficulty in recruiting warehouse and transport workers — makes the productivity improvements from well-implemented WMS and TMS especially valuable.

At the same time, the Australian market is smaller than the US or European markets that most WMS and TMS vendors are primarily designed for. This means that vendor presence, local support, implementation partner availability, and the depth of Australian reference sites all require careful evaluation. A system that works brilliantly for a 500,000-square-foot distribution centre in Ohio may not have the local support infrastructure to deliver the same experience for a 20,000-square-metre facility in western Sydney or Melbourne's south-east.

The sector matters too. FMCG and manufacturing operations have different WMS requirements from retail e-commerce fulfilment centres. Government and defence supply chains operate under compliance and security requirements that constrain technology choices. Health and human services organisations managing pharmaceutical or cold-chain distribution need specialised capabilities. A good selection process accounts for these sector-specific requirements rather than treating WMS and TMS as generic horizontal technologies.

What good looks like

Organisations that consistently deliver successful WMS and TMS implementations share several characteristics.

They invest in upfront requirements definition — spending eight to twelve weeks documenting operational requirements, integration needs, and future-state process designs before engaging with vendors. This investment feels slow at the start but dramatically reduces rework, scope creep, and misalignment later.

They run structured selection processes — evaluating a shortlist of vendors against weighted criteria, using scripted demonstrations based on their specific operational scenarios rather than the vendor's standard demo script, and checking references with comparable Australian operations. They include operational stakeholders in the evaluation, not just IT and procurement.

They treat implementation as an organisational change programme, not a technology installation. They appoint a business-side project lead with the authority and capacity to make decisions, assign experienced operators to the project team, and invest in change management from day one rather than bolting it on as an afterthought.

They plan realistic timelines and budgets — acknowledging that a typical WMS implementation for a mid-complexity operation takes six to twelve months, and a TMS implementation of similar complexity takes four to nine months, and that these timelines include process design, data preparation, integration development, testing, training, and post-go-live stabilisation. They budget for the full programme cost, not just the software licence and implementation services.

They stage their go-live — starting with core functionality, building confidence and competence, and then progressively activating more advanced features like labour management, slotting optimisation, or advanced transport planning. Trying to implement every feature simultaneously is how projects collapse under their own weight.

They also protect institutional knowledge during the transition. The experienced warehouse supervisor who knows every quirk of the operation is not an obstacle to the new system — they're the person who can tell you whether the configured processes will actually work on a Monday morning in peak season. Smart implementation teams capture that knowledge and build it into the system design.

And they define success in business terms — not "the system went live" but "pick productivity improved by X%, inventory accuracy reached Y%, transport cost per unit decreased by Z%." They track these metrics through go-live and hold the programme accountable for delivering the business case.

How Trace can help

At Trace Consultants, we help Australian organisations select and implement WMS and TMS platforms that actually deliver their business case. Our interest is in helping you choose the right system for your operation and getting the implementation right first time.

Our work in this space covers the full lifecycle. We start with operational assessment and requirements definition — working with your warehouse and transport teams to document how the operation runs today, where the pain points and opportunities are, and what the target-state operation needs to look like. This produces the functional and technical requirements specification that drives a rigorous selection process.

We then manage structured vendor evaluation — developing evaluation criteria, scripting vendor demonstrations around your operational scenarios, facilitating site reference visits, and conducting commercial analysis that goes beyond licence fees to evaluate total cost of ownership including implementation, integration, training, and ongoing support.

During implementation, we provide programme management, process design, and change management support — ensuring the project stays on track, the system is configured to support redesigned processes rather than replicate existing ones, and the organisation is ready to adopt the new way of working at go-live. We work alongside your team and the vendor's implementation consultants, providing the independent perspective that keeps the project focused on business outcomes.

We work across planning and operations, warehousing and distribution, procurement, and strategy and network design — which means we understand how WMS and TMS fit within the broader supply chain operating model, not just as standalone technology deployments.

We've supported WMS and TMS selections and implementations across FMCG and manufacturing, retail, resources and energy, health, and government — sectors where getting the technology right has direct, measurable impact on operational performance and cost.

If you're considering a WMS or TMS investment — or if you're partway through an implementation that isn't going to plan — get in touch. The difference between a technology investment that delivers and one that disappoints is almost always in the approach, not the software. We can help you get the approach right.

Trace Consultants is an Australian supply chain and procurement consulting firm. We help organisations select, implement, and optimise logistics technology — independently, practically, and with a relentless focus on operational outcomes. Visit our insights page for more on the challenges shaping Australian supply chains.

‍