10 Manufacturing Quoting Mistakes That Cost You the Margin

Manufacturing quoting mistakes are expensive precisely because they look fine on screen. The quote simulates, the grid paints the margin green, the customer accepts, and the loss shows up two months later on a job that ran late and cost more than it earned. These ten come up repeatedly in the quoting module of EDGEBIC by User Solutions, each with the symptom you would actually notice first.

For the module itself, start with quote simulation explained. For the hands-on version, see how to create a quote, and for the mechanism, how a quote becomes a promise date.

1. Quoting From the Routing Estimate and Skipping the Simulation

Symptom. Quoted lead times are consistently optimistic. The estimate looked right and the shop still could not hit it.

Cause. The quote dialog fills a cost analysis panel from routing math before any simulation runs. It is a useful sanity check and it knows nothing about your current load. The estimate says the job contains 151 hours of work; it does not say your mill already has 320 hours booked that week.

Fix. Simulate before you send, every time. The simulation is the only number that includes shop load, real shift hours, holidays, and setup times. It is the difference between finite and infinite capacity thinking applied to a quote.

2. Leaving a Work Center Rate at Zero

Symptom. Estimated cost is far too low. Margin comes back at a number nobody in the shop believes, and nobody investigates because good news rarely gets audited.

Cause. Labor cost is allocated hours times a rate. The rate resolves as the per-step routing rate first, then the work center's own rate. When both are zero, that step costs nothing and no error is raised.

Fix. Put a rate on every production work center, and treat a zero rate as a data error rather than a default. This is the most common cause of a margin that is too good to be true. Work centers in EDGEBIC covers where the rate lives.

3. Relying on the Material Cost Fallback

Symptom. Material cost on a multi-component assembly is suspiciously round, or matches the end item's unit cost exactly.

Cause. Material cost comes from work centers of material type in the simulated result. When the routing has none, the quote falls back to the product's unit cost multiplied by the quantity. For an assembly with a real bill of components, that fallback prices only the end product's own unit cost and nothing else.

Fix. Model material as material. Add material-type steps to the routing for products with multi-component bills, and let the fallback be a safety net rather than your costing strategy. The graphical routing designer is where those steps get added.

4. Comparing the End Date to the Target Date on a Forward Quote

Symptom. A quote that looked comfortably inside the customer's window ships late.

Cause. Direction confusion. On a forward quote, the target date is where the simulation starts. Comparing a returned end date against a start date answers nothing, but it reads like a feasibility check because both fields are dates.

Fix. Learn the rule and apply it mechanically. On a backward quote, compare the end date to the target date, because the target is the finish-by date. On a forward quote, compare the end date to the customer's wanted date, which lives outside the quote record. Better still, set direction to Backward when the customer has named a date, and let the engine answer directly. Backward scheduling in EDGEBIC covers the rules.

5. Expecting the Unit Price to Follow the Cost

Symptom. Costs change, you re-simulate, and the unit price sits exactly where it was.

Cause. Automatic markup pricing fires only when the unit price is zero. Once a human types a price, later simulations leave it alone. That is a protection, not a bug: a commercial decision should not be silently overwritten by arithmetic.

Fix. When you want the price to follow, say so. Use the apply markup action explicitly, or zero the price and simulate again. Build the habit into your re-quote process so nobody sends an old price with a new cost.

6. Sending a Stale Simulation

Symptom. A quote sent last month is accepted, and the promised date is already impossible on the day the order lands.

Cause. Simulated dates and costs are a point-in-time snapshot. Every order accepted since the simulation consumed capacity the simulation assumed was free, and rate changes move the cost basis.

Fix. Watch for the banner. The quote view flags when work-center rates or capacity have changed since simulation and tells you to refresh and re-simulate. Keep expiry dates honest: the 30 day default exists for exactly this reason, and reviving a 90 day old quote without re-simulating is quoting from fiction.

7. Bumping the Unit Price Instead of Overriding the Cost

Symptom. Six months later, nobody can explain why one job carried 12% more price than the identical job before it, and quote-versus-actual variance reporting on that customer is meaningless.

Cause. Somebody added tooling wear, scrap allowance, or freight by nudging the unit price up. The reason lived in their head and left with them.

Fix. Use the manual cost override. It replaces the rolled-up cost as the pricing basis, so profit, margin, and markup-derived price all follow, while the calculated labor and material split stays stored for later comparison against actuals. In the documented rush-order case a $17,400 simulated cost was overridden to $19,400 and priced at 30% markup, and the original breakdown survived intact.

8. Treating a Quote as Reserved Capacity

Symptom. Two quotes promised the same week. Both customers accept. One of them is now late.

Cause. A quote does not hold anything. A simulation reads the capacity picture and discards its result, so both simulations legitimately saw the same free hours. EDGEBIC provides quote simulation and what-if promise dates; it has no capacity reservation mechanism.

Fix. Manage it with process rather than expecting software to do it. Re-simulate immediately before committing to a large promise, convert promptly once the customer says yes so the order takes its place in the queue, and treat a quoted date on an unaccepted quote as an estimate rather than a slot.

9. Quoting a Product Whose Sub-Assemblies Have No Routings

Symptom. Estimated hours on an assembly come back far lower than the shop knows the job takes, sometimes close to nothing.

Cause. When a routing references a sub-assembly product that has its own routing, that sub-assembly's hours, labor, and material roll into the parent recursively, respecting each step's quantity multiplier. A referenced product with no routing contributes material only, because there is no work content to roll up.

Fix. Give every make-in-house sub-assembly its own routing. The documented rollup resolves a product built from a bracket assembly built in turn from a base plate at 22.5 hours per unit, or 225 hours at a quantity of 10, and none of that appears if the intermediate products are modelled as bought parts. If a sub-assembly genuinely is bought in, material-only is correct and the low hours are honest.

10. Never Reading the Quoted Versus Actual Column

Symptom. The same product is under-quoted for years, and each individual miss looks like bad luck.

Cause. Nobody looks at the feedback. Once actuals arrive from the shop floor, the quote shows quoted hours next to actual hours for the linked order. An empty right side means no actuals yet rather than zero.

Fix. Review that column monthly across completed jobs, and read the two divergence patterns differently. Hours diverging while dates hold means the routing is wrong, and every future quote for that product inherits the error until the routing is fixed. Hours holding while dates slip means capacity was consumed after the simulation ran, which is a process problem rather than a data one. See quoted versus actual lead time for the wider habit.

Two More Worth Knowing

Simulation fails with a routing message. The quoted product has no routing. Build it first; a product with no work content cannot produce a defensible date.

Conversion is refused. Either the quote is already converted, or an order referencing it already exists. Conversion is one way and guarded three times over. For repeat business, create a new quote, which also earns the repeat its own current-capacity simulation.

The Pre-Send Checklist

Eight checks, under a minute. For the full workflow, read the quoting pillar, and for the scenarios you reach for when the base date misses, what-if scenarios explained. The EDGEBIC complete guide maps the rest of the platform.