Supplier lead times and MOQs: planning Shopify reorders around them

For most of the last decade the question a small shop asked its supplier was “how much?”. In 2026 the question that hurts is “when?”. Netstock's 2026 Benchmark Report, published on 23 September and built on platform data from more than 2,500 SMBs, found that no single pressure dominates inventory planning any more: supplier lead-time swings (29%), raw material costs (23%), freight and shipping costs (22%) and demand shifts (21%) came out almost level. Underneath that, nearly three-quarters of SMBs named lead-time variability as a planning challenge, 63% pointed at long lead times, and 60% at minimum order quantities.

That last figure is the one to sit with. MOQs and lead times are not market conditions you can wait out; they are terms your suppliers set, and they belong in the same place as your reorder maths. On Shopify they usually are not. This post is about where they should live, how Restock Ops uses them when it suggests a reorder, and what to do when the supplier's promised lead time and the actual one drift apart.

Where lead time and MOQ live in a Shopify store today

Shopify's native purchase order has a supplier, a destination, line items with cost, an estimated arrival date, and shipping and tax fields. Shopify's help centre describes the flow in Creating and managing purchase orders. What it does not have is a place to record, on the supplier, how long that supplier normally takes, or, on a product, the smallest quantity the supplier will sell you. Every PO starts from a blank estimated arrival date, and the person creating it either remembers the lead time or looks it up in an email thread.

So the information lives in heads and spreadsheets. That works with one buyer and eight suppliers. It stops working when the buyer is on holiday, when a supplier changes its terms, or, as the Netstock data suggests, when the lead time that was reliably four weeks last year is now anywhere between three and nine.

Putting the terms on the supplier and the item

Restock Ops separates two kinds of information. On the supplier record: lead time in days, minimum order value, payment terms and free-text notes for everything that does not fit a field (“ships Tuesdays only”, “add 2 weeks in Golden Week”). On each supplier item, the link between a supplier and one of your variants: supplier SKU, unit cost, MOQ and case size, plus the date you last ordered it from them.

The split matters because the two change at different speeds. A supplier's lead time is a property of the supplier and its route to you; you update it when the route changes. MOQ and case size are per product, and a supplier will happily sell you 200 of one SKU and insist on 1,000 of another. Keeping MOQ on the item rather than in the supplier notes is what lets the reorder report round each line correctly instead of leaving you to do it by hand.

None of this touches Shopify's inventory. Quantities stay in Shopify as the source of truth; the supplier terms are app data, shown wherever you build a PO or look at a product.

How a reorder suggestion uses them

The reorder report in Restock Ops does one simple calculation per item, and it is worth spelling out because the supplier terms sit inside it.

1. Velocity: units sold in the last N days divided by N. N is a shop setting; 30 days is the default. If your store has not granted order access to the app yet, you type a manual velocity per item and the rest still works.
2. Cover: how many days of stock you want on the shelf after the next delivery arrives. Set once for the shop, overridable per item.
3. Target stock: velocity multiplied by (supplier lead time plus cover days). A product selling 4 a day from a supplier with a 21-day lead time and 14 days of cover has a target of 140.
4. Suggested quantity: target minus what is on hand minus what is already on order, rounded up to the item's MOQ and then to its case size. If that comes to 92 and the MOQ is 100 in cases of 12, the suggestion is 108.
5. Trigger: an item appears in the report when on hand plus incoming falls to its reorder point, or when its days of cover drop below the target. Select the lines, pick the supplier, and Create draft PO fills in supplier SKUs and last costs.

Notice where lead time enters: it multiplies velocity. Get lead time wrong by two weeks on an item selling 4 a day and the target is off by 56 units in either direction. That is the mechanical reason the Netstock respondents are right to worry about variability more than about the length itself. A long but stable lead time is just a bigger number in the formula; a swinging one means the formula is wrong half the time.

What to do about variability

The honest answer is that a reorder formula cannot predict a supplier. What it can do is make the assumption visible and cheap to change, so that when the assumption breaks you fix one field instead of recalculating a spreadsheet. Three habits help.

• Record the actual lead time when you receive. Every receipt in Restock Ops is dated, and the PO has its ordered date, so the gap is right there. If the last three deliveries from a supplier took 34, 41 and 38 days and the record says 28, change the record. Receiving is also where partial deliveries get logged, which is its own kind of lead-time information: a supplier that ships 60% on time and the rest three weeks later has, for planning purposes, a longer lead time than its invoice suggests.
• Plan with the slow number, not the average. If a supplier's deliveries land anywhere between 28 and 42 days, entering 42 costs you some extra stock on the shelf; entering 28 costs you stockouts on the late deliveries. For your top sellers the first is cheaper. For slow movers, where the extra units may never sell, use the average and accept the occasional gap.
• Look at cost history alongside lead time. The report's second and third pressures, raw materials and freight, show up on your side as the unit cost on each receipt. Restock Ops keeps a cost history per variant, so a supplier that has gone from 28 to 40 days and from $4.10 to $4.85 a unit in the same year is visible as one story, and the question of whether to look for a second source has some numbers behind it.

MOQs: when the minimum is the problem

Sixty percent of the SMBs in the report called minimum order quantities an obstacle, and it is easy to see why for a Shopify store with long-tail products. A variant selling one unit a week with a 500-unit MOQ is a ten-year commitment. No reorder rule fixes that, but two things make it less painful.

First, the rounding is explicit. The reorder report shows the raw suggested quantity next to the MOQ and case size, so you can see when a line is being pushed far above what velocity justifies and decide whether to order it at all, drop the item, or ask the supplier for a mixed-case arrangement. Second, MOQ and minimum order value are shown when you build a PO, line by line and for the order as a whole, so a supplier's “minimum $500 per order” stops being something you discover from a rejected order confirmation.

A pattern that works for stores with many slow SKUs from one supplier: set days of cover high for that supplier's items, so that several of them come due at once and a single PO clears the minimum order value without over-ordering any one line.

A worked example

The black tote needs nothing because the incoming 50 already covers it; the report knows that only if the earlier PO exists somewhere it can read, which is the argument for creating every PO, even the informal ones. The enamel pin is the MOQ problem in miniature: a raw need of 15 becomes an order of 100 that will last about eight months. That is not a mistake in the maths; it is the decision the report puts in front of you, with the numbers, before you commit.

Where Restock Ops stops

There is no forecast. Velocity is a trailing average, not a prediction, and it does not know about your November or a product that a creator just posted about. Stores that need demand forecasting, safety-stock optimisation across many locations or supplier scorecards should look at the specialised planning tools, including the ones that publish reports like Netstock's. Restock Ops is for the store that has been doing this in a spreadsheet and wants the supplier terms, the reorder maths and the purchase order in the same place, inside the Shopify admin, without a POS Pro subscription. If you have just come off Stocky, the Stocky alternatives comparison covers how it fits next to the other options.

FAQ