Roadmap

Bekijk waar we aan werken en wat er komt.

Roadmap

Bekijk waar we aan werken en wat er komt.

Roadmap

Bekijk waar we aan werken en wat er komt.

Backlog189

Tote picking volumetrics and box selection

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.

Tote pick allocation order investigation

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.

Dedicated returns portal to scan returned orders

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.

Single dispatch task for a mixed pallet - HHD

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.

Stock count back after pick

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.

Over pick for product type KG

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.

Stock take on RF

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.

Stock unit types on conditions

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.

File queuing - enforce processing order

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.

Import tool - allow variables to store values

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.

Being Reviewed67

Remove a single pick task from a consolidated pick when a shipment cannot be completed

Feature Overview Provide a supported way in Clarus WMS to remove a single order's pick task from a consolidated (batch) pick when that order's shipment cannot be completed, while leaving every other order in the batch picked, packed and shipped as normal. Consolidated picks combine many single-line sales orders drawn from a shared bulk location, and today the system blocks removing any individual order once the batch has been picked as a single shared task. Use Cases Pulling one failed order out of a batch to cancel, re-ship or re-pick it without reversing the whole batch. Freeing picked stock that is currently stranded and cannot be released, re-sold or re-dispatched. Avoiding the mismatched quantities and corrupted stock or task state caused by manual force-unallocation workarounds. Goal Allow a single order and its pick task to be cleanly removed from a consolidated pick when its shipment fails, leaving the rest of the batch unaffected and enabling recovery of the affected order.

Include product country of manufacture in carrier API data for international shipments

Feature Overview Include each product's country of origin in the carrier API packet data sent for international shipments in Clarus WMS. International shipping requests currently fail when any item is missing its country of origin, halting the shipment at the packing station. Sending this data ensures cross-border shipments clear customs and are not blocked. Use Cases Successfully transmitting country of origin for every item so international orders clear customs smoothly. Preventing shipments from halting at the packing station due to missing country of origin data. Quickly identifying which product is missing customs data when a shipment fails. Goal Ensure product country of origin is included in the carrier API data for international shipments so orders clear customs without being blocked. Acceptance Criteria System event logs must clearly capture and state the missing country of origin error on shipment failure so the problem product can be identified. Existing manual re-trigger capability must be retained so staff can resubmit the carrier API request once the missing data is corrected.

Custom currency codes on invoices

Feature Overview Allow a custom currency representation to be configured for invoicing in Clarus WMS, so that invoices display the appropriate ISO currency code rather than a localised currency symbol. This ensures invoices show the correct, widely recognised currency notation. Use Cases Displaying a standard currency code on invoices where a localised symbol is only used informally and not appropriate for formal documents. Supporting customers who invoice in regional currencies that require code-based notation. Goal Enable customers to invoice with the correct currency code displayed on their invoices.

Show stock configuration and configuration quantity on receipts and picklists

Feature Overview Retain and display the stock configuration and configuration quantity fields throughout the receipt and sales order lifecycle in Clarus WMS. Currently these fields are only available while a receipt or sales order is in a New, Draft or Pending state, and disappear once the receipt is received or the order is processed onto a picklist. They should remain visible on received receipt lines and on picklist lines during picking and dispatching, as they already are on the stock list. Use Cases Maintaining full oversight of quantity levels for customers working across units and cases. Avoiding manual searches to confirm correct quantities and configuration after processing. Enabling quicker troubleshooting by keeping configuration data visible in one place. Goal Ensure stock configuration and configuration quantity remain visible on received receipt lines and on picklist lines during picking and dispatch, consistent with the stock list.

Granular HHD access control by user role

Feature Overview Introduce more granular control over the visibility of handheld device (HHD) scanner menu items based on user role in Clarus WMS. The current approach supports only a limited number of implementation levels, whereas larger organisations have multiple warehouse roles, each needing access only to the scanner functionality relevant to their responsibilities. Use Cases Restricting operators to only the scanner functions required for their daily tasks, such as putaway and full pallet picking for a junior role. Giving supervisors and administrators broader operational and administrative access. Limiting sensitive actions such as stock adjustments to authorised users, reducing the risk of accidental inventory changes that could affect integrated ERP or WMS systems. Supporting internal audit and compliance requirements. Goal Allow HHD scanner menu item visibility to be controlled per user role so each role only sees the functionality it needs.

Batch control: prevent allocation of batched stock to non-batched order lines

