Inventory Pick vs. Warehouse Pick, Explained

Two Business Central documents are both, quite reasonably, called “a pick.” They look similar enough on screen that it’s easy to assume they behave the same way underneath. They don’t — and the exact moment they diverge is the moment either one finishes, which is precisely the moment that matters for knowing whether an order actually shipped.

Which one exists depends on two toggles, not one

Both documents pull stock from storage to fulfill an outbound order — a sales order, a purchase return, an outbound transfer. Which one a location actually uses comes down to the same Require Pick / Require Shipment pair of location toggles introduced in warehouse shipments vs. sales shipments, explained:

• Require Pick on, Require Shipment off → the location uses an inventory pick.
• Require Pick on, Require Shipment on → the location uses a warehouse pick, working alongside a separate warehouse shipment document.

That’s the whole rule. A location can’t have both documents in play for the same order at the same time — the Require Shipment toggle is what decides which of the two a Require-Pick location actually gets.

Inventory pick: one document, and posting it finishes the order

An inventory pick exists for a location that needs a formal picking step but doesn’t consolidate shipping across multiple orders. It can be created three ways: directly from the source document (the Create Inventory Put-away/Pick action, with the Create Invt. Pick checkbox selected); in bulk, for many source documents at once, via a batch job filtered by document type or number range; or in two steps, where releasing the source order first signals the warehouse that it’s ready, and a warehouse employee later creates the pick from the Inventory Pick page itself.

Recording one is close to what you’d expect: the Bin Code on each pick line is suggested from the item’s default bin, though it can be changed; the quantity actually picked goes in Qty. to Handle; and if the full quantity for a line isn’t sitting in one bin, the Split Line action creates an additional line for whatever remains, so a single pick can legitimately draw from more than one bin without any awkwardness.

Here’s the part that separates it cleanly from its counterpart: choosing Post on an inventory pick does two things in one act — it posts the shipment of the source document lines that were picked, and, if the location uses bins, it creates the warehouse entries reflecting the bin-quantity change. One button, and the order is genuinely shipped when it’s done. There is no separate document waiting to post afterward. For sales lines fulfilled by assembly rather than existing stock, an inventory pick can go further still, posting the assembly output, the component consumption that produced it, and the sales shipment together in that same single post — the identical three-part bundling described for assemble-to-order lines in the warehouse-shipment article, just reached through a different document because this rung doesn’t have a separate warehouse shipment to bundle it into.

Warehouse pick: the same physical work, deliberately split from shipping

A warehouse pick exists at locations advanced enough to also require warehouse shipments — and functionally, it does the identical physical job an inventory pick does: it directs a worker to specific bins for specific quantities. The difference is entirely in what finishing it actually accomplishes. Instead of a Post action that closes out the order, a warehouse pick is registered — and registering it does not post the sales shipment, does not touch the item ledger for the outbound quantity, and does not close anything on the source order. It moves the picked stock to a shipping bin and marks it ready to ship. Nothing more happens until someone posts the separate warehouse shipment document those picks feed into — the mechanism covered in full in warehouse shipments vs. sales shipments, explained.

Warehouse picks can be created the same two ways warehouse shipments generate pick activity in general: push, using Create Pick directly against shipment lines, specifying take and place bins and quantities up front; or pull, through the Pick Worksheet, where Get Warehouse Documents retrieves assigned work, and a fully registered pick automatically clears itself from the worksheet.

Why the split exists at all

It’s worth being explicit about what’s actually being traded here, because “register, don’t post” can look like needless extra process until you see the problem it solves. At a location running one inventory pick per order, there’s no meaningful benefit to separating “picked” from “shipped” — one worker finishes one order’s pick, and shipping it immediately is simply the natural next step, so Business Central lets posting the pick do both. At a location running dozens of orders through a wave with several pickers working simultaneously, forcing every single pick to also post its own shipment the instant it’s done would mean shipping trickles out order by order, mid-wave, exactly when a warehouse manager might actually want every pick for that wave staged and verified together before a single truck gets loaded. Registering, rather than posting, is what lets picking finish asynchronously across many workers while shipping still happens as one deliberate, consolidated event — the same organizational shape that makes consolidated shipping worth the setup cost in the first place (see directed put-away and pick, explained for the broader trade this rung represents).

A worked comparison — the same sales order, two locations

Picture the identical sales order for 20 units of one item, released to two differently configured locations on the same afternoon.

At a location running an inventory pick, one worker opens the Inventory Pick page, sees the suggested bin, handles the full quantity, and chooses Post. That single action posts the shipment and, if the location uses bins, the corresponding warehouse entries. From the customer’s perspective, and from the sales order’s own status, the order is now shipped — full stop, one worker, one document, one action.

At a location running a warehouse pick, the same 20 units might be split across two pickers working the same wave — one covers the first 12 units from a forward pick face, the other covers the remaining 8 from a bulk bin further back. Each registers their portion of the pick as they finish it, independently, on their own schedule. Neither registration ships anything. Only later, once a warehouse manager confirms the wave is fully picked and the truck is actually being loaded, does someone post the warehouse shipment document that both pickers’ registered work feeds into — and that’s the single moment the sales order actually ships. The physical outcome is identical either way; the sequence of who does what, and which action is the one that actually moves the item ledger, is not.

Assemble-to-order splits the same way on both documents

Where some or all of a sales line’s quantity has to be assembled rather than pulled from existing stock, both documents handle the split the same way: a line fulfilled entirely by assembly becomes one pick line carrying the full quantity to assemble; a line fulfilled partly by assembly and partly from stock on hand becomes at least two pick lines — one for the assemble-to-order portion, one for whatever’s picked from inventory — rather than one line trying to represent two different fulfillment methods at once. The bin an assembly-fulfilled line uses for its “take” location isn’t a storage bin at all in the ordinary sense; Business Central resolves it from a small priority list of assembly-specific bin fields, and if none of them are set for the location, a worker has to open Bin Contents directly and choose where the assembled item actually landed.

The one question that tells you which document you’re looking at

If you’re ever unsure which of the two a location is actually running, the location card settles it without any guesswork: check Require Pick and Require Shipment together. Pick on, Shipment off, is an inventory pick, and finishing it ships the order. Pick on, Shipment on, is a warehouse pick, and finishing it only stages the order for a separate shipment document to actually ship. Anyone reporting an order’s status purely from “was it picked” is answering a different question at those two rungs — true and complete at one, and incomplete at the other, without the document itself ever saying so out loud.

Where this goes next

The document a warehouse pick’s registered work eventually feeds into — and exactly what posting that document does — is covered in warehouse shipments vs. sales shipments, explained. For where picking, in either form, sits on Business Central’s broader complexity ladder, see warehouse topology, explained, and for the rung where bin ranking starts actively directing which bin a pick draws from, see directed put-away and pick, explained.

Key terms

New to the vocabulary? Inventory pick / put-away, Pick, and Warehouse activity are defined in the glossary.

Further reading — Microsoft Learn

How to Pick Items with Inventory Picks — inventory pick creation, recording, and the assemble-to-order bundling described above, in full. Ship Items — how warehouse picks are generated from a warehouse shipment and what registering one actually does.