Rush Order Acceptance
Decide whether to accept a rush order, accept it with overtime or expedited freight, or decline it, based on schedule slack, risk-adjusted cost, and net margin.
This order fits entirely inside current schedule slack, with no displacement to already-committed orders. Freight strategy: expedite.
Continue Analysis
Based on your results, these related decisions are available.
Resources
How this works
Comparing a rush order's price against its cost is not enough, because it ignores whether the order fits inside your current schedule or requires displacing already-committed work. This engine runs a two-stage check: first, whether the order fits inside existing schedule slack; second, a risk-adjusted profitability test that scales the cost of any displacement by how risky it is judged to be to your other customers. If the order exceeds slack and that risk is high, the order is declined regardless of margin, because protecting existing commitments is treated as a hard limit, not something a large enough number can outweigh.
Assumptions
- Schedule slack and hours required are already known or estimated by the user
- The displacement penalty and risk level are the user's own estimate of the cost and likelihood of disrupting other committed orders
- Risk multipliers (1.0 / 1.15 / 1.35 for low, medium, high) are a practitioner heuristic for scaling an estimated penalty by qualitative risk, not a statistically derived figure
Limitations
- Evaluates one rush order at a time, not a queue of competing rush requests
- Does not itself calculate available schedule slack; that comes from your current schedule or a direct estimate
- The risk multiplier is a heuristic scaling factor, not a probability-weighted expected value calculation
Sources
The capacity-fit-then-profitability structure follows available-to-promise and order-acceptance treatment in Vollmann, Berry, Whybark, and Jacobs, Manufacturing Planning and Control for Supply Chain Management (6th edition), and Slack, Brandon-Jones, and Johnston, Operations Management (8th edition), cross-checked against the APICS/ASCM Dictionary for standard terminology.
Worked example
A rush order is worth $30,000 in revenue against $12,000 in production cost. It needs 100 hours of production time, but only 60 hours of schedule slack currently exist, so 40 hours would displace already-committed work. Expediting adds $3,000 in overtime and $2,000 in rush freight, and the estimated cost of displacing other orders is $4,000. At medium risk, that penalty scales to $4,600, leaving a net margin of $8,400, so the order is accepted with overtime. At high risk instead, the same $4,000 penalty scales to $5,400, still leaving a positive $7,600 net margin, but the order is declined anyway, because a high-risk displacement of committed customer work is not a decision a positive margin alone should make.
Common use cases
- Deciding whether to accept a rush or expedite request from a customer
- Weighing overtime and rush freight cost against the order's actual profit
- Protecting already-committed customer orders from being silently bumped by a more urgent request
- Building a consistent, explainable accept or decline answer instead of an ad hoc gut call