Why can’t I pick that ****** stock when it’s showing in Bin Contents? - Business Central – explained without screaming (much).

This is giving me a headache!

If you’ve spent any time on the warehouse floor or picking lists in Dynamics 365 Business Central, you’ve almost certainly had this moment:

“The stock is right there. It’s showing in Bin Contents. So why can’t I pick the damn thing?”

This is one of the most common — and most frustrating — questions I get from users, warehouse managers, and consultants alike. And the answer is rarely “Business Central is broken” (even though it often feels like it).

Let’s break down why stock can be visible but not pickable, and what Business Central is actually trying (sometimes badly) to tell you.

1. Bin Contents shows what exists, not what you’re allowed to pick

First, an important mindset shift:

Bin Contents ≠ Available to Pick

Bin Contents is essentially an inventory ledger:

• Quantity

• Location

• Bin

• Variant

• Unit of Measure

It doesn’t care why the stock is there — only that it exists.

Picking logic, however, adds rules on top:

• Is it free?

• Is it reserved?

• Is it blocked?

• Is it in the correct bin type?

• Does it meet FEFO / expiration / lot rules?

• Is it allocated to something else?

So yes — the stock is physically there. No — that doesn’t mean you’re allowed to touch it.

2. Reservations: the silent stock thief

This is the number one cause.

Your stock:

• Appears in Bin Contents ✔

• Refuses to appear on a pick ❌

Chances are it’s reserved.

Reservations can come from:

• Sales orders

• Production orders

• Transfer orders

• Jobs / Projects

• Even other picks

Business Central will happily show:

“You have 10 in the bin”

While quietly muttering:

“…but 9.5 of those are already promised to someone more important.”

💡 Check:

• Item Ledger Entries → Reserved Quantity

• Reservation Entries

• Sales Lines with reservation = Always

3. Bin Type: Yes, this really matters

Another classic.

If the stock is in a bin that is:

• ❌ Not marked as Pick

• ❌ Marked as Receive only

• ❌ Marked as Put-away only

Then it doesn’t matter how much is in there — picking logic will ignore it.

Common offender:

• Stock left in RECEIVE bins after put-away

• Overflow bins that weren’t configured properly

• “Temporary” bins that became permanent by accident

💡 Check:

• Location → Bins → Bin Type Code

• Does the bin allow Pick = Yes?

4. Lot, serial, or FEFO rules blocking you

If you’re using:

• Lot tracking

• Serial numbers

• Expiration dates

• FEFO picking

Business Central gets fussy — and deliberately so.

You may see stock in the bin, but:

• The lot isn’t selected on the source document

• The lot doesn’t meet FEFO

• The lot is expired

• The serial number is already assigned elsewhere

And Business Central’s response?

“I’ll just not show it on the pick. Good luck.”

💡 Check:

• Item Tracking Lines

• Lot Expiration Dates

• Warehouse Setup → FEFO enabled?

• Source document has tracking assigned?

5. Unit of Measure mismatches (a sneaky one)

This one catches experienced consultants out.

Example:

• Bin contains 10 PCS

• Sales order wants 1 BOX

• 1 BOX = 12 PCS

Bin Contents says:

“10 available”

Picking logic says:

“That’s not enough to satisfy a full BOX — nope.”

💡 Check:

• Item Unit of Measure setup

• Quantity per UoM

• Warehouse picks don’t split UoMs nicely unless configured to

6. Warehouse picks follow the source document, not the bin

This is subtle but important.

Warehouse picks do not ask:

“What’s in the bin?”

They ask:

“What does the source document allow me to consume?”

If the:

• Sales line is blocked

• Quantity is already shipped

• Quantity is already picked

• Document status is wrong

Then the bin contents are irrelevant.

💡 Check:

• Sales / Production / Transfer document status

• Qty. to Pick

• Qty. Picked vs Qty. Outstanding

7. Negative picks and “helpful” configuration

Some locations allow:

• Negative picks

• Some don’t

If negative picks are not allowed, Business Central will simply:

• Hide bins that don’t perfectly match demand

• Refuse partial quantities

• Ignore bins it deems “unsafe”

This often looks like:

“The stock is there but BC refuses to acknowledge it”

💡 Check:

• Location Setup → Allow Negative Inventory

• Warehouse Setup → Policies

8. The uncomfortable truth: Business Central is being cautious, not stupid

Most of the time, when you can’t pick stock that you can see, it’s because:

• Business Central is protecting another document

• Or enforcing a warehouse rule

• Or preventing you from creating a bigger mess downstream

Unfortunately, it’s terrible at explaining itself.

There’s no helpful message like:

“This stock is reserved to Sales Order SO-10342”

Instead, you get:

Nothing appears on the pick Queue warehouse frustration

Quick diagnostic checklist

When this happens, run through this list:

✅ Is the stock reserved elsewhere?

✅ Is the bin type pickable?

✅ Is the stock tracked (lot/serial) correctly?

✅ Does the source document still need picking?

✅ Are UoMs compatible?

✅ Is FEFO or expiration blocking it?

✅ Is it already picked on another document?

Nine times out of ten, the answer is in there.

Special Mention to this one!

Another very sneaky one: the ghost of a deleted put‑away 👻

This one is horrible because everything looks right… until it isn’t.

Scenario:

• Goods are received into the location

• A Put-away is created ✅

• Someone deletes the put-away ❌

• The stock is then moved using a Warehouse Movement

• Time passes… life happens…

Now here’s the killer:

If the available quantity drops below the original put-away quantity, Business Central will refuse to let you pick the stock — even though it still shows in Bin Contents.

Why?

Because as far as Business Central is concerned:

• The receipt is still expecting to be put away

• The put-away demand still exists internally

• The numbers no longer reconcile cleanly

So picking logic quietly says:

“Nope. I don’t trust this stock.”

And you get:

• Stock visible in Bin Contents ✅

• Stock not available for picking ❌

• No helpful error message ❌❌

How to spot it

Go to Bin Contents and:

• Look closely for quantities tied back to warehouse receipts

• You’ll often see an amount that shouldn’t still be there

• The bin may look fine, but BC still thinks something is mid‑process

This is especially common in locations that:

• Receive goods and temporarily park them

• Allow warehouse movements instead of completing put‑aways properly

• Have busy warehouses with “we’ll tidy it up later” workflows

The fix (yes, really)

Unfortunately, the fix is a bit “do it properly this time”:

1. Find the original receipt-related quantity in Bin Contents

2. Recreate the Put-away for that receipt

3. Move the stock back to where Business Central expects it

4. Post the put-away properly

Once the put-away is completed and the phantom demand is cleared:

• Picking works again

• Available quantity behaves as expected

• Warehouse sanity is (temporarily) restored

Moral of the story

Deleting a put-away doesn’t always mean:

“Business Central has forgotten about it”

Sometimes it means:

“Business Central will remember this forever and punish you later”

This is why put-away processes matter, even when stock has already “physically moved”.

If your warehouse uses movements as shortcuts, this issue will crop up again — quietly, mysteriously, and usually at the worst possible time.

Final thought

If your users are saying:

“Business Central says the stock is there but won’t let us pick it”

They’re not wrong — they’re just seeing inventory reality, not warehouse logic.

And once you understand that difference, this problem stops being mysterious…and starts being merely annoying.