The replenishment schedule: one weekly rhythm for buying, receiving, and counting

A reorder point is a promise the calendar has to keep. The math can say order HARNESS-M-10 at 293 units; whether that happens Monday or "sometime this week" is the difference between a container landing on schedule and a bestseller sitting empty through the gifting season. A replenishment schedule is the fixed weekly rhythm that makes the math execute: one buying-list review, a set of supplier cutoffs, one receiving window, one count day. This article builds that week for an illustrative 340-SKU pet-supplies store, cutoff arithmetic worked in full.

Two decisions sit upstream of that calendar, and this piece doesn't re-teach them. Which replenishment method fits which kind of SKU is covered in the guide to inventory replenishment methods. How often to order from each supplier — the frequency decision — is covered in how often to order inventory. What's left is the part stores fail at: the rhythm that turns a good decision into POs sent, boxes received, and numbers counted, every week.

Why replenishment fails at the calendar, not the math

Most stores that run out of a bestseller didn't miscalculate; the reorder point was fine. The failure happened downstream: the review happened "when there was time," the PO went out in a Thursday-evening scramble an hour after the supplier's deadline, the cartons sat unopened until Monday, and nothing was counted until the quarterly stock take. Each slip looks small; compounded, they cost weeks, and a supplier that consolidates weekly converts a one-day miss into a seven-day slip.

Empty shelves have costs that never show on an invoice: customers substitute, delay, or buy elsewhere. A schedule also makes the pieces share work. Friday's count verifies the numbers Monday's buying list runs on; Thursday's receiving catches a short-ship while the claim is fresh.

The four fixed points of a weekly rhythm

• Monday: the buying-list review. One sitting, same time every week, 60–90 minutes. Input: SKUs below reorder point, with days of cover, suggested quantities, order-by dates. Output: approved POs. The review approves; it doesn't discover.
• Supplier cutoffs, mapped backward. Every supplier runs a weekly rhythm — consolidation day, ship day, order-entry deadline. The schedule converts each into a send-by day and works backward, so the PO is drafted, acknowledged, and paid before the deadline, not during it.
• A receiving window. One fixed block when every arrival gets counted against its PO, received in Shopify, shelved. Unscheduled receiving is how "the PO said 60, the carton held 54" becomes phantom stock nobody notices for a month.
• Count day. One fixed day, a rotating slice of the catalog. Output: drift measured weekly instead of discovered quarterly, and review numbers days old rather than weeks old.

Four fixed points, roughly five to six scheduled hours a week for a 340-SKU store (illustrative — the arithmetic is in the calendar below). Everything else in replenishment can flex. These can't.

Monday: the review that approves instead of discovers

The illustrative store: 340 SKUs of pet supplies — harnesses, rope toys, carriers, treats — single location, one owner plus a part-time ops assistant. Three suppliers:

*Order date to sellable stock, measured from each supplier's last ten POs.

Monday, 9:00–10:30. The buying list carries 45 SKUs this week (illustrative for early November; 60–80 lines at peak). Its currency is days of cover — how to compute it well, including the in-stock-only wrinkle, is covered in the days-of-cover guide. The review walks the list lowest-cover-first: sanity-check the velocity — dark weeks fake low demand, promo weeks fake lifts, and finding baseline demand covers both corrections — then check the suggested quantity against cash and supplier cartons, mark approve or hold. Approvals become POs before 10:30, with anything that looks off run through the 30-second reorder spot-check first. The discipline: walk in with the list already assembled. If Monday morning is spent discovering what needs ordering, the schedule has already failed — discovery is Sunday-evening or software work; approval is Monday work.

One mention of what we build, because it's this block's input. InventoryX assembles the Monday Buying List (per SKU: days of cover, suggested quantity, order-by date), so the review is approvals rather than discovery. Two standing limits: lead times are entered by hand per supplier, and the list is a draft — MOQs, cash timing, and promo plans are yours to overlay; nothing is ordered without you.

PO cutoff math: order-by dates and the supplier's clock

Lead time tells you how long the gap is; the cutoff tells you which day it starts. Miss a Friday consolidation by an hour and the PO waits seven days in the supplier's queue. Three steps, worked for HARNESS-M-10 at the Monday Nov 9 review (every number illustrative):

Step 1 — days of cover. Velocity 5.5 units/day (in-stock-only, last 30 in-stock days), on hand 338 units:

338 ÷ 5.5 ≈ 61 days of cover

Step 2 — which week? The store runs a 14-day floor on harnesses — how bare a cycle you'll accept is the service-level dial in the service level guide. Weekly membership rule: a SKU joins this week's PO when cover falls to lead time + floor + one week of slack (the time until the next review):

42 (lead) + 14 (floor) + 7 (slack) = 63-day threshold 61 ≤ 63 → on this week's PO

Step 3 — which day? The line crosses its floor in 61 − 14 = 47 days, around Dec 26. Send by the factory's Thursday 5 p.m. cutoff on Nov 12 → consolidates Friday Nov 13 → measured 42 days → sellable ≈ Dec 25, a day ahead of the floor. That fine margin is the price of catching the line at 61 days of cover instead of 75 — the +7 slack exists to be spent earlier in the fall.

