Optimise

Ad-hoc Slotting

Continuous correction — re-slot only what drifted, not the whole building.

Demand drifts every week; full re-slots happen a few times a year. Ad-hoc Slotting closes the gap — it detects the SKUs whose locations no longer fit their demand and generates a minimal, targeted correction plan.

Minimal

moves — only SKUs that breached their coverage targets

Weekly

cadence instead of quarterly upheaval

Full-warehouse slotting is powerful but heavy. Between runs, demand keeps moving: a promoted SKU outgrows its pick face, a seasonal line fades and hoards prime locations. The academic literature is blunt about this failure mode — velocity-based slotting decays under demand drift unless it is continuously corrected.

Ad-hoc Slotting monitors slotted capacity against days-of-cover requirements with tunable tolerances. Overflowing SKUs (too little slotted capacity) and underflowing SKUs (prime space they no longer earn) are flagged, previewed and re-slotted — while everything that still fits stays frozen exactly where it is. Small moves, steady state, no disruption.

How it works

Ad-hoc Slotting, in three moves.

01

01

Detect

Coverage maths compares each SKU’s slotted capacity to its days-of-cover requirement. Breaches are listed with the gap quantified.

02

02

Scope

Only breached SKUs enter the optimiser; the rest of the warehouse is locked. The correction cannot ripple.

03

03

Execute

A short movement list resolves the drift. Run it weekly and the warehouse never strays far from optimal.

Capabilities

  • Overflow and underflow detection against days-of-cover targets
  • Tunable tolerances and minimum-gap thresholds — no nuisance moves
  • Instant preview of breached SKUs before any run is committed
  • Scoped optimisation: non-breached SKUs and their slots are frozen
  • Breach report grading every SKU: resolved, improved or unresolved
  • Same rules, scoring and review flow as full Smart Slotting runs

What you get

Targeted re-slot plan touching only mismatched SKUs
Breach report with required vs slotted capacity per SKU
Movement list sized in hours of work, not weeks
Updated travel KPIs against the standing baseline

See Ad-hoc Slotting run on your operation’s data.