Feature Overview Introduce a hard control in Clarus WMS that prevents stock carrying a batch reference from being allocated to a sales order line that does not explicitly require that batch. Batch identifiers are used as a ringfencing mechanism to reserve specific stock for particular projects or clients, and the system should strictly distinguish reserved (batched) stock from general (null-batch) stock during allocation, while still respecting FIFO rules. Use Cases Protecting high-value or project-specific inventory from being consumed by general sales orders. Ensuring reserved stock is only accessible to orders that specifically request its batch. Avoiding fulfilment delays caused by reserved stock being allocated to the wrong order. Goal Prevent batched stock from being allocated to order lines that do not request a batch, ensuring reserved inventory is only used by orders that explicitly ask for it. Acceptance Criteria The system must hard-stop allocation of a batched stock record to a non-batched order line. Events should be logged where an order remains unallocated because suitable non-batched stock is unavailable.

Dispatch strategy to auto-complete dispatch task on shipment close

Feature Overview Introduce a new dispatch strategy in Clarus WMS that automatically completes the dispatch task when a shipment is closed, removing the need for staff to manually click a complete-all-dispatch-tasks button after packing and labelling. The option would be selectable as a dispatch strategy on the sales order. Use Cases Reducing double-handling of clicks for warehouse teams processing high order volumes. Streamlining the transition from packing to shipping to increase throughput. Applying consistent auto-completion behaviour across both handheld device and front-end packing desk flows. Goal Provide an auto-complete dispatch strategy so dispatch tasks finalise automatically on shipment close across both HHD and front-end packing workflows. Acceptance Criteria A new auto-complete dispatch strategy option can be selected on the sales order. The automation applies to both the handheld device and front-end packing desk flows. The auto-dispatch behaviour functions identically to the existing manual dispatch completion.

Support customer-supplied carrier labels via CSV and XML order files

Feature Overview Allow Clarus WMS to retrieve and use pre-configured carrier labels supplied by a customer within their sales order files. Each order file includes a unique URL that hosts the required carrier label in both CSV and XML formats. The system would store that URL against the order and provide a way to call it, download the label, and print it as part of the sales order flow, including from the handheld device. Use Cases Automatically retrieving and printing customer-mandated carrier labels for high order volumes, where manual retrieval is impractical. Storing the label link on the order so it can be reprinted via a shortcut action. Aligning with the existing pattern used for loading carrier labels from an integrated label provider. Goal Enable Clarus WMS to store the supplied carrier label URL against an order and print the label as part of the sales order and dispatch flow.

Print custom carrier labels in drop sequence order

Feature Overview Allow custom carrier labels in Clarus WMS to print in the drop sequence order defined on the consolidated picklist from which the shipments were created. Where picks are consolidated and each carries a drop number reflecting loading order on the vehicle, the labels should print in that same order. Use Cases Labelling goods in physical drop order without pre-sorting labels first. Saving time for pickers who currently must sort a batch of labels before applying them. Goal Print custom carrier labels in the drop sequence order set on the picklist so labels match the physical loading order.

Show product images on front end and HHD

Feature Overview Allow product images to be stored against products in Clarus WMS and displayed during handheld device (HHD) workflows. During picking, an image of the product to be picked would be shown, and during receipt the image could be used to confirm the correct product has been received. A further enhancement would allow each stock level type (unit, case, inner, outer) to hold its own image that can be pulled into the relevant HHD workflow by configuration. Use Cases Helping HHD users visually confirm the product they need to pick. Checking received goods against a product image during the receipt process. Displaying the correct image per stock level type in receipt or pick workflows. Goal Enable product images to be stored on the front end and shown within HHD picking and receipt workflows.

Active Development10

Update pre-receipt lines on HHD with previously unknown attributes

Feature Overview Customers need to receive stock against pre-receipt lines even when some attributes, such as batch or lot numbers, are not known in advance. Currently any discrepancy on the HHD forces a new receipt line to be created, leaving the original pre-entered line permanently pending and cluttering the system. This is common where large orders are split across several deliveries over weeks and suppliers only confirm batch details when goods arrive. Use Cases Update pre-receipt lines on the HHD with previously unknown attributes at the point of receipt rather than creating new lines. Configure, during discovery, customer-specific validation rules such as preventing products not on the pre-receipt from being added. Goal Allow pre-receipt lines to be updated on the HHD with newly known attributes, reducing manual cleanup and keeping goods-in data aligned with external ERP interfaces.

Synchronise weight and volume on stock creation using specific gravity

Feature Overview When stock is created during goods-in and a weight or volume is entered that differs from the product master value, the other measure is not recalculated; the system keeps the master data value instead. For products such as liquids this causes discrepancies, because the specific gravity factor is not applied to convert between weight and volume. Use Cases When a weight is entered on stock creation, recalculate the volume using the product's specific gravity (and vice versa) so both values stay consistent. Goal Automatically synchronise weight and volume on stock creation using the specific gravity conversion, so stock records reflect the actual quantity received.

Reset transactions filtered by account

