Stock in four places, and one of them is wrong
Shops, a warehouse and a stockroom, each running out of different things. Per-location planning, counts that reconcile properly, and transfers you can value.
- Two or more locations
- Retail floor and back stock
- Counts that never quite agree
A store-wide number hides the truth
Two hundred units across the business sounds healthy right up until you notice one hundred and ninety of them are in the warehouse and the shop that sells them has ten.
- Demand differs by location. The same product sells at different rates in different places, and a single blended rate is wrong for all of them.
- Shelf space is the real constraint. A retail floor holds what fits, not what the forecast wants. Planning it on velocity alone produces numbers nobody can put out.
- Counts drift, then everything downstream is wrong. Once the system and the shelf disagree, every reorder decision built on that number is compromised too.
| Item | On hand | Min | Max | Top up |
|---|---|---|---|---|
| Cream Cap CRM-CAP-OS | 14 Low | 20 | 50 | 36 |
| Waffle Throw · Oat WAF-OAT-01 | 38 | 15 | 40 | 0 |
| Rope Basket · S ROP-BSK-S | 6 Below min | 12 | — | — |
| Linen Napkin Set LIN-NAP-4 | 9 | — | 24 | 15 |
Plan each location on its own terms
Every item at every location gets its own replenishment method, its own numbers and its own reorder date.
- Forecast the warehouse, set levels for the floor. One product can be forecast-driven at the distribution centre and run on fixed min/max levels in the shop.
- Attribute demand where it was fulfilled. Sales can be attributed to the location that filled the order, or pooled across all of them, depending on how your stock actually moves.
- Cycle count without disruption. Count a vendor, a category or a shelf on a weekly rotation. Only what you counted changes, so the count is safe to run during trade.
- Counted against on hand, not available. Units committed to unfulfilled orders are still physically on the shelf. Reconciling against available invents shrinkage that was never there.
Common questions
Does Stockie work with Shopify POS?
Stockie reads Shopify inventory and orders, so POS sales feed your forecasts like any other channel and POS locations plan like any other location. There is no separate POS extension.
Can we transfer stock between locations in Stockie?
You create transfers in Shopify and Stockie mirrors them, valuing what moved at the cost at the time it moved. It is deliberately read-only. Transfers reporting is in beta on Pro Plus.
Can different staff count different locations?
Yes. Stocktakes are per location, so different sites can run independent counts. Multiple staff can also count together in the same stocktake on different devices, with their scans combined and counts synced.
What you would actually use
Min/max levels
For shelf-constrained stock that demand forecasting gets wrong. Set them per item and location, in bulk or by CSV.
ProStocktakes
Full and cycle counts with barcode scanning, multiple staff counting together, variance review and cost impact before you apply.
Pro PlusTransfersBeta
Shopify transfers mirrored into Stockie, costed at the value that actually moved between locations.
Pro PlusAdjustments
Damage, shrinkage, donations and returns, recorded with a reason, a staff member and notes, then synced to Shopify.
Pro PlusSound like your store?
Install Stockie and run it against your own catalogue for a fortnight. If it does not fit, uninstalling costs nothing.