WooCommerce Multi-Warehouse: How to Manage Stock in Several Locations

WooCommerce collegato al gestionale keeps one global stock count per product, so a multi-warehouse setup needs an extension or an ERP that holds a separate quantity for each location. The extension, or better the ERP, becomes the place where stock is decided, and the store only displays and consumes it. PrestaShop is different: it includes an Advanced Stock Management feature, with its own limits. Below you will find how each platform handles several warehouses, how to route orders, and what an Italian business should check before starting.

TL;DR

• WooCommerce tracks a single global stock count by default, so separate quantities per warehouse, shop or distribution center require an extension or an integrated ERP.
• PrestaShop 1.6 documents an Advanced Stock Management module that creates warehouses and links them to products, carriers and shops. Check what your installed version offers before you plan around it.
• Stock sync and order routing are the real work: define which system is the master, how often quantities update, and who resolves mismatches.
• For most SMEs with accounting, production and sales to coordinate, the ERP should own the stock and the shop should receive it through an integration.

Table of Contents

• What multi-warehouse inventory means in an online store
• How WooCommerce handles several warehouses
• How PrestaShop handles several warehouses
• Where the stock logic should live
• Setting up multiple warehouses step by step
• Synchronizing stock without surprises
• Assigning orders to the right warehouse
• What an Italian business should check first
• Our perspective
• How Linkware can help
• Common mistakes to avoid
• FAQ

What multi-warehouse inventory means in an online store

Multi-warehouse inventory management means keeping separate stock levels for each location, such as a central warehouse, a retail outlet or a distribution center, instead of one total per product. The store then knows not only how many units exist, but where they are. That is what makes it possible to ship from the closest location, to show availability per site, or to let customers pick up in a shop.

WooCommerce does not do this natively. As a 2025 guide on the subject describes, the default is a single global stock figure, which is the limitation extensions are built to remove.

It is worth asking first whether you actually need it. You probably do if:

• you keep goods in two or more physical places and sell the same items online from all of them;
• you have a shop or showroom whose stock must be visible to online customers;
• an outside logistics provider holds part of your goods;
• delivery times or carrier costs differ noticeably depending on where an order ships from.

If you have one warehouse and simply want accurate quantities, you need stock synchronization with your management system, not multi-warehouse. Our guide to synchronizing warehouse and ERP for SMEs covers that simpler case.

How WooCommerce handles several warehouses

Extensions and what they add

In WooCommerce you add warehouses through extensions. These provide an interface where you create locations with details such as physical address, shipping methods and a manager. The official documentation for a WooCommerce multi-inventory extension explains that administrators can assign product stock to each location and set an inventory priority, which decides which location is used first.

Typical capabilities you should look for when choosing any extension:

• a stock field per product and per variation, for each location;
• a priority rule, so the store knows which location to draw from first;
• display options on the product page (a single total, or availability per location);
• order assignment, automatic or manual;
• an API to read and write quantities from outside.

That last point matters more than it looks. The same documentation set describes a REST API for the multi-location extension that lets third-party developers or ERP systems read and update inventory by location ID. If your business already runs an ERP, this is the door through which the real warehouse data reaches the shop.

Variations, bundles and the shop front

Before you commit, test the unglamorous cases: variable products (size, color), bundles, backorders, returns, and what the product page says when one location is empty and another is not. Each of these is where multi-location setups usually produce wrong numbers. Run them on a staging copy of the store, not on the live catalog.

What shoppers see also affects how the page performs in search. A clear availability message, consistent structured data and stable product URLs all help, and a guide on what WooCommerce SEO involves is a good complement once your stock logic is stable. For our own view, see our practical guide to e-commerce SEO for Italian online shops.

How PrestaShop handles several warehouses

PrestaShop approaches the problem differently. Its documentation for version 1.6 describes Advanced Stock Management, which lets you create warehouses and associate them with products, carriers and shops, so you can track inventory across different physical locations.

