The advanced warehouse configuration most distributors are licensed for and never enable — and how to switch it on without stopping shipments.
Inventory accuracy is a planning input, not a warehouse metric. Moving from roughly 85% to 98% releases the buffer stock you carry to compensate. This guide covers what that change involves operationally and why we sequence it in three phases rather than one.
Location setup flags, zone and bin structure, bin types, put-away and pick templates, warehouse employee configuration, and the migration path from basic to advanced warehousing on a live location.
Most mid-market distributors implemented Business Central to solve a finance problem, took the basic stock module, and never revisited it. Meanwhile the same licence covers directed workflows, wave planning and cycle counting.
The consequence is a warehouse running on memory and paper, an accuracy figure nobody measures, and safety stock carried everywhere downstream to compensate for a number that cannot be trusted.
Check these before beginning. Most stalled implementations stall on one of them.
Business Central Premium for full warehouse management. Essentials carries basic locations and bins only.
Business Central administrator plus a warehouse manager who knows the physical layout and will own the bin structure.
Handheld scanners tested with your actual Business Central client. Test transaction speed in the aisle before committing.
Item unit of measure and dimension data accurate enough to drive bin capacity. This is usually the hidden work.
Configuration is straightforward once these are clear. Skipping them is why most first attempts produce something that works and cannot be maintained.
Directed Put-away and Pick is a single checkbox that changes the entire warehouse behaviour of a location. Once enabled with inventory present, reversing it is genuinely difficult. This is why we recommend a new location for the transition rather than converting in place.
The bin structure should describe how the warehouse is actually walked. A logically elegant structure that does not match the physical layout produces pick routes that waste time, and the team will stop following them.
Receive, Ship, Put-away, Pick, Put-away and Pick, and QC. These determine which warehouse activities can target a bin. Getting the types wrong produces workflow that stalls in ways that are hard to diagnose.
Settings shown are the ones that matter, not every field on the form. Values are starting points to validate against your own environment.
Walk the warehouse. Number the bins in pick sequence, not in a logical scheme that looks tidy in a spreadsheet.
Establish a bin ranking so put-away favours locations that make subsequent picking efficient. This is where the throughput gain comes from.
Enable the simpler flags first and confirm the team is comfortable, then move to directed. Attempting all flags at once in a live warehouse is the version of this project that becomes a cautionary story.
Put-away templates define where the system looks for a bin, in order. Pick follows a similar logic.
Start with a simple template and add rules once you can see how the warehouse behaves. Over-engineering this before go-live produces routing nobody understands.
Every user performing warehouse activity needs a Warehouse Employee record with a default location. This is a small step that blocks everything if missed, and the error message is not obvious.
Assign one default location per employee; multiple locations require them to switch context explicitly.
Phase counting last. Counting against an inaccurate baseline produces adjustments that mask whether the new workflow is working.
Configure counting periods by item velocity so fast movers are counted frequently and slow movers occasionally.
Every one of these is avoidable, and every one of them is common enough that we check for it by default.
It is difficult to reverse and it changes behaviour immediately. Use a new location and transfer inventory, or accept a hard cutover with a planned outage.
Capacity checking with wrong weights or cubes produces put-away suggestions the warehouse cannot follow, and confidence in the system evaporates in a week.
A five-rule template before go-live produces routing nobody can explain when it does something unexpected. Start simple and add rules from observed behaviour.
Everything appears configured and nothing works. The error is unhelpful and this catches almost every first implementation.
We will review your current warehouse configuration against what your licence already covers, and demonstrate directed picking against your own item and bin data.
Describe the situation in your own words.