Feature Overview Transactions can currently only be reset for a whole domain. When a customer onboards new accounts, this forces them either to run a separate mirror domain or to keep test data in their live system. An account-level filter on the transaction reset would let them clear transactions for a single account only. Use Cases Reset transactions for one specific account while leaving all other accounts untouched, enabling end-to-end testing on a live domain. Goal Add an account filter to the transactions reset so transactions can be cleared for an individual account rather than the entire domain.

Make all product detail fields available on reports and documents

Feature Overview Customers need all product detail fields, including unit and inner fields and attributes such as ABV, to be usable on reports, documents and labels. Some product data cannot currently be referenced, which prevents building the reports and notes customers require. Use Cases Use unit, inner and additional product fields (such as ABV) on custom reports, putaway notes and dispatch notes. Goal Make all product detail fields available for use on reports, documents and labels.

Add Task Targets to pick-and-drop location type workflows

Feature Overview Several customers want to use pick-and-drop (P&D) location types in workflows so that different truck types, for example powered pallet trucks and VNA trucks, can each complete their leg of a picking process. Task Targets are not currently available on pick-and-drop location types, which prevents these multi-stage workflows from completing. Use Cases Run an end-to-end picking process where one truck type completes the first leg and another completes the final leg, using pick-and-drop locations. Goal Enable Task Targets on pick-and-drop location types so customers can complete end-to-end picking across different truck types.

Stepped pricing for charges

Feature Overview Warehouses commonly use a cascading pick charge model where the price per item falls as the number of items picked per order rises, reflecting the lower labour cost of picking additional items from the same location. Clarus WMS charge cards do not currently support this stepped pricing. Use Cases Set banded pick charges on a charge card, for example charging a higher rate for the first few items and progressively lower rates for later quantity bands. Goal Allow users to configure stepped or cascaded pick charges on a charge card by defining quantity bands and a rate for each, applied against the total quantity on a pick list.

Update carrier in the packing desk

Feature Overview Customers need to be able to change or update the carrier from within the packing desk. This lets packing staff correct or set the carrier at the point of packing without leaving the packing workflow. Use Cases Update the assigned carrier for an order directly from the packing desk. Goal Allow the carrier to be updated within the packing desk.

Receipt import via CSV

Feature Overview Customers want to import receipts into Clarus WMS from a CSV file. This allows inbound receipt data to be loaded in bulk rather than entered manually. Use Cases Import receipt details from a CSV file to create receipts in bulk. Goal Provide a CSV import for creating receipts.

Make phone number optional for Transmission shipments

Feature Overview Shipments sent via Transmission do not require a phone number, yet Clarus WMS currently makes the phone number mandatory. This forces users either to obtain a number they do not need or to enter a placeholder in order to ship. Use Cases Create and ship a Transmission shipment without being forced to supply a phone number. Goal Make the phone number field optional for Transmission shipments.

Estimated pallet quantity on HHD for receipts and picks

Feature Overview Customers want the handheld device to show operatives how many pallets are expected to be used, both at the start of a pick and during receiving. Today this information is worked out by supervisors, so operatives lack visibility at the point of work. Use Cases At the start of a pick, show the operative the estimated number of pallets expected for the order, able to be split by group where groups are used. During receipt by product, show how many cases or units make up a full pallet, and display the remaining balance per receipt line once a receive task is done. Optionally display fields such as units expected, cases expected, cases per pallet and cases per layer in the receipt table. Goal Introduce an HHD capability that shows expected pallet usage for picks and receipts so operatives can plan without relying on supervisors.

Released0

Backlog189

Tote picking volumetrics and box selection

Tote pick allocation order investigation

Dedicated returns portal to scan returned orders

Single dispatch task for a mixed pallet - HHD

Stock count back after pick

Over pick for product type KG

Stock take on RF

Stock unit types on conditions

File queuing - enforce processing order

Import tool - allow variables to store values

Being Reviewed67

Remove a single pick task from a consolidated pick when a shipment cannot be completed

Include product country of manufacture in carrier API data for international shipments

Custom currency codes on invoices

Show stock configuration and configuration quantity on receipts and picklists

Granular HHD access control by user role

Batch control: prevent allocation of batched stock to non-batched order lines

Dispatch strategy to auto-complete dispatch task on shipment close

Support customer-supplied carrier labels via CSV and XML order files

Print custom carrier labels in drop sequence order

Show product images on front end and HHD

Active Development10

Update pre-receipt lines on HHD with previously unknown attributes

Synchronise weight and volume on stock creation using specific gravity

Reset transactions filtered by account

Make all product detail fields available on reports and documents

Add Task Targets to pick-and-drop location type workflows

Stepped pricing for charges

Update carrier in the packing desk

Receipt import via CSV

Make phone number optional for Transmission shipments

Estimated pallet quantity on HHD for receipts and picks

Released0