You track it by location, not by a single company-wide count. Every building needs its own real number, transfers between buildings need to be visible as they move, and someone still has to decide what ships from where. Software that only shows one total forces the order desk to guess which building actually has the part.
A sales order prints at the Ohio building. The screen says available. The Ohio shelf is empty. Twelve units of that same part sit on a rack in Utah, and nobody at the order desk knew to look there. Customer service promises Monday anyway, because the number on the screen said the part existed. Now someone has to go find stock that was never actually missing, just sitting behind the wrong door. That gap between what the operation knows and what the order desk sees turns into three costs every week it goes unfixed: delayed orders, wasted labor, and unnecessary inventory.
The order sits while a person hunts for a part that was never lost. Labor goes to phone calls and warehouse walk-throughs instead of picking and shipping. And because nobody trusts the number between buildings, Ohio keeps a cushion of extra stock it does not need, just in case Utah cannot be reached in time.
Most software shows you the problem and leaves you the work. Fishbowl gets the work done. You still make the call.
Fishbowl is the platform. Fishbowl Inventory, Fishbowl Advanced Manufacturing, Fishbowl Advanced Warehouse, and Juno are purpose-built parts of Fishbowl, matched to how the business runs.
What Fishbowl Inventory does once you own more than one building
Fishbowl Inventory tracks quantity by location across every site you own, not just a company-wide sum. That means Ohio’s screen shows Ohio’s shelf, and a picker cannot promise a part that only exists three states away. Transfers between buildings are already part of the product, not a feature you are waiting on: stock moving from Utah to Ohio is a document Fishbowl tracks from the moment it leaves one shelf to the moment it lands on another.
On top of that, data-focused AI on Fishbowl Inventory tells you what is happening right now (Ohio is short, Utah is not), what is coming (a transfer that would clear the shortage before the next order prints), and what needs your attention today. In Fishbowl Inventory, Juno uses live Fishbowl data to prepare purchase orders, sales orders, transfers, receipts, and adjustments for your approval. Nothing is saved or changed without the operator’s approval. Ask, Approve, Done. You still decide whether that transfer moves today or waits for the regular truck.
Telluric’s Brian Garrett puts a number on what that prep work is worth: Juno saves him at least 45 minutes per purchase order, because the draft is already sitting there when he opens the screen instead of a blank one. See more named results on the case studies page.
When a second building actually means Fishbowl Advanced Warehouse
Owning a second warehouse is not, by itself, a reason to move up. Multiple owned locations alone do not require Advanced. What does is the paperwork around them: a 3PL holding inventory on your behalf, EDI documents flowing to a big-box retailer, or transfer and fulfillment rules that have grown past what a straightforward pick-and-ship building needs. That work belongs on Fishbowl Advanced Warehouse, built for 3PL management, EDI-driven fulfillment, and deeper warehouse workflows, alongside its own data-focused AI showing what is happening, what is coming, and what needs attention across those sites.
Named results back this up on the Advanced side. Cascadia Motion brought inventory costs down 18 percent running Fishbowl Advanced with data-focused AI, once the forecasting and procurement view stopped treating each site as a separate guess. Hodo Foods cut stockouts 35 percent the same way. Koken USA cut sales backorders 10 percent once stock across sites stopped being something someone had to call around and confirm. Full detail is on the case studies page.
Fishbowl Advanced Warehouse and Fishbowl Advanced Manufacturing are separate products built for different needs. A warehouse problem does not require a manufacturing purchase, and a plant running bills of materials and work orders is a different conversation than a second building full of finished goods.
Where ecommerce channels fit into a multi-warehouse setup
Fishbowl Channels is the channel-integrations layer. It works with Fishbowl Inventory, Fishbowl Advanced Manufacturing, or Fishbowl Advanced Warehouse. Advanced customers add ecommerce channels in Fishbowl; they do not also purchase Fishbowl Inventory. Whichever building fills the order, Channels keeps catalog, pricing, and availability synced back to Shopify, Amazon, Walmart, and other channel integrations so a customer buying online sees stock that actually exists in a building you can ship from today, not a number a schedule forgot to update three hours ago.
What available has to mean once stock lives in more than one place
Available is not on-hand. Available is on-hand minus committed sales minus stock already spoken for, and that math has to run per building, not per company. Subtract commitments only at the company level and you will oversell the moment two warehouses share a catalog. Software that cannot show one SKU holding stock in two sites at once sends that arithmetic back to a spreadsheet named after the state it covers, and someone on your team already knows which one.
Barcode receiving at the second building stops a clerk from typing the wrong site into a form because it was the only option on a dropdown that day. The Fishbowl mobile app scans in the building where the tote actually is, whether that is receiving, picking, or a cycle count. It is the floor tool tied to one inventory record inside Fishbowl, not a second count competing with the first. Pick tickets need a site printed on them, not just a company name; a ticket that only says “warehouse” is how an Ohio order quietly pulls from Utah’s shelf.
One ledger, many buildings
Two warehouses do not mean two accounting files. You want one ledger and many physical locations. Fishbowl syncs both directions with QuickBooks or Xero: Fishbowl owns quantity and location, the accounting system owns the financial posting. That split matches the argument in the QuickBooks bottleneck post: do not abandon your accounting system to grow, and do not stretch it into a second building’s bins either. Fishbowl runs inventory across every site you own. QuickBooks or Xero keeps the books.
How to stand up a second site without inheriting a bad number
Copy the item master. Do not invent a second SKU for the same part just because it now lives in Ohio. Create the location inside Fishbowl, then run a cycle count at the new building before picking goes live there, so day one starts with a number you trust instead of one you inherited from a spreadsheet.
Train receiving first. Most multi-site messes start with a purchase order received against the company instead of the building, and nobody notices until the count is already wrong. In week two, print stock status by site and walk both floors with the printout in hand. Every line that does not match a shelf is a process hole until you can prove the posting itself was wrong. Fix the posting, then argue about reports.
In-transit is its own state. Stock that left Ohio and has not been received in Utah is not pickable in either building. A system that dumps that quantity back into Ohio’s available count because the transfer is not a finished document yet will let you sell goods still sitting on a truck. Fishbowl Inventory tracks quantity by location and moves stock between owned buildings without pretending complex 3PL or EDI paperwork belongs there; that depth lives on Fishbowl Advanced Warehouse once 3PLs and EDI partners enter the picture.
If site two is a 3PL rather than a building you own, you still need quantity by location inside your own system, plus a clear rule for whose scan wins when the 3PL’s count disagrees with yours. That conversation belongs on Fishbowl Advanced Warehouse, not on a finished-goods setup you have outgrown in name only.
Training on Fishbowl is expert-led, typically six to eight weeks, so the team running two buildings knows the software before go-live instead of learning it during a live oversell. Support afterward is in-house: US experts for US customers, APAC for APAC, by phone, email, or chat, with no AI agent answering your ticket. Fishbowl has run this way for 25 years and works with more than 6,000 businesses, a claim worth checking against your own SKU and your own two sites on a live call, not taking on faith.
See how Fishbowl Inventory handles a real two-site pick, transfer, and QuickBooks sync on a live demo: Get a Demo.
Fishbowl does the work. You make the call.
Frequently asked questions
Do I need a full ERP because I opened a second warehouse?
No. A second building is a location problem: quantity by site, picks that cannot pull stock from the wrong roof, and one ledger that stays one set of books. A full ERP adds a general ledger, HR, and CRM you may not need yet. Fishbowl Inventory tracks quantity by location across every building you own, and heavier fulfillment, 3PL, and EDI work belongs on Fishbowl Advanced Warehouse.
Is a second warehouse a Fishbowl Inventory problem or a Fishbowl Advanced Warehouse problem?
Finished-goods operations that stock, move, and sell out of buildings they own should start on Fishbowl Inventory. Fishbowl Advanced Warehouse fits when fulfillment runs through a 3PL, EDI trading partners, or heavier transfer rules across sites. Owning a second building by itself does not require Advanced.
What does available have to mean across two buildings?
Available is on-hand minus committed sales minus stock already spoken for, calculated per building, not per company. A company-wide total can look correct while one site sits empty and another sits full. Software that cannot show one SKU holding stock in two locations at once sends that math back to a spreadsheet.
Can the same mobile app scan receiving and picking in more than one warehouse?
Yes. The mobile app scans in whichever building the tote is actually sitting in. Receiving, picking, and cycle counts all run from the same app, tied to the location where the scan happened, so a clerk in one site cannot accidentally book a receipt against the other site’s shelf.