Weekly inventory checklist for Shopify — one printable page for the whole week

Short answer: a working week of inventory ops is five short sessions — Monday's metrics pass, Tuesday's PO follow-ups, Wednesday's alert review, Thursday's discrepancy sweep, Friday's receiving close-out — and all five fit on one printable page. This is that page, built as a fill-in worksheet: the numbers you need are defined up top, and every task below takes minutes, not hours.

One boundary before the checklist: the daily numbers — which KPIs to read and the 15-minute Monday ritual that reads them — live in the inventory KPIs guide. This article doesn't re-derive them. It assembles the week around that ritual: everything the ritual surfaces (a dark day, a cover gap, a variance) generates a task, and the other four days are where those tasks get finished. If Monday is the diagnosis, Tuesday–Friday are the treatment.

Fill these in first

The worksheet only works if the inputs are real. Before your first week on this checklist, complete this block — it's five minutes with your Shopify admin and your supplier emails:

The lead-time row matters more than it looks. Cover means nothing in the abstract — the whole point of the days of cover calculation is comparing it against how long a replenishment actually takes, which is why recording actual lead times, not just quoted ones, is a weekly output of this checklist, not a one-time input (the measurement method is in the supplier lead time guide).

Monday — the metrics pass (15 minutes, owned elsewhere)

Monday belongs to the ritual described in the KPI guide: last week's dark days, cover on your A-SKUs versus lead times, the buying list, the edges. Run it as written there. What Monday produces for the rest of this checklist is a task list:

• Every SKU whose cover is shorter than its lead time → an order decision today (Monday's job, not Tuesday's).
• Every SKU that went dark last week → one line in your discrepancy log if the reason isn't obvious (see Thursday).
• Every buying-list quantity → a PO or draft PO written Monday, so the PO clock starts immediately.

Nothing else happens Monday. If Monday runs long, the problem is usually that Wednesday's and Thursday's work is leaking into it — push it downstream.

Tuesday — PO follow-ups (10 minutes)

Every open purchase order gets one line of status. This is the session that catches slips while you can still react — a supplier who promised Oct 27 and is silent on Oct 20 doesn't get better by Friday.

For each open PO, check and note:

1. Shipped? If yes, note the tracking and move the expected arrival to Friday's receiving block.
2. Not shipped, before the promised date? Nothing to do. Confirm and move on.
3. Not shipped, at or past the promised date? Send one follow-up email today — not a scolding, a date: "INV-2027-014 was due Oct 27 — can you confirm the ship date?" The reply either restores your timeline or gives you enough warning to place a split order elsewhere.
4. Arrived short or late? Log it. The pattern across POs is how you discover that a supplier's quoted lead time is fiction — and that's data for your input table above and, eventually, for the conversation about terms.

Ten minutes, every Tuesday, is the entire discipline. Stores that skip it discover supplier slips at the moment shelves go dark, which is the most expensive possible discovery method.

Wednesday — the alert review (10 minutes)

Wednesday is when you look forward instead of backward. Open your low-stock views or alerts and triage anything inside its warning window.

The native mechanics of alerting are covered properly in the low stock alerts guide — including the honest limitation that Shopify's core admin has no built-in low-stock email alert as of October 2026, so stores use saved low-stock views on the Inventory page, Flow automations, or an app. Whatever your setup, the Wednesday review is the same three buckets:

• Order now: anything below its threshold where cover < lead time. If Monday's ritual worked, most of these were already handled — anything appearing here mid-week is either a demand spike or a fast seller you underestimated. Order it, and note the velocity surprise in your log.
• Watch: below threshold but cover still exceeds lead time. No action; it stays on Wednesday's list until it sells or gets ordered.
• False alarm: threshold set wrong (a seasonal SKU carrying its summer threshold into October, say). Fix the threshold now, or you'll train yourself to ignore the alert entirely — and an ignored alert is worse than none.

The trap this session prevents is alert fatigue. If every Wednesday produces fifteen items and you action two, your thresholds are noise. Tighten them until the list is short enough to be taken seriously.

Thursday — the discrepancy sweep (10 minutes)

Somewhere between the spreadsheet, the Shopify admin, and the physical shelf, numbers drift. Thursday is when you hunt the drift before it compounds — because a variance found the week it appears is a mis-scan or a mis-pick, and the same variance found three months later is an unexplained write-off.

Open your inventory adjustments (Shopify keeps an adjustment history with reasons) and scan the week's changes:

