What Shopify's native admin can and cannot do for inventory and reorder

Short answer: Shopify's native admin is a real inventory tracker. It shows on-hand quantity by location, logs inventory history, handles transfers between locations, and its Sidekick assistant can answer one-off questions like "how many units of SKU X do I have left?" As of 2026 it even supports basic purchase orders with a receive step. What it doesn't do is maintain a standing reorder point per SKU computed from your actual sales velocity, surface a days-of-cover view across your catalog, or provide a PO lifecycle with draft, send, partial-receive, and close stages tied to your supplier lead times. Those are the gaps. This page covers what's genuinely there, what's genuinely absent, and what to do about each.

What Shopify native admin does well

Start here, because a lot of the "Shopify can't do inventory" framing is simply out of date.

On-hand tracking by location. Every SKU in your catalog has a live on-hand count, tracked per location. You can see it in the product detail view, in the Inventory section of admin, and in bulk inventory CSV exports. For a single-location store carrying a manageable number of SKUs, that view is usually enough to notice when something is getting low, if you check it.

Inventory history and adjustments. Shopify logs every inventory change: sales, manual adjustments, returns, transfers in and out. The history view is per-product, per-location, and goes back 90 days. That's a useful audit trail, and it's one that a lot of merchants don't know they have.

Transfers between locations. If you move stock from a warehouse to a retail location, Shopify tracks it natively as an inventory transfer, with origin, destination, and expected-arrival date. Items stay in "incoming" status until you accept the transfer. Basic but functional.

Basic purchase orders with a receive step. As of 2025, native Shopify supports a simplified purchase-order workflow. You can create a PO for a supplier, add line items, and mark it received when the goods arrive. For merchants with one or two suppliers, infrequent reorders, and a small catalog, this handles the paperwork.

Sidekick, for one-off questions. Shopify's Sidekick assistant can answer ad-hoc inventory queries. "How many units of my best-selling jacket do I have?" is a fair question to ask it, and it will usually give you the right number. For an occasional spot-check that's genuinely useful.

What native admin doesn't do

1. Standing per-SKU reorder points from your sales velocity

This is the main gap. Shopify will show you on-hand. It won't tell you whether that number is fine or dangerously low relative to how fast the SKU sells and how long it takes to restock.

A reorder point is just: average daily sales × supplier lead time + safety stock. For a product selling 8 units a day with a 10-day supplier lead time and a 5-day safety buffer, the reorder point is (8 × 10) + (8 × 5) = 120 units. When on-hand drops to 120, you place the order.

Native admin doesn't compute or display this. It doesn't keep a running "days of stock remaining" figure per SKU. It doesn't know your supplier lead times or your safety preferences. So a merchant checks on-hand, sees 140 units, and has no way to know from the admin screen whether that's two weeks of stock or two months. They find out at 0.

Sidekick can estimate if you ask it the right question, but that's manual, per-product, and depends on you knowing when to ask. It isn't the same as a dashboard that has already done the math for every SKU before you open the app in the morning.

2. Low-stock alerts keyed to a computed reorder point

Shopify has a low-stock inventory report, and some themes will surface a "low stock" badge on the storefront. But the threshold that triggers "low" is fixed at a number you set per product by hand, not derived from velocity. It doesn't know that a SKU selling 20 units a day needs 300 units in buffer and a SKU selling 2 a day needs 30. You set both, or you leave them blank.

For a store with 15 SKUs and stable sales, manually keyed thresholds work. For 200 SKUs with varying velocities and multiple suppliers on different lead times, keeping those numbers accurate is itself a job, and an easy one to let slide.

3. Days of cover and velocity views

Native admin has no "days of stock remaining" column in the inventory view. It doesn't sort your catalog by which SKU runs out soonest. It doesn't surface which products need attention today versus which are fine for 90 days.

Merchants who want this view typically build a spreadsheet, export inventory as CSV, pull order history separately, and compute it. That works, once, and then it needs refreshing, manually, and usually doesn't get refreshed as often as it should.

4. A purchase-order lifecycle with supplier lead times and partial receiving

Native Shopify's purchase orders handle the basics. Where they thin out is when the order gets complicated: partial shipments arriving on different dates, suppliers with different lead times informing when you should reorder next, minimum order quantities that interact with the quantity you actually need, and a "close" step that finalizes what arrived against what was ordered.

If your supplier ships in two batches and you receive part of the order Tuesday and the rest Friday, native POs don't have clean partial-receive tracking. The PO workflow is flat: send, receive, done.

5. No Stocky replacement since February 2026

The free Stocky app, which handled reorder points and purchase orders inside Shopify for years, was removed from the admin on February 2, 2026. Its APIs go dark on August 31, 2026. Merchants who relied on Stocky for the everyday "when and how much" decision are now using a combination of native admin (for on-hand) and spreadsheets or a replacement app for the rest. Native Shopify absorbed Stocky's very basics (simple POs); it didn't absorb the reorder-point logic that made Stocky useful.

Why the gap matters in practice

The feedback that comes up repeatedly in r/shopify threads on Stocky replacements isn't "Shopify shows me nothing," it's: "Shopify tells me what I have, but it can't tell me if that's enough." That's the precise shape of the gap. On-hand is known. Whether on-hand is above or below the number that matters, and what to do about it, isn't answered.

A store carrying 50 SKUs checking inventory daily by eye will catch problems most of the time, and miss them occasionally, and eventually find out they were out of stock for three days from a customer complaint. A store carrying 300 SKUs can't check by eye, and a spreadsheet updated weekly doesn't give the same visibility as a number that updates every time an order comes in.

The "Caught in time" stat that Parwise tracks is a records-backed count: SKUs that hit their reorder point, got a purchase order raised, and came back above stock before selling out. It's recorded, not estimated. The only way that number exists is because something was watching.

