Bin Setup and Bin Content in Business Central, Explained

Ask most people what a “bin” is in a warehouse system and they’ll describe a shelf with a label on it. That’s close enough for a walkthrough, but it hides a distinction Business Central actually enforces as two separate records: the bin itself, and what’s allowed to be stored in it. Confusing the two is a common source of “why won’t it suggest this bin” support tickets, and it’s worth being precise about which record is actually doing what.

A bin is a structural record, not a rule

A bin, in Business Central’s own terms, is simply the smallest storage unit the system tracks. It can be as coarse as an entire warehouse treated as one giant bin, or as fine as a single numbered shelf slot — the location decides how granular to go, and there’s no requirement to go any finer than the business actually needs. Creating a bin is a small act: it’s a code, up to 20 characters, that exists on a location. On its own, an empty bin with no further setup is a legitimate, complete configuration. Nothing about creating a bin says anything yet about what’s supposed to live there, or how the system should route work to it.

Whether a location uses bins at all is a single toggle — Bin Mandatory, on the location card’s Warehouse tab. Turning it on makes Bin Code and Zone Code fields available on warehouse receipt, warehouse shipment, and warehouse put-away headers and lines. That’s the entire effect of the toggle by itself: it’s a location-level decision to start using bins, independent of whether the location also uses directed put-away and pick (see warehouse topology, explained for how bins fit into that broader ladder). A location can require bins and still leave a worker’s judgment in charge of which bin to actually use; directed put-away and pick is the separate, further step that hands that decision to the system.

Default bins: where documents get their bin code from before anyone chooses one

Once Bin Mandatory is on, the location card’s Bins FastTab asks for a set of default bin codes — for receipts, shipments, inbound and outbound flows, and an open shop floor bin. These aren’t decorative; the codes entered here appear automatically on the headers and lines of the warehouse documents they correspond to, and they define where an item starts or ends its life in the building by default, before anyone overrides them for a specific transaction. If a location isn’t using directed put-away and pick, there’s also a Default Bin Selection field that governs the method Business Central uses to assign a default bin to an item in the first place — the location still needs a rule for “which bin, absent any other instruction,” even at the less automated rungs of the ladder.

A location using directed put-away and pick needs one more default: an Adjustment Bin Code, a genuinely virtual bin with no physical stock of its own. It exists purely to hold the balancing side of a discrepancy — when a warehouse item journal records a difference, or a registered warehouse physical inventory finds one, the real bin gets credited or debited and the adjustment bin absorbs the opposite entry, so the books balance without inventing stock that doesn’t physically exist anywhere.

Bin type: what a bin is allowed to be used for

Bin type only means anything once a location uses directed put-away and pick — below that rung, a bin is a location to be manually chosen, and there’s no automated flow logic to constrain. At the top rung, six bin types exist, and a warehouse doesn’t have to use all of them:

• RECEIVE — items registered as posted receipts, not yet put away.
• SHIP — items already picked for a warehouse shipment, not yet posted as shipped.
• PUT AWAY — bins meant for storage in large units of measure, deliberately excluded from picking; typically low-ranked, so higher-ranked PUTPICK bins fixed to the same item get put away into first, with the put-away bins replenished from periodically.
• PICK — bins used only for picking, often ranked high so they’re offered first — a natural home for stock nearing its expiration date that’s been deliberately staged for priority movement.
• PUTPICK — bins usable for both put-away and picking, typically ranked differently from each other so bulk storage and forward pick faces can coexist under the same bin type with different priorities.
• QC — quarantine. Unlike every other bin type, QC ships with none of the item-handling checkboxes selected by default, which means anything placed in a QC bin is deliberately excluded from the ordinary item flow. It’s the bin type the Adjustment Bin Code typically points to, and it doubles as a genuine quarantine location for defective or inspection-pending stock.

Bin type only steers automated suggestions — a worker can always override a suggested bin on any document, and a warehouse movement can move stock into or out of any bin regardless of type. It’s a routing hint the system uses when generating suggestions, not a hard lock on the physical floor.

Bin content: the record that says what’s actually allowed where

This is the record most people actually mean when they say “I set up the bin” — and it’s a genuinely separate table from the bin itself. Bin content is set up per item, per bin: it’s where a business specifies that item X is stored (or may be stored) in bin Y, and attaches the rules that govern how that bin gets filled. It can be created by hand, one bin at a time, or in bulk with the Bin Content Creation Worksheet, which is the more practical route once a warehouse has more than a handful of bin/item combinations to define.