There is a historical point worth knowing. In a 2017 post on the stock strategy for version 1.7, PrestaShop’s product manager reported that multi-warehouse concerned 20% of the 65 merchants surveyed, and that multi-warehouse and ERP or il software WMS per il magazzino-style features were left out of the planned scope for that release. The core team’s priority was simpler stock visibility, editing and movement tracking.

The practical reading: multi-warehouse is a specialist requirement, and if you run a recent PrestaShop version you should verify what your installation includes, or whether a module or an external system covers the need. Our article on PrestaShop ERP integration, standard module or custom connector explains how to decide, and if you are weighing a platform change, see alternatives to PrestaShop for SMEs.

Where the stock logic should live

There are two architectures, and the choice shapes everything else.

The logistics trade press makes a related point about control. As an article from Warehouse Logistics explains, multi-warehouse control can be distributed across separate WMS instances or centralized in one system. The distributed model requires inventory integration, WMS and ERP coordination and standardized processes, while centralized control gives a single real-time operational view.

For an SME, we usually find the second model easier to live with: one place where purchases, production, sales and stock meet, with the shop receiving quantities from it. If you are mapping a WMS into the picture, the technical side is covered in our WMS and ERP integration guide.

Setting up multiple warehouses step by step

1. List your locations and their roles. For each one, note the address, whether it ships online orders, whether customers can collect there, and who is responsible for it.
2. Decide the master system. Choose where stock is the truth: the ERP or the store. Write it down. Two masters produce conflicts.
3. Clean the product codes. SKUs must be identical in the store and the management system. Duplicates and typos here cause most sync errors.
4. Load opening quantities per location. Do a physical count first, then load the figures in one controlled operation.
5. Set priority and routing rules. Define which location is used first, and what happens when it is out of stock.
6. Connect the systems. Use the extension’s API or a dedicated connector between store and ERP.
7. Test with real scenarios. Orders that split between two locations, returns to a different location, variable products, cancellations.
8. Go live with monitoring. Check the first weeks of orders daily and compare store, ERP and shelf.

Synchronizing stock without surprises

Sync is a set of decisions, not just a technical link. An Italian third-party logistics provider, in a post on ERP and warehouse integration, says a project should define which data is exchanged, how often stock updates occur, how setup and data formats are handled, who resolves mismatches, and how shipment tracking, delivery confirmations and transit times connect to distribution. Those are the right questions for your own project, whether the warehouse is yours or outsourced.

Applied to a store, they translate into a short checklist:

• Frequency. Near real time for fast-moving items, a scheduled batch for slow ones. Decide per product family if needed.
• Direction. Stock flows from ERP to store. Orders flow from store to ERP. Keep these separate.
• Safety buffer. Hold back a small quantity per location so that two orders do not claim the last unit.
• Exceptions. Define who is notified when a quantity goes negative or an order cannot be matched.
• Audit trail. Every movement should be traceable to an order, a transfer or an adjustment.

Our guides on WooCommerce and ERP integration and on automating e-commerce order management go deeper on the order side.

Assigning orders to the right warehouse

With stock in several places, each order needs a fulfillment location. The documentation for a multi-warehouse routing tool describes the two usual modes: automatic assignment based on predefined logic such as stock availability and proximity to the customer, or manual assignment from the order page.

Which rules fit you depends on your business. Common ones, in order of how often they are used:

1. Availability first: ship from the location that has every item in the order.
2. Proximity: among those, choose the one nearest to the delivery address.
3. Priority: if several qualify, use the location you rank first, for example the one with the best carrier rate.
4. Split shipment: only if allowed, ship partly from each location. Check the effect on shipping cost and on the customer experience.

Whatever you choose, the decision must also be written into the ERP, so that picking, delivery notes and invoicing refer to the same location. Invoicing is a particular concern in Italy: our article on integrating e-commerce and ERP with the SdI without rejections explains how to avoid errors on e-invoices.

What an Italian business should check first

