Skip to main content
Question

Problem with reservation (Customer Order)

  • November 21, 2025
  • 2 replies
  • 28 views
B
Do Gooder (Customer)
Forum|alt.badge.img+1

Hello,
I’m experiencing an issue with reservations in the Customer Order module. A few months ago we introduced new processes in the WADACO module, and since then I’ve noticed some irregular behavior related to reservations.

Our workflow is as follows: we create a customer order, and once the pick list is generated, a shipment is automatically created and linked to it. The problem is that the reserved quantities sometimes change unexpectedly.

For example, we sell 100 units of a product, but in the reservation view we can see a higher reserved quantity — it suddenly increases to a larger value, e.g., 120 units, without any clear reason.

Has anyone encountered a similar issue or knows what might be causing this?

Thanks

2 replies

T
Do Gooder (Partner)
Forum|alt.badge.img+4
  • TntKirtaS
  • Do Gooder (Partner)
  • November 24, 2025

Hello,

There could be multiple reasons causing this issue. Maybe you could check this: 
The reservation process uses automatic reservation logic, which includes rules like FIFO, zone ranking, and handling units. This logic might be affecting the reserved quantities if not configured correctly.
And also The system automatically reserves stored sales parts for customer orders and shipments with planned ship dates. If the "Reserve all the lines in CO" option is enabled, it might reserve additional lines based on the parameters set, which could lead to unexpected increases in reserved quantities.
You might want to review the configuration of your reservation logic and ensure that all relevant patches are applied.
 

I recommend try running a sample test:

  1. Create a simple CO line for a test item.

  2. Generate the pick list manually (not via automation).

  3. Do NOT open any WADACO flow.

  4. Observe if reservation stays stable.

  5. Then repeat the test but perform your new WADACO workflow.

  6. Compare Inventory Transactions log after each step.

This will immediately show whether WADACO is the trigger. Also keep checking logs for all the processes for both manual and automatic to check the timestamps for the reservations that take place.
Hope this helps!
 

Regards,
Kirtan Shah

P
B
Do Gooder (Customer)
Forum|alt.badge.img+1
  • Bartosz Affelski
  • Author
  • Do Gooder (Customer)
  • November 25, 2025

Hello,

There could be multiple reasons causing this issue. Maybe you could check this: 
The reservation process uses automatic reservation logic, which includes rules like FIFO, zone ranking, and handling units. This logic might be affecting the reserved quantities if not configured correctly.
And also The system automatically reserves stored sales parts for customer orders and shipments with planned ship dates. If the "Reserve all the lines in CO" option is enabled, it might reserve additional lines based on the parameters set, which could lead to unexpected increases in reserved quantities.
You might want to review the configuration of your reservation logic and ensure that all relevant patches are applied.
 

I recommend try running a sample test:

  1. Create a simple CO line for a test item.

  2. Generate the pick list manually (not via automation).

  3. Do NOT open any WADACO flow.

  4. Observe if reservation stays stable.

  5. Then repeat the test but perform your new WADACO workflow.

  6. Compare Inventory Transactions log after each step.

This will immediately show whether WADACO is the trigger. Also keep checking logs for all the processes for both manual and automatic to check the timestamps for the reservations that take place.
Hope this helps!
 

Regards,
Kirtan Shah



Thanks for the tip. I've already run these tests, and each time, all the logs looked fine. My problem happens randomly every now and then, and I can't simulate this error properly. I also have a situation where the reservation is larger than the available stock.

Thanks and regards,

Bartosz

Terms & ConditionsCookie settingsAccessibility statement