Manufacturing quote approval workflow

Industrial quotes rarely need one generic approval. A bid can meet the headline margin target while relying on an expired supplier price, an unconfirmed production slot, a longer warranty and customer payment after site acceptance. Each issue has a different owner and a different effect on the offer.

The workflow must finish with one releasable quote. Every approval must refer to the same scope, cost, price, schedule and terms. When one of those facts changes, the system should reopen the decisions that depend on it and leave unrelated approvals alone.

Define what approval releases

Name the exact business record that changes state after approval. It might be a customer estimate, CPQ quote, bid package or ERP sales quotation. The released record should contain the approved scope, configuration, cost, price, delivery, payment, warranty, deviations and validity. A signed email or meeting note cannot replace that controlled revision.

Set the release boundary before you write rules. A sales manager may approve a discount, but that decision does not approve an unsupported delivery date. Finance may accept payment timing, but it does not approve a technical deviation. The final release confirms that every required owner has acted on the same quote.

Native systems model this boundary in different ways. NetSuite’s estimate approval example moves an estimate through pending, approved or rejected states. Microsoft Business Central locks a record in pending approval and releases it after the required approvals. Those states are useful only when the released record includes all the commitments the business intends to send.

Check that the quote is ready for approval

Approval time should not pay for missing estimate work. Create an entry gate that checks the customer package, current configuration, complete cost basis, supplier validity, capacity plan, price, margin, requested terms, deviations and proposal deadline. Assign each missing fact to its owner before the request enters an approver’s queue.

A readiness check differs from an approval. The estimator confirms that the cost model is complete and explains uncertainty. The approver decides whether the commercial result is acceptable. A sales executive cannot make a missing supplier quote current by approving the deal.

Allow a documented assumption when the business has a rule for it. State the amount, evidence, owner, expiry and action that replaces it. “Costing complete” hides exposure. “Drive supplier price expires before expected award; $24,000 escalation allowance approved through 31 December” gives finance a decision it can evaluate.

Trigger approval from the decision at risk

Write a trigger for each authority the company wants to control. Common triggers include margin below a product-family floor, discount above authority, price above a deal threshold, low cost confidence, delivery outside the current plan, supplier price expiry, extended payment, non-standard warranty, uncapped liability, liquidated damages and technical deviations.

Use the field that represents the real decision. A total-value threshold may route a large standard repeat to an executive while a smaller first-of-kind package with uncertain cost passes untouched. Combine amount with margin, risk and exception conditions when the policy requires it.

Salesforce CPQ approval rules evaluate defined conditions when a quote enters approval. SAP quote approval configuration lists conditions such as profit margin, discount, quote type, value, project status and credit. The software can evaluate many fields; the company still has to define the authority and evidence behind each one.

Separate price authority from cost confidence

Price approval answers whether the business will offer the deal at the proposed economics. Cost review answers whether the estimate supports those economics. Put them in separate decisions. A manager with authority to approve a discount cannot make an uncertain scope, supplier price or routing accurate.

Show current and downside margin when the quote carries exposure. Display the current estimate, approved allowances and the downside case that would use them. State whether the company measures gross margin, contribution margin or another defined metric. Do not let teams approve different percentages with the same label.

When cost confidence falls below policy, route the underlying line to the owner. Purchasing can refresh the supplier quote. Engineering can close scope. Operations can confirm routing and hours. Finance can then approve price from a supported cost instead of adding a broad reserve after the fact.

Assign one owner to each exception

Build an authority matrix around decisions, not departments. Name the role that can accept the risk, the substitute when that person is unavailable and the higher authority for a threshold breach. Avoid shared queues with no accountable approver.

Use joint approval only when two owners make distinct decisions. Operations can approve the production plan while finance approves the cost of overtime. Legal can approve clause language while the business sponsor accepts the economic exposure. Record both decisions without asking each person to approve the whole document.

Microsoft Business Central supports approver amount limits, substitutes, delegation and overdue handling. Those mechanics solve absence and hierarchy. They do not define who owns warranty, delivery or technical risk. Write that operating model before configuring the workflow.

Give the approver a decision brief

The request should explain what changed, why approval is required and what answer the bid team recommends. Link the relevant source and show the effect on cost, margin, cash, schedule, warranty, liability or customer commitment. The approver should not have to reconstruct the quote from CRM notes, spreadsheets and email.

