Outcomes & ROI

How Real Capacity Data Lets You Turn Down the Wrong Order

User Solutions TeamUser Solutions Team
|
8 min read

Accepting every order is how a healthy backlog turns late, because the cost of an order is not its own margin, it is what it does to the work you already committed to. EDGEBIC by User Solutions makes that cost visible before you commit: run the prospective job through the same finite capacity model your live jobs use, reschedule with it included, and read which existing orders it pushes. Some orders are worth what they displace. The point is that you now know which.

This post covers the order-acceptance outcome. It sits under the EDGEBIC results guide. For the simulation itself, see EDGEBIC quote simulation explained.

The Order That Looked Fine

A 400-piece order arrives at a decent price. Sales looks at the margin, sees a number they like, and accepts. The shop was already loaded, but the shop is always loaded, and it has always worked out.

What happens next is invisible until it is not. The new job lands on the constraint, which was running at 92 percent. The jobs behind it move. Two of them move past their due dates. One belongs to a customer with a chargeback clause. Another needs air freight to arrive on time. A third is fine on paper but pushes a fourth job that was already tight.

By the time anyone connects those four outcomes to the original acceptance decision, the decision is three weeks old and nobody is looking backward. The order gets recorded as profitable, and the lateness gets recorded as a shop problem.

Counting What an Order Actually Costs

An order has two prices. The first is the one on the quote. The second is the delivery risk it transfers to committed work, and it is usually the larger of the two.

New orderConsequences
Revenueas quotednone
Marginas quotednone
Constraint hours consumedrealpushes everything behind it
Committed jobs pushed latezero3 to 4
Chargebacks, premium freight, expeditingzeroreal and recurring

The second column is the one nobody prices, and it is not hard to price once the model shows you which jobs it hits. See the true cost of a single late job for the per-job arithmetic.

The Method: Baseline, Add, Reread

The decision is a controlled comparison and takes about twenty minutes.

Capture the baseline. Three numbers before anything changes: how many jobs are late today, what the constraint station's utilization rating is, and the completion dates of your most at-risk orders.

Add the prospective order and reschedule the same set of jobs. Not a projection, a replan.

Reread the same three numbers. A representative result:

BaselineWith the new order
Late jobs15
Constraint utilizationHIGH, 92%CRITICAL, 111%
At-risk orders1 tight4 slipping 3 to 9 days

Now the meeting is about whether the new order's margin exceeds the cost of four late deliveries. That is a business decision with a defensible answer. Without the model, the same meeting is a disagreement about whether the shop is full, which nobody can win because nobody has the number.

The utilization figure is worth quoting carefully. Two reports here can disagree, because one approximates available hours with a coarse formula and the Work Center Utilization report computes them from real shift calendars and per-day overrides. In an acceptance decision, use the second.

Three Answers That Are Not "No"

Declining outright is the least common outcome, and modeling usually surfaces a better one first.

Reprice it. If the order is only viable at overtime, the overtime is a cost of that order. Quote it accordingly rather than absorbing it into the base price and letting the rest of the book pay.

Requote the date. The simulation returns a date the plant can actually hit. Offering that instead of the customer's requested date converts a probable late delivery into an honest one, and a surprising share of customers accept it. See how credible promise dates win bigger orders.

Model the capacity you would add. A second shift on the constraint, an alternate work center configured but unused, or a weekend under a capacity override. Model each and reschedule. If one of them clears the lateness at a premium smaller than the order's margin, the answer is yes with a plan attached rather than yes with a hope attached. See how what-if simulation wins profitable rush orders.

Only when none of those works is the answer no, and by then you can explain it in a sentence: this order costs four committed deliveries and there is no capacity option that changes that.

Why "Quote It Long and Hope" Fails

The common alternative to declining is padding: quote a date far enough out that it feels safe. It fails twice.

