Local Inventory Setup for Ecommerce
A customer who drives to your shop for an item the website showed in stock, and finds an empty shelf, does not try again. This guide sets up stock per location in Shopify or WooCommerce, gets it onto Google, and sizes the safety stock that covers the lag.
Local inventory for ecommerce means your website, your staff and Google all see how many units of each product sit in each physical place you sell from: the shop, the second shop, the stockroom behind the garden center. A single stock number for the whole business is fine for a webshop that ships from one shelf. The moment you offer pickup, deliver from two places, or want your products to appear in Google’s local results, that single number starts telling lies.
This page covers stock per location in Shopify and WooCommerce, local inventory in Google Merchant Center, the lag between a sale and an updated count, and a safety stock rule with worked numbers. The pickup routine that uses these counts sits in our click and collect guide.
Which counts does a local store need to keep?
Three groups read your stock, and each needs a slightly different number.
| Who reads it | What they need | What goes wrong without it |
|---|---|---|
| Website checkout | Units free to sell at each pickup or delivery location | Pickup offered at a shop that has none; one unit sold twice |
| Staff | Units on the shelf, units promised to orders, units damaged or held back | Staff sell a unit that belongs to an online order |
| Google’s local listings | Availability and quantity per store, matched to your Business Profile | Shoppers see “in stock” for an empty shelf |
Shopify’s inventory states give these numbers names worth borrowing on any platform. On hand is everything at the location. Committed is set aside for unfulfilled orders and cannot be sold. Unavailable is held for other reasons, with damaged stock and safety stock as Shopify’s own examples. Available is what is left to sell. Once your team uses those four words, most stock arguments end quickly.
How does Shopify track stock per location?
In Shopify, a location is any physical place where you sell products, fulfill orders or stock inventory: a shop, a warehouse, a pop-up. Shopify tracks inventory separately at each one, can assign online orders to the location closest to the customer, and connects shop locations to Shopify POS for in-person sales. Order routing rules can assign online orders automatically by stock and distance.
What to set up, from Shopify’s location setup page:
- Add each shop and stockroom under Settings, then Locations.
- Leave “Inventory at this location is available to fulfill online orders” switched on for places that ship or hand over online orders, and switch it off for places that should not, such as a market stall that only sells in person.
- New products start at a quantity of 0 at every new location, so enter real counts before you switch on pickup there.
The number of active locations depends on the plan. Shopify’s setup page lists 2 for Starter, 10 for each plan from the next tier up to Advanced, and 200 for Shopify Plus (checked November 2026). Apps that stock inventory for you, such as a fulfillment service, are listed as separate locations and do not count toward the limit.
What are the WooCommerce options for more than one location?
WooCommerce’s built-in stock management, described in its inventory settings, keeps one quantity per product or variation. You enter the count and WooCommerce subtracts items as they sell. It adds useful controls: email alerts at a low-stock threshold, an out-of-stock threshold, and a “hold stock” timer that releases items from unpaid orders after a set number of minutes.
What it does not have is a count per shop. The Local Pickup locations you add at checkout carry an address and instructions, not stock. For separate counts you need an extension or a connected inventory or POS system. One example on the WooCommerce site is Pickup Location Stock, which keeps a separate quantity for each collection location, shows customers only the locations that can fulfill the whole cart, and reserves the units when the order is placed. Its documentation notes that pickup stock works alongside the product’s normal WooCommerce stock, so the product must still be in stock under the standard rules.
| Your set-up | WooCommerce approach |
|---|---|
| One shop, one stockroom in the same building | Built-in stock, one count |
| One shop plus pickup at a second shop with its own stock | A pickup stock extension |
| Several shops with tills | A POS or inventory system that syncs stock to WooCommerce per location |
If you are still choosing a platform, this difference weighs heavily for multi-shop businesses; our Shopify vs WooCommerce guide compares both for local sellers.
How do your products get into Google’s free local listings?
Google Merchant Center offers two ways to show in-store products: free local listings, at no cost, and paid local inventory ads. Its overview page lists the countries where each is available. The local listings policies add one condition that rules out pure webshops: you need a brick and mortar location where customers can visit, view and buy the item.
The data has two halves. Your normal product data describes each product. A local inventory source then says, store by store, what is there. Per Google’s local inventory specification, each row carries:
- id: the same ID as in your main product data.
- store code: case-sensitive, and it must match the store code on your Google Business Profile.
- availability: in stock, limited availability, on display to order, or out of stock.
- quantity (optional), price if it differs by store, and pickup details if customers can buy online and collect.
One rule in that specification shapes your safety stock: when you send both availability and quantity, Google uses the lower of the two, and treats 3 or more as in stock, 1 to 2 as limited availability, and 0 as out of stock.
The upload options include letting Google read in-store availability from your product pages, a file uploaded once or fetched from a URL every 24 hours, the Merchant API, a local data provider, and website-reported autofeeds through Google Tag Manager. Google asks for local inventory data to be refreshed daily, and suggests waiting 24 hours after linking accounts before the first upload. Shops whose POS supports it can instead connect through the Local Inventory app in their Business Profile, covered in our Business Profile guide.
How fresh does the stock count need to be?
Every count has an age. Map where yours gets old, then decide which gaps matter.
| Link in the chain | Typical lag to check | How to find out |
|---|---|---|
| Till sale to online store | Close to zero when till and website share one system; test any connector | Sell one unit at the till and time the website change |
| Online store to Google | Up to 24 hours with a daily file | Compare the Merchant Center product with the shelf at closing time |
| Returns and damaged items | Until someone updates the count | Check how many returns sit unprocessed at closing |
| Transfers between shops | Until the receiving shop books them in | Count boxes in transit on a Monday |
| Deliveries from suppliers | Until the goods are booked in | Note the hours between unpacking and booking |
Rule of thumb: the faster a product sells, the shorter its lag must be. A product that sells once a month can live with a daily update. A product that sells twelve times a day needs the till and website on the same count within minutes, and a buffer for the Google feed.
What goes wrong when the count lags behind the shelf?
A lag turns into four kinds of cost, each easy to spot in a shop’s week.
- The wasted trip. A customer sees “in stock” on Google at 8:00, drives over at 16:00, and the last unit sold at noon. That customer stops trusting your listings.
- The double sale. An online pickup order and a walk-in buy the same last unit within the same hour. Someone gets a refund and an apology.
- The phantom unit. A damaged item stays in the count for weeks. The website keeps selling it, and staff cancel every order.
- The listing problem. Google’s policies require accurate, up-to-date quantity and price, and retailers may be asked to take part in inventory verifications. Google’s upload guide warns that missing or incorrect local data can lead to disapprovals or limited visibility.
Each of these has a different fix: a shorter lag for the first two, a habit of booking damaged stock as unavailable for the third, and a buffer in the Google feed for the fourth. The next section covers the buffer.
How much safety stock should each location hold back?
Safety stock rule: hold back the units you expect to sell during the longest lag, plus the typical miscount for that product. Round up.
Example shop: a hardware store with two shops. Its Google feed refreshes once a day at 6:00, and its till and website share one system. Last quarter’s stock counts showed an average miscount of 1 unit on small items and none on large ones.
| Product, location | Sales per day | Longest lag | Expected sales in lag | Miscount | Safety stock |
|---|---|---|---|---|---|
| Paint 2.5 l, shop A | 4 | Google feed: 1 day | 4 | 1 | 5 |
| Wood screws box, shop A | 12 | Google feed: 1 day | 12 | 1 | 13 |
| Ladder, shop B | 0.2 | Google feed: 1 day | 0.2, round to 1 | 0 | 1 |
How the store uses it: at 6:00, shop A holds 9 tins of paint. The feed sends quantity 9 minus 5 = 4, which Google shows as in stock. By closing, the shop has sold four tins and still has five on the shelf, so nobody arrived to an empty shelf. If the morning count were 7, the feed would send 2, Google would show limited availability, and shoppers would know to hurry or call.
The website buffer can be smaller than the Google buffer, because the website and till share one count. Our click and collect guide works out that smaller pickup buffer.
How do you keep counts right without closing the shop?
A full stocktake once a year leaves eleven months of drift. Cycle counting spreads the work: count a few products every day, so every product gets counted on a schedule that matches its speed.
- Sort products into three groups by units sold per week: fast (top 10% of products), steady, slow.
- Count fast sellers weekly, steady ones monthly, slow ones each quarter. A shop with 600 products (60 fast, 120 steady, 420 slow) counts about 60 + 30 + 32 = 122 products a week, around 25 per working day.
- Record every difference with a reason: theft, damage, booking error, unrecorded return.
- Fix the cause, not only the number. Ten unrecorded returns a month means the returns shelf needs a daily routine.
- Recalculate safety stock each quarter from the real miscount figures.
Give one person ownership of stock data at each location. When the count is everyone’s job, damaged units sit in the count until a customer finds them. If you deliver from more than one location, set each location’s delivery zones only after its counts hold up for a month.
FAQ
Do I need Merchant Center to show my stock on Google?
Free local listings run through Merchant Center. Shops with a compatible POS and manufacturer barcodes can also connect the Local Inventory app from their Business Profile, which creates the product feed for them and then manages products through Merchant Center.
Does WooCommerce track stock per shop out of the box?
No. Built-in stock management keeps one quantity per product or variation. Separate counts per location come from an extension, such as Pickup Location Stock, or from a POS or inventory system connected to WooCommerce.
How many locations can a Shopify store have?
It depends on the plan. Shopify’s location setup page lists 2 locations on Starter, 10 on each plan from the next tier up to Advanced, and 200 on Shopify Plus (checked November 2026). Deactivated locations do not count.
Should my warehouse be a location?
In Shopify, yes, if it holds stock, since locations exist to track stock per place. For Google’s local listings, no: those need a store customers can visit and buy from, so a warehouse without a counter stays out of the local inventory feed.
How frequently should the Google local inventory feed update?
At least daily, which is what Google asks for. Fast-selling products justify more frequent updates through the Merchant API or website-reported autofeeds; for the rest, a daily file plus safety stock does the job.
What happens if Google finds my local stock is wrong?
Google’s policies for local listings require accurate quantity and price, and retailers can be asked to take part in inventory verifications. Missing or incorrect local data can lead to product disapprovals or limited visibility.
Should customers see exact quantities?
Showing “only 2 left” helps on slow, unique items and invites disappointment on fast sellers when the count lags. WooCommerce lets you show stock always, only when low, or never; pick “only when low” if your counts are reliable.
What should you do next?
List every place that holds stock, set each up as a location (or choose the WooCommerce extension or POS that will do it), and time one test sale from till to website to Google. Then fill in the safety stock table for your twenty fastest sellers and start a weekly cycle count. If you want help turning this into a brief for a developer or inventory provider, send us a note through the MarketPulse contact form.