Bin setup and warehouse classes in Business Central

A bin in Business Central is the lowest-level inventory storage unit — typically a physical shelf, pallet position, or rack location. Bin design is where most warehouse implementations get derailed: too few bins and you lose accuracy, too many and you create unmaintainable complexity.

Where bin setup lives.

• Location card — Bin Mandatory flag, default bins.
• Bins page — the list of all bins at a location. Each bin has Code, Description, Zone Code, Bin Type Code, Warehouse Class Code, Bin Ranking, and capacity attributes.
• Bin Contents — what's currently in each bin, by item, variant, and unit of measure. Populated automatically by warehouse postings.

Bin naming conventions. A common pattern is ZONE-AISLE-RACK-LEVEL-POSITION (e.g. A-01-03-02-04). The naming should sort naturally in pick walk order so worksheet sorts give pickers a sensible path. Don't use names with embedded special characters — many scanner workflows choke.

Bin types. Defined on the Bin Type page. A bin type ticks which warehouse flows the bin participates in:

• Receive — receive zone for inbound.
• Ship — ship zone for outbound.
• Put-away — eligible as a put-away destination.
• Pick — eligible as a pick source.
• Put-away + Pick — most floor bins.
• QC — quality control quarantine.

A receive-only bin can't have stock picked from it directly; it must first be moved to a pick-eligible bin.

Warehouse classes. A Warehouse Class segregates inventory by storage requirement: ambient, refrigerated, frozen, hazmat, oversized. Each item carries a Warehouse Class Code; each bin carries one; the put-away logic only places an item into a compatible bin. This is how cold-chain compliance is enforced — frozen items physically cannot be placed in an ambient bin without overriding the warehouse class check.

Bin ranking. The Bin Ranking number on a bin (higher = preferred) influences put-away and pick suggestions:

• Put-away prefers high-ranked bins (typically the pick face).
• Pick prefers high-ranked bins (faster paths).

Bin ranking is the most underused tuning knob in BC's warehouse module. Time invested ranking bins after the first few months of real picks pays back forever.

Default bins per item. On the Item card, you can set:

• Default bin at a location.
• Bin Content records that explicitly bind an item to specific bins with min/max quantities.

Bin content with min/max enables the Replenishment workflow — moves are suggested when the pick face drops below minimum.

Adjustment bins. Each location has an Adjustment Bin Code on the location card. Quantity adjustments (positive/negative inventory adjustments) post against this bin to keep the bin contents balanced. Without an adjustment bin set, adjustment journals fail to post on a bin-mandatory location.

Cross-dock bins. Some operations cross-dock inbound deliveries straight to outbound shipments without storing them. Configure a cross-dock zone with Cross-Dock Bin Type and enable cross-dock on relevant items; BC will suggest cross-dock movement when an inbound matches an outbound demand.

Bin capacity. Optional but powerful — set Maximum Cubage and Maximum Weight on a bin; put-away logic skips bins that don't have room. Most implementations skip capacity tracking because cubage and weight data on items is rarely accurate. If your data is good, capacity-aware put-away dramatically reduces operator decisions.

Common pitfalls.

• Over-segmentation. Creating dozens of zones and bin types because they sound useful, then nobody understands the workflow. Start simple, layer complexity only when there's a problem to solve.
• Bin code chaos. Inconsistent naming. Mixed length codes. Bin codes that don't sort in walk order. Worth fixing in cutover, very painful to fix after.
• Adjustment bin missing. Posting fails with cryptic errors. Always set during location setup.
• Default bins forgotten on new items. New items get added without default bins; put-away suggests random bins. Build item creation into a checklist with default bin assignment.
• No bin audit. Periodic cycle counts ensure system bin content matches physical reality. Without that, the optimisation built on bin data is worthless.

Bin redesign. A bin layout designed at go-live rarely matches the optimal layout after 18 months of real operations. Building a "bin review" into the operations rhythm — quarterly or annually — keeps the warehouse efficient as product mix and volumes change.