Reorder suggestions

A reorder suggestion answers two questions per variant: how many and when. The “how many” lives in the Actual Reorder Quantity column. The “when” lives in the Reorder Date column. This page explains how each number is calculated, what it means, and how to act on it.

What the suggestion means

Two-bullet TL;DR before the math:

Actual Reorder Quantity is Logistified’s answer to: if I place a PO today, how many units do I need to stay safe through one more lead-time cycle until this stock arrives? It’s the recommended order quantity after MOQ, pack size, and economic order quantity adjustments. When economic order quantity beats the raw demand-based number, you see a green “EOQ” pill in the cell.
Reorder Date is the calendar day your on-hand inventory is projected to drop to the reorder point. Acting earlier is safe; acting later risks running out.

When you create a PO from the Forecast page, the quantity starts from the displayed Actual Reorder Quantity. If the cell shows an EOQ uplift, that uplift is included in the suggested PO quantity.

The Reorder Forecast, end to end

Think of it as running your inventory forward in time on autopilot. Starting from today’s on-hand, Logistified walks one day at a time across the forecast horizon — depleting stock by the forecast model’s daily demand and crediting incoming POs and TOs on their expected arrival dates. The reorder columns fall out of that simulation; they aren’t a separate arithmetic chain.

Here’s the sequence in plain terms:

The forecast model produces a daily demand vector — one number per future day across the horizon.
Starting from today’s on-hand, the simulation walks each future day in turn.
Every day, on-hand drops by that day’s predicted demand.
On dates where an open PO or TO is expected to land, the simulation credits the incoming quantity to on-hand.
Safety stock (auto from service level and demand variability, plus the optional force-majeure factor and — if you’ve enabled it — a supplier-reliability buffer) defines the floor below which the simulation considers you at risk.
The first day the simulated on-hand crosses the lead-time-demand + safety-stock threshold is the reorder point crossing — that day’s date becomes Reorder Date.
The Actual Reorder Quantity is sized so that, if you fire the PO today, the simulation lands you safely above the floor at the end of the next lead-time cycle when the stock arrives.
MOQ and pack size adjust the raw simulated quantity (round up to MOQ, round up to a pack-size multiple). EOQ may bump it up further when ordering more is cost-efficient (then you see the green EOQ pill).
Pending back orders, when applicable, are added on top.

Worked example

Say you sell 2 units per day of a widget. Your supplier needs 30 days to ship. You’ve set safety stock to auto (95% service level → about 10 units for this variant). You currently have 100 units on hand and nothing incoming.

Simulating forward from today at 2 units/day:

Day 0: 100 on hand.
Day 15: 70 on hand. This crosses the reorder threshold (lead-time demand 60 + safety stock 10 = 70). Reorder Date = today + 15 days.
Day 30: 40 on hand. If you do nothing, you’re still above zero but inside the danger zone.

So how many to order today? The simulation answers: enough to cover the next lead-time cycle from the moment the stock arrives. If you fire the PO today, it shows up in 30 days. On that day you’ll be at 40 on hand. Add the next 30 days of demand (60 units) plus safety stock (10) — you need on-hand to land near 70 at delivery. That means an order of about 30 units.

MOQ kicks in: your supplier’s minimum is 50, pack size 10. Round up: Actual Reorder Quantity = 50, with the MOQ progress bar showing emerald (your demand comfortably covers the minimum).

All the inputs

Input	Where set	Default	If blank
Forecast model	Variant detail page, or view settings	Auto	Auto picks
History period	View settings	Auto (optimal per variant)	Auto picks
Lead time	Supplier ↔ variant link	7 days at the supplier link; longer fallback for the Default supplier	Default applies
Safety stock	View settings (forecast settings panel)	Auto — 95% service level	Auto applies
MOQ	Supplier ↔ variant link	1	Defaults to 1
Pack size	Supplier ↔ variant link	1	Defaults to 1
Force majeure factor	View settings	Off	Off
Incoming quantity	Open POs + TOs	Sum of pending	0
Supplier-held stock	View settings (forecast settings panel)	Off — every existing view keeps today’s behaviour	Ignored
Supplier reliability	Per supplier (manually set)	Off — must be enabled in the view’s reorder settings, then set on the supplier	Treated as 100% if unset
Holding cost	Per variant (Settings → Products)	0	EOQ not used
Ordering cost	Per supplier	0	EOQ not used

What the colors mean

