How to Manage Inventory Across Multiple Warehouses and Locations

Inventory quantity is stored at a location. A company total is only the sum of those locations. If Warehouse A has 30 and Warehouse B has 12, you have 42, and you also have two different piles. Selling, transferring, or counting against "the company" without naming a location is how one warehouse is promised stock that is sitting in the other.

A location here means a warehouse, store, stockroom, or other place you receive and hold goods. It is not a bin, a pick face, or an in-transit truck as a separate inventory state.

Company stock is a sum, not a bin

Each balance is for an item at a location. The same SKU can be 30 in one warehouse and 12 in another at the same time. Available to promise from Warehouse A is the Warehouse A quantity, not 42, unless you are willing to transfer first.

That is the whole model. Receipts add quantity at the location named on the receipt. Issues remove quantity at the location you issue from. A transfer decreases one location and increases the other, and it writes that move into movement history. There is no extra "floating" quantity between the two unless you record the transfer.

If you only keep a single on-hand number, a transfer looks like noise. One site's count goes down, the other site's count goes up, and the company total is unchanged. The history still matters, because the next order will be picked in a specific building.

Set up the locations you actually hold stock in

Create a location for each place that receives or stores goods you are willing to count separately. A main warehouse and a second warehouse are two locations. A shop stockroom that you replenish from the warehouse is a third, if you need its quantity to be distinct.

A location can store a name and address details, and one location can be marked primary. Those details help people recognize the site. They do not, by themselves, move stock. Stock appears at a location when a receipt, a transfer in, a sales return, or another inbound movement puts it there.

Free includes one location. Pro and Business do not apply that cap, so additional warehouses are a paid-plan question. The current limits are on the pricing page. Adding a second location in the software before you are allowed to, or before anyone will count it, only creates an empty name. Add it when goods will actually be received or stored there.

A transfer of one SKU between two warehouses

This example is hypothetical.

North Warehouse holds 30 units of SKU FLT-100. South Warehouse holds 12 of the same SKU. No other location stocks it. The company total is 42.

You transfer 10 units from North to South.

The company total does not change. What changed is where an order can be filled without another move. South can now cover a larger pick. North cannot still promise the original 30.

The transfer is a movement with a source and a destination. It is the record you look at later when someone asks why North's count dropped on a day with no sales. Do not "fix" that drop with a second, unrelated adjustment. The transfer is already the explanation.

If the item is batch-tracked, the transfer moves a quantity of a specific lot. Lot FLT-100-A in North is not the same thing as an anonymous 10 units. If the item is serial-tracked, the transfer moves those serials. You are not creating new units at South. You are changing the location of units that already existed. Serial and batch tracking is the identity. The transfer is where that identity goes.

The unit cost on a transfer follows the valuation policy stored for the account, FIFO or weighted average. A transfer does not create a new supplier cost. If North and South should carry cost from the receipts that built the layers or the average, that cost was set when the goods were received, not when they were driven across town. The FIFO and weighted average article covers that policy.

Receipts, sales, and returns are also location events

A purchase receipt adds stock only at the receiving location. If a supplier delivery is unloaded at North, South's balance does not rise until you transfer or until a different receipt names South.

A sale or other issue removes stock at the location you issue from. It does not silently borrow from another warehouse. If South is short, the choice is to transfer first or to refuse the issue. Recording the sale at South when the goods are still at North makes both balances wrong.

A customer return brings quantity back in, at the location you receive the return into. A return to the supplier sends quantity out of the location you ship it from. Those directions are covered in sales returns and purchase returns. For multi-warehouse work, the point is the same: name the location. "It came back" is not a balance.

What movement history is for

Movement history is the list of receipts, issues, transfers, and returns that explain the balance you see now. When two warehouses disagree with a spreadsheet, the useful question is which movement last touched that SKU at that location, not which building feels busier.

A transfer should show the source, the destination, the quantity, and, when the item is tracked, the serials or the batch. A receipt should show the location that took the goods. If a count is corrected, that correction is its own movement. Replacing history with a new total deletes the explanation the next count will need. The audit trail article is about keeping that explanation reversible instead of erased.

People on the floor and people at a desk can both record these movements. The balance is still per location either way. This article does not claim that a phone and the web app show a different stock figure for the same location, and it does not claim offline synchronization. Record the transfer when the goods move, at the locations you actually use.

What this is not

A few warehouse ideas are easy to assume and are not what location balances do.

• Bins. A location is a place you stock, such as a warehouse or stockroom. Inveta does not provide a separate bin, shelf, or slotting system. Do not describe a second warehouse as a bin, and do not describe a location name as pick-path logic.
• In-transit inventory. A transfer reduces the source and increases the destination as that movement. There is no separate in-transit warehouse in this workflow unless you create a location and use it deliberately. Goods on a truck are not automatically a third balance.
• Wave picking and marketplace sync. Nothing here releases pick waves, pushes stock to a marketplace, or pulls marketplace orders. Those are different systems.
• One balance for every channel. If you sell from more than one site, each site's quantity is its own location balance. The company total is the sum, and it is the wrong number to promise from a single dock.

A simple operating rule

1. Receive into the location that unloaded the goods.
2. Transfer when goods physically move, for the quantity and the serials or batch that moved.
3. Issue from the location that is fulfilling the order.
4. Read a location balance before promising that location's stock.
5. Use the company total only when you truly mean every location added together.

If Free is enough, one location is the whole model and transfers do not arise. The moment a second warehouse, van stock, or shop stockroom must be counted on its own, you need another location and a transfer habit. The plan change is the location limit. The habit is recording the move.

Frequently asked questions

If I transfer stock, does the company total change?

No. The source location decreases and the destination increases by the same quantity. The total is unchanged. The place you can pick from is what changed.

Can the same SKU have different quantities in two warehouses?

Yes. That is the normal case. Each location has its own balance. Add them only when you want a company figure, and do not use that figure as the available quantity of one warehouse.

Do serials and batches follow a transfer?

Yes. A serial-tracked unit moves as that serial. A batch-tracked quantity moves as a quantity of that lot. The transfer does not mint a new serial or a new lot.

Does Free include more than one location?

No. Free includes one location. Additional locations are part of the paid plans. See the pricing page for the current limits.

Will a transfer recalculate a new purchase cost?

No. Purchase cost is created by receipts and their landed costs. A transfer uses the valuation policy already stored for the account. It does not replace that cost with a new supplier price.

Name the location, then move the quantity

Two warehouses are two balances. A transfer is how units change buildings without changing how many you own. Receive into the right site, transfer what actually moved, and keep that movement so the next count has a cause.

The same location model is part of the inventory controls on the Inveta homepage. To try a second balance with your own SKU, create an Inveta account and record one transfer before you add a third site.