Skip to main content
GullySystem
Manufacturing

Estimate/Quotation Management for PCB manufacturers

Keep itemised estimates and their approved revisions together.

Finance & Accounting

Does this function belong in your operation?

Use when scope and prices are agreed before an order.

A buyer asks for pricing before confirming work.

A quote prices the board by layer count, copper weight, size, surface finish and quantity. Controlled impedance and gold finish add their own lines. Tooling is charged once per design.

Bring the records the workflow depends on.

  • Items and units
  • Rates and tax settings
  • Approval terms

Outputs to check

  • Versioned estimate document
  • Approval and acceptance history
  • Accepted billing or order input

Follow the estimate/quotation management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Record the requirement

    Capture scope, quantities and the customer's requested terms.

  2. 2. Prepare the estimate

    Use approved units, rates and tax settings.

  3. 3. Review exceptions

    Approve discounts, exclusions and nonstandard terms.

  4. 4. Issue and revise

    Retain the version sent and each subsequent change.

  5. 5. Record acceptance

    Link the agreed version to order creation or final billing.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Sales executive

Sees quotes waiting to be sent, quotes waiting on the client, and today’s follow-up list.

Estimator

Builds the costing behind the quote from measurements, material and labour, and keeps it beside the drawing.

Owner

Sees what went out this week, at what margin, and which discounts were given without being asked for.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Customer changes quantity

Save a revision and recalculate affected lines before acceptance.

Expired validity

Require the price and terms to be reviewed before using the estimate.

Discount beyond authority

Hold the revision for approval and retain the original proposed amount.

Can this work independently?

An estimate can be prepared independently from entered items and rates. Item catalogues, pricing and tax settings improve consistency when connected. Order creation and invoicing are downstream processes; acceptance should preserve the agreed version rather than overwrite the estimate with later rates.

Systems and records it connects with

  • Lead management: Enquiry sources, owners and qualification decisions.
  • Proforma invoice: Provisional supply amounts and related advance requests.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Price lists and schemes: Effective-dated rates and customer eligibility rules.

Configure, test and introduce the workflow.

  • We read quotations you sent recently. You pass over the rate list and a few finished quotes, and we sketch the screen layout.
  • Items, units, discount limits and standard terms go in. Proofreading the list is yours. The printed quotation is matched to your letterhead. A draft PDF is sent for your comments.
  • Executives raise real quotes in parallel with the old method. Mismatches are logged and discussed. New enquiries start in the system. Estimators and executives get a short session each.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Earlier revisions remain available.
  • Totals use approved settings.
  • The accepted version is identifiable.
PCB manufacturers

How the business operates.

A bare board order starts as a set of files and ends as a stack of boards in a vacuum bag. In between, a panel passes a dozen wet and dry steps, and every step has its own scrap. One late revision can sink a lot.

Order and file revision register

Hold the buyer’s Gerber set, fabrication note and revision, so CAM and the floor never image from an outdated pack.

Engineering query tracker

Log each CAM question, send it to the buyer, record the answer and release the lot only when all queries are closed.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Enquiries and quotations. Price boards from layer count, size, panel utilisation, finish and quantity bands, with every revision of a quotation kept.
  • File revision register. Attach the Gerber set, drill file and fabrication note to the order with a revision letter, and show the floor only the released set.
  • Engineering queries. Raise a CAM question, send it to the buyer, record the answer and block the lot until the query is closed.
  • Stack-up and panel plans. Hold the laminate, prepreg and copper weight of each build, with boards per panel and panel size.

Operational bottlenecks to check

The wrong Gerber revision gets imaged

The buyer resends files after CAM has started, and the film is made from the old set while the new revision waits in an inbox that the floor never opens. The error shows only on the electrical test.

Engineering queries wait in email

A clearance question to the buyer sits unanswered while the lot waits for tooling. The planner cannot tell which orders are blocked on a reply.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry and quotation

    A buyer sends files and a fabrication note. The estimator checks layer count, size, finish and quantity, and prices from panel utilisation.

  2. 2. CAM review

    CAM checks clearances and drill data, raises engineering queries and lays out the panel. The order is released only after the buyer’s answers.

  3. 3. Lot creation

    A lot opens with the file revision, stack-up and a traveller by process step. Laminate and prepreg are issued against it.

  4. 4. Process steps

    Imaging, etch, lamination, drilling, plating, mask, legend, finish and routing are each logged with quantity in, quantity out and scrap reason.

  5. 5. Test and inspection

    Open and short test results are saved by board. Final inspection checks dimensions, finish and visual defects.

  6. 6. Packing and shipment

    Boards are counted, bagged and labelled with the date code. The certificate of conformance, test report and packing list are issued.

Industry reports to connect with

  • Yield by process step, by week and by board type
  • Orders waiting on engineering queries
  • Scrap reasons for drilling, plating and etching
  • Lots affected by a given bath change or press load

Questions before implementation.

When should pcb manufacturers consider estimate/quotation management?

Use when scope and prices are agreed before an order. A buyer asks for pricing before confirming work.

What should we bring to the requirements discussion?

Bring anonymised examples of Items and units; Rates and tax settings; Approval terms. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Keep itemised estimates and their approved revisions together. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

An estimate is not a tax invoice or proof of acceptance.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Earlier revisions remain available. Use this check when reviewing the first working version.

Talk to us

Discuss estimate/quotation management for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements