Feature Overview Customers want to automate their tote picking process using volumetrics and system-driven storage unit and box selection. With a trolley that can carry multiple outbound boxes in a range of sizes simultaneously, volumetrics would be introduced at the point of order creation so the system allocates the most efficient packing method using the fewest boxes. This packing information would then be provided to the picker on the RF unit at the start of the tote pick. Use Cases At order creation, the system calculates volumetrics and selects the most effective packing method using the least number of boxes. A picker is presented with system-selected box sizes and packing information on the RF unit at the start of the tote pick. Multiple outbound boxes of varying sizes are handled simultaneously on a single trolley. Goal Introduce volumetrics and system-driven box selection into the tote picking process to optimise packing and guide pickers on the RF unit.
Feature Overview When multiple sales orders are processed to tote picks and empty totes are added to a tote pick wave on the handheld, the pick list IDs appear to be allocated to the totes in a random order rather than chronologically by creation. This investigation covers why pick lists are not allocated to totes in chronological order and how to make the allocation predictable. Use Cases A user adds totes to a tote pick wave and expects pick list IDs to be allocated to totes in chronological order (for example, the first pick list to the first tote). Both the standard start-new-tote-pick option and the start-by-account option behave consistently in allocation order. Goal Investigate and correct tote pick allocation so pick list IDs are allocated to totes in chronological order rather than at random.
Feature Overview This request is for a dedicated returns portal in Clarus WMS where users can scan orders that have been returned. Within the portal, users should be able to grade the stock that comes back and decide what to do with it. This provides a structured process for handling and dispositioning returned goods. Use Cases Scanning returned orders into a dedicated returns portal. Grading returned stock and deciding on its disposition. Goal Provide a dedicated returns portal that lets users scan returned orders, grade the returned stock and decide how to process it.
Feature Overview This request is to allow a single dispatch task to be used for a mixed pallet on the HHD in Clarus WMS. Rather than handling each item or product separately, operatives could dispatch a mixed pallet as one task, streamlining the dispatch process. Use Cases Dispatching a pallet containing mixed products as a single task on the HHD. Reducing the number of separate dispatch actions required for mixed pallets. Goal Enable a single dispatch task for mixed pallets on the HHD to simplify and speed up dispatch.
Feature Overview This request is to enable a stock count back after a pick in Clarus WMS, prompting the operative to confirm the remaining quantity at the location once a pick is completed. This helps validate stock accuracy at the point of picking. Use Cases Counting the remaining stock at a location immediately after completing a pick. Improving stock accuracy by validating quantities during the picking process. Goal Provide a stock count back step after picking so remaining quantities can be confirmed and stock accuracy maintained.
Feature Overview This request allows over picking for products measured by weight (product type KG) in Clarus WMS. This supports scenarios where the picked weight may legitimately exceed the requested quantity, such as catch weight items. Use Cases Picking a weight-based product where the actual picked weight exceeds the requested amount. Handling catch weight items that cannot be picked to an exact requested quantity. Goal Allow over picking for KG product types so weight-based items can be picked when the actual weight exceeds the requested quantity.
Feature Overview This request is to enable stock take functionality on RF devices in Clarus WMS, allowing operatives to carry out stock counts directly from the handheld. This supports accurate, real-time stock counting on the warehouse floor. Use Cases Performing a stock take from an RF device rather than a desktop. Counting stock in real time at the location on the warehouse floor. Goal Provide stock take capability on RF so operatives can perform stock counts directly from the handheld.
Feature Overview This request allows conditions on screens or components in Clarus WMS to be based on stock unit types (for example KG or Box). This enables specific behaviour to be applied only to certain stock unit types rather than all products, supporting scenarios such as catch weight picking and handling decimal or sub-unit quantities. Use Cases Adding a condition to an RF screen or component based on a custom stock unit type. Enabling catch weight picking and decimal or sub-KG quantities for specific stock only. Goal Allow users to add conditions based on stock unit type so that functionality can be targeted to specific stock rather than applied to all products. Acceptance Criteria Given a functioning screen on RF, the user is able to add a condition for a custom stock unit type.
Feature Overview This request is for Clarus WMS to support file queuing so that inbound files are processed in a defined, controlled order rather than concurrently or arbitrarily. This ensures dependent files are processed only after their prerequisite files have completed. Use Cases Ensuring one file is fully processed before a dependent file is processed. Controlling the sequence of file imports where processing order matters. Goal Allow files to be queued and processed in a specified order so that dependencies between files are respected.
Feature Overview This request enhances the Clarus WMS import tool to allow variables to store values during an import. Stored values can then be reused within the import, enabling more flexible and powerful data mapping and transformation. Use Cases Storing a value during an import and reusing it in later steps of the same import. Building more flexible import mappings that reference previously captured values. Goal Allow the import tool to define variables that store values for reuse within an import.