Scheduled Replenishment for Shopify: Fixed-Cycle Ordering
Scheduled replenishment for Shopify puts the calendar in control: fixed cycles, Cycle Reorder Pt, and a review of every draft PO before sending.
Hylke Reitsma is co-founder of Forthsuite and a supply chain specialist with 8+ years of hands-on experience at Shell, Verisure, and Stryker. He holds an MSc in Supply Chain Management from the University of Groningen and writes practical guides to help e-commerce teams run leaner, faster supply chains. Selected by Replit as 1 of 20 founders for the inaugural Race to Revenue Cohort #1 (2026) and certified as a Replit Platform Builder.
TL;DR: Scheduled replenishment for Shopify fits when a supplier calendar—not each SKU crossing a low-stock threshold—controls when you buy. Forthcast sizes recommendations for the next fixed cycle and can create draft purchase orders where automatic drafting is enabled. The draft is not a sent supplier order: the merchant reviews quantities and constraints, then controls the send step.
Last updated: July 2026
Scheduled (Fixed Cycle) Replenishment answers a calendar question: the next supplier order date is approaching—what belongs on the purchase order? Use it for a quarterly container, a monthly supplier review, a weekly co-packer call, or another cadence you cannot move SKU by SKU.
On Demand answers a different question: has this SKU reached its reorder threshold today? Both modes use Forthcast demand forecasts and inventory settings; the difference is the ordering constraint, the horizon used to size the recommendation, and the date on which you review it.
Scheduled vs On Demand: choose by ordering constraint
Choose On Demand when inventory position controls the decision; choose Scheduled when a supplier cadence controls it. The table keeps those two intents separate.
| Decision | On Demand | Scheduled (Fixed Cycle) |
|---|---|---|
| What triggers review? | A SKU reaches its reorder threshold | The supplier's next order date approaches |
| Best fit | Orders can be placed whenever a SKU needs stock | Containers, minimum order quantities, production windows, or fixed review meetings force batching |
| Planning horizon | Reorder-point protection for the relevant lead-time window | Cycle demand, with optional lead-time demand, plus the existing safety buffer |
| Merchant action | Review the recommendation and prepare the PO | Review the cycle recommendation or draft PO, adjust it, and send when approved |
Both modes share the same forecasting engine, the same lead-time settings, and the same safety-stock buffer. The difference is only in how the recommendation is sized and when it fires. You can mix and match too — a shop can run most suppliers On Demand and put a single overseas supplier on a 13-week cycle, or vice versa.
When On Demand fits — and when it doesn't
On Demand fits when you can place a purchase order whenever a SKU reaches its threshold. It works best for shorter lead times, flexible order dates, varied SKU velocity, and suppliers that do not force batching.
It starts to feel wrong when the calendar fights it. If you import from a single overseas supplier and they consolidate everything into one container per quarter, getting an Order Now alert in week 3 is useless — you can't actually place that PO until the next container window. If your domestic supplier has a $5,000 MOQ and you sell $400 of one SKU per week, an alert per SKU is noise. If you've got a fixed Tuesday call with your co-packer and you build the PO together on the call, you don't need a system telling you to order on a Thursday.
Those are exactly the situations Scheduled mode is for.
When Fixed Cycle fits
Scheduled (Fixed Cycle) fits when the calendar or a supplier constraint forces you to batch demand. Use it for recurring containers, minimum order quantities, production windows, buying meetings, or paid-on-order cash planning.
- Container shipments on a fixed cadence. Quarterly containers, bi-monthly LCL shipments, or any consolidation pattern where you order once and ship a lot.
- High MOQs that force you to batch. If a supplier needs a $10k order to ship at all, batching demand into fewer, larger POs is the only realistic plan.
- Predictable supplier review cadence. A weekly call with a 3PL co-packer, a monthly buying meeting, or a quarterly category review.
- Paid-on-order suppliers. If cash leaves the bank the moment the PO goes out, locking spend to a known cadence makes cash flow predictable.
- Categories with strict supplier production windows. Print runs, food production batches, anything where the supplier only opens a slot every N weeks.
How to switch on Scheduled mode
Switch the Replenishment model in Settings from On Demand to Scheduled (Fixed Cycle). Set a default order cycle in weeks and a default next order date, then review supplier-specific overrides.
- Default order cycle (weeks). 4 = monthly, 8 = bi-monthly, 13 = quarterly, 26 = twice a year. Pick whichever matches the rhythm you actually order on. If you're not sure, start with 4 and refine per supplier.
- Default next order date. The date Forthcast will base the first cycle off. You can leave this blank and set it per supplier instead.
You can leave the rest of Forthcast exactly as it is. Forecasting, safety stock, lead times, supplier setup, packaging, bundles — none of that changes. The only visible difference on the Replenishment table is that the Reorder Pt column is replaced by Cycle Reorder Pt.
Per-supplier overrides — different cadences in the same shop
A shop can use a 13-week cycle for an overseas supplier, a 4-week cycle for a co-packer, and On Demand for a local supplier. Supplier values override the shop-wide default, so the mode follows the commercial constraint rather than forcing every supplier into one calendar.
On the Suppliers settings page, each supplier row gets its own Order cycle (weeks) and Next order date. The precedence is straightforward:
- If the supplier has a value set, that value wins.
- If the supplier is blank, Forthcast uses the shop-wide default.
- If both are blank, the cycle defaults to 4 weeks and the next order date prompts you to pick one.
You can leave a supplier on On Demand within a Scheduled shop too — useful for the local supplier you can call any time.
Cycle Reorder Pt — what it actually means
Cycle Reorder Pt is the inventory target used on the next order date to protect the upcoming supplier cycle. It combines cycle demand, optional lead-time demand, and the existing safety buffer.
Cycle Reorder Pt = cycle weeks of forecasted demand + (optional) lead-time demand + your existing safety buffer
When available stock drops below the Cycle Reorder Pt, the row triggers Order Now with a suggested quantity that brings stock back above the threshold for the upcoming cycle. The safety buffer is exactly the same buffer the On Demand model uses — same service-level setting, same lead-time variability inputs — so switching modes doesn't change your stockout protection.
The "include lead time in cycle horizon" toggle
Cycle Reorder Pt has one optional add-on: lead-time demand. There's a toggle under the Replenishment model panel called Include lead time in cycle horizon. When it's on, Forthcast adds lead-time weeks of demand on top of cycle weeks of demand.
Turn it on when you have long lead times or transit-heavy supply chains — the stock you order today won't arrive until well into the next cycle, so you need to cover both the current cycle and the lead time. Leave it off when lead times are short and predictable enough that the cycle alone covers you. A merchant on a 13-week container cycle with an 8-week lead time will almost always want it on; a merchant on a 4-week cycle with a 1-week local supplier almost always won't.
Manual vs. auto Next Order Date
A manual Next Order Date stays under merchant control, while an auto date can advance from recorded purchase-order activity by the configured cycle. Choose the source that matches who controls the real supplier calendar.
- Manual — you set the date by hand. Forthcast never overwrites a manual date. When a PO ships against that supplier, Forthcast asks you to review the date so you can roll it forward yourself. This is the right choice when your supplier dictates the calendar (e.g. "the next container loads on June 5") and you want full control.
- Auto — Forthcast manages the date. After every PO is created or received with that supplier, the next order date advances by exactly one cycle. The advance is anchored to the PO's date — created date when the PO is created, receipt date when it's received — and is clamped to today or later, so a forgotten supplier doesn't end up with a date in the past.
A practical setup can mix both sources: use auto for a steady cadence and manual when a supplier controls a changing container or production date. Review the date whenever the real supplier calendar changes.
Worked example: a quarterly container supplier
A merchant with a 13-week container cycle and an 8-week lead time needs one review horizon that covers the cycle, transit, and safety buffer. The example below shows how that setup reaches a merchant-reviewed purchase order.
The setup:
- Cycle: 13 weeks (quarterly container)
- Lead time: 8 weeks (factory build + shipping)
- "Include lead time in cycle horizon": on
- Today: April 22
- Next order date: May 5
Two weeks before the next order date, the merchant opens the Replenishment table to start building the PO. For every SKU on that supplier, Forthcast computes:
Cycle Reorder Pt = 13 weeks of forecasted demand + 8 weeks of forecasted demand + safety buffer
Anything with available stock below that line shows up as Order Now, with a suggested order quantity that brings stock back to the cycle target. The merchant reviews each row, adjusts for any promotions or price breaks, and sends the PO to the supplier on May 5.
The moment the PO is created, two things happen automatically:
- The Order Now flag clears for every SKU on the PO — they're now "covered" for the upcoming cycle.
- If the supplier is on auto, the Next Order Date advances by 13 weeks to August 4. If the supplier is on manual, Forthcast leaves the date alone and prompts the merchant to review it.
Eight weeks later, the container arrives and is received in Forthcast. Stock is replenished and the cycle starts over for the next quarter.
From recommendation to draft PO: the merchant still sends it
Scheduled mode changes recommendation timing and sizing; it does not remove purchasing approval. Where automatic drafting is enabled, Forthcast can create a draft purchase order, while draft state and email/send state remain separate.
- Review which supplier and SKUs are included.
- Check suggested quantities against promotions, price breaks, minimums, cash and supplier constraints.
- Adjust or remove rows that need commercial judgement.
- Approve and send the purchase order to the supplier.
This boundary matters: an automatically created draft is evidence that a recommendation entered the purchasing workflow. It is not evidence that a supplier received an order, and it never removes the merchant review step.
Switching modes mid-month — and other safety nets
You can switch a supplier or the whole shop between On Demand and Scheduled without changing the underlying demand history, safety settings, lead times, mappings, or PO history. If the real supplier date changes, edit Next Order Date and review the source before the next cycle.
If your Cycle Reorder Pt looks higher than your old Reorder Pt, that's expected. A Reorder Pt protects you for the lead-time window only; a Cycle Reorder Pt protects you for the entire upcoming cycle. The number is bigger because the job is bigger.
Set up Scheduled mode with the review boundary intact
If a supplier cadence controls when you buy, open Settings → Replenishment model, choose Scheduled (Fixed Cycle), set the shop default, then review supplier overrides. Check the first Cycle Reorder Pt recommendations before enabling any automatic drafting, or see Forthcast for Shopify.
Forecast demand and avoid stockouts — Forthcast for Shopify.
Frequently Asked Questions
What is Scheduled Replenishment in Forthcast?
Scheduled (Fixed Cycle) Replenishment is a second replenishment model in Forthcast for Shopify merchants who order on a fixed cadence — for example a quarterly container, a monthly co-packer review or a supplier with high MOQs. Instead of triggering an Order Now alert the moment stock drops below the Reorder Point, Forthcast sizes every PO to cover the entire upcoming cycle using a new Cycle Reorder Pt column.
When should I use Scheduled mode instead of On Demand?
Use Scheduled mode when the calendar dictates ordering: container shipments on a fixed cadence, suppliers with high MOQs that force you to batch, recurring supplier review meetings, or paid-on-order suppliers where you want predictable cash flow. Stay on On Demand when you can place a PO any day of the week and your suppliers don't enforce a rhythm.
How is the Cycle Reorder Pt calculated?
Cycle Reorder Pt = cycle weeks of forecasted demand + (optional) lead-time demand + your existing safety buffer. The lead-time component is controlled by an "include lead time in cycle horizon" toggle — turn it on for long lead times or transit-heavy supply chains, leave it off for short, predictable lead times where the cycle alone covers you.
Can I run different cycles for different suppliers?
Yes. Each supplier can have its own order cycle (weeks) and next order date on the Suppliers settings page. Supplier-level values always win over the shop-wide default; if a supplier is blank it falls back to the shop default; if both are blank the cycle defaults to 4 weeks. You can also leave individual suppliers on On Demand within a Scheduled shop.
What's the difference between manual and auto Next Order Date?
Manual dates are set by you and Forthcast never overwrites them — when a PO ships, Forthcast prompts you to review the date so you can roll it forward yourself. Auto dates are managed by Forthcast: after every PO is created or received with that supplier, the next order date advances by exactly one cycle, anchored to the PO's date and clamped to today or later. You can switch a supplier between manual and auto at any time.
Does Forthcast send Scheduled purchase orders automatically?
No. Where automatic drafting is enabled, Forthcast can create a draft purchase order from recommendations. The merchant reviews and adjusts that draft, then controls whether and when it is sent to the supplier. Draft creation is not supplier delivery.
About the Author
Hylke Reitsma is co-founder of Forthsuite and a supply chain specialist with 8+ years of hands-on experience at Shell, Verisure, and Stryker. He holds an MSc in Supply Chain Management from the University of Groningen and writes practical guides to help e-commerce teams run leaner, faster supply chains. Selected by Replit as 1 of 20 founders for the inaugural Race to Revenue Cohort #1 (2026) and certified as a Replit Platform Builder.
LinkedIn