Clarus WMS implementations are typically led by a dedicated project manager from the vendor or a certified partner, working closely with the client's operations and IT teams. The process heavily involves meticulous discovery of existing physical warehouse workflows, which is then translated into the system's deep configuration. Common breaks occur when the client's internal team lacks the authority to make decisions on process changes, leading to endless re-scoping and delays.

A significant portion of the budget goes into mapping granular bin locations, put-away strategies, and pick-pack-ship workflows. Errors here lead to incorrect task assignments on the floor, requiring manual intervention. The 'go-live' period is often stressful, with an inevitable dip in productivity as staff adapt to the rigid, system-directed tasks. Training on RF scanners is critical but often rushed.

Post-implementation, the biggest cost is often maintaining the rigid configuration. If the business changes its operating model, such as adding a new sales channel or product line, re-configuring Clarus is not a self-service task. It requires engaging professional services, and failing to budget for these changes leads to operators creating 'shadow' manual processes outside the system, defeating the purpose of the WMS.

Deposco implementations are typically run by an implementation partner, often with strong NetSuite experience, collaborating closely with the client's operations team and a nominated internal super-user. Time is heavily invested in designing intelligent workflows within the rules engine, which dictates how stock moves and is picked. What breaks usually arises from unclear ownership of commercial logic—e.g., who determines the priority of B2C vs. B2B orders.

A substantial part of the effort goes into configuring the powerful rules engine to reflect specific business logic for picking, packing, and returns. This requires skilled workflow designers. Where time and money are often lost is in iterating and testing these complex rules; without clear and consistent business requirements, rules become contradictory and lead to operational bottlenecks. Hardware upgrades for Android scanners and robust Wi-Fi are non-negotiable.

After go-live, the focus shifts to governing the rules engine. Operations teams often attempt to solve every new problem by adding another rule, leading to 'rules bloat' where the system becomes difficult to manage. Unmanaged complexity results in orders getting stuck, unexplained system behaviour, and an increasing reliance on the implementation partner for debugging changes that should be managed internally.