Element	Color	Meaning
Reorder Date	Red	Overdue. You should have reordered already.
Reorder Date	Warning yellow	Due today, or within 7 days.
Reorder Date	Muted	Due in weeks or months.
MOQ progress bar	Red	Demand fills less than 70% of the supplier’s MOQ.
MOQ progress bar	Orange	Demand fills 70–99% of MOQ.
MOQ progress bar	Emerald	Demand fully covers MOQ.
”EOQ” pill	Green	EOQ was bigger than the raw quantity; Logistified rounded up to the economic order size.

Product-level MOQ

Some suppliers set their MOQ once per product instead of once per variant — see Suppliers → Lead times & MOQ for where that’s configured. When a row’s supplier is set this way, the Actual Reorder Quantity cell and its hover card change shape:

The MOQ progress bar and pill compare the product’s combined total to the product minimum, not this one row’s quantity to this row’s own MOQ.
A “Product MOQ” badge appears on every affected size once a minimum is set for the product. It’s neutral (gray) when the product already meets its minimum or the group can’t be fully evaluated, and amber only when Logistified actually lifted this product’s quantities to reach the minimum.
A product with more sizes than Logistified can evaluate at once shows “Product MOQ not applied (too many sizes)” instead — none of its rows get the minimum applied; treat those the way you’d treat a per-variant MOQ of 0.
The hover card shows the recommended total across every size, the product minimum, how much of that is to reach the minimum versus pack-size rounding, and the split across sizes (sizes on other pages are marked “(not on this page)”). Read the per-size Reorder Date / Days-until-reorder columns for when to reorder each size — the product minimum only changes how much.

On a product-MOQ row the hover card names the parts that moved this size’s number, alongside the usual safety-stock and pack-size lines:

Row	What it means
Product MOQ share	Units added to this size so the product as a whole reaches its supplier’s minimum.
Pulled forward	This size wasn’t due yet, but it was ordered now because Order soon-due variants too is on — see below.
Order limit	Units taken back off because the size’s maximum order quantity capped what it could take.

Creating a PO from the Forecast page carries the same product-adjusted quantities, so the PO you get already reflects the shared minimum — see Purchase Orders → Line items & costs for how it’s checked afterward if quantities change.

Order soon-due variants too

When a product is short of its supplier’s product minimum, Logistified completes the minimum over the sizes that actually sell. Order soon-due variants too lets it also pull in sizes that aren’t due yet but will be shortly — so you place one order instead of two a few days apart.

The control has two states:

Off (the default) — only what is due gets ordered. The product minimum is still completed over the sizes that sell.
Up to N days — while the product is short of its minimum, any size that reaches its own reorder point within N days of the product’s order day is ordered now, at its regular quantity. N is a whole number of days from 1 to 90; switching the toggle on starts at 7.

The trade-off: any window adds stock for the sizes it pulls forward, and longer windows add more. Leave it off unless you’d rather hold that stock early than send the same supplier a second order a few days later.

Sizes that came in this way are labelled Pulled forward — next to the size’s quantity in Products mode, and as a Pulled forward row in the hover card above.

Where to set it. Open Forecast Settings (the toolbar popover) or the view editor’s Reorder tab, and look under Minimum order quantity (MOQ); the guided view wizard offers the same control on its MOQ step. Like every other forecast setting it is saved on the view, not on the supplier. It only appears when at least one of your suppliers has a product-level minimum in force and the view’s MOQ source is set to Supplier — otherwise it stays hidden and keeps whatever value you last gave it.

Back orders and lost sales

The Actual Reorder Quantity cell’s sub-line gives context based on your variant’s inventory policy:

“X Back Orders” — when the policy is Continue selling when out of stock. The X customer orders that came in while you were out get rolled into the next reorder. Their units are added to Actual Reorder Quantity.
“X Lost Sales due to missed ROP” — when the policy is Deny. Missed demand was lost — no back orders kept. Informational; counts toward stock-out reporting.

How to act on it

Three paths, in order of frequency:

From a single row. Click “Create PO” on the row’s action menu. A dialog opens prefilled with the suggested quantity.
Bulk from the toolbar. Select rows, then “Create PO from selected.” The dialog starts with the suggested quantities and asks you to choose one supplier or split by supplier.
Add to existing PO. When you have a draft PO open, “Add to existing PO” appends the selected lines.

Edge cases worth knowing

The reorder date can show ”—” / no recent sales — a placeholder you can interpret as “no signal.”
Variants with only the Default supplier attached still get a suggestion, but it uses fallback values. Assign a real supplier first.
A pack size of 0 is treated as 1 (a safety net for operator errors).
A negative “days until reorder” is clamped to 0 — meaning “reorder now.”
The force majeure factor stacks on top of the auto-computed safety stock; it doesn’t replace it.