Warehouse Shipments vs. Sales Shipments, Explained
The outbound side of Business Central’s warehousing has the same trap as the inbound side, in mirror image: “shipped” can mean the sales order itself was posted directly, or it can mean a genuinely separate warehouse shipment document was posted — and at the more structured end of that range, picked and shipped aren’t even the same moment. Getting that distinction right matters for anyone trying to answer “is this order actually gone” from outside the warehouse.
Four ways to pick and ship the identical sales order
Business Central documents four methods, governed by two independent location toggles — Require Pick and Require Shipment — each set per document type (sales, purchase return, transfer, service):
Method A — post the pick and shipment straight from the order line. Neither toggle is on. No dedicated warehouse activity exists; posting the sales order’s own line is the whole event.
Method B — post from an inventory pick document. Require Pick alone is on. One inventory pick document per source order, order-by-order.
Method C — post from a warehouse shipment document. Require Shipment alone is on. Multiple sales, purchase-return, transfer, or service orders can now be consolidated onto a single warehouse shipment before it’s posted.
Method D — post the pick from a warehouse pick document, then post the shipment separately from a warehouse shipment document. Both toggles are on — the advanced configuration, and the one where picking and shipping become genuinely separate events rather than two views of one act.
This article is about methods C and D — where a distinct warehouse shipment document exists at all, as opposed to a sales order posting its own shipment line directly.
What a warehouse shipment actually is
A warehouse shipment gathers the lines of one or more released outbound source documents — sales orders, purchase return orders, transfer orders, service orders — into a single shipping pass, the same consolidating role a warehouse receipt plays on the inbound side. It’s created either push (the Create Warehouse Shipment action on a single source document) or pull (Release the source document to signal it’s ready, then a warehouse employee gathers one or more released documents onto a shipment using Get Source Documents or a saved Use Filters to Get Src. Docs. filter, exactly as on the receiving side).
Picking happens inside the shipment, not as an afterthought
For a location that requires picking, a warehouse shipment doesn’t just wait for stock to appear — it drives the pick. Pick activity can be generated two ways: push, using the Create Pick action directly on the shipment lines being worked, which lets a user specify take/place bins and quantities up front; or pull, through a Pick Worksheet, where Get Warehouse Documents retrieves assigned picks, and a fully registered pick automatically clears its lines from the worksheet. For a location that doesn’t require picking at all, the warehouse shipment document itself can simply be printed and used as an informal picking list — the structure is there even when the formal pick step isn’t required.
Cross-docking adds one more wrinkle worth knowing about: where a location uses cross-docking and per-line bins, Business Central continuously calculates how much of a shipment’s demand can be satisfied directly from cross-dock bins — stock that arrived and can go straight back out without ever being put away into regular storage — recalculating those quantities every time a field on the shipment changes.
Quantity to ship follows the pick, or it doesn’t exist yet to follow
At a location that requires picking, the Qty. to Ship field on a warehouse shipment line isn’t something a user fills in directly — it’s populated automatically once the corresponding pick is registered, and it can never exceed the Qty. Picked that registration actually produced. At a location that doesn’t require picking, Qty. to Ship instead defaults to the line’s outstanding quantity the moment the shipment line is created, the same “defaults to everything outstanding” behavior seen on the receiving side — and the same Delete Qty. to Ship / Autofill Qty. to Ship actions exist to zero it out first (useful for a barcode-driven flow confirming quantities one scan at a time) or restore it afterward.
Posting a pick and posting a shipment are not the same act
This is the sharpest, most easily missed distinction on the outbound side, and it’s the mirror of “received but not yet available to pick” from the inbound article. Under method D, registering a warehouse pick does not post the sales shipment, does not reduce the item ledger, and does not close out the sales order. It moves picked stock into a shipping bin and marks it ready — nothing more. The sales shipment, the actual ledger-affecting event, only happens when the warehouse shipment document itself is posted, as its own separate step, potentially well after the pick was registered. A stack of fully picked, fully staged pallets sitting at the dock, correctly registered as picked, can sit there for hours without a single unit having actually left the item ledger — because registering a pick and posting a shipment answer two genuinely different questions: “is this physically ready to go” and “did this actually leave.” Exactly how a pick’s own posting mechanics differ from a shipment’s is covered in full in inventory pick vs. warehouse pick, explained.
Zone and bin codes, the mirrored rule
Where bins are mandatory, Business Central assigns a shipment bin code following the same shape of rule seen on receiving, just phrased from the other direction: at a location using directed put-away and pick, the Shipment Bin Code from the location card is used, and left blank rather than guessed if the item’s warehouse class doesn’t match that bin. At other locations, Business Central still checks the location card’s Shipment Bin Code first, and only falls back to the bin code carried on the source document if the location doesn’t specify one.
Assemble-to-order items get their own accounting inside the same document
Where a sales line is fulfilled by assembling a kit rather than picking existing stock, the warehouse shipment’s Qty. to Ship field takes on a different meaning specifically for that line: it represents how many units workers have actually finished assembling, not a quantity pulled from a bin. Posting the shipment in that case posts three things together in one act — the assembly output, the component consumption that produced it, and the sales shipment for the assembled quantity. Where a sales line is fulfilled partly by assembly and partly from existing inventory, Business Central creates two separate warehouse shipment lines for it — one carrying the assemble-to-order quantity, handled as just described, and one behaving as an ordinary inventory shipment line — rather than trying to force one line to represent both kinds of fulfillment at once.
Why the distinction is worth insisting on
As on the inbound side, none of the four methods is inherently better — a business shipping one sales order at a time to a short customer list has no real need for consolidated shipments or a separate registered-pick step, and the setup and discipline that separation demands would be pure overhead. The question worth asking of any process claiming to track “shipped” status — including a scanning app sitting on top of it — is exactly which of the four methods a given location is actually running, and specifically whether “picked” on that floor already means “gone,” or means “staged, awaiting a still-separate posting step.” Those are different facts on a method-D location, and treating them as interchangeable is exactly how a customer service rep ends up telling someone their order shipped when it’s still sitting, fully picked, at the dock.
Where this goes next
The inbound mirror of this same distinction — where “received” and “available to pick” can likewise be two different moments — is covered in why a warehouse receipt isn’t the same as a purchase receipt. For exactly how registering a pick differs, mechanically, from posting one, see inventory pick vs. warehouse pick, explained. For where picking and shipping sit on the broader complexity ladder, see warehouse topology, explained.
Key terms
New to the vocabulary? Warehouse shipment, Pick, Pick worksheet, and Assembly are defined in the glossary.
Further reading — Microsoft Learn
Ship Items — the four shipping methods, cross-docking, and the assemble-to-order handling described above, in full. Manage Warehouse Activities — shipping in context alongside the rest of the outbound warehouse flow.