How to Replenish Stock Between Warehouses

Why multi-site businesses overbuy

With two or more warehouses or stores, one site runs out of an item while another has more than it will sell for months. The short site raises a purchase order, the supplier ships more, and the business ends up holding extra stock it already owned.

Finding the surplus by hand is slow. Someone compares stock reports for each site, forgets stock already in transit, and creates transfers line by line. By the time the transfer is ready, the shortage has become a lost sale.

Replenishment between sites should start from each item's reorder level, count what is already on the road, and group the moves into one transfer per route, ready for someone to check and send.

Why this happens

• Each site buys for itself without looking at the others.
• Stock in transit is not counted.
• Reorder levels are missing or wrong.
• Transfers are built line by line.
• Regular routes are re-entered every week.

Biznsbook addresses this through replenishment suggestions between warehouses, one draft transfer per route, transfer templates, in-transit tracking on stock transfers, using each item's reorder level and the stock already on the way.

Small gaps in stock movement rarely fail loudly. They show up later as numbers nobody can explain. Recording each step where it happens removes the guesswork.

Step-by-step: Replenish Stock Between Warehouses

Written for operations and warehouse managers running two or more sites with Biznsbook Warehouse Management.

1. Set reorder levels. Make sure items have a reorder level so Biznsbook can tell which site is running low.
2. Open Replenish. Go to Stock Transfers → Replenish (needs Manage inventory).
3. Review the suggestions. Biznsbook lists items below their reorder level at one warehouse, counting stock already on the way, while another warehouse has surplus.
4. Select the lines. Tick the suggestions you agree with. Serial, kit and clothing-parent items are left out.
5. Create the drafts. Biznsbook creates one draft transfer per route from the lines you selected.
6. Check and submit. Review each draft, then Submit. With transfer approval separation on, it waits for approval before it can be picked and shipped.
7. Ship and receive. Ship deducts stock at the source and puts the transfer in transit; Receive books it into the destination, partially if needed.

Review results after the first full weekly cycle. Adjust roles, mappings, or approvals where the same exception repeats.

Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.

Common mistakes to avoid

• Mistake 1: Each site buys for itself without looking at the others. Repeating this each month usually shows up first in stock bought for one site while another holds surplus.
• Mistake 2: Stock in transit is not counted. Repeating this each month usually shows up first in stock bought for one site while another holds surplus.
• Mistake 3: Reorder levels are missing or wrong. Repeating this each month usually shows up first in stock bought for one site while another holds surplus.
• Mistake 4: Transfers are built line by line. Repeating this each month usually shows up first in stock bought for one site while another holds surplus.
• Mistake 5: Regular routes are re-entered every week. Repeating this each month usually shows up first in stock bought for one site while another holds surplus.

Each of these turns into a question the warehouse cannot answer quickly. Fix the process on the record rather than in email threads or spreadsheets.

Best practices that hold up as you scale

• Set reorder levels — Make sure items have a reorder level so Biznsbook can tell which site is running low.
• Open Replenish — Go to Stock Transfers → Replenish (needs Manage inventory).
• Review the suggestions — Biznsbook lists items below their reorder level at one warehouse, counting stock already on the way, while another warehouse has surplus.
• Select the lines — Tick the suggestions you agree with.
• Create the drafts — Biznsbook creates one draft transfer per route from the lines you selected.

Run Replenish before you raise purchase orders, so surplus at one site is used before buying more.

How Biznsbook supports this workflow

replenishment suggestions between warehouses is part of Biznsbook and works on the same records as the rest of stock movement, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

one draft transfer per route is part of Biznsbook and works on the same records as the rest of stock movement, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

transfer templates is part of Biznsbook and works on the same records as the rest of stock movement, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

in-transit tracking is part of Biznsbook and works on the same records as the rest of stock movement, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

Replenish and transfers need Manage inventory; approving transfers needs Approve stock transfers when approval separation is on.

Suggested implementation timeline

1. Week 1: Set up replenishment suggestions between warehouses and the permissions the people involved need.
2. Week 2: Run the real process in Biznsbook only, with no side spreadsheet, for one team or site.
3. Week 3: Review what was recorded with the people involved and tighten the rules where they disagreed.
4. Month 2: Roll out to every team or site.
5. Ongoing: Reviewing replenishment each week.

Related guides

Cluster hub: Inventory guides. Module: warehouse management. Also see transfers between warehouses.

What happens after you submit

A replenishment draft is an ordinary stock transfer. Submitting approves it automatically, or sends it for approval when transfer approval separation is on in Warehouse settings; by default the person who created a transfer cannot approve it, and a rejection needs a reason.

Picking is optional unless your administrator makes it required. Shipping deducts stock from the source and puts the transfer in transit; with Accounting, goods in transit are journaled. For lot-tracked items with no batch chosen, the lots that expire first are taken, and a line is split per lot when one lot is not enough.

Receiving can be partial, and the status shows Partially received until everything is in. Pressing a button twice or two people acting at once never ships or receives twice.

Keeping an eye on capacity and stuck transfers

Moving stock into a site only helps if there is room for it. The capacity dashboard shows overloaded, nearly full and empty bins, and Warehouse settings can warn about or block a receipt or move that would overfill a bin, so a replenishment does not create a new problem at the destination.

The warehouse overview is a landing page with the transfers and bins that need attention, and a combined movement history shows every receipt, transfer and adjustment in one list. A daily alert lists transfers stuck in transit, which is often the first sign that a replenishment draft was shipped but never received.

For routes you run every week, save a transfer as a template from its More menu and start the next one from it. Templates keep the route and lines but never store batches or serials, so the lots that expire first are still chosen when the transfer ships.

Metrics to track monthly

• Items short at one site and surplus at another
• Replenishment drafts created and submitted
• Days in transit per route
• Purchase orders avoided by transfers

Start with three metrics; trend direction matters more than a single point-in-time snapshot.

Manual workarounds vs Biznsbook

Compare common manual workarounds with Biznsbook replenishment suggestions between warehouses and the related capabilities.

Reviewing replenishment each week

Once a week, run Replenish, review the suggestions with the site managers, and submit the drafts you agree with. Check items that keep appearing short at the same site; their reorder level may be too low, or the site may need its own purchasing. Items that keep appearing as surplus at another site are candidates for a lower reorder level there, or for a markdown before they age. Compare the number of transfers created with the number of purchase orders raised for the same items: when replenishment works, purchase orders for items another site already holds should fall month by month, and the stock-in-transit alert should stay short. Share the results with each site manager.

Write the replenishment routine (day, routes, who approves) into your warehouse procedures.

Frequently asked questions

How this differs by industry