Skip to main content
Question

How does the Lot/Batch selection logic work in the Customer Consignment Stock Consumption window?

  • February 2, 2026
  • 0 replies
  • 10 views

Nikila Dis
Superhero (Employee)
Forum|alt.badge.img+14

 

Hi, I am currently handling an issue related to customer consignment stock, where the consumed quantities for certain parts do not match the invoice. This seems to be related to how IFS APP10 handles consignment stock consumption and invoicing when partial reservations exist across multiple lot/batch numbers. Specifically, when a customer performs consignment stock consumption at the header level.

  • Consignment part: 80890121

  • Customer order created: 41883388

  • Reserved quantities in order:

    • 50 → Lot 3107518---1

    • 1150 → Lot 41826419-1-1-1

  • Consumption scenario:

    • Quantities were consumed from the Customer Consignment Stock Consumption window at header level.

    • Total consumption: 1150

    • The system actually consumed stock from lot 3107522---1.

    • The reserved quantities in order 41883388 were not affected.

My questions

  1. How does the system determine which lot/batch to consume in the Customer Consignment Stock Consumption window?

  2. If the system is using FIFO, how can I confirm it, and how can I influence the lot selection (for example, if I want to consume from reserved lots instead of FIFO-selected lots)?

  3. Can the expiration date of a lot influence lot selection during header-level consumption, and why doesn’t changing the expiration date at the Part Lot Size / Part Level reflect in the consumption window?

Observations from my testing:

  • The system seems to pick available stock based on lot availability and expiration date, ignoring the reserved quantities in the order.

  • To consume stock from a specific lot or a reserved order, it seems that manual lot selection at line level is required.

I would like to better understand the logic behind this behavior and best practices for ensuring consumption follows reserved lots when needed. Any insights, tips, or official documentation references would be highly appreciated!

Regards,

Nikila Dissanayake