Three properties on a bin content record matter enough to be worth knowing precisely, because they’re easy to conflate:

Fixed. Selecting Fixed ties an item to a bin as a standing assignment — Business Central will try to put that item there when there’s room, and critically, the assignment survives the bin content dropping to zero quantity. A fixed bin that’s momentarily empty doesn’t disappear from the system’s routing logic; it’s still the bin the system tries to refill first, rather than treating the empty slot as available for something else. Other items can still be placed in a fixed bin if there’s room — Fixed reserves priority, not exclusivity.

Default. If an item’s stock is spread across several bins, outbound picks draw down the non-default bins first, emptying them, and only fall back to the default bin last. A given item can have at most one default bin per location — it’s the bin of last resort, not a preference among equals.

Dedicated. A dedicated bin’s content can only be picked for the specific resource it’s tied to — a particular machine center, for instance — which keeps a pick suggestion from raiding stock a production line is depending on. That protection is narrower than it sounds: only the quantity a Create Pick suggestion would consider is actually shielded. Other, non-pick consumption — an outbound quantity going out through a shipment posting, for example — can still draw against a dedicated bin’s content. Dedicated solves a different problem than Fixed does, and the two can combine on the same bin content record.

Where directed put-away and pick is in use, and an item’s unit-of-measure dimensions are filled in correctly (see units of measure in warehouse operations, explained), the Max. Qty. entered on a bin content record is checked against what the bin can physically hold — not just accepted as an unverified number. Max. Qty. and Min. Qty. together also drive bin replenishment calculations and suggested put-aways: they’re the thresholds the system uses to decide a pick face is running low and needs restocking from bulk storage, not just descriptive fields for a report.

Why the distinction matters in practice

A bin with no content record at all and a bin content record sitting at zero quantity look identical to a casual glance at the floor — an empty spot is an empty spot. They mean different things to Business Central. A bin with genuinely no content record is just an unassigned storage slot, available for anything that needs a home. A Fixed bin content record at zero quantity is a slot the system considers already spoken for — it’s expected to be refilled with that specific item, and replenishment and put-away logic treat it that way even while it’s sitting empty. Setting up bin content without ever using Fixed where it’s actually meant, or marking things Fixed out of habit when a bin should really be floating, produces a warehouse that looks correctly configured on a walkthrough and quietly routes work wrong the first time volume actually moves through it.

A worked mechanism: the production consumption bin

It’s worth seeing this machinery run somewhere concrete, and Business Central’s own logic for choosing a production component’s consumption bin is a good example of how many layers deep bin routing can actually go. When a production order is refreshed, Business Central works out each component line’s bin code through a short decision sequence: first it looks for a matching routing operation (via the component’s routing link code, or the first operation if there’s no link); then, if a routing line is found and its work or machine center’s location matches the production order’s, it picks a bin code carried on that routing line based on the component’s flushing method — an Open Shop Floor Bin Code for Manual, Forward, or Backward flushing, or a To-Production Bin Code for the Pick-prefixed flushing methods. If no routing line supplies a bin, Business Central falls back to the same flushing-method logic applied to the location card’s own bin fields, and only after that falls back to the item’s plain default bin at that location. Finished output takes a different, simpler path: the last routing operation’s From-Production Bin Code flows directly onto the production order line as where the output lands. None of this is exposed as a single obvious setting — it’s a genuine fallback chain, and it’s exactly the kind of thing worth knowing exists before assuming a component consumed from “the wrong bin” because of a bug rather than an unset routing-line field.

Where this goes next

Bin type and bin ranking only start mattering once a location climbs to directed put-away and pick — see directed put-away and pick, explained for the rung this all sits on top of, and warehouse topology, explained for where bins fit into the wider complexity ladder. Bin capacity checking depends entirely on an item’s unit-of-measure dimensions being filled in — see units of measure in warehouse operations, explained.

Key terms

New to the vocabulary? Bin, Bin content, Bin Mandatory, Bin type, and Bin ranking are defined in the glossary.

Further reading — Microsoft Learn

How to Set Up Locations to Use Bins — the Bin Mandatory toggle, default bin fields, and the production consumption-bin logic described above. Create Bin Contents — Fixed and Default in full, and the Bin Content Creation Worksheet. Set Up Bin Types — all six bin types and what each one is for. Manage Warehouse Activities — Dedicated bins, plus bins in context alongside the rest of the warehouse complexity ladder.