• Adjustments you made on purpose (receiving, cycle counts, known damages) — fine, confirm the reason code is right. Reason discipline is what makes this report readable later; "correction" tells you nothing in December.
• Adjustments nobody can explain — one line in the discrepancy log: SKU, expected vs counted, date, who found it. The full variance math and the investigation workflow (recalculate → recount → trace the movement history → root-cause) belong to the inventory discrepancy guide — Thursday is just the weekly trap that feeds it.
• Negative quantities — flag immediately. Negative stock means your records sold units you didn't have; every day it sits, your velocity data is poisoned. Fix the count, then figure out which process let it through (usually receiving logged late, or a sync gap).

Also Thursday: check that this week's received POs were actually entered. Receiving boxes that sit unlogged for days is the single most common source of phantom variance — the shelf has the units, Shopify doesn't.

Friday — receiving and the close-out (15 minutes)

Friday closes the week so Monday starts clean:

1. Receive everything physical. Any delivery that arrived this week gets counted, compared against its PO, and entered in Shopify today — not "when there's time." Discrepancies at the dock go straight into the log while the box is still open and the packing slip is at hand.
2. Quick touch-count on one zone. Not a full count — one shelf, one category, ten units of confidence. Rotating a zone a week means every location gets verified about monthly, which is the lightest possible version of the cycle counting discipline (the full method and cadence live there).
3. Update the worksheet inputs. Any lead-time corrections from Tuesday, any threshold fixes from Wednesday, any new open POs. Thirty seconds now saves re-deriving everything next Monday.
4. Print or duplicate next week's page. Blank tasks, carried-over watches, open POs.

The printable page

Copy this into a doc, scale it to one page, and pin it where you pack orders:

WEEK OF: ____________

INPUTS (update Friday)
Suppliers + actual lead times: ______________________________________
Open POs (no. / supplier / due): ____________________________________
Alert thresholds changed this week: __________________________________

MON — metrics pass (15 min, per KPI ritual)
[ ] Cover < lead time on: ____________ → PO written
[ ] Dark days last week: ____________ → logged
[ ] Buying list quantities: ____________

TUE — PO follow-ups (10 min)
[ ] Every open PO has a status: PO 1 ___ PO 2 ___ PO 3 ___
[ ] Past-due chased (email sent): PO ___ on ______
[ ] Lead time updated if actual ≠ quoted

WED — alert review (10 min)
[ ] Alerts triaged: order ___ / watch ___ / threshold fixed ___
[ ] Mid-week order placed: SKU __________ qty ______ (PO ________)

THU — discrepancy sweep (10 min)
[ ] Adjustment history scanned; reasons correct
[ ] Unexplained variances logged: SKU __________ Δ ______
[ ] Negatives fixed: __________
[ ] Received POs confirmed entered in Shopify

FRI — receiving + close (15 min)
[ ] All deliveries received, counted, entered
[ ] One zone touch-counted: ________ (variance? Y / N)
[ ] Inputs updated
[ ] Next week's page printed

Fifty-five to sixty minutes a week, total. That's the honest cost of never being surprised by your own shelves — and it's less time than one emergency re-order scramble.

Common questions

How often should a small store check inventory? Once a day for sales is automatic in Shopify; the deliberate work — cover versus lead times, alerts, PO follow-ups, discrepancies — fits in about an hour a week split across five short sessions. Below roughly 100 SKUs you can compress it to two sessions; above a few thousand, delegate the daily pieces and keep the weekly review yourself.

What should be on a weekly inventory checklist? Five things: last week's out-of-stock days and cover-versus-lead-time decisions (Monday), open purchase-order follow-ups (Tuesday), low-stock alert triage (Wednesday), an inventory-adjustment and discrepancy sweep (Thursday), and receiving plus a touch-count close-out (Friday). Everything else — deep counts, aging reviews, pruning — is monthly or quarterly work.

Which day is best for inventory checks? Monday, for the metrics pass — you read the full prior week and order in time to beat the week's shipping cut-offs. The other sessions flex around your schedule, but receiving should land on the day deliveries actually arrive, and PO follow-ups work best early in the week while suppliers are reachable.

How long should a weekly inventory review take? About 55–60 minutes total at a few hundred SKUs: 15 minutes on metrics, 10 each on POs, alerts, and discrepancies, 15 on receiving close-out. If it regularly runs longer, the usual culprits are unlogged receiving and threshold noise — both process fixes, not reasons to skip the review.

Do I need software to run a weekly inventory checklist? No — a printable page and Shopify's native adjustment history, saved views, and purchase orders cover the structure at this scale. Apps earn their keep on the parts Shopify doesn't compute natively, like per-SKU dark-day ledgers and days-of-cover-versus-lead-time comparisons, but the weekly discipline comes first and comes free.

Next step: print the page and run it as-is for four weeks before customizing anything — the routine is the asset, not the tweaks. The numbers Monday reads are defined in the inventory KPIs guide, and when a Thursday log starts filling with the same SKU week after week, that's your signal the root-cause workflow in the discrepancy guide needs a proper run.