Minimum-Quantity / All-or-None Constraint Risk: A Slippage Modeling Playbook

2026-03-09 · finance

Minimum-Quantity / All-or-None Constraint Risk: A Slippage Modeling Playbook

Date: 2026-03-09
Category: research (execution microstructure)

Why this matters

MinQty and AON constraints are often used to avoid toxic tiny fills.
But in practice they can turn displayed liquidity into conditional liquidity:

So the cost is not just spread/impact. The hidden cost is eligibility friction.


Failure pattern (common in production)

  1. Desk sets large MinQty (or uses AON) to avoid micro-fills.
  2. Market fragment size shifts smaller (news burst, close approach, venue mix change).
  3. Eligibility rate collapses; order stays live but inactive.
  4. Residual grows as deadline approaches.
  5. Router flips to urgent marketable flow.
  6. Realized slippage is worse than if we had accepted controlled partial fills earlier.

This is a classic “quality-first becomes completion panic” path.


Cost decomposition

For parent order notional (Q):

[ C_{total}=C_{px}+C_{impact}+C_{delay}+C_{opp}+C_{reset} ]

where

With hard size constraints, (C_{delay}) and (C_{opp}) dominate tails.


Core signals (new)

  1. Eligibility Hit Rate (EHR)

    • Fraction of observed contra events that satisfy current MinQty/AON condition.
  2. Constraint-Induced Idle Time (CIIT)

    • Share of parent lifetime where order is live but has no eligible match opportunities.
  3. Constraint Regret (CRG)

    • Ex-post delta between realized cost and counterfactual cost under relaxed threshold policy.
  4. Late Urgency Conversion Rate (LUCR)

    • Probability of switching from constrained passive policy to urgent aggressive policy near deadline.
  5. Eligible Depth Ratio (EDR)

    • Effective executable depth under current constraint divided by displayed depth.

Displayed depth can look healthy while EDR collapses.


Modeling architecture

1) Branch model for constrained orders

Model parent outcome as branch process:

Estimate branch probabilities conditional on state (x_t):

[ P(B_k\mid x_t,\theta_{min}) ]

where (\theta_{min}) is active size constraint.

2) Eligible-flow hazard

Estimate hazard of receiving eligible contra flow:

[ \lambda_{elig}(t)=h(\text{queue state, lot-size mix, venue, TOD, vol regime},\theta_{min}) ]

Lower (\lambda_{elig}) implies higher delay and deadline risk.

3) Counterfactual policy engine

For each decision step, evaluate candidate thresholds:

[ \theta \in {AON,\ MinQty=2000,1000,500,none} ]

with expected objective:

[ J(\theta)=\mathbb{E}[C_{total}\mid x_t,\theta]+\alpha\cdot \text{ResidualRisk}_{q95} ]

Pick (\theta^*=\arg\min J(\theta)), subject to mandate constraints.


State controller (practical)

Use hysteresis (entry/exit buffers) so policy does not flap on transient noise.


Guardrails

  1. No hard AON near cutoff

    • Auto-disable AON inside final execution window unless legally mandated.
  2. MinQty decay schedule

    • Define time-based or risk-based relaxation curve in advance.
  3. Residual cap by time-left

    • If residual exceeds threshold at T-minus buckets, force policy relaxation.
  4. Venue-specific eligibility map

    • Track each venue’s observed eligible-flow profile; avoid one-size-fits-all thresholds.
  5. Tail-budget gate

    • If projected q95 C_total breaches budget, prioritize completion over fill-size purity.

Backtest / replay requirements

Without counterfactual replay, constraint regret stays invisible.


Minimal rollout checklist


Bottom line

MinQty/AON is not a harmless order-typing choice.
It is a latent slippage lever that trades early fill quality against late completion risk.

If you don’t model eligibility friction explicitly, the desk will keep “saving spread” early and paying it back with interest near deadline.