It fails competitively, because a padded date is often longer than necessary and loses work you could have taken. And it fails operationally, because a date on an acknowledgment does not reserve capacity. When the order lands it consumes the constraint on whatever day it lands, and the jobs behind it move regardless of what the paperwork says.

A simulated date is different in kind. It is computed against the same calendars, the same shifts, and the same routings as the live plan, so it is a statement about the plant rather than a guess about it. See finite versus infinite capacity scheduling for why that distinction is the whole game.

The Limits Worth Saying Out Loud

A model is only as good as its inputs. Routing hours that are 30 percent low make every acceptance decision optimistic. Check the plan versus actual variance on the constraint before you trust an acceptance model. See how variance data fixes the routing that was always wrong.

It does not know about orders you have not entered. If three more quotes are about to land, the picture changes. The model reschedules what it can see, so it is a snapshot of a moving book.

It does not price the relationship. Some orders are worth taking at a loss because of what follows them, and some customers are worth protecting even when the arithmetic says otherwise. The model tells you what you are paying. Whether that price is worth it is commercial judgment.

Margin figures need rates loaded. The estimated margin and profit on a quote depend on cost data being present. Without work center rates, the model gives you dates and capacity, not dollars, and the dollar side has to come from your own costing.

The decision has to be made before acceptance. Nothing here helps after the order is in the book. The value is entirely in the twenty minutes between the request and the answer, which is also the twenty minutes sales is under the most pressure to skip. See job shop scheduling challenges for why that pressure is structural.

Want to test an order against your own backlog before you answer it? Bring a live quote to a demo and we will schedule it in and show you what moves.

You decide by pricing the order against what it does to the jobs you already have, not against its own margin alone. In EDGEBIC by User Solutions a quote simulation runs the prospective job through the same finite capacity model as live work, so you can see the date it can genuinely hit and, by rescheduling with it included, which existing orders it pushes. An order that adds 4 percent margin and makes three committed jobs late is usually a loss once the consequences are counted.

It costs the capacity it consumes on your constraint and the delivery risk it transfers to committed work. If accepting it pushes three existing jobs past their due dates, the true cost includes whatever those three late deliveries cost you: chargebacks, premium freight, expediting hours, and the customer relationships involved. Those costs are usually larger than the marginal profit on the new order and they land on customers who did nothing wrong.

Sometimes, and the comparison should be made rather than assumed. Model both. Run the order with the current calendar and read which jobs go late, then model the overtime option as added shift capacity and reschedule the same set. If overtime clears the lateness at a premium smaller than the order's margin, take it. If it does not clear the lateness even with the premium, you are buying a late delivery at a higher cost, which is the version worth declining or repricing.

Expert Q&A: Deep Dive

Q: Sales wants to accept a big order that fills our worst-loaded month. How do I show what it does before we commit?

A: Model it. Capture the baseline first: late job count today, the constraint station's utilization rating, and the completion dates of your most at-risk orders. Then add the prospective order and reschedule the same set of jobs. Read the same three numbers. A typical result is that the constraint moves from HIGH to CRITICAL and four committed orders slip past their due dates by three to nine days. Now the conversation is about whether the new order's margin exceeds the cost of four late deliveries, which is a decision the business can actually make. Without the model, the conversation is a disagreement about whether the shop is full.

Q: We never say no, we just quote a long date and hope. What is wrong with that?

A: Two things. First, a long date quoted without a capacity check is still a guess, so it can be both uncompetitive and wrong at the same time, which is the worst combination available. Second, hope is not a scheduling policy: when the order lands, it consumes the constraint regardless of the date on the acknowledgment, and the jobs behind it move. Quote the date the model returns, and if that date loses the order, you learned something real about your capacity rather than discovering it three weeks into the job. A simulated date you can defend beats a padded date you cannot.

Frequently Asked Questions

Ready to Transform Your Production Scheduling?

User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team

User Solutions Team

Manufacturing Software Experts

User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.

Let's Solve Your Challenges Together