Acumatica gives you real locations inside a warehouse, with quantity tracked at the location level. That puts it well ahead of where a lot of mid-market ERP starts, and it is a big part of why companies pick it.

The catch is that creating a location takes about fifteen seconds, so the setup usually happens fast, early, and without much argument. Then a year of transactions accumulates against those records and the cheap decisions turn expensive.

Here is what I slow people down on.

Naming, because you only get one clean shot

Location IDs sort as text. If you name them A1, A2, A10, then A10 sorts between A1 and A2, and every pick list you print for the rest of the system's life sends someone walking the aisle in the wrong order.

Fixed width, zero padded, in the sequence a person physically walks: A01-14-3-2. Segments for aisle, bay, level, position, with the same width every time.

You can rename a location later, and the system will let you. What you cannot easily do is undo the fact that a year of receipts, issues, and transfers refer to it, or that your team has memorized the old scheme. Renaming during a live operation is a weekend of relabeling plus months of people saying the old name out loud.

Do it before go live. It is the single highest return hour in the whole setup.

Which locations count as available

Every location carries flags that decide whether its quantity is available to promise and whether it can be picked or shipped from.

This is the setting that quietly causes the most confusion later, because it determines whether your on hand and your sellable number agree. Quarantine, QC hold, damaged goods, staging, and returns should generally not be feeding availability. Stock physically in the building that customer service can promise against, when it is actually broken or unreleased, is how you end up shipping something you should not have.

Decide deliberately, per location type, and write down the reasoning. When someone asks in six months why the warehouse total and the available total differ by four hundred units, you want an answer better than a shrug.

Pick priority is your pick path

Locations have a priority that drives the order Acumatica suggests pulling from.

Set thoughtlessly, it produces pick lists that zigzag. Set well, it walks a picker in one direction through the building and empties the pick face before the reserve.

Think about what you actually want to happen. Usually: pick faces before bulk, fast zones before slow, and a sequence that matches the physical route rather than the order the locations were created in. If you run lot or serial with expiry, priority interacts with how allocation picks, so work through a real example rather than assuming.

Primary locations and default receiving

Each item can carry a default location in a warehouse, and the warehouse itself carries defaults for receiving and shipping.

Getting these right is what makes receiving fast, because the system proposes the right home and the receiver just confirms. Getting them wrong is what has everybody overriding the default on every line, which is slower than having no default at all and trains people to ignore what the screen suggests.

Set defaults for the items that move. Do not agonize over the long tail; those can go to a general receiving location and get put away deliberately.

Turning on lot and serial

This one is genuinely hard to reverse, more so than anything else on this list.

Switching an item to lot or serial tracking once it has transaction history and on hand quantity is not a checkbox. It usually means zeroing the item out, changing the setting, and bringing it back in with the tracking populated, which is a controlled exercise you schedule rather than something you do on a Tuesday afternoon.

So decide per item before you load anything, and decide it against a real requirement. A customer contract, a regulator, a recall exposure you can describe. Turning it on because it seems prudent adds handling time to every receipt and every pick, forever, and I have watched teams quietly bypass it within a month, which leaves you with the cost and none of the traceability.

Replenishment between locations

Acumatica can move stock from bulk to the pick face on min and max at the location level.

It is worth setting up, and it is worth setting up second. Get putaway and picking stable first, then turn on replenishment once you trust the quantities. Replenishment rules built on location data that is still settling generate tasks nobody believes, and once your team learns to ignore a queue, getting that trust back takes far longer than the configuration did.

How many locations to start with

There is a temptation to model every shelf on day one. There is an opposite temptation to create one location called MAIN and defer the whole problem.

MAIN is the worse mistake. It looks like a fast go live and it means your quantities carry no positional information at all, so you get the overhead of a location-aware system with none of the benefit, and unwinding it later means introducing locations to items that already have history.

I would rather see a company go live with a modest, correct location scheme covering the areas that matter, and add detail in month four once people are comfortable. Start with the pick faces, the bulk racking, receiving, staging, and whatever quarantine you need. That is usually enough to run on.

Before you configure anything

Walk the building with the person who actually picks in it and draw the route. Write the location names on that drawing. Check that the sequence you have written matches the walk, then check that a stranger could find A03-07-2-1 with no help.

Nearly every location problem I get called about traces back to a scheme designed at a desk by someone who had not made the walk.