Show enough context to understand the decision. A payment exception needs the contract value, billing milestones, expected cash dates, customer credit and proposed counter. A delivery exception needs the required date, supported date, capacity conflict and recovery cost. A technical exception needs the requirement, proposed deviation and customer effect.

Limit the brief to the decision. Attach the complete quote for reference, but do not make every approver read every page. A focused brief improves both speed and accountability because the recorded approval states what the person actually accepted.

Run independent decisions in parallel

Draw the dependencies between decisions. Engineering acceptance may set cost. Cost sets margin. The delivery decision may depend on supplier and capacity dates. Payment and warranty can often run at the same time. Sequence the dependencies and start independent reviews together.

Do not build a chain that sends the same quote from sales manager to finance to operations to legal when their decisions do not depend on one another. That design makes total cycle time equal to every wait added together. Parallel review leaves only the longest independent decision on the critical path.

Create a final release check after all branches close. It confirms that the accepted warranty, delivery, payment and price coexist in the current quote revision. An early finance approval may need review if a later legal decision changes cost or liability.

Use conditional approval for a precise open item

A conditional approval should state the unresolved fact, the permitted boundary, the owner, the due date and the action if the condition fails. It lets the bid continue without pretending the issue is closed. Use it when the remaining uncertainty has a controlled range and the proposal can express that range.

“Approved pending supplier confirmation” is too broad. “Approve price through 31 December if supplier S-14 extends quote Q-882 at or below $410,000 by Friday; otherwise reopen cost and price approval” gives the team a testable condition. When the fallback uses an indexed adjustment, the BLS guide to PPI price-adjustment clauses says to name the base price, index, source, adjustment frequency and calculation mechanics. Put those facts in the condition and the proposal.

Do not use conditions for a hard technical or legal stop. The company cannot release a proposal that promises an unapproved safety deviation or accepts uncapped liability while legal review remains open. Mark those decisions as blocking and make the reason visible.

Reopen only the approvals a revision invalidates

Tie every decision to a quote revision and the inputs it used. When sales changes price, reopen margin authority. When engineering changes configuration, reopen cost, delivery and any technical approval affected by the change. A spelling correction should not restart the workflow.

SAP Sales Cloud documentation describes configurable reset and resubmission behavior after quote changes. The practical design question is which field changes invalidate which decisions. Build that dependency map explicitly instead of resetting everything or preserving approvals that no longer match the quote.

Show the approver a difference view. List the old value, new value, reason and downstream effect. Preserve the earlier decision and record why the workflow reopened it. The new approval should replace the applicable revision, not erase the history. ISO 10013 guidance recognizes electronic documented information and the processes used to create and control it. The approval history belongs to that controlled record.

Set deadlines, substitutes and escalation before a bid arrives

Calculate the approval deadline from the customer submission time. Reserve time for proposal assembly, final checks and authorized submission. Each task needs a due time that protects its dependents, not a generic two-day service level that ends after the customer deadline.

Name a substitute for planned absence and an escalation path for overdue work. Delegation should transfer the authority and show who acted on whose behalf. Do not let a requester reroute a difficult decision to an easier approver.

Use reminders sparingly. One notice with the decision, impact and deadline helps. Repeated alerts with no added context train approvers to ignore the queue. Escalate based on the remaining critical-path time and business impact.

Choose the system around the evidence

Use ERP-native approval when the decision lives on a controlled transaction and the required facts already sit there. NetSuite, SAP and Business Central can route records through approval states, thresholds and approver hierarchies. That works well for straightforward amount, margin or document release rules.

Use CPQ approval when configuration, discount and quote pricing drive the decision. It can evaluate quote conditions and protect approved price output. Check how it handles engineering evidence, supplier validity, capacity, warranty and contract deviations that live outside CPQ.

Use Bourne when the approval depends on evidence across CRM, CPQ, ERP, PLM, supplier responses, cost models and customer documents. Bourne prepares the role-specific decision brief, applies the authority map, tracks parallel decisions and writes the approved price and status back to the system that owns the quote.

Worked example: a compressor package with a healthy headline margin

An OEM prepares a $2.84 million proposal for an engineered compressor package. The current estimate is $2.18 million, which shows a 23.2 percent margin. The product-family target is 25 percent and the floor is 20 percent. Sales asks for approval because the account is strategic and expects follow-on units.