An Italian logistics company, in a 2026 article on multi-warehouse setups in Europe, advises evaluating the geography of demand, the full cost to serve, operational readiness, safety stock set independently for each node, carrier surcharge zones, and whether the order and warehouse systems can route Italian orders and manage split inventory. It also points to Italian VAT, e-invoicing and CONAI packaging obligations as items to verify.

For your own checklist:

• Demand map. Where do your customers live, and would a second location really shorten delivery?
• Cost to serve. Count storage, handling, transfers between sites and returns, not just shipping.
• Tax and compliance. Confirm VAT treatment, e-invoicing and packaging obligations with your accountant for each location.
• System readiness. Can your store, ERP and WMS route orders and handle a split between sites?
• Personal data. Orders contain customer data, so the system holding them must meet GDPR. See GDPR compliance for ERP.
• Hosting. A stock sync that stops when the server is slow is a business problem. Reliable managed hosting belongs in the plan.

Our perspective

We have worked for 30 years on management software, and the pattern is consistent: multi-warehouse problems rarely start in the shop. They start when stock lives in several places that do not talk to each other.

That is why we do not treat the store extension as the answer on its own. An extension can show quantities per location, but the real picture also includes purchasing, production, accounting and shop sales. When those sit in one ecosystem, with the ERP as the master and WooCommerce or PrestaShop connected to it, the numbers customers see match the numbers your team works with.

Every client of ours has one dedicated consultant who learns how the business really works, rather than a call center that sees a ticket. For a multi-warehouse project this matters, because the rules (which location ships first, how transfers are booked, what happens on returns) are specific to each company and have to be configured, not assumed.

Our approach is to configure the management system around your processes, connect the store through an integration, and train your team so that the setup keeps working after go-live.

Claudio

How Linkware can help

If your stock is spread across locations and your store needs to reflect it, we can design the whole chain with you: the ERP configured on your processes, the connection to WooCommerce or PrestaShop, and the training that follows. Our LINKWARE ONE line combines il gestionale Mexal with WooCommerce, PrestaShop and CRM, and our WMS software for warehouse logistics covers locations and movements inside the warehouse.

Tell us how many locations you manage and which store you use, and ask for a demo on our website. A dedicated consultant will look at your processes before proposing anything.

Common mistakes to avoid

• Starting from the plugin instead of the process. Write down your routing and transfer rules first, then choose the tool.
• Two masters for the same quantity. If staff edit stock both in the store and in the ERP, they will overwrite each other.
• Ignoring variations. Size and color combinations multiply the number of stock lines per location.
• No buffer on fast sellers. Real-time sync still has a delay of seconds or minutes.
• Forgetting returns and transfers. Stock moving between locations must be booked, or the totals drift.
• Skipping staging tests. A wrong rule applied to live orders costs more than a day of testing.

If your business also sells on marketplaces, the same stock must feed those channels too. Our guide on marketplace and ERP integration shows how to keep them aligned.

FAQ

Does WooCommerce support multiple warehouses out of the box?

No. By default WooCommerce keeps a single global stock quantity for each product. To track separate quantities per location you add an extension, or connect the store to an ERP that holds stock by warehouse and sends it to the shop.

Does PrestaShop handle multiple warehouses natively?

PrestaShop 1.6 documents an Advanced Stock Management feature that creates warehouses and links them to products, carriers and shops. Later versions changed their stock strategy, so check what your own version offers, or plan to cover the need with a module or an ERP.

How do I stop two warehouses from selling the same last unit?

Use one master system for stock, set a small safety quantity per location and synchronize frequently on fast-moving items. Decide in advance who handles mismatches, so that exceptions are resolved by a person rather than discovered by a customer.

Should the ERP or the online store own the stock?

For a business with several locations, accounting and production, the ERP is normally the better master, because it sees every movement. The store then receives the available quantities through an integration and sends orders back.

Can I ship one order from two locations?

Only if your routing rules allow split shipments and your store and ERP can manage them. Check the effect on shipping costs and on invoicing before you enable it.

Recommended

• WooCommerce ERP Integration: A Practical Guide for Italian Businesses
• Warehouse Barcode System: How to Plan One in Italy