Home / Glossary

Order fallout

Also called: Order exceptions, kick-backs

Orders that can't flow straight through to production because something in them is invalid, unpriced, unbuildable or unclear, and needs a person to fix it.

In a configure-to-order business a perfect order touches no human between the dealer's click and the plant's schedule. Fallout is every order that doesn't make it. Each one costs someone's time, and many cost a delivery date.

Where it comes from

CauseLooks likeReal fix
Missing constraintAn unbuildable combination was allowedAdd the rule and a test
Stale orderabilityA retired part is still selectableLifecycle state and effectivity
Pricing gapAn option with no pricePublish rules and prices together
Master dataWrong unit, code or descriptionData governance
TimingA change landed mid-orderBetter cut-in dates

The habit that matters

Fixing the order is the easy half. The useful half is asking what let it through and fixing that, then saving the failed configuration as a test so it can't return. I was the single-point owner of order fallout for North American B2B dealers and OEMs at MillerKnoll, and working this way is part of how we reduced quoting errors by 30%. The longer version is in Order fallout is a product problem.

Questions people ask

Is some fallout normal?

Yes. Truly special requests will always need a person. The goal is that what falls out is genuinely special, not a repeat of last week's error.

How should it be measured?

As a rate (orders needing intervention over all configured orders), by cause, and by repeat cause. Repeat fallout is the most telling number.

Updated November 2026. Think I've got something wrong? Tell me.