In a Strict Hub and Spoke model, Recurrency purchases into the hub and transfers out to spokes. By default, a spoke only counts as downstream need on the hub PO when that spoke is at or below min. If the spoke is between min and max, Recurrency does not add that remaining fill to the hub buy — so the next spoke sale can drop it below min, a transfer pulls from the hub, and you need a second PO.
Replenish Spokes to Max changes that. When it is on, Recurrency includes the full fill-to-max for stockable spokes in the hub quantity to order, even when those spokes are still above min. One hub PO covers the hub’s own replenishment and the pending spoke fills.
⚠️ Note: This setting changes hub purchase quantities only. It does not change Transfer Replenishment recommendations. Transfers still fire when a spoke is at or below min. Your team still decides when to move stock from the hub to the spokes.
How Replenish Spokes to Max works
For each stockable Min/Max spoke on a replenishment path, Recurrency looks at how far that spoke is below its max:
Spoke fill = max − net stock (if the spoke is below max; otherwise 0)
The hub quantity to order becomes:
Hub QTY to order = greatest(hub max − hub net stock + sum of spoke fills, 0)
That extra quantity is purchased into the hub. Spokes still do not get their own purchase recommendations in Strict Hub and Spoke.
If the hub is already above max, that excess offsets spoke need. The hub PO can be zero when on-hand at the hub already covers the pending spoke fills.
Fills from spokes and spokes-of-spokes roll up to the purchasing hub — the location that actually places the PO — not only the immediate parent.
Example
Location | Role | Min | Max | Net stock | Setting off | Setting on |
DC | Hub | 2 | 10 | 0 | PO 10 (hub to max) | PO 14 (10 hub + 4 spoke) |
Branch | Spoke | 1 | 5 | 1 | Not included (above min) | 4 units included in the hub PO |
With the setting off, the first hub PO brings the DC to 10. When the branch sells its last unit, Recurrency recommends a transfer of 5, which immediately draws the hub down and prompts another PO. With the setting on, the first hub PO already includes the 4-unit spoke fill, so that inventory is sitting at the hub when the branch needs it.
When this applies
Replenish Spokes to Max is used when all of the following are true:
Your workspace uses the Strict Hub and Spoke planning model
Netstock aggregation is enabled for purchasing
Replenish Spokes to Max is turned on for your workspace
The spoke is stockable
OP/OQ spokes are excluded from the “below max” trigger. They still only count as downstream need when net stock is at or below min.
How to get started
Confirm you are on Strict Hub and Spoke, with replenishment paths defined from hub to spokes.
Ask your Recurrency CSM to enable Replenish Spokes to Max.
Wait for Recurrency to refresh purchasing recommendations (this can take up to a day).
In Purchase Targets, open a hub line where spokes are between min and max. QTY to order should now include those spoke fills.
What Replenish Spokes to Max does not do
It does not change recommended min or max
It does not recommend hub-to-spoke transfers when a spoke is between min and max. Transfer Replenishment still uses the at-or-below-min rule
It does not create transfer orders or transfer backorders automatically
It does not purchase directly into spokes in Strict Hub and Spoke
It does not apply to Flexible Hub and Spoke, or to workspaces that are not using hub and spoke
If you want Recurrency to prompt transfers as soon as a spoke is below max, that is a separate workflow. Talk to your CSM.
Things to know
Enablement: Recurrency turns this on for your workspace. You will not see a self-serve toggle on Settings.
Refresh: After it is enabled, wait for the overnight purchasing refresh before QTY to order changes.
Hub excess counts: If the hub is already above max, that extra stock reduces how much Recurrency adds for spokes.
Nested paths: Need at a spoke-of-a-spoke rolls all the way to the purchasing hub.
Related workflow: Teams that use Transfer Replenishment + Transfer Backorders instead of netstock aggregation should see How to Purchase Inventory That Covers a Hub and All Its Spokes.
FAQs
Why is QTY to order higher at the hub even though the spoke is not understocked?
That is expected with this setting on. The spoke is below max, so Recurrency is pre-positioning that fill at the hub. The spoke itself still only shows a transfer
recommendation when it hits min.
Will Transfer Replenishment now suggest transferring every spoke that is below max?
No. Transfers stay on the original rule: recommend a transfer when the spoke is at or below min, and fill to max at that point.
Does this change Planning min/max?
No. Min and max stay the same. Only the hub purchase quantity changes.
What if the hub is already overstocked?
Recurrency subtracts hub stock above max from the spoke fills. If the hub already has enough extra to cover those fills, QTY to order is 0.
Do I still need to run Transfer Replenishment?
Yes, if you want Recurrency to recommend moving the stock from hub to spoke. This setting gets the units onto the hub PO. It does not move them for you.