AI, in your work.

An earlier pick can block the next one

Microsoft merged a warehouse availability correction into the main BCApps branch on October 23, 2026. BCApps is the Business Central applications repository. The merge is recorded in PR 12842.

According to the recorded commit, a registered but unshipped pick at a basic warehouse location can be missed by the calculation when it uses a non-default shipment bin. Validation incorrectly resets the picked quantity to zero; the reservation calculation can then block another pick with “Nothing to handle”, despite free stock remaining.

What changes in the calculation

The availability code adds a check in `CalcQtyOnShipmentBins` only when the previous result is zero. It finds shipment lines for the same item, location and variant, with a positive picked quantity and a populated, non-default bin. It reuses `CalcQtyOnBin`, preserving item-tracking filters.

The search stops when it finds a nonzero quantity. This check therefore should not be interpreted as an exhaustive total of stock across all alternative bins.

What the added tests cover

The repository tests cover the alternative destination and a default-bin control. They configure a FEFO warehouse with lot tracking: from 100 units, a first pick registers 60 without shipping, leaving 40 free. They then request another pick for 30. Assertions check its lines and that the first shipment retains its picked quantity; the second pick is not registered.

Nexo reviewed the code without running these tests. Their presence does not establish coverage of every combination of reservations, tracking and movements.

A hypothetical example for investigating an incident

This Nexo example uses different quantities from the published tests. It helps organize a check; it describes neither a real case nor an executed test. It assumes the same item, variant and lot, with no other movements.

Nexo's interpretation for consultants and support

The practical value of this change lies in reconstructing what happened between picking and shipping. To investigate a similar case, we suggest gathering the following information before attributing it to this issue:

• Installed version and build, together with the warehouse configuration.
• Default shipment bin and the actual destination of each line.
• Inventory by item, variant and lot or serial number, where applicable.
• Quantities reserved, picked, outstanding on open picks and shipped.
• Document sequence and the exact message when requesting the next pick.

Availability: merged code and an open backport

When checked on November 8, 2026, PR 13213, intended to backport the correction to `releases/29.x`, remains open and is assigned to milestone 29.1. That milestone expresses a work target; it does not establish a delivered update or an activation date.

The consulted sources do not confirm which distributed build includes the correction or whether it is present in a particular environment. Resolving an incident requires checking the installed build and testing the relevant scenario.