What Parwise adds on top of native

Parwise is a standing layer on top of Shopify's inventory tracking. It doesn't replace native on-hand tracking: Shopify's number is always the source of truth. What it adds is the math and the workflow that native doesn't compute.

Low-stock alerts and an on-hand dashboard, free. A daily view of what's about to run out, ranked by urgency. Not the same as checking inventory one product at a time.

A reorder point on every SKU, computed from your real sales velocity, free. The formula is average daily sales (trailing 30-day window) × lead time + safety stock. It's displayed, not buried. Lead time and safety stock are editable per SKU or as a store-wide default, so you set your actual supplier lead time once and the reorder points update from there. This is transparent velocity math, not machine learning and not seasonal forecasting. It's a trailing average, which means it reflects recent reality, not a prediction of future demand. If you're heading into a known peak, you raise the reorder point by hand. The math is honest about what it is.

Days of cover and velocity view, free. How many days of stock you have left, at the current sales rate, per SKU. The "what needs attention today?" question, answered before you have to ask it.

Purchase orders with a real receiving lifecycle, Pro ($39/mo). Draft, send to supplier, partial-receive, close. Parwise pre-fills the recommended order quantity (roughly two reorder points of cover, minus what you have on hand, floored at your supplier's MOQ) so you're adjusting a sensible number rather than guessing from blank fields. Supplier lead times and minimum order quantities are stored per supplier and inform the recommendation.

Supplier management, Pro ($39/mo). Lead time, MOQ, and unit cost per supplier, linked to the products they supply. When a supplier's lead time changes, you update it once and every reorder point that depends on that supplier updates automatically.

Multi-location per-location visibility and automated supplier-feed ingestion, Scale ($79/mo). If you have more than one location and want the reorder view broken out per location rather than aggregated, that's Scale. Supplier-feed automation (bulk supplier catalog sync) is also Scale.

Flat pricing: $0 / $39 / $79/mo. The bill doesn't grow if your revenue or order volume or SKU count grows. What you pay for is the feature tier, not a percentage of the business.

No customer personal data. Parwise reads orders for SKU, quantity, cost, and date. It never requests read_customers and never stores customer names, emails, or addresses. Raw order webhooks are purged within 7 days.

The honest comparison: native + Parwise vs native alone

Native admin is not a failed product. It's the right tool for what it does, which is accurate on-hand tracking, basic transfers, inventory history, and now a simplified PO workflow. For a store with a short, stable catalog and a single supplier, native alone is often enough, especially if the merchant checks it regularly.

The case for adding Parwise starts when the manual check doesn't scale. When the question isn't "how many do I have?" (Shopify answers that) but "should I be ordering right now, and how much?" (Shopify doesn't). When a supplier's lead time is 3 weeks and finding out you should have ordered last week is a real cost. When 50 SKUs have 50 different velocity profiles and updating reorder thresholds by hand is a task that keeps slipping.

In those cases, Parwise's job is to make sure you never have to discover a stockout from a customer complaint.

FAQ

Does Shopify have reorder points natively? No. Shopify's admin tracks on-hand inventory and lets you set a manual low-stock threshold per product, but it doesn't compute or maintain a reorder point from your sales velocity. That calculation (average daily sales × supplier lead time + safety stock) requires knowing how fast each SKU sells and how long your supplier takes to deliver, which Shopify admin doesn't keep per-SKU. Apps like Parwise add that layer.

Can Shopify Sidekick help with reorder decisions? Sidekick can answer one-off questions about on-hand quantities and recent sales if you ask it directly. It doesn't maintain a standing per-SKU reorder point across your catalog or alert you when a SKU drops below its reorder level. It's a query interface, not a monitoring layer.

What happened to Stocky, the free Shopify reorder app? Shopify removed Stocky from the admin on February 2, 2026. The Stocky APIs go dark on August 31, 2026. Shopify's native admin absorbed Stocky's simplified purchase-order workflow but not the reorder-point logic. Parwise is one direct replacement for the reorder and replenishment side of what Stocky did.

Does native Shopify support purchase orders? Yes, natively since 2025. You can create a basic PO, add line items, and mark it received. The native workflow doesn't cover partial receiving across multiple shipments, or tie the PO to a supplier's specific lead time for future reorder planning. Parwise's Pro tier ($39/mo) adds draft, send, partial-receive, and close stages, plus the recommended order quantity pre-filled from the reorder math.

What does Parwise add to Shopify's native inventory tracking? Four things native doesn't do: (1) a standing reorder point per SKU computed from sales velocity, editable lead time, and safety stock; (2) a days-of-cover view showing how long stock will last at current sales rates; (3) low-stock alerts keyed to the computed reorder point rather than a manually set threshold; and (4) a purchase-order lifecycle with draft, send, partial-receive, and close stages tied to supplier lead times and MOQs. Native tracking (on-hand, history, transfers) remains the source of truth; Parwise adds the layer on top.

Does Parwise use AI or machine learning for reorder predictions? No. Parwise's reorder point is transparent velocity math: average daily sales (trailing 30-day window) × supplier lead time + safety stock. The formula is displayed per SKU and every input is editable. It's a trailing average, which means it reflects recent sales history, not a forecast of future demand. If your sales are strongly seasonal and anticipating the curve matters, a dedicated demand-planning platform with machine-learning forecasting (such as Inventory Planner, Prediko, or Cogsy) is a better fit. Parwise earns its keep on steady-selling products where transparent, editable math is more useful than a black box.

Does Parwise store customer data? No. Parwise reads Shopify orders for SKU, quantity, cost, and date. It never requests the read_customers scope and never stores customer names, emails, or addresses. Raw order webhooks are purged within 7 days.