Your first restock: placing the second PO without overreacting to early sales
Your first restock order is where most stores overorder. How to read launch-week sales, place the second PO on schedule, and size it without panic.
InventoryX is in development and not available today. ClearStock is the live Shopify app.
Twelve sales in your first four days means almost nothing. Neither does one sale in the two weeks after. First-month data is dominated by the launch spike — your newsletter, the launch discount, the friends and collab posts — and the most expensive mistake of a store's first restock is reading that spike as steady demand and placing a giant second PO against it. The fix is a floor, not a forecast: wait for a post-spike read, compute a run rate you can defend, and let days of cover — not emotion — set the day the PO goes out. Here's how, with the arithmetic.
Why launch week lies
A merchant we interviewed while researching this series sold 12 units in the four days after launch, then one the entire following week. Neither number is demand. Week one of a launch is a mixture of one-time forces: your own audience seeing the announcement, a launch discount pulling purchases forward, friends and family, and plain novelty. Strip those out and a baseline usually appears somewhere in weeks two to four — but only if you look for it.
The first restock is a different question from the first buy. The first buy solved for "don't die before we learn something." The restock is the first time you're buying against measured demand, on a measured lead time — and the data you're measuring is at its noisiest right now.
A worked example: the enamel pin that sold 70 in a month
Illustrative numbers, but the shape will look familiar. You launched a fox enamel pin (PK-FOX-01) with a first buy of 150 units, sized by the pre-launch first-buy framework. The first month:
| Week | Units sold | What was happening |
|---|---|---|
| 1 | 42 | Launch day, newsletter send, collab post, 10% launch code |
| 2 | 9 | Nothing scheduled |
| 3 | 11 | One organic mention |
| 4 | 8 | Nothing scheduled |
The naive read, the one that feels responsible: 70 units in 28 days is 2.5/day, so with 80 left you have 32 days of cover — reorder everything, today.
The floor read: drop the launch week as spike and average the rest — 28 units over 21 days ≈ 1.3/day. Now the same 80 on hand is 61 days of cover, not 32. That single correction moves your reorder from "emergency" to "scheduled."
The rest of the math:
- Lead time: 24 days door-to-door, measured from your own first PO (not the supplier's quote — measuring it from PO history is a separate skill if you haven't done it yet).
- Reorder point: 1.3 × 24 + 10 units of buffer ≈ 41 units. The buffer here is deliberately small — a week of demand — because the SKU is new and cash is tight.
- Order day: you cross 41 units when (80 − 41) ÷ 1.3 ≈ 30 days from now. Not today. The spreadsheet says "scheduled in a month," which is exactly the emotional distance you want from a first restock.
- Second PO quantity: cover the next 90 days at the floor rate: 1.3 × 90 = 117 → order 120–130.
- The MOQ problem: the pin factory's minimum is 200. The extra ~75 units at an illustrative $1.10 unit cost is about $85 estimated — cheap insurance that also buys you calendar space if demand ticks up. Run the same overshoot on a $22 unit-cost product and it's a genuinely different decision; where MOQs break your math, the MOQ explainer walks the options.
What month one is telling you: the signal table
The floor method assumes a launch spike over a real baseline. Sometimes month one is saying something else entirely:
| First-month pattern | Most likely meaning | What to do |
|---|---|---|
| Most sales in week 1, then quiet | Launch spike: your audience plus launch discount | Use only the post-spike weeks |
| Steady week over week | A real baseline is emerging | Trust the average; keep a small buffer anyway |
| Strong week 1, then zero | Traffic or listing problem — or no demand | Diagnose sessions and conversion before ordering anything |
| One variant takes nearly all sales | Demand is concentrated | Reorder that variant only, not the full assortment |
| Sold out mid-week 2 | Velocity is understated | Correct for the dark days before sizing (below) |
The third row is the one merchants skip. A launch that flatlines isn't a reorder decision — it's a diagnosis. Ordering more of a product whose problem is its listing just converts inventory into a future markdown.
Two situations that break the rule
You went out of stock during month one. If the pin was dark for 6 of 28 days, your floor rate is understated — those days hide demand you couldn't serve. The correction — excluding dark days and re-basing the rate on in-stock time only — is covered in why velocity numbers lie during out-of-stock days; apply it before you run the reorder math or the reorder point will inherit the hole.
The launch genuinely stepped up. A press hit, a viral post, a wholesale inquiry that converts — if weeks two through four are rising rather than flat, you're no longer reading a spike over a baseline; you're in a new regime with almost no data. When that happens, order sooner and smaller than the math suggests, in stages: half now, the rest triggered by the next two weeks of data. Staging costs you a little in freight efficiency and buys you a lot in not owning 400 units of a trend you misread.
The Monday habit that makes restocks boring
The first restock is the first loop of the cycle you'll run for the life of the store: on hand ÷ run rate gives days of cover; compare cover against lead time plus buffer; the day cover crosses that line is your order day. Run it every Monday on every active SKU and the question "should I reorder yet?" stops being a feeling you have to manage. The days-of-cover metric — and why it beats "units left" — is the reference here; it's the same number that will drive your reorders at 50 SKUs and 5,000.
One cash note while you're at it: the second PO is ideally funded by the first batch's sales. In the pin example, the ~$140 estimated PO cost lands a month out, by which point 70 units have sold. If the timing doesn't work that way — long lead times, big MOQs — size the order down before you finance the gap by accident.
The conversation that comes with PO number two
The second PO is also the first time you and the supplier have history, so use it. Open with the actuals: "The first order took 24 days door-to-door against your 20-day quote — I'm planning on 24 this time." Suppliers adjust how they schedule small buyers when the buyer demonstrates they measure. Then ask two things most first-time reorders never ask: what their production calendar looks like over your next order window (if your restock lands near a holiday, you're about to meet lead-time inflation the hard way), and whether unit price moves at your new quantity. A 130-unit repeat at the same price is normal; a 500-unit order at the same price is a missed conversation.
Finally, put the measured lead time in writing on the PO itself — an expected ship date, not "as soon as possible" — so the next disagreement has a document instead of a memory.
Common questions
When should I place my second purchase order? When days of cover at your post-spike run rate reaches your measured lead time plus a small buffer. In the worked example that's 41 units on hand at 1.3/day with a 24-day lead — a date about a month after launch, not a decision made in the adrenaline of launch week.
How do I calculate sales velocity with only one month of data? Drop the launch week entirely, average the remaining post-spike days, and correct for any days the product was out of stock. A month that reads 2.5/day naively often runs closer to 1.3/day once the spike and dark days are removed — and the difference decides whether your second PO is 90 units or 240.
How much should I order on my first restock? Your planning horizon times the floor rate: 90 days at 1.3/day is about 120 units in the example. Then reconcile with the supplier's MOQ — overshooting a $1 unit by a few dozen is cheap; overshooting a $22 unit is a cash decision that deserves its own math.
My first product sold out during launch — how do I plan the restock? Your velocity is understated because the dark days hid demand. Correct the rate for out-of-stock time, consider a preorder or waitlist to hold the momentum until stock lands, and stage the next buy so a misread doesn't compound. A fast first sellout is a good problem; restocking it on launch-week extrapolation is how it becomes a bad one.
Should the second PO match the first order's quantity? No — the two orders answer different questions. The first buy solved for surviving launch with unknown demand; the restock covers a planning horizon at a measured rate. Copying the first quantity usually means buying your launch spike twice.
Next step
Compute the floor rate for your most recent launch today: total first-month sales minus launch week, divided by the remaining days. Then check days of cover against your measured lead time plus a one-week buffer — if cover is already below that line, the PO is due now, not Monday; if it isn't, write the crossing date on the calendar and stop thinking about it until then.