The ready check finds four exposures. The main compressor supplier’s $410,000 quote expires 33 days before the expected customer award. The requested 34-week delivery needs $68,000 of unapproved overtime and subcontract work. The customer asks for a 36-month warranty that adds a $42,000 service reserve. Payment at net 90 after site acceptance adds an estimated $31,000 financing effect. With a $24,000 supplier escalation allowance, the exposure case reaches $2.345 million and 17.4 percent margin.

The workflow sends delivery to operations, supplier validity to purchasing, warranty to service and legal, and payment to finance at the same time. Operations supports 36 weeks without the $68,000 recovery plan. Purchasing secures price validity through the decision date. Service approves 24 months in the base and prices 36 months as an option. Finance requires 20 percent at order, 70 percent at shipment and 10 percent after site acceptance, all due within 30 days.

Sales revises the base price to $2.98 million. The approved cost becomes $2.24 million after current supplier pricing, the supported schedule and the accepted service position. Margin is 24.8 percent. The final proposal states 36 weeks, the payment milestones, 24-month warranty, the priced warranty option and 30-day offer validity. The release record shows who accepted each condition.

Run one final release check

The release check compares the current quote with every approved decision. It confirms price, margin, delivery, validity, payment, warranty, freight, currency, technical deviations and proposal options. It also confirms that blocking conditions closed and that non-blocking conditions appear in the customer-facing documents. When the proposal uses an Incoterms rule, verify the named place and the allocation of transport, risk, insurance and customs against the ICC Incoterms 2020 rules.

Check the proposal, price schedule, technical offer and terms together. A correct value in CPQ does not protect the business if the attached proposal still shows the earlier date or warranty. Generate or update documents from the approved record where possible, then compare the rendered files before submission.

Only an authorized role should release or send the quote. Record the sent version, attachments, recipient, time and channel. If the team changes the package after release, create a new revision and run the dependency rules again.

Carry approvals into order review and execution

The customer purchase order should be checked against the accepted quote and its approved exceptions. Payment, warranty, delivery, options and technical deviations must survive that comparison. If the PO changes one of them, route the difference to the same owner who approved the bid position.

Pass the approved conditions to engineering, procurement, operations, service and project management. A 24-month warranty needs the service plan. A supplier validity condition needs a purchase release date. A delivery assumption needs the capacity slot. An approval that ends at proposal submission leaves execution to rediscover the commitment.

Use the approval record during change control. When the customer asks for an earlier date or added scope, the team can see the basis behind price and authority. The new decision can update the same chain instead of starting from an email with no context.

Measure the workflow by decision quality and speed

Track time from a ready request to final release. Separate queue time from review time and rework. Measure by decision type and approver role so the company can fix the real delay. A single average hides a legal review that takes four days and a margin approval that takes twenty minutes.

Track reopened approvals and the reason. Missing evidence points to a weak ready gate. Quote revisions after approval may point to poor dependency rules or late customer changes. Margin leakage, missed delivery and unplanned warranty cost show whether the approved basis survived execution.

Review overrides as a portfolio. Frequent below-target approvals may reflect an unrealistic target, overstated standard cost, strategic pricing or weak discipline. Require a reason code and compare the forecast outcome with the order result before changing policy.

How Bourne runs quote approval

Bourne reads the current quote, cost model, supplier responses, capacity plan, customer terms and technical exceptions. It applies the company’s authority rules and creates one decision brief for each owner. Finance sees economics and payment. Operations sees the delivery plan. Engineering sees technical deviations. Legal and service see the clauses and exposure they own.

Independent decisions run together. Dependencies wait for the input they need. Every approval records the quote revision, evidence, decision, conditions and authority. When a cost, date or term changes, Bourne reopens the affected branches and preserves the rest.

After the final check, Bourne writes the approved price and status back to the quote system and passes the accepted commitments into proposal generation and customer PO review. The company releases one supported offer and can trace each promise to the person and evidence behind it.

Buğra Gündüz

Buğra Gündüz is the co-founder and CEO of Bourne and co-founder of HockeyStack. He built HockeyStack into an eight-figure AI business. At Bourne, he works with entrepreneurs and established companies to create AI products and services.