Skip to main content
Question

Warehouse Task Default Priority - Can it pull from the Customer Order/Source

  • November 24, 2025
  • 1 reply
  • 32 views

Forum|alt.badge.img+7

Within Warehouse Tasks and Task Priorities, Help suggests twice that Warehouse Task Priority can come from the Task Source (assume the Customer Order) before the Default Priority from the Task Type is fetched. 

 

“The priority of the warehouse task can be received from the different sources of warehouse tasks at the time of creation, dependent on such the varying importance of different customer order lines. It can also be set from the default priority value entered for every different type of task in the warehouse task type setup. Priority is an important component of all the business logic created around the information of the warehouse task, including needs for sorting rows according to priority order.”

 

And;

 

Priority - The priority is a numerical value valid from 1 to 99999 where value 1 means the highest priority. The attribute is mandatory; a valid priority number must be entered for each task type. It should, however, be possible to enter the same priority value for all task types if so desired. The attribute value is designed to be used as a default for priority on the warehouse tasks if priority is not sent from the task source.

 

I cannot get Customer Order Priority influencing the Default Priority of the Warehouse Task generated at all. It always takes the Default Priority from the Warehouse Task Type, irrespective of CO priority being manually set or determined from the Customer or a Priority Rule.

 

Help seems a little misleading to suggest this can come from the “source priority”. We have a customer who wants to allocate tasks based on priority but I can’t get this triggering at all. Can anyone assist please? ​@Fgray09 

1 reply

Forum|alt.badge.img+7
  • Do Gooder (Partner)
  • December 30, 2025

In current IFS, there is nothing “wrong” to fix; CO priority is simply not passed to the warehouse task, so the only way to change behaviour is process plus configuration (and optionally customization).​

1. Stabilize current behaviour

  1. Open Warehouse Task Type setup

    • Page: Warehouse Task Type / Warehouse Task Setup.​

  2. For each task type used for CO picking:

    • Set Default Priority to reflect your intended base priority (e.g., 100 for normal picks, 10 for rush tasks).​

  3. Communicate to users that warehouse tasks will use this default, not CO priority.

2. Operational workaround for urgent COs

  1. When an urgent customer order is released:

    • Identify its related Warehouse Tasks (via Warehouse Task page, filter on Source = Customer Order and CO No).​

  2. On those tasks:

    • Manually set Operative Priority (or Priority if allowed) to a higher value (e.g., 1–5).

  3. Ensure your task picking lists / handhelds sort by Operative Priority first.

3. Request product enhancement / correction

  1. Log a ticket with IFS Support (or via your partner) including:

    • The help text excerpts stating that priority can be received from the task source.

    • The community thread “Warehouse Task Default Priority – Can it pull from the Customer Order/Source”.​

  2. Ask for one of:

    • A product change to let Customer Order Priority be used as warehouse task priority when configured, or

    • A correction of the help text if that is not intended.

4. Optional: implement customization

If you need automatic alignment now:

  1. Design a small event action or projection customization:

    • Trigger: On Warehouse Task create.

    • Read the source CO line priority.

    • Write that value into Warehouse Task. Priority or Operative Priority.

  2. Test on a non‑prod environment to ensure no performance or logic side effects.

These steps do not “switch on” a hidden setting; they give you a controlled way to work with current standard and, if needed, extend it so warehouse task priority finally reflects CO urgency.