Inventory is where ecommerce businesses quietly lose money. Oversell and you disappoint customers and damage your marketplace metrics. Overstock and you have cash sitting on a shelf. Run out of a bestseller and you lose sales you had already paid to acquire.<\/p>\n
Shopify’s native inventory handles more than people assume, and a lot of stores buy an app to solve a problem they could solve with better process. But past a certain complexity, native tracking<\/a> does run out, and the signals are fairly clear.<\/p>\n Worth knowing before you shop, because it is more than the marketing of inventory apps implies.<\/p>\n Shopify tracks stock levels per variant, supports multiple locations<\/a> with stock allocated across them, decrements automatically on sale, prevents overselling when configured to, handles transfers between locations, and gives you basic reporting on stock levels and sell-through. Multi-location inventory in particular is a substantial capability that many stores never fully configure.<\/p>\n For a single-location store with a few hundred SKUs and straightforward replenishment, that is perfectly sufficient. Adding an app on top of it buys reporting you may not use.<\/p>\n These are the honest triggers, and they are mostly about complexity rather than size.<\/p>\n You are forecasting in a spreadsheet.<\/strong> If someone maintains a purchasing spreadsheet alongside Shopify because the native reporting cannot tell them what to reorder and when, that spreadsheet is the app you have not bought yet.<\/p>\n You manage purchase orders manually.<\/strong> Shopify has no proper purchase order workflow. If you raise POs to suppliers, track what is inbound, and reconcile deliveries by hand, that is a clear gap.<\/p>\n You hold stock in several places that need coordinating.<\/strong> Multiple warehouses, a 3PL plus your own stock, retail locations, and marketplace-held inventory all needing to stay aligned.<\/p>\n You manufacture or assemble.<\/strong> If you build products from components, you need to know component stock, not just finished goods. Shopify does not model bills of materials.<\/p>\n You sell across several channels.<\/strong> Marketplaces, wholesale, retail, and your own store all drawing from the same pool, where a sync failure means overselling.<\/p>\n Your SKU count has grown past what a person can hold in their head.<\/strong> Somewhere in the thousands, judgement-based replenishment stops working and you need demand forecasting.<\/p>\n You are regularly out of stock on bestsellers or sitting on dead stock.<\/strong> Both are symptoms of replenishment decisions made without good data.<\/p>\n If none of these apply, you probably do not need an app. If three do, you likely need more than an app \u2014 see the ERP section below.<\/p>\n Forecasting and replenishment.<\/strong> The core value. Using sales velocity, lead times, and seasonality to tell you what to order and when, rather than leaving it to someone’s judgement. This is what most stores are actually buying.<\/p>\n Purchase order management.<\/strong> Raising POs, tracking inbound stock, receiving against them, and reconciling discrepancies. A genuine gap in Shopify.<\/p>\n Multi-location and multi-channel sync.<\/strong> Keeping stock accurate across warehouses, 3PLs, retail, and marketplaces. The complexity here rises sharply with each additional channel, and sync reliability matters more than features.<\/p>\n Bundles and bills of materials.<\/strong> Handling products assembled from components, which matters for makers, kitting operations, and anyone selling bundles as covered in article 233.<\/p>\n Reporting depth.<\/strong> Stock ageing, dead stock identification, sell-through rates, stock turn, and margin by product. Shopify’s native reporting is thin here and the difference is useful for purchasing decisions.<\/p>\n Supplier management.<\/strong> Lead times, minimum order quantities, costs, and supplier performance tracking.<\/p>\n Barcode and warehouse operations.<\/strong> Scanning for receiving, picking, and stock counts, if you run your own warehouse.<\/p>\n Verify current details before publishing.<\/p>\n Lightweight forecasting apps<\/strong> focus on telling you what to reorder based on velocity and lead time, with purchase order basics. For a growing store whose main problem is replenishment decisions, these are the right level and are priced accessibly.<\/p>\n Full inventory platforms<\/strong> such as Cin7, Katana, and similar tools handle multi-location, multi-channel, purchase orders, bills of materials, and manufacturing workflows. These sit between an app and an ERP, and suit brands with real operational complexity but no appetite for an enterprise system.<\/p>\n Warehouse management systems<\/strong> go deeper on the physical operation \u2014 bin locations, pick paths, barcode scanning \u2014 and matter when you run your own warehouse at scale.<\/p>\n ERP systems<\/strong> such as NetSuite and Brightpearl subsume inventory into broader business management covering finance, purchasing, and operations. These are a different category of commitment entirely.<\/p>\n Shopify’s own tooling<\/strong><\/a> continues to develop, and it is worth checking current native capability before buying, particularly around multi-location and stock transfers.<\/p>\n Two situations where buying an inventory app is the wrong move.<\/p>\n When the real problem is process.<\/strong> Plenty of stores with inventory chaos have accurate systems and undisciplined habits \u2014 stock not counted, receipts not recorded promptly, adjustments made without notes, several people changing numbers with no accountability. An app will not fix that and will give the disorder a more expensive home. If your counts do not match reality, start with process.<\/p>\n When you actually need an ERP.<\/strong> If inventory complexity comes with equivalent complexity in purchasing, finance, manufacturing, and multi-channel operations, bolting an inventory app onto Shopify creates another system to reconcile. At that point an ERP with a proper Shopify integration<\/a> is the coherent answer, and it is a considerably bigger project that deserves scoping as such.<\/p>\n The middle case \u2014 where an app is right \u2014 is a store with real replenishment and purchasing needs but whose finance and operations are otherwise manageable.<\/p>\n A skincare brand with around four hundred SKUs across their own warehouse and a 3PL came to us about frequent stockouts on bestsellers while holding substantial dead stock.<\/p>\n Their process was revealing. Shopify held stock levels. A spreadsheet held reorder points, supplier lead times, and purchase orders. A second spreadsheet tracked what was inbound. The two were updated by different people at different times, and neither matched Shopify reliably.<\/p>\n The stockouts were not a forecasting failure exactly \u2014 they were the consequence of nobody having a single trustworthy view of what they had, what was coming, and what was selling.<\/p>\n We implemented an inventory platform<\/a> handling forecasting, purchase orders, and multi-location sync, and connected it properly to Shopify and their 3PL. The spreadsheets were retired. Replenishment became data-driven rather than reactive.<\/p>\n Stockouts on their top products largely disappeared within two quarters, and dead stock reduced as purchasing decisions started reflecting actual sell-through.<\/p>\n The part worth noting: the platform cost less than the value of the stock they had been writing off, and considerably less than the sales they were missing on out-of-stock bestsellers. Inventory tooling is one of the few app categories where the return is usually calculable in advance.<\/p>\n Count regularly.<\/strong> Cycle counting \u2014 checking a subset frequently rather than everything annually \u2014 keeps your data honest. No system survives inaccurate physical counts.<\/p>\n Record lead times accurately, including variability.<\/strong> A supplier who usually takes three weeks and occasionally takes six needs the six factored into your reorder point.<\/p>\n Set reorder points deliberately per product.<\/strong> Fast movers and slow movers need different logic, and a single rule across the catalogue guarantees you are wrong on both ends.<\/p>\n Review dead stock monthly.<\/strong> Cash tied up in stock that is not moving is the least visible cost in ecommerce, and the sooner you discount or bundle it, the more you recover.<\/p>\n Watch stock turn, not just stock level.<\/strong> How quickly inventory converts to cash is the number that matters for a growing business.<\/p>\n Reconcile channels regularly.<\/strong> If you sell in several places, verify that system counts match reality on a schedule rather than discovering a drift during a busy period.<\/p>\n Whatever system you run, these are the metrics that turn inventory from a record into a decision tool.<\/p>\n Stock turn.<\/strong> How many times you sell through your average inventory in a year. Low turn means cash trapped on shelves; very high turn may mean you are stocking out. It is the single best summary of how hard your inventory is working.<\/p>\n Sell-through rate by product.<\/strong> What percentage of stock received has sold in a given period. This identifies both your winners and the products quietly failing.<\/p>\n Days of cover.<\/strong> How long current stock will last at recent sales velocity. More actionable than a raw stock number, because it tells you when to act rather than what you have.<\/p>\n Stockout frequency and duration on top sellers.<\/strong> Every day a bestseller is unavailable is lost revenue on traffic you already paid for. This is usually the most expensive inventory failure and the least tracked.<\/p>\n Dead stock value.<\/strong> Cash sitting in products that have not moved in ninety days or more. Reviewing this monthly and acting on it \u2014 discount, bundle, or write off \u2014 recovers working capital that would otherwise sit still indefinitely.<\/p>\n Lead time accuracy.<\/strong> Actual supplier delivery times against promised ones. If your reorder points assume three weeks and reality is five, you will stock out regardless of how good your forecasting is.<\/p>\n Inventory accuracy.<\/strong> How closely system counts match physical counts. Below a high percentage, every other number here is unreliable.<\/p>\n Most stores track stock level and nothing else, which tells you what you have but nothing about whether it is the right thing.<\/p>\n Selling in more than one place multiplies the ways inventory can drift, and it is worth understanding the failure modes before they bite.<\/p>\n Sync latency causes overselling.<\/strong> If your marketplace updates stock every fifteen minutes and you sell three units in five, you have promised something you do not have. The faster your sales velocity, the more the sync interval matters. Ask any integration<\/a> what its actual update frequency is, not what it claims in marketing.<\/p>\n Buffer stock protects you and costs you.<\/strong> Holding back a few units per channel prevents overselling and means you sit on unsold stock. For fast movers a small buffer is sensible insurance; applied indiscriminately across the catalogue it quietly locks up meaningful capital.<\/p>\n Allocation versus shared pools.<\/strong> You can either allocate specific stock to each channel or let all channels draw from one pool. Allocation prevents overselling and creates the situation where one channel sells out while another holds stock. A shared pool is more efficient and requires reliable, fast syncing. Most stores should use a shared pool and invest in the sync.<\/p>\n Returns re-entering stock.<\/strong> A returned item needs to become available again promptly and in the right location. Delays here are a common and invisible source of understated inventory.<\/p>\n Wholesale allocations.<\/strong> A large trade order committing most of your stock should be visible to your consumer storefront before it sells the remainder. This is a frequent gap for brands running both.<\/p>\n Marketplace-held inventory.<\/strong> Stock sitting in a marketplace’s fulfilment network is often invisible to your other channels. Decide deliberately how it is represented rather than letting it fall out of your numbers.<\/p>\n<\/span>What Shopify does natively<\/span><\/h2>\n
<\/span>The signals you have outgrown it<\/span><\/h2>\n
<\/span>What separates inventory apps<\/span><\/h2>\n
<\/span>Where the main options sit<\/span><\/h2>\n
<\/span>When an app is not the answer<\/span><\/h2>\n
<\/span>A worked example: the spreadsheet that was the system<\/span><\/h2>\n
<\/span>Getting value from whatever you use<\/span><\/h2>\n
<\/span>Side by side<\/span><\/h2>\n
\n\n
\n \nCapability<\/th>\n Shopify native<\/th>\n Forecasting apps<\/th>\n Inventory platforms<\/th>\n ERP<\/th>\n<\/tr>\n<\/thead>\n \n Stock levels per variant<\/td>\n Yes<\/td>\n Yes<\/td>\n Yes<\/td>\n Yes<\/td>\n<\/tr>\n \n Multi-location<\/td>\n Yes<\/td>\n Yes<\/td>\n Yes, advanced<\/td>\n Yes<\/td>\n<\/tr>\n \n Prevent overselling<\/td>\n Yes<\/td>\n Yes<\/td>\n Yes<\/td>\n Yes<\/td>\n<\/tr>\n \n Demand forecasting<\/td>\n No<\/td>\n Core feature<\/td>\n Yes<\/td>\n Yes<\/td>\n<\/tr>\n \n Purchase orders<\/td>\n No<\/td>\n Basic<\/td>\n Full workflow<\/td>\n Full workflow<\/td>\n<\/tr>\n \n Bills of materials<\/td>\n No<\/td>\n No<\/td>\n Usually<\/td>\n Yes<\/td>\n<\/tr>\n \n Manufacturing<\/td>\n No<\/td>\n No<\/td>\n Some<\/td>\n Yes<\/td>\n<\/tr>\n \n Multi-channel sync<\/td>\n Basic<\/td>\n Limited<\/td>\n Strong<\/td>\n Strong<\/td>\n<\/tr>\n \n Stock ageing & turn reporting<\/td>\n Thin<\/td>\n Good<\/td>\n Strong<\/td>\n Strong<\/td>\n<\/tr>\n \n Supplier management<\/td>\n No<\/td>\n Basic<\/td>\n Yes<\/td>\n Yes<\/td>\n<\/tr>\n \n Barcode \/ warehouse ops<\/td>\n No<\/td>\n No<\/td>\n Some<\/td>\n Often<\/td>\n<\/tr>\n \n Finance integration<\/td>\n Via apps<\/td>\n Limited<\/td>\n Good<\/td>\n Native<\/td>\n<\/tr>\n \n Typical cost<\/td>\n Included<\/td>\n Low<\/td>\n Moderate<\/td>\n Significant<\/td>\n<\/tr>\n \n Suits<\/td>\n Single location, simple replenishment<\/td>\n Replenishment decisions<\/td>\n Multi-location, purchasing, assembly<\/td>\n Complex operations end to end<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n <\/span>The numbers worth tracking<\/span><\/h2>\n
<\/span>Multi-channel: where inventory goes wrong fastest<\/span><\/h2>\n