Now the miss, because that's what the schedule defends against:

PO finished 5:40 p.m. Thursday → cutoff missed → consolidates Nov 20 → sellable ≈ Jan 1 Cover on Jan 1: 61 − 53 (days from Nov 9 to Jan 1) = 8 days — six below the floor (14 − 8) × 5.5 = 33 units × $34.95 illustrative retail ≈ $1,150 estimated revenue at risk on one SKU

One hour late, one week late, an estimated four figures dark on one line. The cutoff measures your error in days; the supplier's rhythm measures it in weeks.

Domestic suppliers run the same math on a kinder clock. CARRIER-L-02 crosses its floor Dec 1; work backward: Dec 1 − 9 days = Nov 22 order-by; the maker's last Wednesday noon cutoff before that is Nov 18; ships Thursday; sellable ≈ Nov 28. Miss Wednesday noon by an hour and it ships the following Thursday: sellable ≈ Dec 5, four days past the floor — even 9-day suppliers forgive less than expected. The 5-day distributor with a Thursday 2 p.m. cutoff is the forgiving one.

Receiving windows and count day

Receiving: Thursday 2:00–3:30, plus a Monday slot. Shopify supports receiving quantities against a PO so each receipt has a defined scope to check against (Shopify Help Center, accessed November 2026). The distributor's Monday delivery is received right after the review; everything else lands in the Thursday window. Rules: count cartons against the PO before shelving, receive in Shopify before shelving rather than after (the native PO receiving flow supports this — Shopify Help Center, accessed November 2026), and log discrepancies the same day; short-ship claims land differently the week of delivery than a month later. Receiving is where system-shelf drift is manufactured; a scheduled, count-first window is the cheapest accuracy there is.

Count day: Friday 8:00–9:00, before opening. The rotation covers all 340 SKUs every six weeks ≈ 57 per session (340 ÷ 6, illustrative), front-loaded with fast movers — your own velocity ranking supplies the ordering, and since Fall '26 counts can be scheduled natively in admin and POS, the rotation lives in the system, not in someone's memory (Shopify Fall '26 Editions, accessed November 2026). Reconcile on the spot, log the cause with the correction, finish before open. Count Friday, buy Monday — the review runs on numbers verified 72 hours earlier, and Thursday's receipts get a within-a-day recount.

The whole week on one page

Copy the shape, not the times — the times belong to this store's suppliers:

Total: about five and three-quarter scheduled hours, mostly in two sittings, shareable between owner and assistant. Two design notes. The sequence — count, review, cutoffs, receive — is a loop, not a list: Friday's counts feed Monday's list, Monday's POs clear Thursday's cutoff, Thursday's receipts get verified Friday. And every block ends in an output, not an activity — "factory PO acknowledged" is an output, "review done" is not — which is what makes the schedule delegatable on a day the owner is out.

Keeping the rhythm through peak season and absences

• Peak season bends the dates, not the shape. Q4 factory queues lengthen, and overseas closures (Golden Week in early October, Chinese New Year in late January) add whole weeks if they surprise you. Measure the seasonal stretch in your own PO history, add it to the affected supplier's lead time, and let the cutoff math move order-by dates earlier on its own. For a second-season product, the year-two seasonal buy plan resizes those dates from corrected history.
• The one immovable object is the overseas cutoff. Domestic cutoffs can slide a day; the factory's Thursday edge costs a week. If a block has to be skipped in a chaotic week, skip anything else.
• Absences are the real test. Each block has a written output, so a filling-in partner can execute. A schedule that lives only in the owner's head dies the first week of vacation; when the absence is permanent, that rhythm is half the inventory manager handover template.
• Audit monthly. Count days skipped, POs sent on cutoff day, receipts older than 24 hours uncounted — the misses show which block needs more time or more help.

Common questions

What is a replenishment schedule? A fixed weekly rhythm that turns reorder math into executed POs: one buying-list review, supplier cutoffs mapped backward into send-by days, one receiving window, one count day. The math decides what to order; the schedule decides when the decision happens, and keeps it from slipping.

What day should the weekly review be? Monday, before the week's earliest supplier cutoff. It gives factory POs days of slack before a Thursday consolidation deadline, so acknowledgment and deposits fit inside the week; count day goes before it, Friday, so the review runs on freshly verified numbers.

How do I calculate an order-by date? Work backward: take the date you need stock sellable, subtract the supplier's measured lead time (PO sent to sellable), then snap to that supplier's cutoff on or before that date. On a weekly-consolidating supplier, missing the cutoff slips a full cycle — one late day becomes seven lost days.

How much time does the weekly rhythm take? For a 300–400-SKU single-location store, roughly five to six scheduled hours a week (illustrative): a 90-minute Monday review, short daily follow-throughs, a 90-minute receiving window, a 60-minute count. Most stores already spend that time unscheduled; the schedule puts the work where the cutoffs are.

Next step

Take 30 minutes today and write one page: every supplier, its measured lead time, its cutoff day and time. Then put two blocks on the calendar — Monday review, one receiving window — and make the weekly inventory checklist your Friday close, so the rhythm audits itself. If days of cover isn't yet your buying currency, the days-of-cover guide fixes that in ten minutes.